Open jikechao opened 10 months ago
Hi @jikechao Is it GPU specific issue? How does it work on CPU? It will help to determine a component to investigate
@ilya-lavrenov GPU and CPU and the same problem. Both of them in OpenVINO have different output shapes with PyTorch.
That is a known issue. Same as for MaxPool, however it was fixed for MaxPool https://github.com/openvinotoolkit/openvino/blob/9decbb538bcd791cbc394cd18f8754370e1b300a/src/frontends/pytorch/src/op/max_poolnd.cpp#L58-L101 But the fix is not great in terms of performance and it generates incorrect indices for that case. This problem is caused by a known issue in torch, which wouldn't be fixed AFIK and can be treated as a feature at this point. We are discussing a possibility to support it with a new opset version of pooling ops.
OpenVINO Version
2023.1.0-12185-9e6b00e51cd-releases/2023/1
Operating System
Ubuntu 18.04 (LTS)
Device used for inference
CPU/GPU
Framework
PyTorch
Model used
No response
Issue description
For the model shown in the below script, OpenVINO and PyTorch gave an different output shape.
Step-by-step reproduction
Relevant log output
Issue submission checklist