Archimedes 2013!!!

[Jimmy Cao]

Originally Posted by efoote868

If I understand the original model,

For each team
  For each match
    Add opponents ranks to current team's difficulty of schedule
    Subtract alliance ranks from current team's difficulty of schedule

Rank team's difficulty of schedule in ascending order.

In this model,

For each team
  Rerank teams without current team
  For each match
    Add opponents ranks to current team's difficulty of schedule
    Subtract alliance ranks from current team's difficulty of schedule

Rank team's difficulty of schedule in ascending order.

Yes, this is correct. However it's still important to realize that this approach has numerous shortcomings.

As an extreme, place the #1, 2, and 3 teams against #97, 98, 99.
The #1, 2, 3 teams would each get a huge boost to their result, making it seem like an easier schedule, whereas #97, 98, and 99 seem to have very hard schedules. But this is only for 1 match, and this 1 match will have a disproportional impact on the final ranking (it might account for well over half the "points", while it only accounts for 1/12 of the final seeding).

[The Lucas]

Originally Posted by Jimmy Cao

Seeinghttp://www.chiefdelphi.com/forums/sh...&postcount=136 made me curious who had the "easy" or "hard" schedules in Archimedes. Using the same analysis method, with one minor change*, I generated the following list:

Team Difficulty Rank
3627	-51	1
4810	39	2
1756	74	3
1610	79	4
1595	81	5
1747	125	6
2457	132	7
3504	146	8
2614	156	9
801	165	10
639	200	11
4499	201	12
4265	206	13
2590	208	14
172	234	15
2705	238	16
326	247	17
930	249	18
469	249	18
4466	251	20
78	253	21
433	270	22
2081	272	23
4501	274	24
2604	278	25
1660	285	26
20	288	27
1011	293	28
4471	298	29
254	299	30
812	305	31
1334	307	32
4537	313	33
379	320	34
291	326	35
71	330	36
3003	332	37
2165	334	38
4067	336	39
973	348	40
2704	349	41
1448	352	42
321	358	43
2408	358	43
4731	373	45
3044	376	46
3478	385	47
846	387	48
3245	388	49
910	389	50
2137	391	51
3145	395	52
840	399	53
525	404	54
1071	408	55
51	409	56
694	424	57
2959	425	58
868	429	59
1714	431	60
2709	436	61
3467	450	62
314	451	63
1967	455	64
236	455	64
2016	455	64
1902	456	67
1796	465	68
1075	467	69
1519	470	70
1868	472	71
948	473	72
126	477	73
11	482	74
836	484	75
4637	498	76
4585	503	77
3310	508	78
2468	529	79
3242	543	80
4470	547	81
33	567	82
4673	581	83
2486	584	84
2415	584	84
955	597	86
1100	610	87
4545	622	88
4589	648	89
3612	656	90
987	668	91
4753	675	92
316	691	93
1836	713	94
4450	737	95
701	755	96
3008	773	97
365	776	98
3314	787	99

*Instead of ranking teams by OPR 1-99, I ranked them by OPR if the team itself was removed from the division 1-98. I think this prevents the average result of a large number of samples from breaking down into a strictly OPR based list.

In no way do I think this is a very good way of ranking match difficulties, but it was rather easy to do.

Did you remove surrogate matches from your calculations?
If not I think you need to remove the third match of 433, 930, 987, & 3044

[Jimmy Cao]

Originally Posted by The Lucas

Did you remove surrogate matches from your calculations?
If not I think you need to remove the third match of 433, 930, 987, & 3044

I forgot about those. Corrected results are below, after removing those 4 surrogate matches. As before, lower number in "difficulty" column = harder schedule.

Team	Difficulty Rank
3627	-51	1
4810	39	2
1756	74	3
1610	79	4
1595	81	5
1747	125	6
2457	132	7
3504	146	8
2614	156	9
801	165	10
433	187	11
639	200	12
4499	201	13
4265	206	14
2590	208	15
930	222	16
172	234	17
2705	238	18
326	247	19
469	249	20
4466	251	21
78	253	22
2081	272	23
4501	274	24
2604	278	25
1660	285	26
20	288	27
1011	293	28
4471	298	29
254	299	30
812	305	31
1334	307	32
4537	313	33
379	320	34
3044	322	35
291	326	36
71	330	37
3003	332	38
2165	334	39
4067	336	40
973	348	41
2704	349	42
1448	352	43
321	358	44
2408	358	44
4731	373	46
3478	385	47
846	387	48
3245	388	49
910	389	50
2137	391	51
3145	395	52
840	399	53
525	404	54
1071	408	55
51	409	56
694	424	57
2959	425	58
868	429	59
1714	431	60
2709	436	61
3467	450	62
314	451	63
1967	455	64
236	455	64
2016	455	64
1902	456	67
1796	465	68
1075	467	69
1519	470	70
1868	472	71
948	473	72
126	477	73
11	482	74
836	484	75
4637	498	76
4585	503	77
3310	508	78
2468	529	79
3242	543	80
4470	547	81
33	567	82
4673	581	83
2486	584	84
2415	584	84
955	597	86
1100	610	87
4545	622	88
4589	648	89
987	648	89
3612	656	91
4753	675	92
316	691	93
1836	713	94
4450	737	95
701	755	96
3008	773	97
365	776	98
3314	787	99

[martin417]

Looks like all the other fields have the match schedule and results up, but not Archi. What's up with that?

[bduddy]

Looks fine to me...

http://www2.usfirst.org/2013comp/eve...chresults.html

[martin417]

Originally Posted by bduddy

Looks fine to me...

http://www2.usfirst.org/2013comp/eve...chresults.html

Dang cache!

I had to do a shift-reload to get it.

[dodar]

Spyder has everything updating too.

[mdituri]

rest assured, we did not go undefeated so we will not have the opportunity to be turned down by many teams. and while destroying the ability for the best of the best to be together may be some people's style, as a second pick worthy robot, we understand our limitations and do pure best to help our alliance win every match. we are certainly not going on the fieldand doing nothing. and as many of the MAR teams that I respect know, we would rather play against three good robots in the finale than screw alliance selection. we want to see Archimedes to win Einstein, maybe with a MAR bot in the alliance.
On a side note, thank you to 2016, the Mighty Monkey Wrenches for saving us when we had the perfect storm of disasters happen on the way to st Louis which had us finally arriving at the dome around noon on Thursday instead of Wednesday by seven. School bus accident. cancelled them delayed flight, missed connection, forced to spend the night in Charlotte rather than st Louis, and delayed a.m. flight. my team is thankful we are even herer to compete this weekend. thank you 2016 for putting up our Egyptian pit. fixing our bent axles. and being an amazing team. they might be ranked low, but I hope you have them on your radar. maybe someone will have enough confidence in 3314 to choose us for our reliable autonomous, three cycles, ten point hang, and our 80 prior matches of experience this season. Good luck to everyone on Archimedes.

[bam-bam]

Match 120

1075-987-2415 Red
33-1610-2543 Blue

211-85, Red

2415 cements #1 position.

[mdituri]

congrats wiredcats. well deserved!

[Jon K.]

Congrats to all the teams in Archimedes!!! It was an amazing weekend to be on the field, and to be able to watch such high caliber teams was truly an awe inspiring event for me personally. I was privileged to have been able to be a part of your referee crew on Archi!!! That being sad, I am hoping the FIRST community here on Chief Delphi can assist me in looking for my WALL-E figure. He went missing from the Archimedes field on Saturday and I am trying to find him. My sister bought him for me a few years ago, and they no longer produce/sell them. I have taken him to numerous events over the past few years, and have a whole facebook album devoted to him and these pictures. I am saddened that I will not be able to continue this album, and many of my friends were upset about this as well. It has brought a lot of joy to many people both in and out of FIRST to see the picture updates. Attached is the last picture I have of him from the Archimedes field. If you could please ask your teammates to see if anyone may have accidentally taken him I would appreciate it!!!

[twetherbee]

First off, I had a great time at the Championships as did our entire team. The Archimedes Division did not disappoint this year. I always enjoy meeting and working with new teams each year, such as 33, 469, 291, 1714, 694, 868, 2590, 948 and seeing old friends like 51, 71, 254, 365, 525, 973, 1902, and 3245. I wish the Championships were a few days longer so we could get to know more, but I guess that will have to wait until next year now.

I want to thank our Alliance Captain, Team 2415, for choosing us to be a part of the #1 seed. Going undefeated at the Championships is never easy and you guys earned the #1 seed with your solid robot and game play. We have still never gone undefeated during qualifications at the Championships after coming so close with one loss in 2006, 2008, 2012, and now 2013. (This year's loss is going to sting for a while.)

I also want to thank our other great Alliance Partner, Team 2959. You guys were such a great scoring machine (worthy of a 1st pick) that I was shocked that our Alliance was able to steal you at the end. A great undervalued Michigan team that was a pleasure to work with this year.

Congratulations to Teams 33, 469, and 1519 for winning the Archimedes Division. The finals matches were incredible and all six teams left everything out on the table. I wouldn't want to win or lose any other way. We were pulling for you all the way through Einstein.

Congrats to the Archimedes Teams for their Championship Awards:

254 Industrial Design Award
1902 Imagery Award
33 Quality Award
3478 Engineering Inspiration
2614 Entrepreneurship Award

And again, we were sorry to Team Crush for the hit in Match 2. I don't think we could recreate that if we tried, but at least it is a video clip that we'll both be remembered by for a while. As Greg mentioned in another post, they were next to us in the pit and were gracious enough to give us use some of the glue/solvent, with which they repaired their robot after Match 2, later in the day after we cracked a part of our intake chute. Great team from our neck of the woods (or desert).

Good luck to all of the teams in the offseason. See you at IRI or next year!!

Now back to work....

[Ken Streeter]

This message is simply to thank the many teams on the Archimedes field that made the 2013 Championships an unforgettable day for everybody on 1519. This will probably be a "tl;dr" for many of you, but we'd like to thank you anyway!

During the first three days of the event, there were countless teams that helped us in various ways. We thank all of the teams that tolerated our rudeness on Wednesday night when we shooed you away so that we could completely rebuild the top half of our robot with a different climber and improved shooter. (This might be the best thing about the Wednesday night pit time - uninterrupted time to work on the robot!) On Friday, we could not have repaired our shooter without the encoder MARS 2614 generously gave us, and the Red Devils 1334 repeatedly helped us out with things like thread taps, talcum powder, and encouragement. Other teams made space for us on the informal practice field to test full court shooting, and yet others provided stories of what tricks or techniques worked for them when making the long shots. Please know that you were each some of the many teams in FIRST that helped us this season and you deserve a portion of the credit for any recognition we received. Thanks!

During the qualification matches, our partners were generally fantastic in the strategy sessions, demonstrating the gracious professionalism of FIRST by being willing to set aside their own interests in showcasing their robot or simply doing what they wanted to do, but rather collectively working with us to come up with an alliance strategy that was in the best interest of winning of the match, even if it meant we or they would be playing lowly defense instead of high-profile shooting. Sometimes key, timely, penalty-free defense is the key to winning a match!

For 1519, though, this posting couldn't be complete without a big THANKS to our alliance partners, The Killer Bees (33) and Las Guerrillas (469)! We're especially thankful to the scouting and strategy folks on 33 who saw the potential in our robot and team to bring some significant capabilities and unique diversity to complete the 33/469/1519 alliance, despite our rather mediocre 50th place ranking in Archimedes and our 4-4 record. We made some significant improvements on Friday evening / Saturday morning which were demonstrated in our only Saturday morning qualification match. Before 33 picked us, we were concerned that we may be packing up our pit in a few minutes. Instead, our robotics team had the most incredible ride of our 9 years to date! However, we wouldn't have experienced any of it without 33 and 469 leading our alliance. We're thankful to have had the opportunity to play in the big show, with all of the FRC world watching.

The whole concluding day of the 2013 FRC Championships is a day I'll surely never forget. Thanks to 33 and 469 for inviting us to share the magic with them. We'd love to be allied with either of your teams again some day; I can only hope that your teams both feel the same. Thank you!

We'd also like to extend our congratulations to Team 3467, Windham Windup, of New Hampshire for winning the only judged award for veteran teams on the Archimedes division. Your robot transformation at the Pine Tree Regional was part of the inspiration that we could do a complete upper robot rebuild at the Championship event. It was definitely worth it!

There are a few other non-Archimedes teams that deserve our thanks, too: Without Team 435, The Robodogs, picking us at NCR, we might not have been in St. Louis at all! Back home in New Hampshire, we would have had little chance to develop the FCS in the first place without the practice field space of 1512, the Metal Vidsters, of St. Paul's School.

Thank you all!

[Akash Rastogi]

Sorry to bring this back up, but does anyone have video of 254's quarterfinal matches? All I found video of was 1519's matches.

[JohnSchneider]

Originally Posted by Akash Rastogi

Sorry to bring this back up, but does anyone have video of 254's quarterfinal matches? All I found video of was 1519's matches.

http://www.youtube.com/user/RobotBillMD?feature=watch has all of archimedes I think (although from a weird angle)