Open TouchDeeper opened 3 years ago
This error is independent of TF, it is coming from the camera _info topics. The camera projection matrix for the right camera_info should have P(0,3) negative. Can you show the camera_info of the left and right cameras?
@matlabbe Thank you for your reply.
The camera_info of left_infra is:
header:
seq: 867
stamp:
secs: 1608946479
nsecs: 473160331
frame_id: "camera_infra1_optical_frame"
height: 480
width: 640
distortion_model: "plumb_bob"
D: [0.0, 0.0, 0.0, 0.0, 0.0]
K: [383.15728759765625, 0.0, 319.8735046386719, 0.0, 383.15728759765625, 241.6318359375, 0.0, 0.0, 1.0]
R: [1.0, 0.0, 0.0, 0.0, 1.0, 0.0, 0.0, 0.0, 1.0]
P: [383.15728759765625, 0.0, 319.8735046386719, 0.0, 0.0, 383.15728759765625, 241.6318359375, 0.0, 0.0, 0.0, 1.0, 0.0]
binning_x: 0
binning_y: 0
roi:
x_offset: 0
y_offset: 0
height: 0
width: 0
do_rectify: False
the camera_info of right_infra is:
header:
seq: 1473
stamp:
secs: 1608946499
nsecs: 644384161
frame_id: "camera_infra2_optical_frame"
height: 480
width: 640
distortion_model: "plumb_bob"
D: [0.0, 0.0, 0.0, 0.0, 0.0]
K: [383.15728759765625, 0.0, 319.8735046386719, 0.0, 383.15728759765625, 241.6318359375, 0.0, 0.0, 1.0]
R: [1.0, 0.0, 0.0, 0.0, 1.0, 0.0, 0.0, 0.0, 1.0]
P: [383.15728759765625, 0.0, 319.8735046386719, 19.151988983154297, 0.0, 383.15728759765625, 241.6318359375, 0.0, 0.0, 0.0, 1.0, 0.0]
binning_x: 0
binning_y: 0
roi:
x_offset: 0
y_offset: 0
height: 0
width: 0
do_rectify: False
19.151988983154297 should be -19.151988983154297
@matlabbe Thank you for your reply. But it is not convenient to modify the camera_info, this should be caused by realsense's firmware, and other people will also encounter this problem. What's more, I think the positive 19.151988983154297 makes sense in the frame convention of my realsense d435i. Could you please provide some advice to modify rtabmap to adapt to this situation?
@matlabbe please help~, someone encountered the same problem as me, here is the issue.
Hi, Mathieu
I used the
test_d435i_vio.launch
to run vins-fusion supported rtabmap. An error occured:[ERROR] [1608127730.914892966]: The stereo baseline (-0.049985) should be positive (baseline=-Tx/fx). We assume a horizontal left/right stereo setup where the Tx (or P(0,3)) is negative in the right camera info msg.
I find the
realsense_stereo_imu_config.yaml
in VINS-FUSION has a different frame convention with my realsense d435i, the default frame convention ofrealsense_stereo_imu_config.yaml
is: The frame convention of my realsense d435i is below: you can note that the body frame convention is different with the config in VINS-FUSION. I can run VINS-FUSION well with my config calibrated by Kalibr. Then I use my config to runtest_d435i_vio.launch
, but errors about stereo baseline occur. My configrealsense_stereo_imu_config_me.yaml
is (omit the same content with the default config):The
test_d435i_vio.launch
is the same as yours except I use my own configrealsense_stereo_imu_config_me.yaml
Could you please provide some advice? Thank you a lot! The output information of
test_d435i_vio.launch
is below: