-
Notifications
You must be signed in to change notification settings - Fork 24
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
Mesh not loaded correctly (ObjectRecognizer crashes) #11
Comments
hi, I fixed this in trunk, is there any way you can try using the sources ? |
Yes, I could test with the source, but where did you fix it (i.e. what code should I pull)? (I couldn't see any recent commit in the master branch). |
I fixed your original problem but I also added a mandatory build of Assimp3 (with an updated version), please let me know how that goes. |
I've just tested it and it works well. Loads the mesh from DB and recognizes the object. |
I can confirm I get detections with tabletop now! |
As this was fixed, closing. |
As discussed in https://groups.google.com/forum/#!topic/object-recognition-kitchen/ijpfJdG9q8E
The ObjectRecognizer.cpp tries to read a mesh called "original" from the DB, but the default way to generate a mesh (i.e. rosrun object_recognition_reconstruction mesh_object --all --commit) doesn't generate a file with such a name.
I modified it to get a bit further. See the following commit.
shadow-robot@2c149db
Then I get the following output. The file is correctly read from the DB, and parsed using the assimp library (aiImportFile()) but for some reason it crashes in line 176 of ObjectRecognizer.cpp (in my modified version) when trying to access the number of indices of the first face of the mesh (face.mNumIndices). This seems to point to a bug in the mesh generator, or a bug in the assimp library. Any ideas?
The text was updated successfully, but these errors were encountered: