-
Notifications
You must be signed in to change notification settings - Fork 189
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
Find object issues with large session file (> 4GB) #66
Comments
I think this issue maybe related with OpenCV |
I don't have crash with the dataset you sent me. Here is the end of the update of the vocabulary with parameters saved in your session 1gb-model.bin (clicking on "update objects" on GUI):
When saving this session to test2.bin and reload it from console with the scene:
If I use your session:
Only one object is detected. I suspect that regenerating the vocabulary on my system (maybe different OpenCV version) gave a slightly different vocabulary: This is the opencv version I am using (Ubuntu 16.04, with ROS Kinetic installed):
cmake output:
|
Hi matlabe, Can you share your config when load object above so I can compare with my config? You can try with 4gb-model.bin and object-session-4GB.zip, I have uploaded it |
I used the same config file. I tested the 4GB dataset, and there was a maximum vocabulary size limitation with how the session was saved and loaded. The code is using QByteArray to save the data, for which the maximum data that it can hold is 2GB (max integer). I compress now the vocabulary to limit the size of the exported vocabulary size under 2 GB (900MB compressed instead of 3GB uncompressed on this dataset). If compressed vocabulary is over 2 GB, an error will be shown. See commit 556bf5f Example:
Detection:
|
Thanks matlabe |
Hi matlabe,
When I use find-object to load my dataset (~ 25000 files) and save as session, file generated is big (4.1 GB)
I reload session to find-object in Linux (CentOS) and it cause strange behaviour.
Without tcmalloc:
With tcmalloc:
Load with smaller subset data (1GB)
Note:
The text was updated successfully, but these errors were encountered: