|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||||
|
|||||
|
Re: Division Pre-Scouting
wouldn't it be better if you had 1 sheet per division? Or is this just for every robot going to champs?
|
|
#2
|
||||
|
||||
|
Re: Division Pre-Scouting
This is just a template. It will be split into one for each division once divisions are released, so there will be 8 of these.
|
|
#3
|
|||
|
|||
|
Re: Division Pre-Scouting
This looks really cool. Good to see a organized sheet like this one.
If you want some help once divisions are released, let me know. Also, congrats on winning the Chairmans Award! |
|
#4
|
|||
|
|||
|
Re: Division Pre-Scouting
This is a really cool spreadsheet. These are just some stuff that I have been looking at (especially earlier on when I was tracking events / reveal videos more closely) because I thought the split was interesting. They're probably not all possible to put in, but I put the ones that I think could be added fairly easily at the top:
- Weight - Landfill or human player? - Can they use sideways containers? - If they do step containers, how many? (Maybe make it a number input rather than a 1 or 0?) - If they have an auto set or container set, how many of each do they get? (same as above?) - Are they a purely stacking or capping robot? These are the ones that were harder to quantify and that are less important: - If they can use sideways containers, do they right them or stack them sideways? - If they get totes from the human player, do they have a preference to the side they use, and to which scoring platform they put the stacks on? - If they have an auto stack, do they knock over containers? - If they do coop, how many do they put down? Can they only do it first, at certain heights, or at any heights? - Do they have a predictable pattern? If so, what is it? - Average height of stacks / number of stacks (compared to max) - Ability to drive over scoring platform - Ability to drive over noodles |
|
#5
|
||||
|
||||
|
Re: Division Pre-Scouting
Quote:
|
|
#6
|
|||
|
|||
|
Re: Division Pre-Scouting
Maybe ramp should be two categories, those that allow you to queue up 3+ totes and those that let you do just the one at a time.
|
|
#7
|
||||
|
||||
|
Re: Division Pre-Scouting
Maybe in the teleop section, there should be input for ideal stack configuration that has columns for number of stacks, number of totes in each stack, whether or not the stack has an RC on it, and whether there is litter in/on the RC.
|
|
#8
|
|||
|
|||
|
Re: Division Pre-Scouting
I like it. I particularly like the section where you differentiate between capping your own stack or someone else's. In addition, I would add which Center/Step RC's are grabbed and how often the robot misses getting them.
|
|
#9
|
||||
|
||||
|
Re: Division Pre-Scouting
I like it! I'll definetely be helping fill this out, seeing as I've done similar before.
|
|
#10
|
|||||
|
|||||
|
Re: Division Pre-Scouting
I think doing it bit masking style would work here in the field already provided. Four binary digits to represent which cans are grabbed, with the first digit being the can closest to the field perimeter with the scoring platform in front of it (Left from either side's alliance station).
Last edited by dellagd : 13-04-2015 at 22:10. |
|
#11
|
||||
|
||||
|
Re: Division Pre-Scouting
I think we need to be careful not to put in too much information. Less information with more team participation than getting lots of information from a handful of teams that are willing to input it in. Also, there are plenty of ways to simplify many of the variables for example, instead of having 1/0 for the different ways a robot gets totes (hp, ramp, landfill). Also step containers can be moved to the canburglar section. Otherwise it looks pretty good. I'm not a fan of the events, event wins, awards section because it doesn't tell you anything specific about the robot.
|
|
#12
|
|||
|
|||
|
Re: Division Pre-Scouting
This is a great thing to do with my time... im not even going to champs, nor is my team. But I need something to do, and it is entertaining watching 10+ people editing the same document at the same time.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|