-
Notifications
You must be signed in to change notification settings - Fork 0
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
continued refactoring of feature extractor and classifier #38
Conversation
There are a few issues with running the classier, most of them so far seem minor:
With some poking around in the code I could have the classifier at least spit out the frame predictions, making it work with the downstream knitting code needs a few more little edits. I have not yet tried to create a new model and use that. About combining model config and classifier config... I assume classifier config means those settings that effect how the classifier operates, like frameRate, and that model config refers to settings like num_layers and dropout. If we combine them then it has to be made clear that the user cannot simply change the latter since they are inherent to the model chosen. Also, I thought the model settings were saved with the model when it was created (alongside the results file), which is why I had model_file and model_config: model_file: "modeling/models/20231026-164841.kfold_000.pt"
model_config: "modeling/models/20231026-164841.config.yml" I wasn't necessarily happy with that and was thinking about just having model: "modeling/models/20231026-164841.kfold_000.pt" and have the code figure out where to find the configuration of that model. Merging the two does not impact the trainer's export code, but we do now manually take some of the settings from the config export and add them to another config file. It looks like we now would need to manually update the configurations when we pick a different model. |
@keighrim Are the configuration settings in |
I ran the classifier again using the positional model that I created yesterday, same error:
The config file used here was the same as
It did still have a reference to "other" in the labels list so I got rid of that. This gave more errors:
I also tried creating the model again:
And after that we get an error. |
… regarding negative labels in configs
New commits contain many fixes including a fix for the positional encoder bug that ended up with 60768-dimensional vectors. |
With the latest changes the classifier now runs on the convnext model with positional encodings. After some more testing I will merge this into the 14-clamsapp branch and prepare a new app version. |
... or I may just review this pull request so it can be merged into develop |
I made one more small change before merging this. (please find the latest commit msg helpful). |
more fix for #31
Cherry picked old commits of mine, and tried to resolved all the conflicts with current code. @marcverhagen could you verify the code runs? A few notes;
modeling/config/classifier-full.yml
filemodeling/config/classifier-no-position.yml
symlinked toexample-config.yml
that has configs for the "old" model w/o pos_enctrain.py
module, though.Let me know if you have questions.