onnx error with different input size about gen-efficientnet-pytorch HOT 4 CLOSED

I assume you exported to onnx with the same resolution set? If yes, I don't have an answer. The onnx ecosystem is a bit touchy, I've seen numerous breaks over the past few PyTorch and onnx version changes. TensorRT adds yet another variable. Good luck, please update if you find a solution to help others.

from gen-efficientnet-pytorch.

if I use the feature size (105 x 105) do your designed conv with stride 2 ,
the output size will be (53 x 53)

and the https://github.com/lukemelas/EfficientNet-PyTorch
do the same thing , the output size will be (52 x 52)
why? thanks

from gen-efficientnet-pytorch.

@alicera I'm not sure what your issue is? as far as I understand 53x53 is the correct output if the input is 105x105, stride 2, and padding is set to 'SAME' or 1, as it should be for the stride 2 convs in this network.

from gen-efficientnet-pytorch.

https://github.com/lukemelas/EfficientNet-PyTorch
if I set the input size (1,3,840,840)
and the layers output are
P0 torch.Size([1, 16, 420, 420])
P1 torch.Size([1, 24, 210, 210])
P2 torch.Size([1, 40, 105, 105])
P3 torch.Size([1, 80, 52, 52])
P4 torch.Size([1, 112, 26, 26])
P5 torch.Size([1, 192, 13, 13])
P6 torch.Size([1, 320, 6, 6])

and if I use the same input size (1,3,840,840)
the P3 output will be ([1, 80, 53, 53]) in your project

from gen-efficientnet-pytorch.