What do you guys think? Is there anything you would add/remove?
As for data analysis, we are going to hopefully use a Google Form/Excel input to do some data analysis. Does anyone know a easy way to input data and keep it up to date when there is little to no internet connectivity? I’ve heard of using an Access database/form, have any teams used that to get scouting info in a reliable format? How have teams implemented it? We MIGHT have access to a couple school Chromebooks, and we can use the not-as-functional programming laptops for Excel/Access/etc.
Also, what info are teams looking at for Pit Scouting?
“Can get fuel in high goal”
“Can get fuel in low goal”
These items may not produce the data you are looking for. Many teams will be able to do these, its the amount and # of cycles that will differentiate.
I would suggest adding an “approximate fuel per cycle” of 10-25-50-75 etc and then counting the “#number of fuel cycles” to give a better estimate of performance to differentiate robots.
This high level stuff is great for pit scouting. Really talking to teams about what they’ve done and what they wish they’ve done makes a large difference in the grand scheme of things (it also gives you good ideas for next year ;)).
For our scouting, we’re trying our best to focus on quantitative data when watching matches. That way, if we are able to choose alliance members, we’re able to rank teams in terms of compatibility and choose from there.
DM me if you have questions about the specific data points we’re asking our scouters to look for.
Excel is going to give you more value than forms if you use formulas. I highly recommend it.
Its odd the sheet says “can do x” instead of “did x” or even better yet “x” and a big space for tally marks. Its not about what a team can do, it’s what they did. This reminds me of a pit scouting sheet.
If you’re going to load data into spreadsheets, consider condensing the collection sheet. Maybe it seems like a good idea to record the day the match is taking place and bumper colors, but by the end of quals that will be over 1000 data points! Just look at the schedule if you need that info.
Also, bianary data is boring to copy into excel. You’ll be hitting 1, 0, tab, and enter for hours on end. Spice it up,with some totals! Saying things like “Woah that team scored how many gears?” Is the only joy you get while entering data. Dont deny yourself that opportunity.
I created a release from my scouting system last year. Take away the ranking predictor stuff and it’s a fairly accessible easy to replicate system. If you want a paper system with excel based data analysis, give it a look! Feel free to dm me
At least attempting to count how many balls go in a goal is going to be so much better than “can they do it”. So this post is general advice for teams on how to attempt to do that.
You don’t need to count accuracy if you can’t do that - you really only care how many balls make it into the goal, right? Ten balls of ten versus ten balls of fifty, not much difference if it’s done in the same amount of time, and “low accuracy” can be mentioned in the comments.
Get one of those clicky counter things that they use at offices or ticket stands or at shows to count. Have scouts click that button every time a ball goes in the high goal successfully. At the end of the match, write it down.
The low goal, you’re going to have to estimate, you will generally not be able to see what goes in there.
Personally, I significantly prefer quantitative data, even if it’s rough - it tells the whole story.
Last year, my team decided not to pit scout. It was one of our best years of district performance, and as drive coach/alliance selection rep, I did not miss having that information. If anything, this year i plan to have a space in our app for students to write notes about each team at the event about what they learned about the robot - things like new sensors to consider buying, wiring strategies, etc.
I think the question to be asked here is how did you use that data? Were you collecting information that wasn’t going to be used when answering your big questions (the ones that actually help the drivers) or did you think you’d use the information and it turned out to not work?
I personally like pit scouting as it’s a great icebreaker to talk to other teams. Through the conversations I had with other teams last year, we’ve made so many improvements to our team it holds a special place in my heart.
This is exactly why I still plan to have members talk to each team at the event - they have to write something special about each robot on the app, so they can ask interesting questions to team members. I’d definitely prefer it to kids with forms mindlessly asking questions, which often seemed to happen.
I was about to put that question as an example in my response! Yeah, I don’t want to put any team through that, especially through someone in a 2876 t-shirt. I’ve found the “What makes your robot unique?” is a great icebreaker that teams will actually have interesting comments regarding.
"