Skip to content

Publish ground truth data to /<name>/pose instead of /<name>/pose_static #760

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

Closed
wants to merge 1 commit into from

Conversation

adlarkin
Copy link
Contributor

@adlarkin adlarkin commented Jan 19, 2021

Currently, ground truth pose data is being published to a robot's pose_static topic, which is problematic for the following reasons:

  1. This implies that the ground truth pose doesn't change (or doesn't change often, at least), which is not true for most use cases.
  2. The pose_static topic publishes at a rate of 1Hz, making the ground truth data difficult to use for real-time debugging (the pose topic publishes at a rate of 250Hz).

Resolves #659 and resolves #607.

TODO:

Signed-off-by: Ashton Larkin [email protected]

@adlarkin adlarkin requested review from nkoenig and acschang January 19, 2021 17:11
@adlarkin
Copy link
Contributor Author

Closing this because the same solution was proposed in #759

@adlarkin adlarkin closed this Jan 19, 2021
@adlarkin adlarkin deleted the adlarkin/ground_truth_nonstatic branch January 19, 2021 18:51
@osrf-jenkins
Copy link

Build finished. No test results found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ground Truth TF's slow after update Ground truth pose publishers should not publish static TFs
2 participants