-
Notifications
You must be signed in to change notification settings - Fork 236
Migrate NNM Settings to SQLITE #1894
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
@mcm001 How do we want to handle importing object detection models from 2025? iirc all we had was the ability to export the |
Also if anyone feels like reviewing the backend stuff, that's pretty much done. |
@Override | ||
public boolean saveUploadedNeuralNetworkProperties(Path uploadPath) { | ||
// TODO I'm not implementing this cause nobody with the legacy config is gonna have one of these | ||
throw new UnsupportedOperationException( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean this exception may be caught. Nuclear option is to System.exit
* family. A suggested solution is to add other version attributes, and the | ||
* attribute for an unused version is to be left null. | ||
*/ | ||
public class ModelProperties { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider a static record
Description
This migrates all the characteristics for neural network models to the sqlite database. The
.rknn
files themselves will stay in the file-system.Each model will have a resolution characteristic (width x height), list of labels, nickname, family (currently only RKNN, but other families might be PRed later), and version.
When selecting the option to upload a custom model, users will be prompted to provide the model file and resolution. Family will be determined using file extension, and users will be prompted to select a version based on the the family. Nickname will be assigned to the name of the file initially, and can be changed in the UI.
When shipped with the jar, each model will have an accompanying json file listing its characteristics.
Also deletes object detection tests as they only reference the name parsing. More tests will be implemented at a later date (see #1905).
#1900 blocking cause I'm lazy and don't want to deal with merge conflicts on the front end.
Meta
Merge checklist: