2010 Regional Stats

[Mark McLeod]

I like to play with spreadsheets and thought I'd take a look at Regional field performance numbers. So far FIRST seems to be meeting it's average goal of 10 matches per event. Large events have fewer matches, while small events have more.

The worst so far has been the Israel turnaround (~13 minutes/match on average) with all of their unique communications problems.

The best so far has been the Oregon Regional at a few seconds under 7 minutes per match.

Anyone think of other interesting statistics to track on an event basis?


# teams # matches Matches/team Match cycle
Overall Averages ----------- 48 ---------- 78 ---------- 10 ---------- 08:14.9

Week 1 (Mar 4-6)
San Diego Regional ----------49 ---------- 82 ---------- 10 ---------- 07:57.7
Washington DC Regional ----- 59 ---------- 89 ----------- 9 ---------- 07:58.6
Peachtree Regional --------- 50 ---------- 82 ---------- 10 ---------- 07:11.4
Bayou Regional ------------- 38 ---------- 60 ----------- 9 ---------- 09:03.1
Greater Kansas City Regional 60 ---------- 99 ---------- 10 ---------- 07:07.5
BAE Granite State Regional - 48 ---------- 80 ---------- 10 ---------- 07:38.2
Finger Lakes Regional ------ 44 ---------- 74 ---------- 10 ---------- 07:41.4
Autodesk Oregon Regional --- 61 ---------- 92 ----------- 9 ---------- 06:53.3
New Jersey Regional -------- 61 ---------- 92 ----------- 9 ---------- 07:33.0
Traverse City District ----- 38 ---------- 76 ---------- 12 ---------- 09:09.0
Kettering District --------- 40 ---------- 74 ---------- 11 ---------- 09:49.0

Week 2 (Mar 11-13)
Arizona Regional ----------- 56 ---------- 94 ---------- 10 ---------- 07:39.6
Florida Regional ----------- 53 ---------- 89 ---------- 10 ---------- 07:48.1
WPI Regional --------------- 29 ---------- 58 ---------- 12 ---------- 07:48.0
Chesapeake Regional -------- 50 ---------- 92 ---------- 11 ---------- 07:13.5
Wisconsin Regional --------- 50 ---------- 84 ---------- 10 ---------- 07:14.1
New York City Regional ----- 64 ---------- 84 ----------- 8 ---------- 09:02.2
Pittsburgh Regional -------- 31 ---------- 62 ---------- 12 ---------- 07:54.9
Cass Tech District --------- 40 ---------- 72 ---------- 11 ---------- 09:35.7
Ann Arbor District --------- 40 ---------- 80 ---------- 12 ---------- 08:00.0
Israel Regional ------------ 55 ---------- 27 ----------- 3 ---------- 12:54.7


Source data (http://www.team358.org/files/frc_records/2010-RegionalMatchCycles.xls)

[Nawaid Ladak]

I remember seeing Seattle and Oregon on the top of a simular turnaround list last year. It seems like the Pacific Northwest has some great volunteers that really know how to work the field

[vhcook]

Coincidentally, I've been doing the same thing today.

I've broken down the turnaround times by day section on the qualification matches. For a normal regional, session 1 is Friday morning, session 2 is Friday afternoon, and session 3 is Saturday morning.

Week-Event------------------------Session 1--Session 2--Session 3--Overall
1----Autodesk Oregon Regional-----07:27.50---06:58.29---06:36.00---06:58.65
1----Greater Kansas City Regional-07:24.00---07:12.86---06:45.52---07:07.50
1----Peachtree Regiona------------07:56.47---07:30.00---06:10.00---07:11.39
2----Chesapeake Regional----------07:45.71---06:50.00---07:25.38---07:13.48
2----Wisconsin Regional-----------08:22.86---06:51.67---06:47.50---07:14.07
2----Arizona Regional-------------10:06.32---07:36.00---05:45.00---07:28.35
1----BAE Systems Granite State----08:51.43---07:05.63---07:17.50---07:38.18
1----New Jersey Regional----------10:00.00---07:20.00---07:01.71---07:38.18
1----Finger Lakes Regional--------07:27.00---08:33.10---06:46.36---07:41.41
1----Washington DC Regional-------10:03.75---07:38.05---06:45.52---07:47.44
2----Florida Regional-------------09:06.32---06:38.05---08:41.54---07:48.14
2----WPI Regional-----------------07:36.67---08:02.86---07:48.75---07:50.18
2----Pittsburgh Regional----------09:30.00---07:35.56---07:53.08---07:54.92
2----San Diego Regional-----------09:40.00---07:24.32---07:32.50---07:57.72
2----FIM Ann Arbor----------------10:21.82---08:04.62---08:11.11---08:26.49
2----New York City Regional-------10:28.42---08:50.63---08:20.00---09:02.22
1----Bayou Regional---------------10:55.71---08:27.86---08:26.25---09:03.10
1----FIM Traverse City------------10:25.00---09:37.50---08:06.21---09:09.04
2----FIM Cass Tech----------------10:33.33---09:43.64---09:06.67---09:35.65
1----FIM Kettering University-----13:30.00---09:34.55---09:22.50---09:49.01
2----Israel Regional--------------21:24.00---15:00.00--------------17:22.22

X----Overall Average--------------09:29.40---08:03.60---07:31.20---08:12.00

X----Average (without Israel)-----09:04.80---07:49.20---07:31.20---07:59.40


You can see the improvement through many of the events. Arizona managed to get to a blistering pace of 5:45.00 by Saturday morning.

Looking at this has also changed my opinion of Kansas City for the better. As an attendee and volunteer, it felt like we were way behind all day Friday. When you look at the statistics like this, we were attempting more matches than any other regional so far and maintaining a very good match turnaround time relative to the rest of the country. :]

[Chris is me]

Can you factor Israel out of the average?

[vhcook]

Can you factor Israel out of the average?

Sure. I've edited accordingly.

[EricH]

Starting six matches behind can really make you move quickly... Arizona's Session 3 is including a double-length field reset due to the field router going down suddenly.

Speed demons: Session 1, Kansas City; Session 2, Florida; Session 3, Arizona; Overall, Oregon

Arizona started slow and gained pace in the afternoon. About 3:15, the inspectors finally finished, so I wandered out to watch a few matches. I spent the rest of the afternoon following the FTA around with a stopwatch to tell him when extra speed was needed in a reset. Did that Saturday morning, too, and the speeds went really high--one of the queuers told me there was a 5-minute turnaround. Then I had to go inspect some more (we started elims inspections at something like 10:30-11:00).

[Leav]

Can you factor Israel out of the average?

Ouch... :rolleyes:

(just kidding.. no offense really taken :))

[rwood359]

Then I had to go inspect some more (we started elims inspections at something like 10:30-11:00).
The AZ inspectors were really thinking ahead. They knew that we had been to San Diego, so they were in our pit as soon as the robot was unpacked and on the cart, asking if we were ready to inspect. Saturday, they had us inspected for elimination, before the last matches were completed. Thanks to all the volunteers that make the competitions happen.

[Mark McLeod]

This week's results show some improvement.

Silicon Valley & St. Louis both beat the best average time set by Oregon.
West Michigan seemed to be very regimented and liked to start matches exactly on the minute mark. they stayed almost right on the schedule pace they set for themselves.

Overall averages include previous weeks results.

# teams # matches Matches/team Match cycle
Overall Averages ----------- 48 ---------- 77 ---------- 10 ---------- 08:09.2

Week 3 (Mar 18-20)
Silicon Valley Regional ---- 50 ---------- 84 ---------- 10 ---------- 06:43.7
Midwest Regional ---------- 42 ---------- 70 ---------- 10 ---------- 07:45.7
Boilermaker Regional ------ 39 ---------- 72 ---------- 11 ---------- 07:33.9
St. Louis Regional -------- 35 ---------- 70 ---------- 12 ---------- 06:27.8
Dallas Regional ----------- 53 ---------- 78 ----------- 9 ---------- 07:03.2
Utah Regional ------------- 33 ---------- 55 ---------- 10 ---------- 09:03.5
Virginia Regional ---------- 63 ---------- 95 ----------- 9 ---------- 09:04.6
Detroit District ----------- 38 ---------- 76 ---------- 12 ---------- 08:49.3
West Michigan District ----- 41 ---------- 82 ---------- 12 ---------- 07:22.0
Be interesting to see what Victoria's intermediate results show this week.
Those should show marked improvement too.

[Alex Dinsmoor]

This weeks results show some improvement.

Silicon Valley & St. Louis both beat the best average time set by Oregon.
West Michigan seemed to be very regimented and stayed almost exactly on the schedule pace they set for themselves.

Overall averages include previous weeks results.

# teams # matches Matches/team Match cycle
Overall Averages ----------- 48 ---------- 77 ---------- 10 ---------- 08:09.2

Week 3 (Mar 18-20)
Silicon Valley Regional ---- 50 ---------- 84 ---------- 10 ---------- 06:43.7
Midwest Regional ---------- 42 ---------- 70 ---------- 10 ---------- 07:45.7
Boilermaker Regional ------ 39 ---------- 72 ---------- 11 ---------- 07:33.9
St. Louis Regional -------- 35 ---------- 70 ---------- 12 ---------- 06:27.8
Dallas Regional ----------- 53 ---------- 78 ----------- 9 ---------- 07:03.2
Utah Regional ------------- 33 ---------- 55 ---------- 10 ---------- 09:03.5
Virginia Regional ---------- 63 ---------- 82 ----------- 8 ---------- 10:34.2
Detroit District ----------- 40 ---------- 76 ---------- 11 ---------- 08:49.3
West Michigan District ----- 41 ---------- 82 ---------- 12 ---------- 07:22.0


Be interesting to see what Victoria's intermediate results show this week.
Those should show marked improvement too.

Detroit ended up being 38 teams with 12 matches per team.

But anyways, this just shows how fast you guys are out west :) Constantly turning around matches minutes faster than many of the other regionals!

[James Tonthat]

I did field reset at Dallas, I'm glad we're on the lower end of the spectrum. :)

[PayneTrain]

This week's results show some improvement.

Silicon Valley & St. Louis both beat the best average time set by Oregon.
West Michigan seemed to be very regimented and liked to start matches exactly on the minute mark. they stayed almost right on the schedule pace they set for themselves.

Overall averages include previous weeks results.

# teams # matches Matches/team Match cycle
Overall Averages ----------- 48 ---------- 77 ---------- 10 ---------- 08:09.2

Week 3 (Mar 18-20)
Silicon Valley Regional ---- 50 ---------- 84 ---------- 10 ---------- 06:43.7
Midwest Regional ---------- 42 ---------- 70 ---------- 10 ---------- 07:45.7
Boilermaker Regional ------ 39 ---------- 72 ---------- 11 ---------- 07:33.9
St. Louis Regional -------- 35 ---------- 70 ---------- 12 ---------- 06:27.8
Dallas Regional ----------- 53 ---------- 78 ----------- 9 ---------- 07:03.2
Utah Regional ------------- 33 ---------- 55 ---------- 10 ---------- 09:03.5
Virginia Regional ---------- 63 ---------- 95 ----------- 9 ---------- 10:34.2
Detroit District ----------- 38 ---------- 76 ---------- 12 ---------- 08:49.3
West Michigan District ----- 41 ---------- 82 ---------- 12 ---------- 07:22.0
Be interesting to see what Victoria's intermediate results show this week.
Those should show marked improvement too.

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.

[Mark McLeod]

The Virginia Regional ran 95 matches, with 9 matches per team.
I fixed that.
I got fooled because match 82 was replayed at the end and I just looked at the last match #.

That also brings the match cycle time down to a little more than 9 minutes. On a par with Utah.

[vhcook]

Here's the update with week 3:

Week--Event----------------------Session 1--Session 2--Session 3--Overall
3-----St. Louis Regional---------06:46.36---06:31.11---06:00.00---06:27.76
3-----Silicon Valley Regional----06:57.27---06:34.55---06:43.85---06:43.70
1-----Autodesk Oregon Regional---07:27.50---06:58.29---06:36.00---06:58.65
3-----Dallas Regional------------09:08.57---06:46.67---06:16.80---07:03.20
1-----Greater Kansas City--------07:24.00---07:12.86---06:45.52---07:07.50
1-----Peachtree Regional---------07:56.47---07:30.00---06:10.00---07:11.39
2-----Chesapeake Regional--------07:45.71---06:50.00---07:25.38---07:13.48
2-----Wisconsin Regional---------08:22.86---06:51.67---06:47.50---07:14.07
3-----FIM Western Michigan-------07:00.00---07:41.43---07:00.00---07:22.03
2-----Arizona Regional-----------10:06.32---07:36.00---05:45.00---07:28.35
3-----Boilermaker Regional-------07:24.00---07:30.00---07:50.53---07:33.91
1-----BAE Systems Granite State--08:51.43---07:05.63---07:17.50---07:38.18
1-----New Jersey Regional--------10:00.00---07:20.00---07:01.71---07:38.18
1-----Finger Lakes Regional------07:27.00---08:33.10---06:46.36---07:41.41
3-----Midwest Regional-----------10:10.59---07:01.82---06:45.88---07:45.67
1-----Washington DC Regional-----10:03.75---07:38.05---06:45.52---07:47.44
2-----Florida Regional-----------09:06.32---06:38.05---08:41.54---07:48.14
2-----WPI Regional---------------07:36.67---08:02.86---07:48.75---07:50.18
2-----Pittsburgh Regional--------09:30.00---07:35.56---07:53.08---07:54.92
2-----San Diego Regional --------09:40.00---07:24.32---07:32.50---07:57.72
2-----FIM Ann Arbor--------------10:21.82---08:04.62---08:11.11---08:26.49
3-----Virginia Regional----------07:24.00---08:57.50---08:47.27---08:43.52
3-----FIM Detroit----------------08:55.71---08:15.88---09:31.20---08:49.32
2-----New York City Regional-----10:28.42---08:50.63---08:20.00---09:02.22
1-----Bayou Regional-------------10:55.71---08:27.86---08:26.25---09:03.10
3-----Utah Regional--------------10:52.00---08:18.26---08:21.43---09:03.46
1-----FIM Traverse City----------10:25.00---09:37.50---08:06.21---09:09.04
2-----FIM Cass Tech--------------10:33.33---09:43.64---09:06.67---09:35.65
1-----FIM Kettering University---13:30.00---09:34.55---09:22.50---09:49.01
2-----Israel Regional------------21:24.00---15:00.00--------------17:22.22

X-----Overall--------------------09:29.40---08:03.60---07:31.20---08:12.00

X-----Overall (except Israel)----09:04.80---07:49.20---07:31.20---07:59.40


Western Michigan appears to have gone like clockwork. It's absolutely uncanny, when compared to the rest of the data. My congratulations to everyone involved.

St. Louis looks to have gotten off to a very fast start, with the current record for Friday morning and Friday afternoon, but no one has approached Arizona's speed for Saturday mornings yet.

Virginia also ran a couple of matches Saturday morning before what I suspect was a break for the opening ceremonies. I didn't count the time across opening ceremonies, since that is not remotely under control of the field crew. I saw the same thing on New Jersey when I was doing my initial analysis and handled it the same way. New York might have done that, but there were two morning delays and I couldn't guess which one to discount (if anyone who was there can tell me, I'll be happy to update the averages accordingly).

[DonRotolo]

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]

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.

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]

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.

[Creator Mat]

Anyone think of other interesting statistics to track on an event basis?


Could you put average total score in the stats? that would be something interesting to track as the game evolves and more strategies are created.

[Mark McLeod]

Now for Week 4 field results.
Overall averages include previous weeks results.

# teams # matches Matches/team Match cycle
Overall Averages --------- 48 ---------- 79 ---------- 10 ---------- 08:05.4

Week 4 (Mar 25-27)
Waterloo Regional -------- 30 ---------- 55 ---------- 11 ---------- 07:34.6
Los Angeles Regional ----- 58 ---------- 97 ---------- 10 ---------- 06:47.2
Colorado Regional -------- 41 ---------- 45 ----------- 7 ---------- 08:18.3 (incomplete-not Sat.)
Hawaii Regional ---------- 28 ---------- 56 ---------- 12 ---------- 07:22.4
Boston Regional ---------- 53 ---------- 80 ----------- 9 ---------- 07:13.2
SBPLI Long Island Regional 48 ---------- 88 ---------- 11 ---------- 06:55.8
Buckeye Regional --------- 60 ---------- 90 ----------- 9 ---------- 07:25.9
Oklahoma Regional -------- 55 ---------- 92 ---------- 10 ---------- 06:59.3
Philadelphia Regional ---- 44 ---------- 66 ----------- 9 ---------- 06:28.6
Palmetto Regional -------- 34 ---------- 63 ---------- 11 ---------- 08:42.0
Microsoft Seattle Regional 64 ---------- 96 ----------- 9 ---------- 06:09.7
Troy District ------------ 40 ---------- 80 ---------- 12 ---------- 07:08.6

[Mark McLeod]

Could you put average total score in the stats? that would be something interesting to track as the game evolves and more strategies are created.
That's a good idea.
Why don't you add that? :)

[Mark McLeod]

Here's another way to look at it all.
This focuses on the number of matches overall which is a risky gamble for an event. Guessing how many matches you'll be able to do before you've started and found what problems teams and the field will have is a real challenge.


------------------------------- # teams ---- # matches ---- Matches/team
Overall Averages --------------- 39 ----------- 79 ----------- 10
Greater Kansas City Regional-- 60 ---------- 99 ---------- 10
Los Angeles Regional ---------- 58 ---------- 97 ---------- 10
Microsoft Seattle Regional ----- 64 ---------- 96 ----------- 9
Arizona Regional -------------- 56 ---------- 94 ---------- 10
Autodesk Oregon Regional ---- 61 ---------- 92 ----------- 9
New Jersey Regional ---------- 61 ---------- 92 ----------- 9
Chesapeake Regional ---------- 50 ---------- 92 ---------- 11
Oklahoma Regional ------------ 55 ---------- 92 ---------- 10
Buckeye Regional ------------- 60 ---------- 90 ----------- 9
Washington DC Regional ------ 59 ---------- 89 ----------- 9
Florida Regional --------------- 53 ---------- 89 ---------- 10
SBPLI Long Island Regional --- 48 ---------- 88 ---------- 11
Wisconsin Regional ------------ 50 ---------- 84 ---------- 10
New York City Regional ------ 64 ---------- 84 ----------- 8
Silicon Valley Regional -------- 50 ---------- 84 ---------- 10
San Diego Regional ----------- 49 ---------- 82 ---------- 10
Peachtree Regional ------------ 50 ---------- 82 ---------- 10
Virginia Regional -------------- 63 ---------- 82 ----------- 8
West Michigan District -------- 41 ---------- 82 ---------- 12
BAE Granite State Regional --- 48 ---------- 80 ---------- 10
Ann Arbor District ------------ 40 ---------- 80 ---------- 12
Boston Regional -------------- 53 ---------- 80 ----------- 9
Troy District ------------------ 40 ---------- 80 ---------- 12
Dallas Regional -------------- 53 ----------- 78 ----------- 9
Traverse City District --------- 38 ---------- 76 ---------- 12
Detroit District --------------- 38 ---------- 76 ---------- 12
Finger Lakes Regional ------- 44 ---------- 74 ---------- 10
Kettering District ------------ 40 ---------- 74 ---------- 11
Cass Tech District ----------- 40 ---------- 72 ---------- 11
Boilermaker Regional -------- 39 ---------- 72 ---------- 11
Midwest Regional ----------- 42 ---------- 70 ---------- 10
St. Louis Regional ----------- 35 ---------- 70 ---------- 12
Philadelphia Regional -------- 44 ---------- 66 ----------- 9
Palmetto Regional ----------- 34 ---------- 63 ---------- 11
Pittsburgh Regional ---------- 31 ---------- 62 ---------- 12
Bayou Regional ------------- 38 ---------- 60 ----------- 9
WPI Regional --------------- 29 ---------- 58 ---------- 12
Hawaii Regional ------------ 28 ----------- 56 ---------- 12
Utah Regional -------------- 33 ----------- 55 ---------- 10
Waterloo Regional --------- 30 ----------- 55 ---------- 11
Colorado Regional --------- 41 ------------- 45 ------------ 7 (incomplete)
Israel Regional -------------- 55 ------------- 27 ------------ 3 (unusual circumstances)

[cziggy343]

despite the fact the numbers dont indicate it, palmetto was a very well run regional. since there were not a large number of teams, teh intentionally made the time between matches longer, in order to make sure that everything ran smoothly.

and ps: only ONE real field delay at palmetto:eek:

[PaW]

Now for Week 4 field results.
Overall averages include previous weeks results.

# teams # matches Matches/team Match cycle
Overall Averages --------- 48 ---------- 79 ---------- 10 ---------- 08:05.4

Week 4 (Mar 25-27)
Waterloo Regional -------- 30 ---------- 55 ---------- 11 ---------- 07:34.6
Los Angeles Regional ----- 58 ---------- 97 ---------- 10 ---------- 06:47.2
Colorado Regional -------- 41 ---------- 45 ----------- 7 ---------- 08:18.3 (incomplete-not Sat.)
Hawaii Regional ---------- 28 ---------- 56 ---------- 12 ---------- 07:22.4
Boston Regional ---------- 53 ---------- 80 ----------- 9 ---------- 07:13.2
SBPLI Long Island Regional 48 ---------- 88 ---------- 11 ---------- 06:55.8
Buckeye Regional --------- 60 ---------- 90 ----------- 9 ---------- 07:25.9
Oklahoma Regional -------- 55 ---------- 92 ---------- 10 ---------- 06:59.3
Philadelphia Regional ---- 44 ---------- 66 ----------- 9 ---------- 06:28.6
Palmetto Regional -------- 34 ---------- 63 ---------- 11 ---------- 08:42.0
Microsoft Seattle Regional 64 ---------- 96 ----------- 9 ---------- 06:09.7
Troy District ------------ 40 ---------- 80 ---------- 12 ---------- 07:08.6


Seattle was incredibly efficient, considering the number of rookie and 2nd year teams. The field crew, the queuing areas, the cart paths, the scoring results... it was all very very well run. Big kudos to all the volunteers working there. Everyone was helping everyone.

Not too much excitement on the pit PA system though. Was hoping someone would've asked to borrow 469's robot. ;)

[Brian C]

Interesting stats Mark. Now I see why Barat felt comfortable moving into the FTA position at SBPLI. 48 teams with 11 matches looks pretty darn good.

From the statistics West Michigan looks like it was well done too.

[Mark McLeod]

Colorado numbers have been posted finally.

#teams #matches matches/team Match-cycle
41 62 9 08:43.7


Sacramento has also finished Qualifying matches

#teams #matches matches/team Match-cycle
38 76 12 08:05.7

[Mark McLeod]

Here are the average combined Qualification & Elimination match scores by event (blue + red alliance score).
Elimination scores were usually much higher of course.
The trend is that later events scored higher than earlier events, especially in the Qualification rounds.
District events where the majority of participants have now played twice really demonstrate this.
Practice makes perfect.

These are just straight scores including penalties. It doesn't include any of that co-opertition score or extra 5pts for the winners, etc.

-----Avg----Avg
Wk-Qual---Elim ---- Event
4 --- 10.3 --- 15.2 ---- Troy District
3 ---- 6.5 --- 14.7 ---- Silicon Valley Regional
4 ---- 6.8 --- 14.5 ---- Los Angeles Regional
4 ---- 6.6 --- 13.1 ---- Boston Regional
1 ---- 6.2 --- 13.1 ---- Kettering District
3 ---- 8.0 --- 12.9 ---- Detroit District
4 ---- 9.0 --- 12.8 ---- Philadelphia Regional
2 ---- 4.4 --- 12.7 ---- Cass Tech District
4 ---- 9.9 --- 12.5 ---- Waterloo Regional
1 ---- 5.6 --- 12.5 ---- New Jersey Regional
3 ---- 6.1 --- 12.3 ---- Midwest Regional
3 ---- 9.1 --- 11.8 ---- West Michigan District
4 ---- 6.0 --- 11.8 ---- SBPLI Long Island Regional
1 ---- 5.1 --- 11.8 ---- BAE Granite State Regional
3 ---- 4.9 --- 11.8 ---- Dallas Regional
5 ---- 6.6 --- 11.7 ---- Sacramento Regional
3 ---- 5.6 --- 10.9 ---- Virginia Regional
2 ---- 6.5 --- 10.7 ---- Florida Regional
4 ---- 6.2 --- 10.7 ---- Hawaii Regional
2 ---- 7.0 --- 10.6 ---- Wisconsin Regional
2 ---- 5.7 --- 10.6 ---- Chesapeake Regional
2 ---- 4.7 --- 10.5 ---- Arizona Regional
2 ---- 5.2 --- 10.4 ---- Ann Arbor District
3 ---- 7.3 --- 10.3 ---- Boilermaker Regional
1 ---- 5.2 --- 10.2 ---- Greater Kansas City Regional
2 ---- 7.3 --- 10.0 ---- Pittsburgh Regional
1 ---- 5.6 ---- 9.9 ---- Finger Lakes Regional
4 ---- 5.8 ---- 9.7 ---- Buckeye Regional
4 ---- 4.8 ---- 9.7 ---- Oklahoma Regional
4 ---- 4.5 ---- 9.6 ---- Microsoft Seattle Regional
3 ---- 7.4 ---- 9.4 ---- St. Louis Regional
4 ---- 4.3 ---- 9.2 ---- Colorado Regional
4 ---- 5.9 ---- 8.7 ---- Palmetto Regional
2 ---- 3.7 ---- 8.7 ---- New York City Regional
1 ---- 4.5 ---- 8.4 ---- San Diego Regional
1 ---- 3.3 ---- 8.1 ---- Peachtree Regional
1 ---- 4.5 ---- 7.9 ---- Autodesk Oregon Regional
1 ---- 4.4 ---- 7.9 ---- Traverse City District
2 ---- 4.5 ---- 7.8 ---- WPI Regional
3 ---- 4.4 ---- 7.2 ---- Utah Regional
2 ---- 2.6 ---- 6.3 ---- Israel Regional
1 ---- 3.8 ---- 5.7 ---- Washington DC Regional
1 ---- 4.2 ---- 5.3 ---- Bayou Regional


P.S.
If anyone wants to play with the numbers they are linked in my original post. I keep updating it.

[GaryVoshol]

In the first 30 matches of the Michigan Championship, the total team score (red + blue, after penalties) has averaged 14.47.

[Huskie65]

In the first 30 matches of the Michigan Championship, the total team score (red + blue, after penalties) has averaged 14.47.
I think that number will go up to...
It will be fun to compare this and other Regionals to the divisions at nationals.

[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

[Mark McLeod]

Michigan State really proved that practice makes perfect. Every team there had at least two prior events under their belt and the Qualification scores were quite high.
I expect we'll see a bit of this in Atlanta...

Here are the average combined Qualification & Elimination match scores by event (blue + red alliance score).

-----Avg----Avg
Wk-Qual---Elim ---- Event
5 --- 16.5 --- 24.2 ---- Michigan State Championship
5 ---- 8.6 --- 16.1 ---- Greater Toronto Regional
4 --- 10.3 --- 15.2 ---- Troy District
5 ---- 9.2 --- 14.9 ---- Connecticut Regional
3 ---- 6.5 --- 14.7 ---- Silicon Valley Regional
4 ---- 6.8 --- 14.5 ---- Los Angeles Regional
5 ---- 8.5 --- 13.7 ---- Las Vegas Regional
5 ---- 6.7 --- 13.3 ---- North Carolina Regional
4 ---- 6.6 --- 13.1 ---- Boston Regional
1 ---- 6.2 --- 13.1 ---- Kettering District
3 ---- 8.0 --- 12.9 ---- Detroit District
4 ---- 9.0 --- 12.8 ---- Philadelphia Regional
2 ---- 4.4 --- 12.7 ---- Cass Tech District
5 ---- 6.5 --- 12.7 ---- Minnesota 10000 Lakes Regional
4 ---- 9.9 --- 12.5 ---- Waterloo Regional
5 ---- 4.9 --- 12.5 ---- Minnesota North Star Regional
1 ---- 5.6 --- 12.5 ---- New Jersey Regional
3 ---- 6.1 --- 12.3 ---- Midwest Regional
5 ---- 4.7 --- 12.1 ---- Lone Star Regional
3 ---- 9.1 --- 11.8 ---- West Michigan District
4 ---- 6.0 --- 11.8 ---- SBPLI Long Island Regional
1 ---- 5.1 --- 11.8 ---- BAE Granite State Regional
3 ---- 4.9 --- 11.8 ---- Dallas Regional
5 ---- 6.6 --- 11.7 ---- Sacramento Regional
3 ---- 5.6 --- 10.9 ---- Virginia Regional
2 ---- 6.5 --- 10.7 ---- Florida Regional
4 ---- 6.2 --- 10.7 ---- Hawaii Regional
2 ---- 7.0 --- 10.6 ---- Wisconsin Regional
2 ---- 5.7 --- 10.6 ---- Chesapeake Regional
2 ---- 4.7 --- 10.5 ---- Arizona Regional
2 ---- 5.2 --- 10.4 ---- Ann Arbor District
3 ---- 7.3 --- 10.3 ---- Boilermaker Regional
1 ---- 5.2 --- 10.2 ---- Greater Kansas City Regional
2 ---- 7.3 --- 10.0 ---- Pittsburgh Regional
1 ---- 5.6 ---- 9.9 ---- Finger Lakes Regional
4 ---- 4.8 ---- 9.7 ---- Oklahoma Regional
4 ---- 5.8 ---- 9.7 ---- Buckeye Regional
4 ---- 4.5 ---- 9.6 ---- Microsoft Seattle Regional
3 ---- 7.4 ---- 9.4 ---- St. Louis Regional
4 ---- 4.3 ---- 9.2 ---- Colorado Regional
4 ---- 5.9 ---- 8.7 ---- Palmetto Regional
2 ---- 3.7 ---- 8.7 ---- New York City Regional
1 ---- 4.5 ---- 8.4 ---- San Diego Regional
1 ---- 3.3 ---- 8.1 ---- Peachtree Regional
1 ---- 4.5 ---- 7.9 ---- Autodesk Oregon Regional
1 ---- 4.4 ---- 7.9 ---- Traverse City District
2 ---- 4.5 ---- 7.8 ---- WPI Regional
3 ---- 4.4 ---- 7.2 ---- Utah Regional
2 ---- 2.6 ---- 6.3 ---- Israel Regional
1 ---- 3.8 ---- 5.7 ---- Washington DC Regional
1 ---- 4.2 ---- 5.3 ---- Bayou Regional

[Mark McLeod]

Week 5 field performance results including all previous weeks.
So you can brag about how good your field crews were.
Seattle's record was tied by the crew working the Minnesota North Star Regional, while across the street lagged by 30 seconds per match.

Michigan was a trial version of how Championship Divisions will be run with Quals beginning on Thursday afternoon.

# ------ total ----- Matches - Avg match
teams - matches - team ---- cycle -------- Event
48 ----- 80 --------- 10 --- 0:07:45 ---- Overall Averages

64 ------ 96 ---------- 9 ---- 0:06:10 ---- Microsoft Seattle Regional
63 ------ 95 ---------- 9 ---- 0:06:10 ---- Minnesota North Star Regional
35 ------ 70 --------- 12 ---- 0:06:28 ---- St. Louis Regional
44 ------ 66 ---------- 9 ---- 0:06:29 ---- Philadelphia Regional
44 ------ 77 --------- 11 ---- 0:06:33 ---- Las Vegas Regional
50 ------ 84 --------- 10 ---- 0:06:44 ---- Silicon Valley Regional
58 ------ 97 --------- 10 ---- 0:06:47 ---- Los Angeles Regional
63 ------ 95 ---------- 9 ---- 0:06:49 ---- Minnesota 10000 Lakes Regional
61 ------ 92 ---------- 9 ---- 0:06:53 ---- Autodesk Oregon Regional
55 ------ 94 --------- 10 ---- 0:06:55 ---- Connecticut Regional
48 ------ 88 --------- 11 ---- 0:06:56 ---- SBPLI Long Island Regional
66 ------ 99 ---------- 9 ---- 0:06:57 ---- Lone Star Regional
52 ------ 87 --------- 10 ---- 0:06:57 ---- Greater Toronto Regional
55 ------ 92 --------- 10 ---- 0:06:59 ---- Oklahoma Regional
53 ------ 78 ---------- 9 ---- 0:07:03 ---- Dallas Regional
60 ------ 99 --------- 10 ---- 0:07:07 ---- Greater Kansas City Regional
40 ------ 80 --------- 12 ---- 0:07:09 ---- Troy District
50 ------ 82 --------- 10 ---- 0:07:11 ---- Peachtree Regional
53 ------ 80 ---------- 9 ---- 0:07:13 ---- Boston Regional
50 ------ 92 --------- 11 ---- 0:07:13 ---- Chesapeake Regional
50 ------ 84 --------- 10 ---- 0:07:14 ---- Wisconsin Regional
44 ------ 66 ---------- 9 ---- 0:07:21 ---- North Carolina Regional
41 ------ 82 --------- 12 ---- 0:07:22 ---- West Michigan District
28 ------ 56 --------- 12 ---- 0:07:22 ---- Hawaii Regional
60 ------ 90 ---------- 9 ---- 0:07:26 ---- Buckeye Regional
63 ----- 130 --------- 12 ---- 0:07:30 ---- Michigan State Championship
61 ------ 92 ---------- 9 ---- 0:07:33 ---- New Jersey Regional
39 ------ 72 --------- 11 ---- 0:07:34 ---- Boilermaker Regional
30 ------ 55 --------- 11 ---- 0:07:35 ---- Waterloo Regional
48 ------ 80 --------- 10 ---- 0:07:38 ---- BAE Granite State Regional
56 ------ 94 --------- 10 ---- 0:07:40 ---- Arizona Regional
44 ------ 74 --------- 10 ---- 0:07:41 ---- Finger Lakes Regional
42 ------ 70 --------- 10 ---- 0:07:46 ---- Midwest Regional
29 ------ 58 --------- 12 ---- 0:07:48 ---- WPI Regional
53 ------ 89 --------- 10 ---- 0:07:48 ---- Florida Regional
31 ------ 62 --------- 12 ---- 0:07:55 ---- Pittsburgh Regional
49 ------ 82 --------- 10 ---- 0:07:58 ---- San Diego Regional
59 ------ 89 ---------- 9 ---- 0:07:59 ---- Washington DC Regional
40 ------ 80 --------- 12 ---- 0:08:00 ---- Ann Arbor District
38 ------ 76 --------- 12 ---- 0:08:06 ---- Sacramento Regional
34 ------ 63 --------- 11 ---- 0:08:42 ---- Palmetto Regional
41 ------ 62 ---------- 9 ---- 0:08:44 ---- Colorado Regional
38 ------ 76 --------- 12 ---- 0:08:49 ---- Detroit District
64 ------ 84 ---------- 8 ---- 0:09:02 ---- New York City Regional
38 ------ 60 ---------- 9 ---- 0:09:03 ---- Bayou Regional
33 ------ 55 --------- 10 ---- 0:09:03 ---- Utah Regional
38 ------ 76 --------- 12 ---- 0:09:09 ---- Traverse City District
40 ------ 72 --------- 11 ---- 0:09:36 ---- Cass Tech District
40 ------ 74 --------- 11 ---- 0:09:49 ---- Kettering District
63 ------ 82 ---------- 8 ---- 0:10:34 ---- Virginia Regional
55 ------ 27 ---------- 3 ---- 0:12:55 ---- Israel Regional

[vhcook]

Better late than never, here's my update including weeks 4 and 5:

Week—Event----------------------Session 0--Session 1--Session 2--Session 3--Overall
4---Seattle--------------------------------06:48.46---06:04.86---05:42.00---06:09.68
3---St. Louis Regional---------------------06:46.36---06:31.11---06:00.00---06:27.76
4---Philadelphia---------------------------06:38.82---06:06.43---06:53.33---06:28.57
5---Las Vegas------------------------------06:46.36---06:39.38---06:09.00---06:33.24
5---Minnesota North Star-------------------07:08.28---06:08.57---06:30.00---06:33.91
5---Minnesota 10k Lakes--------------------06:40.00---06:46.29---06:24.00---06:37.17
3---Silicon Valley Regional----------------06:57.27---06:34.55---06:43.85---06:43.70
4---Los Angeles----------------------------07:05.00---06:52.50---06:26.00---06:47.23
4---Connecticut----------------------------07:27.27---06:41.86---06:34.62---06:50.77
5---Lone Star------------------------------07:08.28---06:22.11---07:16.55---06:52.50
4---Long Island----------------------------07:32.50---06:08.82---07:22.22---06:55.76
1---Autodesk Oregon Regional---------------07:27.50---06:58.29---06:36.00---06:58.65
4---Oklahoma Regional----------------------07:47.14---06:56.47---06:13.33---06:59.33
3---Dallas Regional------------------------09:08.57---06:46.67---06:16.80---07:03.20
1---Greater Kansas City -------------------07:24.00---07:12.86---06:45.52---07:07.50
4---FIM Troy-------------------------------07:00.00---07:18.33---07:00.00---07:08.57
1---Peachtree Regional---------------------07:56.47---07:30.00---06:10.00---07:11.39
4---Boston---------------------------------07:48.00---07:00.00---07:02.61---07:13.25
2---Chesapeake Regional--------------------07:45.71---06:50.00---07:25.38---07:13.48
2---Wisconsin Regional---------------------08:22.86---06:51.67---06:47.50---07:14.07
4---North Carolina*------------------------07:33.00---07:16.80---07:14.12---07:21.29
3---FIM Western Michigan-------------------07:00.00---07:41.43---07:00.00---07:22.03
5---Greater Toronto------------------------07:16.00---07:53.57---06:55.38---07:22.14
2---Arizona Regional-----------------------10:06.32---07:36.00---05:45.00---07:28.35
5---FIM Michigan State Champs---08:22.76---06:47.59---06:53.68---08:06.00---07:30.00
4---Buckeye--------------------------------09:42.50---07:00.00---06:23.64---07:31.03
3---Boilermaker Regional-------------------07:24.00---07:30.00---07:50.53---07:33.91
4---Waterloo-------------------------------07:14.12---07:20.00---08:21.43---07:34.62
1---BAE Systems Granite State--------------08:51.43---07:05.63---07:17.50---07:38.18
1---New Jersey Regional--------------------10:00.00---07:20.00---07:01.71---07:38.18
1---Finger Lakes Regional------------------07:27.00---08:33.10---06:46.36---07:41.41
3---Midwest Regional-----------------------10:10.59---07:01.82---06:45.88---07:45.67
1---Washington DC Regional-----------------10:03.75---07:38.05---06:45.52---07:47.44
2---Florida Regional-----------------------09:06.32---06:38.05---08:41.54---07:48.14
2---WPI Regional---------------------------07:36.67---08:02.86---07:48.75---07:50.18
4---Hawaii---------------------------------09:04.29---07:36.52---07:18.75---07:54.34
2---Pittsburgh Regional--------------------09:30.00---07:35.56---07:53.08---07:54.92
2---San Diego Regional --------------------09:40.00---07:24.32---07:32.50---07:57.72
5---Sacramento-----------------------------07:54.78---08:12.41---08:54.29---08:18.90
2---FIM Ann Arbor--------------------------10:21.82---08:04.62---08:11.11---08:26.49
4---Palmetto-------------------------------08:03.75---08:06.67---10:14.12---08:42.00
3---Virginia Regional----------------------07:24.00---08:57.50---08:47.27---08:43.52
4---Colorado-------------------------------09:35.29---08:25.38---08:18.75---08:43.73
3---FIM Detroit----------------------------08:55.71---08:15.88---09:31.20---08:49.32
2---New York City Regional-----------------10:28.42---08:50.63---08:20.00---09:02.22
1---Bayou Regional-------------------------10:55.71---08:27.86---08:26.25---09:03.10
3---Utah Regional--------------------------10:52.00---08:18.26---08:21.43---09:03.46
1---FIM Traverse City----------------------10:25.00---09:37.50---08:06.21---09:09.04
2---FIM Cass Tech--------------------------10:33.33---09:43.64---09:06.67---09:35.65
1---FIM Kettering University---------------13:30.00---09:34.55---09:22.50---09:49.01
2---Israel Regional------------------------21:24.00---15:00.00--------------17:22.22

X---Overall---------------------08:22.76---08:40.71---07:36.61---07:23.38---07:50.14

X---Overall (except Israel)----------------08:25.44---07:27.74---07:23.38---07:38.70


To keep the naming conventions consistent, I've dubbed the Thursday afternoon session at the Michigan State Championships as Session 0.

There was an anomaly in the North Carolina data in which match 23 shows a start time two hours after the last other match concluded Friday. I've given them the benefit of the doubt and discounted it from the averages, but I'm very curious as to the story there.

On the whole, the week 4 and 5 regionals put on a very strong performance, in terms of turnaround time. Troy District turned in another precision performance with every reset at 7 or 8 minutes. Seattle broke Arizona's half-day record by 3 seconds per match on Saturday morning, those regionals being the only two to maintain an average below 6 minutes for an entire session.

Thanks to all the queuing and field crews across the country who have done their best to keep things moving. Good luck Atlanta volunteers!

[EricH]

There was an anomaly in the North Carolina data in which match 23 shows a start time two hours after the last other match concluded Friday. I've given them the benefit of the doubt and discounted it from the averages, but I'm very curious as to the story there.
I'd guess that it was a replay, caused by a field fault, and run at the very end of the day on Friday to keep everything else on schedule. Good idea to not count it.

[Mark McLeod]

All Championship fields had:
86 teams
144 total matches
10 matches per teamDon't know what the target match turn-around times were, so can't say how close to the target each of the fields was.

------------ Avg match ---- Avg Qual ---- Avg Elim
Field --------- cycle --------- Score ------ Score

Archimedes - 0:06:24.9 -------- 15.6 -------- 25.8
Curie -------- 0:06:16.4 -------- 14.6 -------- 24.1
Galileo ------ 0:06:12.0 -------- 13.8 -------- 22.8
Newton ----- 0:06:00.0 -------- 13.0 -------- 25.9

Einstein ----- 0:18:40.0--------- n/a -------- 29.3


The average elimination score for all fields is on a par with the Michigan State event, so it seems this represents the optimum scores that can be expected from Breakaway! after teams have gained experience at a couple of regional/district events.

[ATannahill]

------------ Avg match ---- Avg Qual ---- Avg Elim
Field --------- cycle --------- Score ------ Score

Newton -- 1-2 presentations----- n/a -------- 29.3



I think you spelled Einstein wrong.

[Mark McLeod]

Thanks

[vhcook]

Per session cycle times for Championships, where 0 is Thursday night, 1 is Friday morning, and so on:

Session......0........1........2........3
Archimedes...0:06:21..0:06:13..0:06:18..0:06:35
Curie........0:06:28..0:05:46..0:06:20..0:06:06
Galileo......0:06:08..0:06:00..0:06:06..0:06:22
Newton.......0:05:58..0:05:39..0:06:04..0:06:02

I took a look at the match schedule on Thursday before most had run, and it appeared they were targeting 6 minute turnaround.

[Mark McLeod]

One last note...
I related this year's event match turnaround and scores with previous year's.
A jump in #matches offered to teams while the # teams per event has stayed fairly constant. Championship match cycles are understandably lower, since everyone (drive teams, field staff) have experience in the new yearly game. Einstein scores are typically much higher than those seen at early events.

Scores are per Alliance.


Regional/District Averages
2008 2009 2010
Teams per event 46 49 48
Total matches 71 71 80
Matches per team 9 9 10
Avg. Match turnaround 6:40 7:21 7:45
Avg. Qualifying score 36.1 52.4 3.1
Avg. Elimination score 48.6 52.8 5.6


Championship Averages
2008 2009 2010
Teams per Division 85 87 86
Total matches 100 102 144
Matches per team 7 7 10
Avg. Match turnaround 5:58 6:13 6:13
Avg. Qualifying score 67.3 71.4 7.1
Avg. Einstein score 101.6 72.4 14.6

[Jared Russell]

It looks like you used the average single-alliance score for all data points but Einstein in 2010, where it looks like you used the sum of both alliances.

[Mark McLeod]

It looks like I forgot to divide all the scores by 2 for 2010. I'll go through them and fix those in a minute.

Thanks.