Modules

Here is a list of all modules of SaigeVision.
Classification
Detection
Segmentation
OCR

Common workflow

This section show a basic workflow common to all modules.

1. Construct handles of model file and inspection results through Handle construction.
   
   • Creating model file's handle is the first step to conduct a inspection.
   • Once model file's handle is created, all information about model file is loaded on buffer and then used for following steps.
   • Inspection results's handle is passed to Inspection functions and used to store inspection results. User can get inspection results from the handle through Inspection results.
   • Handle construction
2. (Optional) Check Class information.
   • User can get Class information which is set in training session.
   • This step is optional.
   • Class information
3. (Optional) Check Inspection options and set new values if required.
   • User can get or set Inspection options.
   • When user set new options, the values on buffer is changed and effect following inspections.
   • If you user want to overrite new options on model file, boolean input (writeOnModelFile) can be passed to set function of Inspection options. (ex, SR_SetClsTestAdditionalScore).
   • This step is optional.
   • Inspection options
4. Allocate memory on cpu and gpu through Memory-allocation functions.
   • Allocate memory on cpu and gpu required to conduct inspections.
   • Possible to return memory-related errors, eErrorType::OUT_OF_GPU_MEMORY, eErrorType::INAPPROPRIATE_GPU_NUMBER etc.
   • Memory-allocation functions
5. Inspect images through Inspection functions.
   • Apply SaigeVision's deep-learning based machine vision algorithm to inspect images.
   • Only 8-bit images are currently supported (1,3,4 channles).
   • Pass a inspection results' handle to store inspection results in handle.
   • Batch inspection mode is supported for Classification and Segmentation modules.
   • Inspection functions.
6. Retrieve inspection results through Inspection results.
   • Retrieve results from a results' handle by calling appropriate functions.
   • Inspection results
7. Destruct handles of model file and inspection results through Handle destruction.
   • Constructed handles must be manually destructed by calling Handle destruction to prevent a memory leak.
   • Handle destruction