-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
Clarify use_fast
parameter in docstring
#20840
Conversation
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 great, made a minor suggestion if it resonates.
So as you added an additional suggestion to check architectures - what happens if the architecture supports it but the model doesn't? as is the case now with OPT models - some do and some don't.
The documentation is not available anymore as the PR was closed or merged. |
Hmm that's a good question! Do you happen to know if any of the other architectures have this issue or if it is just a bug with OPT? I'll remove the suggestion to check the supported framework list so we don't end up confusing anyone. |
It's the first time I run into this inconsistency across models of the same arch, but I have never needed to ensure it was So +1 to remove the suggestion unless we somehow can stand behind it. |
This was the bug for OPT, so it shouldn't happen for other models. |
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.
Thanks!
* clarify use_fast parameter * make style * remove check frameworks, apply review
* clarify use_fast parameter * make style * remove check frameworks, apply review
* clarify use_fast parameter * make style * remove check frameworks, apply review
* clarify use_fast parameter * make style * remove check frameworks, apply review
* clarify use_fast parameter * make style * remove check frameworks, apply review
This PR addresses the ambiguity of the
use_fast
parameter raised in #20817.