-
Notifications
You must be signed in to change notification settings - Fork 998
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
Bring old seed technique back #2319
Conversation
re-done version of #2264, rebase issues 😓 |
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
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.
In principle, this LGTM. I added some comments, but no blockers for merging.
Regarding the original issue(s), do we have confirmation that the usage of SeedableRandomSampler
causes problems for the validation/test scores when the seed is fixed correctly?
Even if not, I can see the argument for going back to the previous default for conserving previous behavior, but arguably it should be recommended to use this new setting then.
Hi @muellerzr , we observed that the test |
Correct. I’ll be doing that this week/next |
* Redo stage 1 * Fix rest of tests * Expand doc * Expand x2 * Expand x2
hi @muellerzr , just want to follow up and check if we can make Trainer take an accelerate configuration so to make our test pass on cloud TPU v3. |
@vanbasten23 almost. See the PR for it here: huggingface/transformers#28664 |
Hi @muellerzr , could you check if huggingface/transformers#28664 is ready to merge? We would like to build on top your PR and bring the TPU tests into a successful state. Thanks! |
What does this PR do?
This PR disables the seedable random sampler by default. While yes it can make user results fully reproducible, it has a questionable degradation in quality which outweighs its benefits. It can be enabled explicitly in the
Accelerator
.Fixes #2268
Fixes #2208
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@BenjaminBossan