You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 6, 2024. It is now read-only.
Now that the subsystems are hooked into the scheduler (new base class implementation), these methods will get called. Currently just making updates to driveOdometry object - but should make sure we understand any side effect and handle them as necessary.
The text was updated successfully, but these errors were encountered:
Making updates to the driveOdometry during the periodic cycle is actually what we want to make trajectories work properly. This may have been at the root cause of our earlier trajectory issues. I don't really see a point in doing odometry updates in another method.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Now that the subsystems are hooked into the scheduler (new base class implementation), these methods will get called. Currently just making updates to driveOdometry object - but should make sure we understand any side effect and handle them as necessary.
The text was updated successfully, but these errors were encountered: