Page Comparison

...

1. Add some NN module.

   • genderage: gender and age

     • Det_10g + genderage

     • LightFace + genderage

2. Based on the current main framework of SNNF, provide a porting tool so that users can easily add a new model to the Customized zone using the official generated nbg code as the source. The initial version of this tool is currently available, and there will be further updates in the next version.

3. Fix some known issues, such as:

   • OCR have a probability of crashing.

   • HumanAttr have a probability of crashing.

   • When multiple models are connected in series, if the last model comes out, the result may have an unfinished flag fin=false.

4. Standardize post-process code.

5. Organize samples and unittest codes:

   • samples is a sample code for snnf command sample which is just for snnf_run.sh.

   • unittest/modelTest is just for a buildin model's test sample.

   • unittest/pluginTest is just for the plugin model's test sample.

   • unittest/sequntialTest is the sample for the pipeline in which several models are sequentially linked together in series.

6. Add NN filter, which can facilitate users to do their own private data processing at the application layer. Users only need to insert the filter directly into the corresponding position of the pipeline when creating the model flow, and then perform private and correct processing at the most appropriate location. The advantage of this is that there is no need to write a dedicated module within SNNF for this private processing, only the official interface of SNNF needs to be called. Of course, SNNF provides some commonly used private processing filters internally, such as label filtering. For example, when Object Detect+HumanAttr, the label results of Object Detect can be filtered, and only the person can be passed to HumanAttr. If the requirements of the application layer happen to match this usage, there is no need to implement it yourself at the application layer. Simply call the methods provided by SNNF.

7. Provide users with a mAP test sample to compare the precision of the C3V platform's model running results with the precision of the model's official PC running results. The default test model is yolov8s object detection. Users can refer to this mAP sample to rewrite the model they need to test mAP values for. Please refer the SOP.

8. Improve the toString() function for each model's result, and support the detection result toString JSON format.

9. Update some make config.

   • In addition to cross compilation on the server, we also provide compilation methods on the C3V platform.

     • If it is cross compilation on the server, please confirm the config CROSS_COMPILE := ON in makefile_config.mk .

     • If compilation is required on the C3V platform, please confirm the config CROSS_COMPILE := OFF in makefile_config.mk .

   • Users can choose the model plugin in makefile_config.mk that needs to be compiled according to their own needs, which can effectively reduce the code size of specific projects and shorten compilation time.

...