Fabrice noreils

I used Kalibr to calibrate the camera and this time I got the following message: ``` I0928 09:33:04.050410 5641 KimeraVioRos.cpp:58] Destroy Ros Display. I0928 09:33:04.050428 5641 KimeraVioRos.cpp:62] Creating Ros Display....

@ToniRV Thank you for your message Actually I tried many calibrations and I used this one those values are quite close to the values provided by infra1/infra2/camera_info (I assume that...

@pherbers thanks for the information, I managed to display the meshes as well and I need to changed to background color as well (the meshes are displayed in white) Fabrice

Here is an update: I found some issues in utilsRos.cpp `cam_params->distortion_model_ = cam_info->distortion_model;` There is an error because one wants to assign a string to an enum. However when I...

@khumanhan for me kimera-VIO is working at least with the rosbag provided for tests - I am working on plugin my ZED2 for real tests now. To resume: - I...

@khumanhan I had the same result - I did not see the trajectory but actually I was not looking for it... Regarding the display of the meshes, have a look...

@tftangming with the ZED2, actually not yet because the missing calibration data is `imu_time_shift` and to get it, I need to do a calibration and thus generate a rosbag. But...

@zinuok Did you manage to make it working? With ` autoInitialize` set to 1 there is no more `Requested initialization from Ground-Truth pose ` but there is still a problem...

@Jaeyoung-Lim Following @mzahana if we consider that the drone is equipped with a camera, it will be great to include the yaw and yaw velocity in the flattargetCallback and thus...

@mzahana thank you I will have a look @Jaeyoung-Lim yes you are right, but I was thinking it may be interesting to limit the rate to avoid slam issues (camera...