Skip to content
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

Declare/formalize a model file format #673

Open
NickleDave opened this issue Jun 26, 2023 · 0 comments
Open

Declare/formalize a model file format #673

NickleDave opened this issue Jun 26, 2023 · 0 comments

Comments

@NickleDave
Copy link
Collaborator

#672 describes replacing several options in the config file with a single option model_path.
The semantics of the model_path option are that it points to a directory generated by vak train. We should formalize this as a file format, ideally baked into the code, e.g. as an attrs class.

Since we don't have existing constraints we can put this in place now to make life easier later--I would rather capture as much info as possible, in a directory, about model provenance, training procedure, etc, instead of needing to put a lot of that into code (like the torchvision weights abstraction).

Currently the "file format" is:

  • directory
  • with log file
  • config file
  • checkpoints folder
    • that has "intermittent save" checkpoint as well as "best performance on validation set" checkpoint
  • parts of transform pipeline, e.g. SpectScaler -- could we save the whole transform pipeline?
  • for frame classification: labelmap.json
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant