You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Hi, I am a undergraduate and have been using trying to run kimera vio ros along with intel d435i.
I am able to run the easy v101 rosbag with no issues with this kimera vio ros installation.
I have managed to get it to build and successfully run, but then receive a laggy output when it comes to textured mesh.
Besides on that, I have also tried to calibrate the cameras using Kalibr, but have no changes in the performance yet.
Can I get your insight as to what might be the problem? I have highlighted some console output I have that might be significant, but I am not sure that might the problem.
The main issue is that the output freezes every now and then, and the console for kimera_vio_ros_realsense_IR.launch switches between 2 states, as shown below in the console output. It will freeze in state1 and then switch to state 2 briefly, then starts to move for a while.
The files that I have changed are basically rs_camera.launch, kimera_vio_ros_realsense_IR.launch and kimera_vio_realsense.rviz, as well as nodelet.launch.xml. The major changes are:
Hi, I did a rostopic echo camera/imu and found out the imu messages from the d435i camera freezes from time to time. So to rectify that, I lowered the fps for gyro and accel in rs_camera.launch to 200 and 63 fps, the fixed fps rate found out using rs-enumerate-devices. Based on that, I now no longer get freezing output.
I would now just like to verify if the output I am getting now if its correct? Because the representation I am getting is quite different from playing back a rosbag file.
Description:
Hi, I am a undergraduate and have been using trying to run kimera vio ros along with intel d435i.
I am able to run the easy v101 rosbag with no issues with this kimera vio ros installation.
I have managed to get it to build and successfully run, but then receive a laggy output when it comes to textured mesh.
Besides on that, I have also tried to calibrate the cameras using Kalibr, but have no changes in the performance yet.
Can I get your insight as to what might be the problem? I have highlighted some console output I have that might be significant, but I am not sure that might the problem.
The main issue is that the output freezes every now and then, and the console for kimera_vio_ros_realsense_IR.launch switches between 2 states, as shown below in the console output. It will freeze in state1 and then switch to state 2 briefly, then starts to move for a while.
Links:
I have included a youtube link here of a demo of the output i am getting: https://youtu.be/uvWD0-YqHjs
Here is a link to the entire screen log of the output for kimera_vio_ros_realsense_IR.launch: https://drive.google.com/file/d/1jWju043nz0kkA6HzRJssPfWc4cyy-sQr/view?usp=sharing
Here is a link to the screen log for rs_camera.launch:
https://drive.google.com/file/d/1tdibWVNbaBJAoIymEm2dci-RENHXnqN6/view?usp=sharing
The files that I have changed are basically rs_camera.launch, kimera_vio_ros_realsense_IR.launch and kimera_vio_realsense.rviz, as well as nodelet.launch.xml. The major changes are:
Command:
Console output:
Additional files:
Please attach all the files needed to reproduce the error.
changed files.zip
Please give also the following information:
*KimeraVioRos:afeb7ec80945da0c8ed6a7edea4f6f5ecd644743
Merge pull request Remove pragma once in .cpp files #101 from MIT-SPARK/fix/pragmas
*opencv3_catkin: 880da1510aa80a247b80adca32ac2941ddfa94ff
Merge pull request Use camera_info rather than hardcoded param files. #27 from ethz-asl/fix/unordered_map_flag_rename
The text was updated successfully, but these errors were encountered: