-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feature/852 simple nav gyro #227
Conversation
250e85c
to
439a35f
Compare
439a35f
to
26560ad
Compare
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.
Would we ever use omega_Dot directly from a gyro? Isn't deltaTheta and omega coming from a gyro, and then we take omega and numerically differentiate to find omegaDot? Regardless, I approve.
26560ad
to
4ebdd47
Compare
4ebdd47
to
71cbd6c
Compare
edcff57
to
b33a208
Compare
f40c9c3
to
7ed5223
Compare
7ed5223
to
e32aed2
Compare
2d42911
to
617a82e
Compare
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.
I just spotted some additional things worth considering. We could also come back later for a large module refactor.
src/simulation/navigation/simpleNav/_UnitTest/test_simpleNav.py
Outdated
Show resolved
Hide resolved
50ef508
to
321aaba
Compare
321aaba
to
126d4a4
Compare
Description
Update simple nav to write out the accelerometer packet message (containing acceleration and rate information). This change allows for a user to set a cadence of gyro measurements per time step (100 measurements per time step for instance) and set gyro biases and standard deviations
Verification
The unit test contains data to check the time output by the message (mean time for all the measurements) and the statistics on the noise
Documentation
Updated given new message
Future work
The module needs a healthy refactoring