-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
TypeError: 'int' object is not iterable when importing YOLO dataset #8958
Comments
@eKevinHoang |
@Eldies You can download any dataset in YOLO format from roboflow.com and try it. For example, you can use this dataset: https://universe.roboflow.com/object-detection-ifpbo/vehicle-detection-vkwyt/dataset/4 I'm using docker and launch CVAT by Let me know if you need further assistance! |
Additionally, I noticed that in CVAT's dataset selection menu, the option for YOLO Dataset refers to version 1.0. However, I attempted to convert my dataset to the YOLO v1.0 structure, and it still could not be imported. The system also requires data.yaml file, which aligns more with newer YOLO formats. I believe the version label in the supported dataset list should be updated to reflect the actual YOLO version it supports. This would help users better understand the required dataset structure and avoid confusion. Let me know if you'd like to refine this further! |
I think this is caused by a mismatch between the keys cvat expects in In my case I had the |
@beaglebot I have replaced the key nc with classes. My data.yaml file now looks like this:
I have referred to this link: Based on that, I updated my data.yaml file to the following:
However, I am still encountering the same error: Could you please help me identify what might be missing or incorrect? |
My path: .
train: train.txt
valid: valid.txt
classes: 3
names:
0: person
1: car
2: nzpost I can upload annotations with this and it works correctly. |
Actions before raising this issue
Steps to Reproduce
Expected Behavior
The YOLO dataset should be imported successfully, and the annotations should be visible for editing.
Possible Solution
No response
Context
The dataset structure is as below:
Environment
The text was updated successfully, but these errors were encountered: