Closed scpeters closed 3 years ago
Can we add a test for this new topic?
I'll add a test for the new system to match the other system tests, and I'll look into adding some test cases to simulation_runner_test that checks the Pose_V
messages.
I've added some test expectations to confirm that model and link Id's are unique. I'm halfway through adding a test for the new system
Can we add a test for this new topic?
I'll add a test for the new system to match the other system tests, and I'll look into adding some test cases to simulation_runner_test that checks the
Pose_V
messages.
I've added a unit test for the new system in a2a1372. The main thing missing is an integration test. I'll how hard it would be to add this
Can we add a test for this new topic?
I'll add a test for the new system to match the other system tests, and I'll look into adding some test cases to simulation_runner_test that checks the
Pose_V
messages.I've added a unit test for the new system in a2a1372. The main thing missing is an integration test. I'll how hard it would be to add this
added an integration test in 541441a
it doesn't capture the odd behavior of the vehicle with id 0
, but I'll address that in a follow-up PR
To update object pose information, the
Scene3D
plugin inign-gui2
expects a Pose_V message, whiledelphyne
currently publishes that in aModel_V
message. Instead of using link names to associate the poses to specific objects, the Pose_V message uses an id field that should be a unique integer. This pull request adds a translation fromModel_V
toPose_V
and publishes thesePose_V
messages on the/visualizer/pose_update
topic. This also required adding unique ids for each link, by using thestd::hash
of a string combining the model id and link name.