Skip to content
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.

Sign up for GitHub

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

Jump to bottom

averagePooling2D calculates wrongly with torch backend #19721

Open
AGFACBNNR opened this issue May 17, 2024 · 1 comment
Open

averagePooling2D calculates wrongly with torch backend #19721

AGFACBNNR opened this issue May 17, 2024 · 1 comment
Assignees
@mattdangerw @sachinprasadhs
Labels
backend:torch type:Bug

Comments

@AGFACBNNR
Copy link

As shown in this colab,
AveragePooling2D generate an output with wrong shape with torch backend.
Specifically, the bug is triggered only when padding='same' and input_height != input_weight.
Details can be checked in the shared colab, currently the output is:
1715913721152
When the bug is triggered(line 2 and line 5 in output), the output has an wrong shape.
@AGFACBNNR
Copy link
Author

AGFACBNNR commented May 17, 2024 •
edited

Besides, averagePooling3D and maxpooling2D have similar problems, possibly because of their same base class.

@chunduriv chunduriv added type:Bug backend:torch keras-team-review-pending Pending review by a Keras team member. labels May 20, 2024
@mattdangerw mattdangerw removed the keras-team-review-pending Pending review by a Keras team member. label May 23, 2024
@mattdangerw mattdangerw self-assigned this May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mattdangerw mattdangerw

@sachinprasadhs sachinprasadhs

Labels
backend:torch type:Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mattdangerw @AGFACBNNR @sachinprasadhs @chunduriv