-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
YOLOv8 Conduct training,but labels.jpg not data #93
Comments
👋 Hello @xiaolieat, thank you for submitting a
It seems your description mentions the issue with
Additionally, please ensure that your dataset adheres to the YOLO format described in the documentation. If you haven't already, you might find our dataset preparation guide useful! Lastly, if this issue relates to the functionality of the YOLOv8 model, remember that this repository is specifically dedicated to assets. 😄 For training and inference-related issues, you might want to refer to the This is an automated response to guide you efficiently, but don’t worry—an Ultralytics engineer will assist you soon. 🚀 Thank you for helping us improve! |
@xiaolieat thanks for including details. The empty plots typically indicate missing or invalid labels in your validation set. Let's verify:
For dataset verification, you can run: If issues persist, please share your dataset structure (number of images/labels in train/val) and consider testing with the standard COCO8 dataset from our Object Detection Datasets Guide to isolate the issue. |
Hello, when I was training with YOLO, I used the following line of command for training, my dataset is a YOLO format dataset downloaded from kaggle, I don't know why after training, there is only the number of categories in the labels.jpg, and there is no data for the other three graphs
yolo train data=YOLO_format/data.yaml model=ultralytics/cfg/models/v8/yolov8n.yaml pretrained=yolov8n.pt epochs=100 batch=64 resume=True
Here's a picture from my labels.jpg

Here's my version of YOLO

Here's a configuration file for my dataset

The text was updated successfully, but these errors were encountered: