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

Record trajectory and using ov_eval with ROS2 #483

Open
diplodocuslongus opened this issue Nov 8, 2024 · 1 comment
Open

Record trajectory and using ov_eval with ROS2 #483

diplodocuslongus opened this issue Nov 8, 2024 · 1 comment
Labels
bug Something isn't working enhancement New feature or request

Comments

@diplodocuslongus
Copy link

Hi,
I've managed to save the state by following this but can't figure out how to save a trajectory to a text file in ros2.

How can one record a trajectory in ROS2, and then how to use ov_eval for performance evaluation (ATE, ...)?

Related:
https://docs.openvins.com/eval-error.html#eval-ov-transform
#347

The record.launch file in src/open_vins/ov_eval/launch/record.launch doesn't seem to have a launch.py equivalent.
The subscribe.launch.py (for ros2) file doesn't seem to fully reproduce what the ros1 subscribe.launch does, in particular there is no node name="recorder_estimate" (the subscribe.launch* files are in install/ov_msckf/share/ov_msckf/launch/ ).

Thanks for any hint you may provide!

@goldbattle goldbattle added bug Something isn't working enhancement New feature or request labels Nov 23, 2024
@goldbattle
Copy link
Member

I think the ros2 launch should be updated to match what we have for the ros1. You can try modifying it yourself. Feel free to post it here if you do get a modified version working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants