Skip to content
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

corrupt JPEG data: premature end od data segment | training yolov8m #16389

Open
1 task done
Vinaygoudasp7 opened this issue Sep 20, 2024 · 5 comments
Open
1 task done
Labels
detect Object Detection issues, PR's question Further information is requested Stale Stale and schedule for closing soon

Comments

@Vinaygoudasp7
Copy link

Search before asking

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

Question

@glenn-jocher i geting this error corrupt JPEG data: premature end of data segment while traing yolov8m and it showing this error on each epoch bvut it complete 700 epoch but when i used this model for converting into hailo it showing the error that NegativeSlopeExponentNonFixable: Quantization failed in layer custom_violation_model_700epoch/conv83 due to unsupported required slope. Desired shift is 13.0, but op has only 8 data bits. This error raises when the data or weight range are not balanced. Mostly happens when using random calibration-set/weights, the calibration-set is not normalized properly or batch-normalization was not used during training.

so plz i am requesting you to give solution for this
thank you

Additional

No response

@Vinaygoudasp7 Vinaygoudasp7 added the question Further information is requested label Sep 20, 2024
@UltralyticsAssistant UltralyticsAssistant added the detect Object Detection issues, PR's label Sep 20, 2024
@UltralyticsAssistant
Copy link
Member

UltralyticsAssistant commented Sep 20, 2024

👋 Hello @Vinaygoudasp7, thank you for reaching out and for your interest in Ultralytics 🚀!

We recommend checking out our Docs for additional guidance. If you’re new, there are helpful Python and CLI usage examples that might address common questions.

For your JPEG issue, it seems like you might be encountering a 🐛 bug. Please provide a minimum reproducible example to assist us in debugging this issue effectively. This will help a lot!

Regarding the training conversion issue, could you ensure that your calibration set is properly normalized and verify your batch-normalization settings during training? 🤔

Join the Ultralytics community for real-time support or discussions. Check out our Discord 🎧, engage in our Discourse, or explore conversations in our Subreddit.

Upgrade

Make sure you're running the latest version of the ultralytics package. You can upgrade with:

pip install -U ultralytics

Environments

Here's where YOLOv8 can be executed seamlessly:

  • Notebooks: Run on Gradient Open In Colab Open In Kaggle
  • Cloud Platforms: Google Cloud, Amazon AMI, Docker. Check out our quickstart guides for Google Cloud, AWS, and Docker.

Status

Ensure the systems are operational by checking our Ultralytics CI tests! ✅

Please note, this is an automated response. An Ultralytics engineer will follow up with you soon. Thank you for your patience and understanding! 😃

Copy link
Collaborator

I don't think it's related to the corrupted JPEG. It's probably failing for some other reason.

@Vinaygoudasp7
Copy link
Author

yes now i have deleted the corrupted jpeg and retrain with some epoch to test but still it geting same error @Y-T-G @glenn-jocher

Copy link
Collaborator

You should ask it on Hailo GitHub probably since it's not ultralytics related.

Copy link

github-actions bot commented Dec 9, 2024

👋 Hello there! We wanted to give you a friendly reminder that this issue has not had any recent activity and may be closed soon, but don't worry - you can always reopen it if needed. If you still have any questions or concerns, please feel free to let us know how we can help.

For additional resources and information, please see the links below:

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 YOLO 🚀 and Vision AI ⭐

@github-actions github-actions bot added the Stale Stale and schedule for closing soon label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
detect Object Detection issues, PR's question Further information is requested Stale Stale and schedule for closing soon
Projects
None yet
Development

No branches or pull requests

3 participants