2010 Regional Stats

[DonRotolo]

Originally Posted by vhcook

Virginia also ran a couple of matches Saturday morning before what I suspect was a break for the opening ceremonies.

There were a few 30-40 minute stops during the day Friday for unexplained reasons, and we were so far behind by the end of Friday they decided to try and make it up early Saturday, pausing around 9:30 for a quick opening ceremony.

The field problems continued on Saturday. I cannot blame the field staff; they were the ones trying to fix it. Although not as bad as some other regionals, I did notice people who came in off the street to watch were put-off by the delays and walked out. When FMS finally failed and they went to hand-scoring, and then went with only 2 representatives for most awards, I knew they had pulled out all the stops in an effort to minimize the effects of running so very late. (several ties in the semifinals didn't help either)

I'd love to say "Why can't FIRST make a more robust FMS", but that would be doing a disservice to everyone: The FMS is actually quite good, but I think that we're still stressing it further than it can handle sometimes. I don't know the architecture (Windows?) but perhaps they will redouble their efforts on robustness next year.

[Tom Line]

The West Michigan regional was incredibly well-run. I suspect the average would have been even better than it was, but the field shut down for over 40 minutes because someone was running their N router in the pits and it was preventing the teams from connecting to the field, so they stopped running matches.

[Lil' Lavery]

Originally Posted by PayneTrain

The Virginia Regional ran 95 matches, with 9 matches per team. The field cycle was really odd compared to the NJ Regional, going about 3 minutes slower due to problems that went unexplained. I think it had something to do with WPA keys and and router models. The FMS live-scoring died in the middle of the marathon semifinals, which left me a little edgy the entire time. All I know is that we never broke for lunch, which was a little depressing. 422 is not a very large team, and having to video tape every match, I couldn't leave the center all Saturday.

The regional was lots of fun, I just hoped the match cycle would have gone down a minute, not up three minutes.

Originally Posted by Don Rotolo

There were a few 30-40 minute stops during the day Friday for unexplained reasons, and we were so far behind by the end of Friday they decided to try and make it up early Saturday, pausing around 9:30 for a quick opening ceremony.

The field problems continued on Saturday. I cannot blame the field staff; they were the ones trying to fix it. Although not as bad as some other regionals, I did notice people who came in off the street to watch were put-off by the delays and walked out. When FMS finally failed and they went to hand-scoring, and then went with only 2 representatives for most awards, I knew they had pulled out all the stops in an effort to minimize the effects of running so very late. (several ties in the semifinals didn't help either)

I'd love to say "Why can't FIRST make a more robust FMS", but that would be doing a disservice to everyone: The FMS is actually quite good, but I think that we're still stressing it further than it can handle sometimes. I don't know the architecture (Windows?) but perhaps they will redouble their efforts on robustness next year.

I'll let the FTA and other field crew get into as many specifics as they feel are necessary, but rest assured, the field crew was doing absolutely everything they could to get the event running as quickly as possible. There were issues with communications and FMS that slowed the event down dramatically (especially interesting considering the same field had almost no issues with it the previous two weeks in DC and Baltimore).
While I wasn't volunteering in an official capacity this weekend, and only attended the regional on Saturday, I have worked with most of the volunteers at the event before. They are some of the hardest working and best volunteers I've come across, and are typically great at solving field issues (VCU was a week 1 regional until last year).
We're lucky that VCU is so supportive of FRC, and the delays were taken in stride by the VCU employees (unlike the crews at some other venues).

[kjohnson]

Originally Posted by Lil' Lavery

I'll let the FTA and other field crew get into as many specifics as they feel are necessary, but rest assured, the field crew was doing absolutely everything they could to get the event running as quickly as possible. There were issues with communications and FMS that slowed the event down dramatically (especially interesting considering the same field had almost no issues with it the previous two weeks in DC and Baltimore).

Our FMS/communication problems were problems with robots linking with FMS because of differences in wireless radios. The problem arose when any robot using the original (square and black) Linksys gaming adapter linked with FMS before a robot using the newer, silver adapter. This caused a problem in FMS and the remaining radios would not link, causing FMS to have to be restarted.

We eventually worked out a process to solve this link problem: We first ensured all driver stations were linked, then allowed robots with new radios to power up and link, then booted all remaining robots with old radios. After we figured it out, this longer and time consuming process worked most of the time, but we still had to restart the FMS router periodically.

We began keeping track of teams using the newer radios, and used this process in each match they competed in. We ended with 7/63 teams using new radios (about 11%). Those 7 teams cycled through about every 10 matches. Time between matches without new radios ran about 6.5 minutes, matches with new radios of course ran longer.

[quinxorin]

As of 7:31 today,
Average world score per alliance per match for Week 5: 3.88.

And, since I am from a Michigan team,
Average score at the Michigan State championships: 7.97