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 vec2vec #334
Fix vec2vec #334
Conversation
Fix to follow immediately :-)
This should fix this. No other side effects, as far as I could tell.
rot_back = np.dot(Rp, v) | ||
sign_reverser = np.sign((np.sign(rot_back) == np.sign(u)) - 0.5).squeeze() | ||
|
||
# Multiply each line by it's reverser and reassmble the matrix: |
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.
# Multiply each line by its reverser and reassemble the matrix:
(sorry)
# Everything's fine, up to a sign reversal: | ||
rot_back = np.dot(Rp, v) | ||
sign_reverser = np.sign((np.sign(rot_back) == np.sign(u)) - 0.5).squeeze() | ||
# Multiply each line by it's reverser and reassmble the matrix: |
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.
typo
Thank you for the bug fix. Please fix this tiny typo and I will happily do the merge :) |
Done! On Sun, Mar 16, 2014 at 4:50 PM, Eleftherios Garyfallidis <
|
This fixes a small bug in the calculation of rotation matrices.
The fix in the sims module follows, because test failures upon applying this fix indicated that this calculation was front-to-back. I think everything's alright now