Some questions about yolov11 training custom data #18282
-
i am use yolov11 train my custon datasets, and now have two question |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 9 replies
-
👋 Hello @jaffe-fly, thank you for your interest in Ultralytics 🚀! We appreciate you taking the time to share your questions. If this is a 🐛 Bug Report, please ensure you provide a minimum reproducible example (MRE) to help us better understand and debug the issue. For the questions you raised:
Please also verify you are using the latest pip install -U ultralytics If you’re seeking guidance on custom training, data augmentation, or other advanced configurations, sharing additional details such as dataset specifics, training logs, or examples of your inference outputs can go a long way in assisting us to help you effectively. This is an automated response, but rest assured, an Ultralytics engineer will review your question in greater detail soon! 😊 |
Beta Was this translation helpful? Give feedback.
-
@jaffe-fly 1. The issue of an object being detected with two classes and high confidence could arise from ambiguous or overlapping labels in your training dataset. Regularly reviewing and ensuring high-quality annotations can help. Tools like Label Studio or other annotation platforms may assist in identifying labeling issues.
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Is the generalization ability of yolov11 better than yolov8? Under the same dataset training and the same parameters, and then tested in a new scene, yolo11 can detect part of object, but yolov8 cannot,Even if you set conf= 0.3,yolov8 still cant detect anything |
Beta Was this translation helpful? Give feedback.
The smallest detectable object size depends on the model's stride and the image resolution during training. For YOLO11, the stride for
yolov11l-obb
is typically 32 pixels. With a2560x1440
image resized to1024x576
during training, the smallest detectable object would be approximately(1024 / 32) = 32 pixels
in the resized image, equivalent to(32 * original_image_width / imgsz)
in the original resolution.