Improve magnetic anomaly calculation and refactor navigation data structures#71
Merged
Conversation
…raits for Vec<f64> and DVector<f64>
… improved navigation data handling
…ty and consistency
…ization and explicit IMUData struct
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Update the magnetic anomaly calculation to return
NANinstead of0.0to avoid warnings. Refactor theIMUDataandStrapdownStatestructures, implementingFrom/Intotraits forVec<f64>andDVector<f64>. Introduce theNEDCovariancestruct and enhance conversions inNavigationResultfor better navigation data handling. Refactor UKF initialization and testing parameters for improved clarity and consistency, and update documentation examples forStrapdownState.Fixes #56, #55, #45, #66, #24