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 #2451

Closed
thx13 opened this issue Mar 13, 2021 · 7 comments · Fixed by #3638 or #4548
Closed

corrupt JPEG data #2451

thx13 opened this issue Mar 13, 2021 · 7 comments · Fixed by #3638 or #4548
Labels
question Further information is requested Stale Stale and schedule for closing soon

Comments

@thx13
Copy link

thx13 commented Mar 13, 2021

Excuse me.When i was training my data, the cmd would show this problem: 'corrupt JPEG data:Premature end of data segment'. Would it influence the result? My train data adds some background images.

@thx13 thx13 added the question Further information is requested label Mar 13, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Mar 13, 2021

👋 Hello @thx13, 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://www.ultralytics.com or email Glenn Jocher at [email protected].

Requirements

Python 3.8 or later with all requirements.txt dependencies installed, including torch>=1.7. To install run:

$ pip install -r requirements.txt

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):

Status

CI CPU testing

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), testing (test.py), inference (detect.py) and export (export.py) on MacOS, Windows, and Ubuntu every 24 hours and on every commit.

@glenn-jocher
Copy link
Member

@thx13 this is a low level C error caused by corrupt or incomplete jpeg images in your dataset, it is not easy to detect in python. See https://stackoverflow.com/questions/33548956/detect-avoid-premature-end-of-jpeg-in-cv2-python

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale Stale and schedule for closing soon label Apr 13, 2021
@glenn-jocher glenn-jocher linked a pull request Jun 16, 2021 that will close this issue
@glenn-jocher
Copy link
Member

glenn-jocher commented Jun 16, 2021

@thx13 good news 😃! Your original issue may now be fixed ✅ in PR #3638. To receive this update:

  • Gitgit pull from within your yolov5/ directory or git clone https://github.com/ultralytics/yolov5 again
  • PyTorch Hub – Force-reload with model = torch.hub.load('ultralytics/yolov5', 'yolov5s', force_reload=True)
  • Notebooks – View updated notebooks Open In Colab Open In Kaggle
  • Dockersudo docker pull ultralytics/yolov5:latest to update your image Docker Pulls

Thank you for spotting this issue and informing us of the problem. Please let us know if this update resolves the issue for you, and feel free to inform us of any other issues you discover or feature requests that come to mind. Happy trainings with YOLOv5 🚀!

@glenn-jocher glenn-jocher linked a pull request Aug 26, 2021 that will close this issue
@glenn-jocher
Copy link
Member

glenn-jocher commented Aug 26, 2021

@thx13 good news 😃! Your original issue may now be fixed ✅ in PR #4548. This PR automatically restores and saves corrupted JPEGs before training starts, and all images are now used for training, including the restored JPEGs.

To receive this update:

  • Gitgit pull from within your yolov5/ directory or git clone https://github.com/ultralytics/yolov5 again
  • PyTorch Hub – Force-reload with model = torch.hub.load('ultralytics/yolov5', 'yolov5s', force_reload=True)
  • Notebooks – View updated notebooks Open In Colab Open In Kaggle
  • Dockersudo docker pull ultralytics/yolov5:latest to update your image Docker Pulls

Thank you for spotting this issue and informing us of the problem. Please let us know if this update resolves the issue for you, and feel free to inform us of any other issues you discover or feature requests that come to mind. Happy trainings with YOLOv5 🚀!

@KKhaledZen13
Copy link

@glenn-jocher Hello, I believe the same issue is present using yolov8 if you run it through the proposed tiger pose dataset.
Though i will mention... i didnt install ultralytics lib instead i took the "bin" file yolo from the bin folder and i use it on the ultralytics folder.

@glenn-jocher
Copy link
Member

Hello @KKhaledZen13! It appears there might be a mix-up in your setup process. For optimum performance and compatibility with our datasets, including the "tiger pose" dataset, it's recommended to fully install the Ultralytics library rather than relying on binaries directly from the "bin" folder. This ensures all dependencies and necessary components are correctly aligned. Could you try installing the library following the provided guidelines and verify if the issue persists? Here's a quick reminder on how to install:

pip install ultralytics

If the problem continues even after installation, please let us know. We're here to help! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested Stale Stale and schedule for closing soon
Projects
None yet
3 participants