-
Notifications
You must be signed in to change notification settings - Fork 74
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
Incorrect Data Path in YOLOv8 Dataset Configuration #240
Comments
same problem |
Hey @tomershukhman . Did some digging around the source code and struggled to see if this was an Ultralytics issue or a pathing issue in Roboflow. Did changing the ultralytics settings affect anything? If not, can you check your environment variables for a |
I posted this error in ultralytics repository and this was their response. |
Bug Report: Incorrect Data Path in YOLOv8 Dataset Configuration
Description
While using the Roboflow Python client to download a YOLOv8 dataset for a tennis ball tracking project, I encountered an issue with the generated
data.yaml
file. The file's paths were incorrectly set, leading to aRuntimeError
when attempting to train the YOLO model.Steps to Reproduce
Download the dataset using the Roboflow Python client:
Observe the downloaded
TennisBallTracker-9
folder with the standard YOLOv8 dataset structure.Check the
data.yaml
file, which incorrectly references paths for training, validation, and test images.Expected Behavior
The
data.yaml
file should correctly point to the respective image directories within the dataset folder.Actual Behavior
The
data.yaml
file contains incorrect paths, leading to aRuntimeError
when the YOLO model attempts to access the image directories:TL;DR
The issue might be related to residual settings from a previous project (
android_figurine
) that seems to interfere with the current dataset configuration. It's unclear why the old dataset path is being referenced.Temporary Solution
I modified the
data.yaml
file manually to correct the paths, which allowed the training to proceed successfully:Environment
Python version: 3.12
The text was updated successfully, but these errors were encountered: