How did your scouting work?

[Ethulin]

We used our freely available PHP based scouting app. We had 6 scouts, 4 from our team, 2 from 694. It worked out ok, we had such a horrible view, so we missed some stuff.

I feel pretty bad though, on the day of the eliminations I tried to find some one from 694. I looked for a while, went to their pit, but was still not able to find them.

Well I finally found them. Sadly it was when we were up against them! I offered to set up an adhoc right then, but they said don't bother, if we beat you then you can. Well we beat them, and I am still pretty pissed off, because I know I would not be happy if my team put work into something and was unable to reap the rewards.

But for our alliance was our scouting data was VERY helpfully. We were the 8th alliance, 2nd pick, so normally a team in that situation does not have much of a say, but we showed them our scouting data and they were very interested, so we did allot of strategy organizing.

Well 8th seed alliance got devision finalists! so I guess it paid off.

Shout out to 1108 and 447, two $@#$@#$@#$@# good alliance partners, quite to upset to go from 8th seed to devision finalists.

[Not2B]

Our scouting was AMAZING this year. Go Julie for running it all. First year our scouting really was useful.

Low tech - best way to go.

Each team had a sheet. First, look at them in the pits. Then, for each match they played, the sheet would come out, and observations would be recorded.

But here was the key... shortly before each of our matches the head scouter would review all data for each team in the match. It would go onto a summary sheet, and a runner would take it down to the drive team. There, the drive team and alliances would be able to review the op-force info, as well as what our partners REALLY could do. (How many times has a team "embeleshed" their skills??)

I credit our scouters for many of our best matches. We knew EXACTLY who to interfere with, and when our alliance stacking would be faster than the other team. (Yes... I mean time... average time per tetra was important to us.)

Julie said she was going to explain our scouting in a white paper this summer, because we thought is was good and unique. And it should be good no matter the game or year.

[Joe J.]

Yeah our scouting rocked. As the driver I can say they helped us win our matches. The summery sheets were great seeing as we had time to talk to our alliance partners (robot never broke down) we got a lot of planning in before each match. What was also nice was we had review sheets of each of our matches ya know what actually happened those of us on the drive team could get a full picture of what we did right and wrong in each match.

[EricH]

One trick we did was to go around on Thursday and either talk to the teams or get a picture of every robot (a tedious process). When we had that info, we could compare it (somewhat) to the records on Friday to see if a team was using hyperbole in describing what they could do. Our scouting worked really well during both regionals we went to and nationals. It morphed a bit, but remained mostly the same as when I put it together during build.

[rufu5]

We ( 447 ) set up a wireless ad hoc laptop network and had a set of pit scouts compile data on practice day, and then input match data thought the qp matches. Needless to say with only 3 people scouting there were a LOT of holes and a lot of scouted matches left un entered into the database but it was our first time using a laptop system and it was still very useful.

i would defiantly say that 492 scouting system was the best Ive seen so far (rivaling 461 's at the boiler maker regional)

Originally Posted by Ethulin

We used our freely available PHP based scouting app.

i would love if you could post a link here, or send me the prog asimovchess@yahoo.com and i can host it on my teams website because it was mega awesome