View Single Post
  #1   Spotlight this post!  
Unread 04-04-2015, 20:44
nathanwalters nathanwalters is offline
Registered User
FRC #0111 (WildStang)
Team Role: Alumni
 
Join Date: Dec 2011
Rookie Year: 2011
Location: United States
Posts: 75
nathanwalters has much to be proud ofnathanwalters has much to be proud ofnathanwalters has much to be proud ofnathanwalters has much to be proud ofnathanwalters has much to be proud ofnathanwalters has much to be proud ofnathanwalters has much to be proud ofnathanwalters has much to be proud of
Preview of WildRank v2

For those of you that remember the WildRank scouting system that Team 111 released at the end of last season (link here), we've rewritten the app from scratch using best practices and a new data storage engine based on Couchbase, a noSQL database. We'll be doing a formal announcement once we wrap up some features and add some documentation, but we'd like to share one of the cool data collection and analysis features that the new system makes possible and which would be almost impossible to do with paper.

In our match scouting screen, we have an interface to collect data on every single interaction a team has with any of the game elements. When a team intakes and ultimately scores and game element, our scouters record that in the app. The interface for that is below.

Click image for larger version

Name:	Screenshot_2015-04-05-18-31-59.png
Views:	181
Size:	46.5 KB
ID:	18770

Based on this data, we can create a visual representation of a team's performance over the course of an event, which can convey a team's abilities, consistency, and performance very quickly.

Take Mars/Wars, for example. Their unique mechanism means that they tend to place stacks of 3 totes and a container on an existing stack and they can get a noodle but don't do so often.

Click image for larger version

Name:	Screenshot_2015-04-05-18-31-13-1.png
Views:	228
Size:	37.1 KB
ID:	18771

Argos, on the other hand, can consistently crank out stacks of 6 (sometimes 7) with a container, but never a noodle.

Click image for larger version

Name:	Screenshot_2015-04-05-18-31-23.png
Views:	151
Size:	38.6 KB
ID:	18772

It's not shown, but stacks that were dropped are also shown by coloring the stack red. Obviously, we still have room for improvement; for instance, we could use our data on coopertition stacks to display those on this screen. Regardless, we hope this will act as an inspiration for other teams for creative ways they can design their scouting data collection and viewing systems.