Change gyros to have a getRotation3d() and getAccel() methods #44
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.
I feel like creating the Rotation3d at the gyro level instead of the SwerveDrive level could make more sense. I've also added a getAccel() method (even though we're not using that for pose estimation anymore) which creates a Translation3d at the gyro level, so it might also be better for the Rotation3d to be there too.
I have the array filler still there, but we could also remove it in this PR. Thoughts?