Robot Info Page

Originally Posted by Gray Adams

Personally, I don't believe in scouting from the pit for the purpose of alliance selection. I'm not saying it's a bad thing to look at robots, ask how they work, what they do and all that, but I wouldn't trust a single piece of information that someone tells me about what their robot can do for selection purposes. It's all about what their robot does do, on the field. Our (mostly) identical practice bot was shooting 95% from multiple key locations on a practice field, but our competition bot was shooting about 10% when we hit the real field (due to software issues). But on Thursday, we were telling people we could shoot 95% because we didn't know otherwise yet.

I think the OP was meaning to give out the info for the robot info, not match info. But, like you said, the best stats are the ones directly in a match. As my mentor always says, "We need to be all action and no talk". Of course, talking is still great, but you understand the quote.

BTW, what was the difference between the software used in Chesepeake and the software used at SVR that messed up your robot? 192 deserved a muc higher rank than you guys had.

[Gregor]

Originally Posted by SuperNerd256

BTW, what was the difference between the software used in Chesepeake and the software used at SVR that messed up your robot? 192 deserved a muc higher rank than you guys had.

As did 772 at GTR west

[akoscielski3]

Originally Posted by Gregor01

As did 772 at GTR west

Our robot had sooooo many issues Friday, that we didn't have on Thursday. Although they probably could have been fixed if we didn't have COM issues on Thursday for 4 hours. GTR West felt more like a three day practice day to me, than a comeptition...

[Gray Adams]

Originally Posted by SuperNerd256

I think the OP was meaning to give out the info for the robot info, not match info. But, like you said, the best stats are the ones directly in a match. As my mentor always says, "We need to be all action and no talk". Of course, talking is still great, but you understand the quote.

BTW, what was the difference between the software used in Chesepeake and the software used at SVR that messed up your robot? 192 deserved a muc higher rank than you guys had.

We weren't able to get image tracking working for Chesapeake, so we switched to shooting 2 point fender shots right after the match. The code seemed good enough for SVR, but we missed 5 matches due to the computer being assigned an IP address that caused comm failure, and then the workaround caused the tracking to not work. On top of that, the angle change of our visor caused the 2 point shot to fail by the time we could finally start using it.

On the bright side, I discovered that I'm apparently pretty good at defense.

Originally Posted by Gray Adams

On the bright side, I discovered that I'm apparently pretty good at defense.

It's always a great skill to have. Ever year defense is undermined and shoved aside, and nobody realizes its true potential as an advantage in a match. When you can stop 254 cold in a match with decent defense, it shows how important it is in this game, and how important key shooting is.

256 will be going hardcore D at Central Valley because of this, and we have an excellent strategy to work with it.

If you can, try out some good D in a match at championships. Chances are you'll be able to impress a lot of good offensive teams looking for a defensive partner

[akoscielski3]

I feel the same way about pit scouting. But people still come to our pits to ask us questions. Even when im EXTREMELY busy i am told to talk to them. Thats why i want to give the pamphlets out.

They could also be given out to visitors that dont know much about FIRST and are just wondering about your robot.

[legogeek24]

In this years game, especially with the bridge, it seems as though information about the drive train would be very helpful in a pamphlet. Scouts for a triple balance are interested in your orientation, overall dimensions, center of gravity, wheel type and number, weight, gearing, etc. That isn't always obvious from match scouting, and could prove vital in eliminations.

Originally Posted by legogeek24

In this years game, especially with the bridge, it seems as though information about the drive train would be very helpful in a pamphlet. Scouts for a triple balance are interested in your orientation, overall dimensions, center of gravity, wheel type and number, weight, gearing, etc. That isn't always obvious from match scouting, and could prove vital in eliminations.

As a defensive robot, information like this greatly influences our match strategy. We can easily push most teams who gear high, and had complete control over over a mecanum bot in a previous match (may have been a scrimmage, I forget). We also used this for balancing strategy.

[Grim Tuesday]

I wouldn't believe everything/anything I see in a pamphlet. They all say "so great at everything" but then when you actually watch the robot, they're really not.

We pit scout for purely quantitative data that you couldn't get otherwise or is easiest gathered in the pits: Robot dimensions (wide/long), robot height (for balancing and CoG), and number of CIMs on the drive.

[JosephC]

We pit scout for things that people can't lie about.

Drivetrain Type (mechanum, 6-wheel, 8-wheel, etc.)
Chassis Orientation (wide/long)
Shooter Type (long range, fender, no shooter)
Bridge Manipulator (yes/no)

There's way more then that, but I can't think of them right now.

[Koko Ed]

We make a robot card containing basic robot information that was from an original design by team 1002.

[JosephC]

Originally Posted by Koko Ed

We make a robot card containing basic robot information that was from an original design by team 1002.

Nice! Why does it have 2 bump sections?

[Koko Ed]

Originally Posted by JosephC

Nice! Why does it have 2 bump sections?

If you mean in the front, it's for the ball intake.

[JosephC]

Fail on my part, I read Ramp as Bump on the backside.