-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: json algebra reading #1081
fix: json algebra reading #1081
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1081 +/- ##
=======================================
Coverage 48.64% 48.64%
=======================================
Files 341 341
Lines 17489 17489
Branches 8256 8256
=======================================
Hits 8507 8507
Misses 3208 3208
Partials 5774 5774 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good ! Is the reason for this that Eigen Affine transform apply the translation first followed by the rotation ?
I don't think Eigen Affine transforms to anything special here. I think this is related to the code changed here using |
I am not sure I follow your point here, |
Exactly. But Eigen does not apply translation and rotation separately I don't think. |
I probably didn't express myself properly. What I meant is that the Transform3 type we use is equal to Translation x Rotation x Scaling. So if you want to build it with translate and rotate, translate need to go first; but if you want to use pretranslate and prerotate, prerotate need to go first. I think we agree and at that point it is just miscommunication :) |
Change the order of translation / rotation when reading transforms back from
json
.This is necessary that the transforms are correctly re-created.