-
Notifications
You must be signed in to change notification settings - Fork 617
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
[Fix] attn_dropout #123
[Fix] attn_dropout #123
Conversation
c389a1b
to
4bfb18f
Compare
maybe a semi-recent change, I think that @fmassa is right in that we should refactor core/. Else for some variant the setting was silently ignored (but not explicitly present in the constructor), so it would just fail for the factory, not as bad but still... Unit tests for the win, this should not happen again |
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.
Really nice catch!
_ = multi_head(inputs, inputs_shuffled, inputs) | ||
att = multi_head(inputs, inputs_shuffled, inputs) | ||
|
||
# Check that dropout actually drops some values |
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.
Great to have this test now!
Codecov Report
@@ Coverage Diff @@
## main #123 +/- ##
==========================================
+ Coverage 87.56% 87.61% +0.04%
==========================================
Files 50 50
Lines 2558 2567 +9
==========================================
+ Hits 2240 2249 +9
Misses 318 318
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Very small update to doc, command for benchmarking
What does this PR do?
Fixes #122 + adds a unit test to catch faulty dropouts
@fmassa is rewriting some of that part, but in the meantime
main
should not be knowingly brokenBefore submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.