-
Notifications
You must be signed in to change notification settings - Fork 37
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
Drop inefficient functions for rotation? #86
Comments
julia> using Quaternions
julia> angle(1+im)
0.7853981633974483
julia> angle(Quaternion(1+im)) # This issue is related to https://github.com/JuliaGeometry/Quaternions.jl/issues/62
1.5707963267948966
julia> angle(-1)
3.141592653589793
julia> angle(Quaternion(-1,0,0,0)) # This issue is not related to complex-quaternion compatibility
6.283185307179586
julia> -1 == Quaternion(-1,0,0,0)
true x-ref: #62 |
I wonder if someone doesn't need that high performance with Rotations.jl but wants to avoid heavy load time with StaticArrays.jl. I'm planning to remove the functions after adding deprecated messages, but if you want that functionality, feel free to comment on this issue. We can consider reverting them later. |
I think removing these would be fine. I'm okay with |
The following functions return
Array
which is less efficient thanStaticArrays.StaticArray
.rotationmatrix
rotationmatrix_normalized
axis
These can be replaced with efficient functions in
Rotations.jl
package. Adding warning messages to replace these functions withRotations.jl
package, and removing them in the next breaking release would be better, I guess.Both
Quaternions.jl
andRotations.jl
packages are maintained under JuliaGeometry organization, so I think this change will not be problematic.The text was updated successfully, but these errors were encountered: