Fixed initialization of position and velocity #621
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
|
👍 |
jslee02
added a commit
that referenced
this pull request
Feb 23, 2016
Fixed initialization of position and velocity
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 position and velocity of freshly-constructed
Joints was being set to zero instead of, respectively,mInitialPositionandmInitialVelocity. These values would only be applied if the user manually callsresetPosition()andresetVelocity().This pull request modifies the
SingleDofJointandMultiDofJointconstructors to use the correct values for initialization. I believe all other joints (exceptWeldJoint, which has no DOFs) inherit from these base classes, so we don't need to make any other changes.