-
Notifications
You must be signed in to change notification settings - Fork 27
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
Convert DDS rosbag to iceoryx #13
Comments
Ok, i am not even able to record anything via
|
yes, the rmw_iceoryx currently lacks a proper interface to serialize messages: https://github.com/ros2/rmw_iceoryx/blob/master/rmw_iceoryx_cpp/src/rmw_serialize.cpp Thanks for opening this ticket though. I hope to get some time to get that serialization done in the next few days. |
'Introspection_ara_msgs' are our built-in topics in iceoryx. For these we have no ROS messages. Does a bag record want to measure all the topics that are listed with ros2 topic list? Does this make sense? |
... or make them available as ROS2 messages? Or are they really, really special, so they can not be represented in the OMG IDL? |
Exactly! They are needed mainly to get the iceoryx internals in the rmw. So we suppress them for now (commit is already on a branch) ROS messages would be cool in future. Then you could have the information like memory pool usage also via ROS tooling. We will check if we can describe them with the ROS IDL. They use some of our special fixed size containers, so maybe this will not be straight forward |
@blackliner any chance you could give #15 a shot? With the latest rosbag2 master, you should be able to record rosbags with iceoryx. |
ROS2 eloquentI tried all of that with the eloquent based package release from Ubuntu 18.04, i will try foxy from master later. Of course. ✔️ Record by topic nameRecording with a named topic (in this case bash outputfberchtold@FB-UBUNTU:~/drvline$ RMW_IMPLEMENTATION=rmw_iceoryx_cpp ros2 bag record /bool_test
2020-03-27 12:02:04.286 [ Debug ]: Application registered management segment 0x7ff86e321000 with size 201703392 to id 12020-03-27 12:02:04.287 [ Info ]: Application registered payload segment 0x7ff84a934000 with size 595259200 to id 2
[INFO] [rosbag2_storage]: Opened database 'rosbag2_2020_03_27-12_02_04/rosbag2_2020_03_27-12_02_04_0.db3' for READ_WRITE.
2020-03-27 12:02:04.305 [Warning]: Cache size for subscribe too large 1000, limiting to MAX_RECEIVER_QUEUE_CAPACITY = 256
[INFO] [rosbag2_transport]: Listening for topics...
[INFO] [rosbag2_transport]: Subscribed to topic '/bool_test'
[INFO] [rosbag2_transport]: All requested topics are subscribed. Stopping discovery...
^C[INFO] [rclcpp]: signal_handler(signal_value=2)
fberchtold@FB-UBUNTU:~/drvline$ RMW_IMPLEMENTATION=rmw_iceoryx_cpp ros2 bag info
Files: rosbag2_2020_03_27-12_02_04/rosbag2_2020_03_27-12_02_04_0.db3
Bag size: 16.5 KiB
Storage id: sqlite3
Duration: 8.0s
Start: Mar 27 2020 12:02:04.968 (1585306924.968)
End Mar 27 2020 12:02:12.969 (1585306932.969)
Messages: 9
Topic information: Topic: /bool_test | Type: std_msgs/msg/Bool | Count: 9 | Serialization Format: shared_memory ❌ Record all topics via
|
Thanks for the reports here. I think you assest the situation currently in that As for the the missing functions, you've seen that #18 will add these and you shouldn't see these warnings any further. |
Hi, i have some rosbags which were recorded with the default ROS2 rmw (fast_RTPS) and i would like to do a performance comparison between different other rmw choices. Iceoryx sounds awesome, but i am not able to replay those rosbags. Is there something i missed? Do i need to build ROS2 together with iceoryx and rmw_iceoryx with some special env-variables set?
Cheers
The text was updated successfully, but these errors were encountered: