-
Notifications
You must be signed in to change notification settings - Fork 180
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
Model library #317
Comments
Hey @bw4sz , I would like to work on this issue, Can you please guide me? |
What have you done so far? |
It seems like moving to Hugging Face for model distribution is the most common solution here. If we use the pytorch integration: https://huggingface.co/docs/hub/models-uploading#upload-a-pytorch-model-using-huggingfacehub then we can use the model.from_pretrained("weecology/deepforest-trees") I setup an org account https://huggingface.co/weecology and can add @bw4sz & @henrykironde if this sounds like the general way to go. |
@henrykironde this will be an issue i'll connect to alive/dead model. |
What we want
|
@ethanwhite, @henrykironde and I were discussing that as the number of trained models increase, we probably want some more refined way of versioning them and calling them. Right now they are saved alongside the release tags. Each new model would get a "use_release" method, with redundant code, etc.
An example release looks like:
https://github.com/weecology/DeepForest/releases/tag/1.0.0
Which is fine. When use_release is called, the model checks github for the latest release. A couple problems.
https://pytorch.org/blog/introducing-torchvision-new-multi-weight-support-api/
I have not read deeply enough to know if they can be used in parallel.
The text was updated successfully, but these errors were encountered: