AssertionError: (torch.Size([1, 3, 640, 640]), (1, 3, 640, 480))

[Specialized123]

Search before asking

• I have searched the YOLOv5 issues and discussions and found no similar questions.

Question

Hello!
I use Jetson Xavier NX to deploy programs

Environment：
Jetpack: 4.6
Tensorrt: 8.0.1.6
Python: 3.6.9
Pytorch: 1.8.0
torchvision: 0.9.0a0+01dfa8e
cuda: 10.2

I use this statement to export：
python export.py --best.pt --include engine --imgsz 640 480 --device 0
I used to export on the same device

Run
I use this statement to run the program：
python detect.py --weights best.engine --source 0
I connected a usb camera

Bug
AssertionError: (torch.Size([1, 3, 640, 640]), (1, 3, 640, 480))

I hope you can help me solve this problem

Many thanks and best regards！

Additional

No response

[github-actions]

👋 Hello @Specialized123, thank you for your interest in YOLOv5 🚀! Please visit our ⭐️ Tutorials to get started, where you can find quickstart guides for simple tasks like Custom Data Training all the way to advanced concepts like Hyperparameter Evolution.

If this is a 🐛 Bug Report, please provide screenshots and minimum viable code to reproduce your issue, otherwise we can not help you.

If this is a custom training ❓ Question, please provide as much information as possible, including dataset images, training logs, screenshots, and a public link to online W&B logging if available.

For business inquiries or professional support requests please visit https://ultralytics.com or email [email protected].

Requirements

Python>=3.7.0 with all requirements.txt installed including PyTorch>=1.7. To get started:

git clone https://github.com/ultralytics/yolov5  # clone
cd yolov5
pip install -r requirements.txt  # install

Environments

YOLOv5 may be run in any of the following up-to-date verified environments (with all dependencies including CUDA/CUDNN, Python and PyTorch preinstalled):

• Google Colab and Kaggle notebooks with free GPU:
• Google Cloud Deep Learning VM. See GCP Quickstart Guide
• Amazon Deep Learning AMI. See AWS Quickstart Guide
• Docker Image. See Docker Quickstart Guide

Status

If this badge is green, all YOLOv5 GitHub Actions Continuous Integration (CI) tests are currently passing. CI tests verify correct operation of YOLOv5 training (train.py), validation (val.py), inference (detect.py) and export (export.py) on MacOS, Windows, and Ubuntu every 24 hours and on every commit.

[rglkt]

i meet the problem too, i think the wrong is on common.py 299 line .when it will set imgsz as 64 stride forcely when your model is 32 stride. the solution is set 299 line stide as 32

[rglkt]

#7342 you can try as my code

[github-actions]

👋 Hello, this issue has been automatically marked as stale because it has not had recent activity. Please note it will be closed if no further activity occurs.

Access additional YOLOv5 🚀 resources:

• Wiki – https://github.com/ultralytics/yolov5/wiki
• Tutorials – https://docs.ultralytics.com/yolov5
• Docs – https://docs.ultralytics.com

Access additional Ultralytics ⚡ resources:

• Ultralytics HUB – https://ultralytics.com/hub
• Vision API – https://ultralytics.com/yolov5
• About Us – https://ultralytics.com/about
• Join Our Team – https://ultralytics.com/work
• Contact Us – https://ultralytics.com/contact

Feel free to inform us of any other issues you discover or feature requests that come to mind in the future. Pull Requests (PRs) are also always welcomed!

Thank you for your contributions to YOLOv5 🚀 and Vision AI ⭐!

[lifenghong]

hello , I am missing the same problem
Run
I use this statement to run the program：python detect.py --weights best.engine -- images
error:
,I hope you can help me solve this problem

Many thanks and best regards！

[rglkt]

hello , I am missing the same problem Run I use this statement to run the program：python detect.py --weights best.engine -- images error: ,I hope you can help me solve this problem

Many thanks and best regards！

It seems that what you encountered is not the same problem, the problem of this issue has been solved in this pr. The problem you encountered seems to be that the channel is wrong, is there no unsqueeze?

#7342

[glenn-jocher]

@rglkt hi there! It seems like the issue you encountered might be different from the one originally reported. It looks like the problem in the image you provided might be related to incorrect channel handling. Have you checked if there is a need for unsqueezing the data? The solution provided in the pull request you mentioned may not directly apply to your case.

Let me know if you need further assistance with this or if there's anything else I can help you with. Thank you!