use robot_localization instead of graft #56
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
in Indigo, there are several problems, for example
the 1st bug is probably fixed in Melodic. |
k-okada
added a commit
to jsk-ros-pkg/jsk_robot
that referenced
this pull request
Oct 27, 2019
fix fetch robot localization and navigation (graft vs robot_localization is still under discussion; ZebraDevs/fetch_robots#56 )
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Switch from
grafttorobot_localizationgraftis no more maintained.(see ros-perception/graft#29)
we are now testing on our fetch robot with Indigo.
we cannot test it on melodic because we don't have melodic fetch and any plan to update our fetch to melodic.
related: jsk-ros-pkg/jsk_robot#1147