hi guys
just a quick question. is the fusion with the imu “enabled” yet? in the past there was some talk to enable it and not just as a fallback.
If so, is there anyway to check if it is working?
Thank you
hi guys
just a quick question. is the fusion with the imu “enabled” yet? in the past there was some talk to enable it and not just as a fallback.
If so, is there anyway to check if it is working?
Thank you
Thank you for your message. Let me address all of your questions:
Visual Inertial Odometry is currently enabled only for a single stereo camera at this time.
We have a special input parameter called debug_imu_mode to verify the correct orientation of the axes of the IMU.
This mode is specifically designed for validating the direction of the IMU axes. When in this mode, CUVSLAM will continue to receive all information, but the translation component will be forcibly disabled. The expected behavior is that the rotation of the IMU (as part of a stereo camera) should have a similar direction in the real world as in the visualization system (rviz or Foxglove). Here are a few comments about IMU_fusion:
does one of the published topics offer the path without the odometry correction?
or what is the difference between the published path topics?
The cuvslam library uses different solvers for visual odometry (stereo images only) and inertial visual odometry (stereo images + IMU measurements)
are these open source?
No, the cuVSLAM library is not open-source, but for commercial support and access to source code, please contact NVIDIA
Hi, can you provide more information about commercial support and how to get access to the source code?
Welcome to the Isaac ROS forum. As I mentioned in my previous post, I suggest following the link above or: contact NVIDIA
Hi Raffaello,
That link seems to be a general newsletter, not a form to initiate discussion for accessing the source code. What contact would be a good start for this?