-
Notifications
You must be signed in to change notification settings - Fork 791
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
ORB_SLAM3::Tracking::Tracking no matching function call when building RTABMap #886
Comments
Accidentally closed the issue, sorry! To bypass this error, I am using ORB-SLAM3 v0.4-beta for now, and it builds and works just fine. Support for ORB-SLAM3 v1.0-release needs to be implemented. |
Stick to https://github.com/UZ-SLAMLab/ORB_SLAM3/releases/tag/v0.4-beta with this patch https://gist.github.com/matlabbe/f5cb281304a1305b2824a6ce19792e13 for now. They did a lot of API breaking changes between v0.4 and v1.0. Would need to take 1 day or two to make it work with v1.0. |
Is there any update about ORB-SLAM3 v1.0 integrating with rtabmap in IMU_RGBD mode? |
@matlabbe |
I created a pull request here till I have more time to debug. There are some issues when enabling IMU... that seems more related to ORB_SLAM3. |
I am trying to build RTABMap (from the noetic-devel branch, and also the latest) with ORB_SLAM3 support on Ubuntu 20. It seems that there is a mismatch at this point between
/rtabmap/corelib/src/odometry/OdometryORBSLAM.cpp
andORB_SLAM3/include/Tracking.h
.I build RTABMap with the following cmake options:
cmake .. -DWITH_G2O=OFF -DWITH_QT=OFF -DWITH_ORB_SLAM=ON
, and here is the output:While running
make
, I get the following errors inOdometryORBSLAM.cpp
:and some more. I can add the whole log if it helps. But one of the issues as I see it is that the constructor in
ORB_SLAM3/include/Tracking.h
,line 61
:has the additional
Settings* settings
argument which is not taken care of by the call inOdometryORBSLAM.cpp
,line 60
:Tracking(pSys, pVoc, pFrameDrawer, pMapDrawer, pMap, pKFDB, strSettingPath, sensor)
Any advice on how I could resolve this?
The text was updated successfully, but these errors were encountered: