dae should use Y_UP for clean collision in ompl #298
Merged
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
toliver
added a commit
that referenced
this pull request
Jun 4, 2015
dae should use Y_UP for clean collision in ompl
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.
From @guihomework:
Be careful, if you use
the new file for collision too, OMPL might have issues (similar to #144)
DAE collision model should have the option 'up_axis Y_UP' because OMPL
reads this tag when rviz/gazebo do not (so mode render correctly).
Blender uses by default Z_UP in DAE exports which turns the colliding
model 90 degree in OMPL and collides with the environment while planning
although the display in RVIZ is OK