Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Checklist for Model Hub
See original GitHub issue🚀 Feature request
I want to propose a checklist for model hub. Model hub is increasingly being used by transformers users. It is imperative that users exactly know what model they are downloading and importing for transparency and research-related reasons. It should be mandatory for users to upload a REAME.md while uploading model on model hub. Additionally, it will reduce the need to send a seperate PR for model cards.
Checklist should contain the following elements:
- Details of training and validation set used. Specify the split if not using default.
- A table with results on the validation set
- Model name (can be inferred from
config.json) - Objective used for training
- Hyperparameter configurations if default ones are not being used
- Link to implemented code (if available, and is different from default examples)
- For how many epochs the model was trained for ?
- Associated paper (if published)
These are just the general ones. Happy to hear about other suggestions. This is just a suggestion which would help many users. Thanks for this feature.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes! This is something we’ll build, step by step. I’ll post more about our roadmap for this in the coming weeks.
Maybe you can create a web-based interface with input fields/drop downs that can generate the model card automatically. Just a thought.