More robust SDF parsing -- Patch for Release 5.0 #444
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
mxgrey
changed the title
|
👍 This fixed the issue I was having. Thanks @mxgrey! |
|
I added regression test for this. Will wait for build tests and merge if they are happy. |
jslee02
added a commit
that referenced
this pull request
Jul 11, 2015
More robust SDF parsing -- Patch for Release 5.0
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.
The SDF parser currently assumes there is at least one Joint in the model, so it fails to correctly parse a model that has no Joints (i.e. all bodies are root nodes).
This pull request fixes that issue, and should be more robust in general because it iterates through bodies instead of joints when constructing a Skeleton.