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
Wrong number of classes in data.yaml #88
Comments
Thanks @sannicosan for opening the issue, I've escalated this internally and we will reply soon :) |
Here I attach another evidence of how the unexisting/unused class appears out of nowhere: |
hey @sannicosan could you please add help@roboflow.com to your workspace? |
Hi @sannicosan! I took a look at your project, and I was able to export a version while dropping the 'typo class'. Not sure why the '/' class didn't show up in your class remapping window. Checkout version 28 and see if that gets you what you need. |
Hello, The same thing is happening to our data set. We have 5 labels for objects we are looking for circles of color: blue, red, purple, orange, yellow. After running through RoboFlow to convert the Pascal VOC labels to .txt for yoloV8, the data set .txt labels had 10 classes. It created a red-circle, blue-circle, ... etc. The new classes that appear out of nowhere are being assigned to some of the classes have labeled. There is an option to delete classes after the creation of all the .txt files. Does this delete all the false class created to replace them back to what they need to be. Meaning class "blue-circle" will revert back to "blue" |
Description
After labelling all the images in the dataset, when generating a new dataset version and downloading it, the data.yaml created additional non-existing classes.
Steps to reproduce
Expected result
You should only get the classes that you labeled
Actual result
The roboflow creates additional non-existing classes (this also alters the class_id of the real classes)
Note: While labeling, there were some classes that were created by mistake, but they were deleted afterwards since they were never used. This somehow was still picked up by the roboflow.
Evidence
You can clearly see I had 2 classes:
When downloading the dataset, its data.yaml config file looked like this:
This remapped my original class_id's of course.
This was my original data.yaml:
The text was updated successfully, but these errors were encountered: