STEMLey Cup

We just finished competing in the STEMley Cup yesterday! Lots of good things to review, and we placed third captaining the 7th alliance captain.

Scouting Review

The scouting system half functioned with our new website.

Remember to bring power brick for scouting laptop

Allocate a phone for data to push stuff, check to see if it works on apple.

Communicate with scouts about event-strategy channel threads and can input on match planning

Look into sim card dongle data thing so we don’t have to sacrifice a phone, team could get a cheap data plan

There wasn’t a lot for the third pit student to do, given that the the work and roles had been divided between the other two students for the season and they were accustomed to their tasks at that point.
- Next season, we would want to have a third role and checklist defined
Not specific to this event, but the bumpers took a harsh beating this year.
- It may be worth trying iron on numbers next season - the numbers can be off to the left or right instead of centred on the long side of the robot so that it’s more feasible to align them with our reversible bumper design.

Their full talk can be found here

We can slightly modify our current Priority List process to make things clearer and ensure we have good design processes.

Simplify our requirements process by making sub lists for each requirement.
- Each subsystem should have requirements for
  - Speed
  - Orientation/Location
  - Consistency/reliability
- There should also be overall robot requirements like:
  - COG
  - Holding things inside frame perimeter
Remember that these goals can have timelines where the mechanism can evolve and get better over time.

Make sure requirements are specific, measurable, attainable and relevant.

-Brennan