Donate Now!
Creating a Feature List
Allows us to plan our codebase structure and modify it as our feature demands change
Mapping out buttons and required subsystem code changes
Template a code base, getting a head start in programming
“Pseudocoded” the robot
Worked together in groups to write the code setting aside syntax
WPILib VSCode
Software libraries + code editor
Pathplanner
Autonomous path creation
AdvantageScope
Simulation testing
GitHub
Version control
Separate groups are responsible for handling different parts of the robot’s code.
Subsystems (Lead: Vignesh)
Creates subsystems layers, i.e., code that directly manipulates the hardware (motors, LEDS, distance sensors)
Vision (Lead: Pranav)
Robot position estimation using cameras
Object detection
Drivers and Auto (Lead: Chinmay)
Creates autonomous paths
Creates commands (scoring algae, setting elevator height, etc.)
We use different software to test our code
Advantage Scope
Allows us to simulate our robot with the game map which helps us test commands and autons
Creating a Bug list
Helps the team stay organized and on track of all current issues in the code
Creating videos of commands and autons working in simulation
For everyone on the team to learn more about our code and our autos
Allows us to fine tune the performance of mechanisms to fit our exact needs
Increment and decrement tunable values to achieve our ideal state
Thoroughly test the physical robot for any bugs, and run all mechanisms to ensure no faulty code
Work in parallel to get physical systems working and all bugs fixed
