Release Notes 5.10
This section lists the new functionality, improvements and some of the major changes related to DEEPCRAFT™ Model Converter.
New Features and Enhancements
Validate Models on Desktop or Target Using the Validation Tab
Model Converter now supports model validation through the Validation tab. You can validate a model against the original model outputs or against reference outputs provided in the Code Generation tab.
Model Converter supports two validation modes: Target Validation and Desktop Validation. Use Target Validation to stream validation data to a connected target device over UART. This mode supports one quantization configuration at a time. Use Desktop Validation to run validation on the desktop using QEMU for the selected quantization configuration, or compare results across all supported quantization configurations. To know more, refer to Model Validation.
Explore the model using the Model Viewer feature of model converter
The Model Converter integrates the open-source Netron network visualizer, allowing you to inspect model layers and weights to better visualize, analyze, and understand model architecture. Using Model Viewer, you can inspect your model at different stages of optimization, including which operators are accelerated by the U55 NPU and how the model is converted from one framework to another, such as .h5, .keras, or .pt2 to .tflite. To know more, refer to Model Viewer.
Generated File Naming
The generated code file names no longer include the quantization type. For example, model_float.c/h and model_int8x8.c/h are now generated as model.c/h.
If you are using version 1.0.0 of the Code Example, manually add the quantization suffix to the generated file names to maintain compatibility with that version. See the Code Example README.md file for the version number.
Fixes
- Resolved an issue that prevented the CLI tool from running in environments without a display adapter, such as Docker containers.
- Resolved an issue in the Use Provided Reference validation mode that caused incorrect validation results due to improper clipping of quantized data.
- Other small bug fixes and improvements