Skip to content
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 data_id when importing dataset #211

Closed
ClementLeBihan opened this issue Feb 29, 2024 · 1 comment
Closed

Wrong data_id when importing dataset #211

ClementLeBihan opened this issue Feb 29, 2024 · 1 comment
Assignees

Comments

@ClementLeBihan
Copy link

ClementLeBihan commented Feb 29, 2024

Hi,
When importing big dataset with annotations, it happen that some frame lose its annotation.

When opening the data_annotation_object, I can see the data_id field that is weird for the corresponding frame that hasn't correctly loaded the results.

image

Do you know this issue ?

@ClementLeBihan
Copy link
Author

ClementLeBihan commented Feb 29, 2024

I investigated more :
1 - The problem occurs randomly,
2 - When it happen for a frame, in saveBatchDataResult the dataIdMap missmatch the TempDataId of dataAnnotationObjectBOList :
For exemple the dataIdMap will be {-696053440268826030=31, -1259394534141999808=34, 3904700820343092532=30, -7117869251104120990=32, 1357986784990387562=33} while TempDataId of dataAnnotationObjectBOList are [2924171183170165039, -696053440268826030, -7117869251104120990, 1357986784990387562 , -1259394534141999808]
We can see that the first one doesn't have key in dataIdMap
3 - When I set parseExecutorService corePoolSize to 1, I don't have the bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants