Changes between Version 5 and Version 6 of Playbook/Events/PreparingForDistrictLevelCompetitions

Timestamp:

Feb 23, 2018, 4:52:45 PM (7 years ago)

Author:

Timothy Lin

Comment:

--

Playbook/Events/PreparingForDistrictLevelCompetitions

@@ -72 +72 @@
   * coprocessors (e.g. Raspberry PI's) and code/images/SD cards
   * robot radios
-  * 
+  * etc.
 
 * laptops
-* connectors
+* connectors (ethernet, USB, etc.)
 
 == !Loading/Transportation
@@ -132 +132 @@
 
 '''Prepare for Queue:''' There should be a '''checklist''' of mandatory items to verify before the robot goes to queue.
+  {{{#!div style="border:1pt dotted; color:orange"
+  Qualities of a Good Checklist
+    * detailed and precise enough that someone else could take over if needed
+    * broken up into individual tests of specific things
+      * don't say "check all connections", but "tighten bolts on arm-shooter connection"
+    * not be cumbersome; each item should be intuitive
+  }}}
+  When you carry out the checklist, there should be at least 2 people. One person reads off each item from the checklist; the other actually performs each check. Ideally, a third person can double check each item's completion.
+
+'''Play the Match:''' Go watch! (Or watch from the pit)
+
+'''Debrief/Evaluation:''' Some will need to discuss how the game went and evaluate next steps, others should begin inspecting robot.
+  Go through the checklist again. Then, also do cursory examinations on the robot to make sure everything else is okay too.
+
+  The debrief should primarily involve key decision makers, but should not be closed off from other members. A thorough debrief discusses the match from pre-match setup to robot removal from the field, and includes both the '''good''' and '''bad'''.
+
+'''Take Actions as Needed'''
+  Once a decision has been reached about the next steps, they will be implemented by the pit crew.
+
+{{{#!div style="color:red; align:left"
+If you make modifications to the robot, you should go through the checklist again.
+}}}
+
 === Judges
-
+Judges aren't supposed to divulge what award they're judging for, and they come around and ask questions about your robot, operations, team, etc. It's usually a good idea to have someone versed in technical and someone verses in the non-technical aspects of the team available. If everyone's busy, it's okay to ask them to come back again a little later.
 === Safety Inspection
 See the page on [wiki:Playbook/Events/PitSafetyRequirements Pit Safety], section on Safety Inspections.
 
 === Load-Out
+Load out can begin after the team's last match. Load out, just like loading and load-in, should have been coordinated well beforehand.
+
+1. Bag and lock up the robot using a new tag.
+2. Load the transport with all items.
 
 == Post-Competition
+=== Loading
+Loading time should be coordinated with teachers, students, and the transporter beforehand. (Unless you're transporting a spur-of-the-moment full-size field carpet on the bus, in which it can be okay to leave it to the last minute.)
+
+=== Post-Mortem !Analysis/After-Action Report
+Ideally at the next meeting, go over what went well and what could be improved from the past competition.
+
+Discuss things such as:
+* changes to the robot
+* changes to the pit, including items forgotten
+* pre-match checklist items
+* team effectiveness
 
 == Archive of Important Past Documents