-
Notifications
You must be signed in to change notification settings - Fork 324
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
ROS 2 support #6784
Comments
Yes, ROS2 is on our roadmap: rerun/docs/content/reference/roadmap.md Lines 34 to 38 in 776e2e9
In the meantime I can refer you to https://rerun.io/docs/howto/ros2-nav-turtlebot |
following.... Specifically hoping for rosbag and/or MCAP support. Anything to load archives from ROS pub/sub. |
Hello Rerun, just wanted to start off by saying that the tool is amazing and superb for our visualization needs. I'm wondering though what exactly does Official ROS2 bridge entail? Are there more specifics that could be provided? For example, replay from rosbag2, or mcap files, subscribing directly to ros topics, publishing its own topics, tf2 support, launch file support, etc...? appreciate the feedback 😄 |
A quick update: we're working on a production grade ROS bridge in Rust over here. We're working hard to get it ready to handle more contributors within the next weeks, but we're not there yet. |
Is your feature request related to a problem? Please describe.
I am from Autoware community, which is an open sourced autonomous driving software based on ROS 2.
We use RViz and sometimes Foxglove on a daily basis, but the former one is not a modern tool and the latter one is announced to become closed.
Describe the solution you'd like
Thus, including me, developers from ROS 2 and especially Autoware community are very interested in rerun for similar visualization feature, such as runtime visualization and offline visualization from ROSBAG with seek bar UI.
Describe alternatives you've considered
As stated above, we are using RViz and Foxglove. But RViz is not the best solution for some of our usecases, and Foxglove is going to be closed-sourced.
Additional context
N/A
The text was updated successfully, but these errors were encountered: