paper: Cyber Blue 234 Match Prep Form - 2017

Thread created automatically to discuss a document in CD-Media.

Cyber Blue 234 Match Prep Form - 2017
by: Chris Fultz

This is summary form we used during 2017 to document and track our match configuration, issues, and changes.

This is a summary form we used during 2017 competitions.

This form was mainly completed and used by the drive team, with input from the pit crew and programming team.

We included basic match information (alliance, position, partners, other alliance) and specific robot information.

We documented our “pre-match” configuration, including software version and battery, as well as any changes made since our last match. We tracked basic of match performance (Auto, Scoring, Climb).

We documented any mechanical, programming or electronic issues and potential changes we felt were needed.

Lastly, any changes incorporated were listed at the bottom of the form and then transferred to the changes portion of the next match page.

This detail helped us identify when changes were implemented so that it was clear to the drive team what had changed (or not changed) between matches.

After the competitions, this information helped us evaluate the impact of changes on match performance.

Cyber Blue 2017 Match Prep Sheet.pdf (171 KB)

This is a summary form we used during 2017 competitions.

This form was mainly completed and used by the drive team, with input from the pit crew and programming team.

We included basic match information (alliance, position, partners, other alliance) and specific robot information.

We documented our “pre-match” configuration, including software version and battery, as well as any changes made since our last match. We tracked basic match performance (Auto, Scoring, Climb).

After the match, we documented any mechanical, programming or electronic issues and potential changes we felt were needed.

Lastly, before leaving the pits, any changes incorporated were listed at the bottom of the form and then transferred to the changes portion of the next match page.

This detail helped us identify when changes were implemented so that it was clear to the drive team what had changed (or not changed) between matches, and then we could identify the impacts of those changes.

After the competitions, this information helped us evaluate the impact of changes on match performance by comparing configuration and changes implemented to scouting data.

Thank you so much for sharing. this is fantastic piece of documentation, and if taken seriously would be incredibly beneficial towards finding issues should they arise.
Do you also do any pit team “checklists” before matches?

This is an amazing document. On 5484, we look up to you guys so I will be using this with my drive team next year for sure. I think this would help us diagnose problems faster, so thank you for posting.

This year we did not have a specific pit checklist.

We did system checks before each match, and since we were recording the battery number each time we knew we had that covered. We did some checks as we placed the robot for a match.