-
Notifications
You must be signed in to change notification settings - Fork 3k
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
WiderFace import does not work #7258
Comments
Ok, I did some more investigation and found out that the root cause of the problem is within the |
Hi, if I understand correctly, fixing the
I think it's a problem in the Datumaro example, and it should be fixed there. |
@nmanovic and @zhiltsov-max, I've reproduced the error in my local development and according to the error there seems to be problem with the annotations label in the dataset, specifically, one of the bbox doesn't have a corresponding label as mentioned above. As this issue is still open, can you give me a hint on the work to be done here? If there is any, I would like to take it work on it. |
@teja1412-hub, it seems like the problem can be resolved just by updating the format example in our Datumaro fork, as it's being referenced by CVAT documentation. So, to fix this issue, please clone Datumaro locally and setup the dev environment, update the test dataset, update relevant tests in this file, and send us a PR in that repo. Please also check if the CVAT documentation on this format can be improved. |
@nmanovic @zhiltsov-max Okay. Can you assign this to me please. |
@nmanovic & @zhiltsov-max Could you review this and give me comments. As the error was occurring due to absence of a label named "face" which is being looked up by the CVAT in the dataset_meta.json file and as according to the format of WiderFace, the labels.txt file is optional but if dataset_meta.json is present, it looks up to the label named "face", so adding "labels": ["face] inside the object resolves the error. Although in the dataset_meta.json file, the labels_map which was previously mentioned as Additionally, 2) Task frame error while importing taskname.zip/ |
@teja1412-hub, thank you for the investigation. I suggest that we start from the first problem. Regarding the second problem, do you have any ideas on how it can be resolved? |
@nmanovic @zhiltsov-max For the first problem, addition of "labels": ["face"] in the dataset_meta.json file would suffice. I was able to import the dataset successfully once this change was made. I wrote the above message so I could inform you before sending a PR incase you suggest anything after reviewing. Also, I forgot to mention that the images in the WideFace dataset in datumaro repository are erroneous. The images have a problem, need to look into them. |
@nmanovic @zhiltsov-max I've fixed the first issue being encountered in the widerface dataset of datumaro repository. Pls find the link for the PR #36 and can you please review it. |
<!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> Closes #7703 Related: #7258 Related: #7125 Related: #7699 Changes: cvat-ai/datumaro@8a14a99...82982b1 - Fixed WiderFace dataset example - Fixed export without images in Datumaro format - no empty `media` and `point_cloud` fields should be in the results ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] I submit my changes into the `develop` branch - [ ] I have created a changelog fragment <!-- see top comment in CHANGELOG.md --> - [ ] I have updated the documentation accordingly - [ ] I have added tests to cover my changes - [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [ ] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern.
Actions before raising this issue
Steps to Reproduce
I am getting an error with the following message:
Expected Behavior
The dataset gets imported.
Possible Solution
No response
Context
Well, I started with the WiderFace dataset from huggingface, but unfortunatly it didn't work, even after considering CVAT docs. When using VGGFace2 1.0 with the corresponding example dataset works fine.
Environment
The text was updated successfully, but these errors were encountered: