Individual Afterthoughts

Will:

• We still do not master networking since we had a lot of problems both on Orloge and Blitz. Need to get even more expertise
• We need to solve the Blitz communications sometimes getting buggy (A button not working, slow foxglove, etc.). We currently fix this via a reboot
• Optimizing time on track is now super important. In 10 minutes, we need to be able to flawlessly run a mapping and a base raceline. We sometimes wasted some track time by debugging stuff or network issues
• Orloge still need a couple of mechanical design iterations for battery placement, rear wing fixing, VESC cable not interfering with battery and protecting gears (Differential gear, motor pinion and spur gear)
• Too much time lost on the raceline GUI. With a 10 minute practice, we should be able to spin up a raceline without the need of the GUI.
• To get the most out of a practice session, we should have a CLEAR deployment protocol. Each person should have a well defined role and we should practice our communication (If the track is big, we can't hear each other so we need either signs or phones with earbuds)

Nico:

• We need to update the deployment checklist to include stuff like an android phone with sim card.
• We need to finish new stack integration and stabilize it.
• We need to finish f1tenth_gym_ros integration.
• We should be able to run the robots with and without a visual interface like foxglove, vscode and rqt_reconfigure. (Relocalize, edit parameters, browse files...)
• We should buy actual radios to communicate. Phones and earbuds still depend on internet connection.
• We need to spend time deploying the robots regularly.
• We need to think about how to simply manage surface changes and ramp.
• We need to work in f1tenth-gym with hard maps to understand loop closure parameters.

Mohamed:

Jayson:

Alissa:

Pierre-Luc:

• We should make it clear when the vroom_restart command fails, currently some failiures happen silently in the screens.
• We should debug and improve the f1tenth_gui interface since it is hard to use and learn.
• The wait time required after using vroom_restart is ambiguous, we should make it so the command returns only after its job is done.

Oli: