looking at the current implementation for pose data type it seems like it's being processed as a joint_state data type instead of a 6dof pose as stated in README:
- pose
Data: Float32Array (7 values: [x, y, z, qx, qy, qz, qw])
Required metadata: { "primitive": "pose" }
Is this the correct behavior?
looking at the current implementation for
posedata type it seems like it's being processed as ajoint_statedata type instead of a 6dof pose as stated in README:Is this the correct behavior?