Add no_std
support to orbita3d_kinematics crate
#93
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.
Thanks for your help resolving #92. As mentioned here is a PR with the work I have done to make
orbita3d_kinematics
no_std
compatible.I have made a number of changes:
PI
,TAU
, etcuse nalgebra::{ComplexField, RealField};
for methods such assin
,atan2
, etcGammasOutOfRange
error instead of returning aBox<dyn std::error:Error>
inverse.rs:145compute_valid_solution
to remove need for Vec inverse.rs:201I did some simple bench-marking to ensure I wasn't significantly impacting performance. There was improvements in inverse kinematics (-9%) and significant improvements in forward kinematics (-69%). Bench code here