-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
How to optimize #12719
Comments
It looks like you're trying to optimize the model training parameters! For the given
An example command might look like this: yolo train data=coco.yaml model=yolov8s-seg.pt imgsz=1280 epochs=100 flipud=0.5 fliplr=0.5 lr0=0.01 mosaic=0.1 mixup=0.2 Adjust the additional augmentation parameters ( |
Thank you, very valuable for reference The problem has been resolved But when reasoning, it must be 640 to avoid any problems model.predict('bus.jpg', save=True, imgsz=640 ) |
@monkeycc i'm glad to hear that your problem is resolved! 🎉 Regarding your question, the discrepancy you're seeing in image sizes between training and inference typically relates to the model's handling of different input dimensions. During training ( Here's the key: make sure the inference image size ( If you need to maintain both high accuracy and performance during inference, you might consider retraining your model at a lower |
Training model predict predict What is the reason |
Hi there! It seems like you're encountering a drop in recognition rate when using This could be due to a few factors:
For consistency and performance, it’s generally recommended to use the same image size for training and prediction. If Here's a quick check you can do in prediction: model = YOLO('path/to/model.pt')
results = model.predict('path/to/image.jpg', imgsz=1280) # test at high resolution
print(results.xyxy) Hope this helps! Let me know if you have more questions. 🚀 |
Search before asking
Question
yolov8s-seg.pt
imgsz=1280 , epochs=100, flipud = 0.5 , fliplr = 0.5
Additional
No response
The text was updated successfully, but these errors were encountered: