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
[RST-2340] Add serialization support to fuse #98
Conversation
if (graph_publisher_.getNumSubscribers() > 0) | ||
{ | ||
fuse_msgs::SerializedGraph msg; | ||
msg.header.stamp = stamp; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you also set msg.header.frame_id = "map";
? (same below for the transaction)
I don't know if it's possible to retrieve the frame of the graph / transaction somehow from their classes. If they don't have that field, I think for now this should be fine, or a ROS param to set the frame.
This is important to visualize the graph in rviz
, for example.
All commits in this PR have been reviewed independently. Merging. |
This PR adds serialization to the API of the Variable, Constraint, Graph, and Transaction classes. Support for additional class types can be added as needed.
Additionally, a ROS msgs have been added to transport serialized Graph and Transaction objects using standard ROS comms mechanisms. To demonstrate this ability, a fuse Publisher was created to serialize and publish the updated graph, and a stand alone utility, fuse_echo, was created to subscribe, deserialize, and print the graph.
All commits in this PR have been reviewed independently.