-
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
Exporting project with duplicate image names incorrect #8076
Comments
I have an approach to solve this issue, we can edit the renaming mechanism by the following ways:
These are some feasible reasons, please check and confirm @zhiltsov-max @alexyao2015 |
The second option seems like it would work as a simple fix. Alternatively, there could be a check to see if the file exists already in the export and append something else to the filename until it no longer conflicts. |
Yeah that's right, should i work on this issue @alexyao2015 ? |
That would be great. Please go ahead. |
Assign me this issue,(◔‿◔) |
@BarryByte, consider adding endpoint parameters and some UI elements to control the behavior (e.g. the prefix or filename pattern). It will be nice if you create a detailed description of the suggested changes first. |
An even simpler way is to just rename all images to image_1, image_2, etc., without preserving the original filename. |
@alexyao2015, it's already being done. The problem is that there is no way to find out the real source of the image in the exported dataset. |
Right so as you are exporting images, you export and rename the image regardless of if it's overlapping. What's going on now is it's seeing a potentially duplicate name and renaming if it's duplicate. I would just use a simple counter, incrementing with each image, and export the images with a fixed name so it's impossible to have overlapping names. |
@alexyao2015, yes, it will fix the problem with name collisions. But it doesn't solve the problem with determining the origin of the frame. |
Have a map with the job id and original image name to the remapped image name in memory? Is there something I'm missing? |
@alexyao2015, it's needed for users, not for export to work. The problem is: there were some images with some names in the tasks in the project. Then the project is exported in some format, with image names mangled. Now, the resulting dataset contains some modified frame names, and the user can't get their origin to do some further analysis of the exported dataset. They need to match the output names with source task or job names, but there is no way to determine this for the user. Simple potential ways of solving the problem - provide an output mapping or change the added suffix from _N to _job_N. |
Hi all, Is there any update on this issue? Happy to help if needed. Thanks, |
Hello, |
Actions before raising this issue
Steps to Reproduce
image_1.jpg
,image_2.jpg
,image_3.jpg
,image_4.jpg
, etc.image.jpg
. I actually used the python sdk like follows to create this.image_1.jpg
, etc are overwritten by the images of the other jobs.I believe CVAT attempts to rename the other jobs conflicting names by adding
_1
,_2
, etc. ,but it doesn't account for those names existing in other jobs or in the current export dataset.Expected Behavior
Images should not be overridden by images in other jobs when exporting a project
Possible Solution
No response
Context
No response
Environment
No response
The text was updated successfully, but these errors were encountered: