Fix for relative frame errors (lunar-devel) #663
Merged
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.
{ port of pull request #605 }
I noticed a lot of errors when using relative reference frames in Gazebo. When spawning the object, wrong multiplication order of quaternions is applied (as per here). The operation q1 *= q2 results in q1 = q1 * q2, but we wish to have q1 = q2 * q1, since we apply rotation to q1.
When obtaining the relative pose of the object w.r.t. to a frame, I noticed strange and inconsistent transformations. I used the reference for chaining transformations defined here to make the transformations cleaner.
Also, instead of using the relative entity, in the whole code the entity is transformed to a link, which does not allow for specifying a model as a relative entity.