Initial attempt to populate HF-related metadata #1958
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Do not merge
Metadata Update Summary:
Total models processed: 452
Successfully updated: 216
Models not found in metadata: 160 (could not find metadata yaml file)
Success rate: 47.8%
Discussion:
If a user submitted a model that exists on HuggingFace but trained it entirely themselves, do we want to link to a HuggingFace model that was trained differently? Furthermore, often times a user will fine-tune a model themselves but not include that detail anywhere. How can we confirm that it was fine-tuned and can we assume that the pre-training was as described on the HuggingFace model page?