This repository has been archived by the owner on Jan 13, 2025. It is now read-only.
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.
Description
This PR pulls in our Gatorade mechanism/procedure/OI/auton code into the 2024 repo, under the
com.team766.robot.gatorade
package. It also pulls in the Odometry code from 2023{-Gatorade} code, although that code currently has a dependency on the Gatorade code (specifically the Gyro mechanism). A future PR will decouple the Odometry code from specific robots to allow us to use it across robots.The PR looks like a lot of new code due to challenges using a more simple
git merge
given the existing merge history, where we only merged non-robot specific code from 2023-Gatorade into MaroonFramework (which was copied for 2024). However, it's purely a copy of the code under Gatorade's com.team766.robot plus com.team766.odometry. From there, the only changes we made are:com.team766.robot
tocom.team766.robot.gatorade
.com.team766.robot.gatorade
(temporarily).DriverStation.getAlliance()
to handle a return value ofOptional<Alliance>
(vs just anAlliance
) - one of the 2024 breaking API changes.This PR does not update
GenericRobotMain
to refer to the Gatorade robot code; we will merge this code intomain
(to allow for future CLs to pull out Swerve and Odometry code for code sharing) and then create agatorade
branch for Gatorade-specific work.We are doing this PR now to set up for Odometry, Trajectory following, and Vision development off of common code.
How Has This Been Tested?
Not tested yet. Will test on Gatorade after we are able to start using it for 2024 development (updating it to the 2024 RoboRio image, etc). We're looking to set up this code in advance to allow for developing some of the above in the 2024 repo.