Open kparichay opened 2 years ago
:octocat: cibot: Thank you for posting issue #1709. The person in charge will reply soon.
There are two possible options to store information 3. with the model:
Note: the information regarding 3. can be stored in the BIN file but it is not a good option as BIN file description is to provide the model weights. Any information related to model configuration (this optimization is part of model configuration up to certain extend) is better suited to INI. Note: the information regarding 3. can also be stored in a new file format but we already have 2 file formats: INI for model architecture and configuration, and BIN for model weights. Adding a third file format is not recommended.
For 1. Adding tflite information to the *.fbs should do no harm technically, but once we start to put some information, it's no longer a mere mirror of the file but will deviate from the original schema anyway. We need to decide if this is acceptable before moving on.
We have three kinds of optimization being done for the models which can become expensive over time once optimization techniques are enhanced:
The information generated from these optimizations is as below:
Information from 1. and 2. can be stored in the existing ini format while saving the model, allowing the optimization to be done offline, and skipped when loading the optimized ini file. However, storing the information from 3. requires new support.