Day 87

Author: AwtyBotsOfficial

assets/js/recaps.js

@@ -2,7 +2,7 @@ let days =
 [
     0, 1, 3, 4, 5, 6, 7, 8, 11, 12, 13, 14, 15, 18, 19, 20, 21, 22, 24, 25, 26, 27, 28, 29, 31, 
     32, 33, 34, 35, 36, 38, 39, 40, 41, 42, 43, 45, 46, 47, 48, 49, 51, 52, 53, 54, 55, 56, 57, 
-    59, 60, 61, 62, 66, 67, 68, 69, 80, 81, 82, 83
+    59, 60, 61, 62, 66, 67, 68, 69, 80, 81, 82, 83, 87
 ];
 
 let day = days.length - 1;

assets/recaps/Day 87.md

@@ -0,0 +1,38 @@
+# 9 days until DCMP
+
+We did our usual recap of our event and tried to focus more on robot performance since we know we need to be consistent for DCMP.
+
+We achieved our goals for SC\#2 and that was in spite of having programming issues plague us the whole event (again). The robot performed better with the upgrades we made and we think it wasn’t at it’s fullest potential due to the programming issues.
+
+Here’s what else we discussed below:
+
+# What Went Right?
+
+- Intake worked better  
+- Shooting was good even though auto aim didn’t work  
+- Got the Energize RP 11/12 matches  
+- We won an Engineering award
+
+# What Went Wrong?
+
+- Programming  
+- Information from Scouting wasn’t good  
+- Intake off track every match
+
+# Goals at State Champs
+
+- Auton works every match  
+- Be consistent throughout the event  
+- Don’t break down  
+- Fuel per match:  
+  - Need: 180  
+  - Want: 240
+
+# What needs to be improved?
+
+- Programming  
+- Rate of fire  
+- Intake  
+- Scouting 
+
+Even though we know this robot has room to improve, we don’t feel it’s a DCMP winning robot. Our goals now are to tune this robot more and make sure all the issues are resolved (i.e. no more programming hindrances) and focus on building a new robot that we think is more inline with the meta of the game. We are setting limits on ourselves so that we don’t bring a robot that isn’t ready to DCMP because we still want to give ourselves a chance to make it to the world championships. We don’t want to ruin it by bringing a robot that isn’t ready to compete.