I know there are probably a lot of threads out right now about preparing for build season technical/design-wise, but I’m looking for a way to prepare on a more programming aspect of things. Are there any teams that people look at, libraries that people recommend or anything in general people want to share on this topic?
You should be reviewing New for 2023 — FIRST Robotics Competition documentation if you haven’t already done so.
2 Likes
Our controls team is focused on a few things:
- Training new-ish students. We had some join late this year and are picking up as much as they can.
- Filling gaps in knowledge: Dialing in trajectory / path planning abilities for the swerve drivebase we made this off-season.
- Trying out some new sensors and adding publicly available code for them.
- Keeping tabs on PhotonVision AprilTags support
2 Likes
A few things you should be doing:
-
Get a template code base setup for 2023 that has all your drive base setup and is ready to be upgraded when 2023 wpilib comes out.
-
Have a plan for your auton tooling. You need to get this started as soon as you can, dedicate someine to it if you can.
-
Figure out vision. Next year you can either use the usual tape or AprilTags. You should have hardware on hand asap.
-
Get base mechanism code down. Write code for an elevator and arm assuming you already have shooter code.
-
Get some sleep! Delegate! Train!
5.1. Really focusing in setting clear boundaries for who’s doing what, when things should be done so you don’t burn yourself out. If you’re a small programming team, steal from the best, invent the rest.
2 Likes
Spend time preparing your DevOps plan. That is how students will work with requirements, repositories, tests, integration, and deployment.
2 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.