[Hot_Copper_Frog]

Step 1: Scout. We've developed a shift system with four teams of six students each. Every shift has a captain, and they are responsible for their team making it to their shift on time. This way, every robot is scouted by on person every match, and we rotate the kids out to allow for rest and socializing. Data is preferably entered after every match.

Step 2: Analyze. We have a few student excel wizards that have written incredible code to crunch scouting data. It gives us information about every quantifiable aspect of the game, and allows us to cross reference with the rest of the field quickly and accurately. Note: Teaching several of your students how to use VBA and/or write macros can be VERY useful to the team. It is also a helpful life skill to have in your toolbox.

Step 3: Know what you need. Prior to looking at data for the purpose of creating a pick list, we outline various scenarios that could shake down during alliance selections. We first outline the best/ideal alliance and identify what parameters we need to look for within the data. Then, we flesh out with other scenarios and what we would need to do from there. For example, we mainly operated from the chute, but COULD do landfill effectively. Ideally, we would have 1 other very strong chute bot that could do 3-tote auton, and an ok landfill bot with a fast 2-container stealer.

Step 4: Create lists for your scenarios. Creating only one list is a little short sighted, because it limits your ability to quickly respond to changing conditions. As a result, it's wise to make several (if possible) in excel, then employ code to black out those options as you enter teams that have been picked. This way, you can see across all your lists who is still available while still having time to deliberate with your partner for a third round pick.

Step 5: Realize it's all about the numbers, except when it isn't. We ask our students to write comments for every match for a reason. We interview our drive team regarding other drive team's behavior/conduct for a reason. If a team has qualitative problems that aren't reflected in the numbers, it needs to be addressed when ranking for a pick list.