-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Inconsistent ch
attribute not working as expected
#18229
Comments
👋 Hello @NicolasDrapier, thank you for your interest in Ultralytics 🚀! We appreciate you bringing this to our attention. While we cannot resolve your issue immediately, an Ultralytics engineer will review it soon. In the meantime, here's some guidance to assist you: ✅ Recommendations
🐞 Bug ReportsIf this is a bug, please provide a minimum reproducible example (MRE) demonstrating the issue. This helps us debug more efficiently and understand your case better. Based on your description, sharing the exact 📚 Resources
🌐 CommunityFeel free to join our vibrant community for real-time support or discussions: 🚀 EnvironmentsTo ensure a smooth experience, we recommend running YOLO in one of the following verified environments with up-to-date dependencies:
✅ Continuous Integration (CI) Status
Once you've gathered an MRE or further information, feel free to update this thread, and we'll assist you further. Thank you for your patience! 😊 |
You should use a different yaml filename so that it doesn't conflict with the default yaml filenames. |
Let me try next week |
@NicolasDrapier take your time! If you encounter any issues or have further questions, feel free to reach out. The YOLO community and Ultralytics team are here to help. |
Search before asking
Question
Hello,
I am encountering an issue when trying to specify a custom number of channels using the
ch
attribute in my.yaml
configuration file. Specifically, I setch: 6
, and then attempt to run the model as follows:This results in a runtime error indicating a channel mismatch. It seems like the model still expects a 3-channel input, despite having
ch: 6
defined in theYAML
.Error message
RuntimeError: Given groups=1, weight of size [64, 6, 3, 3], expected input[1, 3, 640, 640] to have 6 channels, but got 3 channels instead
Stacktrace
Expected Behavior:
I expect that when I set
ch: 6
in the .yaml file, the model should correctly accept an image tensor with 6 channels as input, without throwing a channel mismatch error. Is it a bug?Additional
ultralytics==8.3.49
The text was updated successfully, but these errors were encountered: