Skip to content
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

svo node not publishing any results using stereo+imu camera #45

Open
david-delmoral opened this issue Mar 10, 2023 · 4 comments
Open

svo node not publishing any results using stereo+imu camera #45

david-delmoral opened this issue Mar 10, 2023 · 4 comments

Comments

@david-delmoral
Copy link

I am attempting svo with a realsense t265, but when I launch the node with a launch file similar to the fla_stere_imu.launch, Rviz opens up but nothing is displayed, there is no error message, although the svo node in not publishing data in any of the topics.

The step I've followed are:

  • Since the camera publishes the IMU data segregated on different topics, I have made a python node that mixes them in a single IMU message.
  • In the launch file, I set the camera topics to the ones published by the t265, and the IMU topic to the one published by the python node.
  • For the calibration file I used the format of the fla_stereo_imu.yaml introducing the distortion values and intrinsics published by the t265 at /camera/fisheye1/camera_info and /camera/fisheye2/camera_info.
  • For the parameter file I used the same as in fla_stere_imu.launch
  • I have tried both running from a bag file with the three topics recorded, and running the camera node live and in either case I get the same result.
    In rqt I get the following chart:
    image
    where you can see that the svo node is subscribed to the camera and IMU topics, but none of the topics between svo and vis contain any data.
    I don't know if I have missed any steps needed to use svo with a custom stereo + imu camera.
    Thank you for the help
@zauberflote1
Copy link

@david-delmoral Did you find a solution?

@david-delmoral
Copy link
Author

@david-delmoral Did you find a solution?

No. I ended up using other algorithms for my proyect bc I couldn't get svo working

@MauUnterKarottenbaum
Copy link

same... waiting for further tips

@aatb-ch
Copy link

aatb-ch commented Mar 11, 2024

i also stumbled upon the same issue, running fine in mono but no results in stereo, the stereoCallback in svo_interface expects exact timestamps for both camera streams, if you switch the sync policy from ExactTime to ApproximateTime it works fine. My camera (oak-d pro w) outputs slightly different timestamps for both streams so no result was published, as soon as I switched to ApproximateTime and recompiled it started working fine.

typedef message_filters::sync_policies::ExactTime<sensor_msgs::Image, sensor_msgs::Image> ExactPolicy;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants