-
Notifications
You must be signed in to change notification settings - Fork 19.6k
Modified compute_output_shape function to handle broadcasting behavior in layers.Rescaling #21351
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
Conversation
…ur in layers.Rescaling
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #21351 +/- ##
==========================================
+ Coverage 82.65% 82.74% +0.09%
==========================================
Files 565 565
Lines 54823 55339 +516
Branches 8514 8639 +125
==========================================
+ Hits 45315 45793 +478
- Misses 7414 7440 +26
- Partials 2094 2106 +12
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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 for the PR! The change should be accompanied by a unit test.
Please fix the failing torch test
|
Hi @fchollet,
Output shapes :
However, in CI environment, and specifically with the Torch backend, the output shape has an extra dimension. |
The key bit is that torch tests run with |
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, thank you
compute_output_shape()
inRescaling
to correctly handle the broadcasting and ensure consistent shapes inmodel.summary()
andmodel.output_shape
.Rescaling
layer docstring with detailed description ofscale
andoffset
parameters.Fixes #21319