You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on @brendanburkhart pull request, we should use modern C++ to automatically determine how to convert the header part of cisst and ROS data types. In general, cisst potentially has:
timestamp
valid flag
reference frame
moving frame
ROS potentially has:
header/timestamp
header/frame_id
child_id
Since the conversion for these fields can be performed automatically, it should be done outside mtsROSToCISST and mtsCISSTToROS. Note that the mtsCISSTToROS should return a boolean based or the value of IsValid or absence of method IsValid. Once implemented, this approach should be ported to the ROS 2 bridge.
The text was updated successfully, but these errors were encountered:
* mtsROSToCISST: created separate conversion method to handle the cisst and ROS headers automatically at compilation time (issue #18)
* mtsROSToCISST header: added case for child_frame_id to MovingFrame
* mtsCISSTToROS: updated for #18, compile time choice for header conversion
Based on @brendanburkhart pull request, we should use modern C++ to automatically determine how to convert the header part of cisst and ROS data types. In general, cisst potentially has:
ROS potentially has:
Since the conversion for these fields can be performed automatically, it should be done outside
mtsROSToCISST
andmtsCISSTToROS
. Note that themtsCISSTToROS
should return a boolean based or the value ofIsValid
or absence of methodIsValid
. Once implemented, this approach should be ported to the ROS 2 bridge.The text was updated successfully, but these errors were encountered: