-
Notifications
You must be signed in to change notification settings - Fork 279
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
reconstruction error with an external feature detector #62
Comments
I am traveling this week so I will investigate this next week when I return to the office |
Actually I see the error immediately: E0222 16:06:51.872550 29987 solver.cc:484] Terminating: Can't use SPARSE_NORMAL_CHOLESKY with SUITESPARSE because SuiteSparse was not enabled when Ceres was built. You need to rebuild Ceres with SuiteSparse |
tried that but I get the same error. Do I need CXSparse? |
Did you run make install in Ceres after adding suite sparse? Then you will On Wed, Feb 24, 2016, 12:23 PM Edgar Riba notifications@github.com wrote:
|
Did you resolve the Ceres dependency? If so, could we please close this issue? |
I didn't. I compiled Ceres with Suitespare flag ON (even tried with cxspare and eigensparse), removed old Ceres and Theia from system and installed again but still getting the same log error with GLOBAL pipeline. |
If it is still saying Ceres was not built with SuiteSparse then something is wrong with your Ceres installation still. When you build Ceres I would make sure in the CMake step that it is indeed using SuiteSparse. Perhaps you should contact the Ceres authors to receive direct help? |
yes, it's weird. I have used Ceres before and I haven't had such error. thanks! |
Hi @sweeneychris,
I'm trying to reconstruct a scene (fountain) with Theia using an external feature detector (AKAZE from OpenCV) but I haven't succeed with that. You can find the source code that I'm using here with the error log which is a slightly modification of the sample you provide in here. I'm looking forward to hear any tip or fix. Thanks in advance!
The text was updated successfully, but these errors were encountered: