Skip to content
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

When setting a 2D Pose Estimate, RViz incorrectly logs "Setting goal" #417

Closed
rotu opened this issue Jun 19, 2019 · 4 comments · Fixed by #427
Closed

When setting a 2D Pose Estimate, RViz incorrectly logs "Setting goal" #417

rotu opened this issue Jun 19, 2019 · 4 comments · Fixed by #427

Comments

@rotu
Copy link
Contributor

rotu commented Jun 19, 2019

When setting a 2D Pose Estimate, RViz incorrectly logs "Setting goal".
Below is the log output from setting a 2D Pose Estimate then setting a 2D Nav Goal:

[INFO] [rviz2]: Setting goal: Frame:map, Position(1.30849, -2.7475, 0), Orientation(0, 0, 0.624316, 0.781172) = Angle: 1.34851
[INFO] [rviz2]: Setting goal: Frame:map, Position(-2.8186, 2.15941, 0), Orientation(0, 0, 0.555852, 0.831281) = Angle: 1.17878
@testkit
Copy link

testkit commented Jul 3, 2019

This is a blocker issue for navigation, see ros-navigation/navigation2#905 and ros-navigation/navigation2#901.

@rotu
Copy link
Contributor Author

rotu commented Jul 3, 2019

This is a blocker issue for navigation

I don't think this issue should block you. Despite that the log says "setting goal", it still publishes an initial pose that I have successfully used in AMCL to seed localization.

@testkit
Copy link

testkit commented Jul 3, 2019

Yeah, I probably should say "the rviz2 no responding issue" is a blocker issue which we met in both ros-navigation/navigation2#905 and ros-navigation/navigation2#901.

@Martin-Idel
Copy link
Contributor

But that's a different issue. This issue is about the fact that the log message for the 2d pose estimate is wrong. That's true but it definitely doesn't affect any publishing of the goal itself.

You should probably open a different issue for each potential bug for tracking purposes.

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 a pull request may close this issue.

3 participants