You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of freedom is left to creators of models and datasets, particularly model dependencies and data formats - Scivision is supposed to work with a wider range of models and data than we could anticipate.
Despite this, there are certainly some recommendations we could make, even if it would be hard to make them requirements.
We can link to recommendations from others (general advice or community/library specific).
Some ideas below - please update the list with more!
General
Create a page in the docs for collecting these (or update model and data pages)
Model authors
platform portability
package dependencies. Ideally pin all primary dependencies either to a range (including both top and bottom) or to the current version (which is known to work)
Tensorflow-specific advice
...
pytorch-specific advice
...
Testing
Include a test that runs the model on toy data (check the output at the right level - could check for NaN, probably don't want to insist on bitwise reproducibility. Classifier could check most probable class etc.)
A lot of freedom is left to creators of models and datasets, particularly model dependencies and data formats - Scivision is supposed to work with a wider range of models and data than we could anticipate.
Despite this, there are certainly some recommendations we could make, even if it would be hard to make them requirements.
We can link to recommendations from others (general advice or community/library specific).
Some ideas below - please update the list with more!
General
Model authors
Data providers
The text was updated successfully, but these errors were encountered: