-
Notifications
You must be signed in to change notification settings - Fork 570
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
Use default model_name
in metadata_update
#1157
Conversation
The documentation is not available anymore as the PR was closed or merged. |
To be honest, I don't know enough about metadata to really have an opinion on the "name" under "model-index". But I agree with you that in general we don't want to bother users about very specific features. I ping @nateraw would worked on that and might be more opinionated. Otherwise, I noticed that for (3) you are talking about the repo name (e.g. "bart-base") and not the repo id (e.g. "facebook/bart-base"). I guess that's intended but wanted to highlight it for others in the discussion. And also if we move forward on this PR, @lvwerra could you please add at least one test that triggers case (2) or (3) (e.g. a case that is currently broken but that your PR solves). Thanks in advance ! |
Yes, will add tests if people are happy with the suggested change, thanks @Wauplin! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
personally I would use the full repo_id, but otherwise, lgtm!
Co-authored-by: Julien Chaumond <julien@huggingface.co>
Sounds good, also added some tests :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks for adding the test !
Please wait for @nateraw 's review before merging :)
Just getting to his ( was off on Friday ). Having a look! |
Agree with repo ID but I'm not too opinionated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks for the update. One concern is that we do mention this required name in the docs for model card.
Do we need to update the docstring around this? Mentioned in eval_result kwarg docstring as well.
Thanks for docstring update. ❤️ once quality tests/other tests pass this is good to go I think :) |
Codecov ReportBase: 84.54% // Head: 84.70% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #1157 +/- ##
==========================================
+ Coverage 84.54% 84.70% +0.16%
==========================================
Files 42 42
Lines 4147 4184 +37
==========================================
+ Hits 3506 3544 +38
+ Misses 641 640 -1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
I'm finally merging the PR. Thanks @lvwerra for all the modifications ! :) |
As reported by a user, the
metadata_update
does not work anymore (likely introduced in #940) if no"name"
field in the"model-index"
is provided. This breaks for exampleevaluate.push_to_hub
where evaluation results are pushed to the hub.With this PR the following behaviour is supported:
"model-index"
of new metadata has a"name"
it is used (1)"name"
Since the
"name"
is I think a little known feature of the PwC integration and providing a model name when pushing the results to a model repo seems a bit redundant I feel like having good defaults and not bother the user with it is a good idea. If you think this is a bad idea, we can throw an error in case (3).cc @julien-c