2013 Washington DC Regional
 

Currently, the DC Regional is at 57 teams, with 4 rookie teams! Team 166, The Chop Shop, will be there this year! Who else will be there?

Current Team List:

53 Alien Cow Abductors
79 Team Krunch
116 Epsilon Delta
138 Entropy
166 Chop Shop
303 TEST team
339 Kilroy
379 RoboCats
383 Brazilian Machine
422 Mech Tech Dragons
467 Shrewsbury Colonials
612 Chantilly Robotics
614 Night Hawks
615 Knights
620 Warbots
623 Cougar Robotics
836 RoboBees
1095 RoboCavs
1195 G2H2
1389 The Body Electric
1418 Vae Victis
1446 BAE League of Extraordinary Engineers
1731 Fresta Valley Robotics Club
1735 Green Reapers
1748 Lab Rats
1849 Griffins
1885 ILITE Robotics
1915 MTHS Firebird Robotics
2121 Mecha Clerks
2377 C Company
2415 WiredCats
2421 Rolling Thunder Robotics
2534 The Lakers
2537 RAID
2590 Nemesis
2630 Thunderbolts
2642 Pitt Pirates
2866 Phoenix Robotics
2900 The Mighty Penguins
2911 CoolBots
2912 The Panthers
2914 TIGER PRIDE
2961 Crimson Tide Engineers
2962 EagleBots
2963 AnaDroids
2964 Robopanthers
2974 Walton Robotics
3196 Team SPORK
3650 Robo Raptors
4067 The Incredible Hawk
4099 Falcons FIRST
4137 Wilde Bunch
4242 Fresh T.E.C.H.S.
4456 Cadet Robotics
4464 Team Illusion
4466 Robo Hamsters
4638 Jaguars

EDIT: Added Team names, also this list is REALLY long!

Re: 2013 Washington DC Regional
 

Can't wait for the competition. Only two days away!

166 just got into DC and can't wait for the competition!

Re: 2013 Washington DC Regional
 

You forgot to add 2849 Ursa Major who will be competing at DC

Re: 2013 Washington DC Regional
 

Members from 4472 & 2068 will be at the competition as competition volunteers, we're excited to see all the robots and some great competition!

Re: 2013 Washington DC Regional
 

I'm packing now... (flight leaves in < 8 hours and I'm over an hour from the airport)

Re: 2013 Washington DC Regional
 

Looking forward to the DC competition this weekend. Has the webcast link been established?

Re: 2013 Washington DC Regional
 

Is their a webcast link yet?

Re: 2013 Washington DC Regional
 

Sorry about that! when I made that list you were not listed as attending yet, and the website also said there was 0 slots left so I assumed the regional was full.

Re: 2013 Washington DC Regional
 

There will be a webcast, I'll post the link when it gets up and running.

Wetzel

Re: 2013 Washington DC Regional
 

It's ok i just was running thru the list in my dorm I'm an alumni so i understand possible we entered it later after you made the list.
Does anyone know who the MC is?
How many 30pt climber are their attending DC? If so which teams?

Re: 2013 Washington DC Regional
 

Unfortunately team 2866 will not be attending, TheBlueAlliance was wrong on this one. Sorry

Re: 2013 Washington DC Regional
 

2630 thunderbolts are coming all the way from israel! good luck everyone!

Re: 2013 Washington DC Regional
 

Headed in now, lovely day for a bike commute! See you all there!

Wetzel

Re: 2013 Washington DC Regional
 

Here are two webcast links to try:


Direct link to web cast:

http://robotics.nasa.gov/events/live...dcregional.php



NASA Robotics Webcast Page:

http://robotics.arc.nasa.gov/events/...s.php#webcasts

Click the Webpage link for Washington DC Regional

Enjoy: :)

Re: 2013 Washington DC Regional
 

What's up with audio? Anyone else getting Jeff Seaton announcing old matches on audio while the live feed of the opening ceremonies is on video?

Re: 2013 Washington DC Regional
 

Yea I'm getting the same thing. Hearing about coopertition bridges while the opening ceremony is shown

Re: 2013 Washington DC Regional
 

Anyone know why the sound on the NASA feed is from last year even though they are showing the video feed from this year?

Re: 2013 Washington DC Regional
 

Don't know why...or how ... but I do know event folks are aware and are working on it.

Re: 2013 Washington DC Regional
 

Field communication already at DC 3 matches in what happend

Re: 2013 Washington DC Regional
 

is there a match list anywhere? or can some kind soul tell me which matches 2415 is in?

Re: 2013 Washington DC Regional
 

I gotchu Santosh.

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

Re: 2013 Washington DC Regional
 

I'm going to do my best to archive individual matches at www.watchfirstnow.com/archive.php

I should have them up within 2 or 3 hours of the match.

Re: 2013 Washington DC Regional
 

Can somebody tell me what going on with 2849 Ursa major who's at the event I'm wondering why their not shooting or climbing

Re: 2013 Washington DC Regional
 

Alliances for eliminations:

1 -- 4464, 2974, 623
2 -- 116, 2415, 4466
3 -- 612, 2630, 1735
4 -- 422, 2642, 166
5 -- 79, 379, 383
6 -- 836, 138, 611
7 -- 620, 2914, 1885
8 -- 2534, 1522, 2961

Re: 2013 Washington DC Regional
 

1719 replacing 2961 in the 8th alliance. Updated alliances.

1 -- 4464, 2974, 623
2 -- 116, 2415, 4466
3 -- 612, 2630, 1735
4 -- 422, 2642, 166
5 -- 79, 379, 383
6 -- 836, 138, 611
7 -- 620, 2914, 1885
8 -- 2534, 1522, 2961, 1719

Re: 2013 Washington DC Regional
 

As an alumnus of 2421, I have to give a shout out to Kurt Willstater who won the WFFA at DC this weekend. Great man, great inspiration for all. Even after his daughter graduated, he remained involved and has led the team to become a very stable organization that is sustainable.

Re: 2013 Washington DC Regional
 

836 declined 4464
79 declined 422
3123 replaced 2415 for F-3

Re: 2013 Washington DC Regional
 

It appears that 2415 sat out their last match and let 3123 have a run in the last match of the event.

Anyone know what all that was about?

- Sunny G.

Re: 2013 Washington DC Regional
 

They won F1, but between F1 and F2, 2415 lost the image on their CRIO. In final F2, they could not function, and sat out the match. Their alliance lost. They continued to attempt to repair the problem, but were forced to call for a replacement bot. 3123 had already bagged their bot, but pulled it out of the bag at the side of the field to play match F3.

A crappy way to lose, and not an altogether satisfying way to win, but them's the breaks. Such is life in FIRST robotics. Learning from their pain, be assured that I'll be making sure we have a spare CRIO, flashed with the current software, available as a spare whenever we play future elimination matches.

Re: 2013 Washington DC Regional
 

How does a cRIO suddenly lose its image?

Re: 2013 Washington DC Regional
 

Beats me. I'm a mechanical guy. It's happened to us before, though. Everything's working, then suddenly not. Re-imaging, or downloading code, or something, fixes the problem. Maybe 2415 will be able to give a better answer as to what truly went wrong. I just happened to be in their pit right after the matches, taking pictures of their awesome floor pickup arm.

Re: 2013 Washington DC Regional
 

We had something like that happen at VCU last year...We didn't know if it was
the C-rio or the radio...it cost us a match. We changed both out and kept on going. In 2011 we lost the PDB and did'nt pack a spare....we lost out on two matches before we got a loaner....We learned from that and try to pack two or three spares of everything now This year we had a sidecar go bad at Palmetto....stuff happens. Kyle Johnson (who was a CSA at Palmetto and VCU
this year is a mentor for our team and could probably explain it more if he sees
this.

Re: 2013 Washington DC Regional
 

A cool thing about this regional, the wild card rule kicks in big time.

The winning alliance is 79, 379, and 383.

79 already won the Orlando Regional, and 379 already won the Queen City Regional. That means that the finalist alliance captain (2415) and first pick (116) get wild card invitations to the Championships. That takes away the sting a bit...

Re: 2013 Washington DC Regional
 

116 got E.I. also.....Dave must be very happy tonight.

Re: 2013 Washington DC Regional
 

I was so happy to see the Brazilians on the winning alliance after they were overlooked in their visit to Boston last weekend.
They come from so far away and don't have the local team support that we may be able to take advantage of.

Is there more to the story about the alliance selections?

Also glad about the two wildcards.

Re: 2013 Washington DC Regional
 

This. ? .

I'm a little rusty on the rules about the wildcard spots, but 2415 already has a championship spot with their Engineering Inspiration award at P'tree. Does this mean that their next team receives that invite?

- Sunny G.

Re: 2013 Washington DC Regional
 

Team 4466 would like to thank 1885, I LITE Robotics for graciously helping us by providing us with students for our team when the few students (except my son) that we had decided to quit at the last minute. They were the perfect example of what FIRST is all about. They provided us with 3 students for our drive team as well as students for our pit and mentors to help us out. Without them we would NOT have been able to compete.

The students they had helping us were great. I can only imagine how hard it must have been to compete against their own bot in the quarter finals. These same students have even graciously accepted our request that they join us at worlds to continue on as our drive team, even knowing that they will be competing against their own team yet again.

Thanks again! Without them we would have not gotten our spot at Worlds.

Re: 2013 Washington DC Regional
 

You are correct. 79, 379, and 2415 had attained wildcards previous to DC. That means all of the robots competing in the finals are going to the championships.

Re: 2013 Washington DC Regional
 

I'll allow Sean and whoever else from 2415 to elaborate on this, but 2415 also had cRIO issues at peachtree, which caused them to sit idle in a few matches. This time around, the issue was that it mysteriously dumped all of the code and wouldn't let them reload any of it. I think they've been through 2 cRIO's already, I'm wondering if it may be some sort of short in the way they are wiring the cRIO itself or the modules.

Re: 2013 Washington DC Regional
 

2415 also won E.I. at Peachtree so they were good on champs as well. I guess those spots (116 and 2415) go somewhere else now.

Re: 2013 Washington DC Regional
 

We didn't compete at this regional, but I came up to watch Saturday as a spectator for my first time since becoming a mentor. The experience was thoroughly enjoyable. I spent the morning mostly looking at robots in the pits, and picking up as many best practices as possible. Then, in the afternoon, the elimination matches were great!

Before going to bed, I wanted to get some video of the finals up on youtube. Enjoy it here.

Re: 2013 Washington DC Regional
 

Since there's already been a lot of talk of 2415's issues, I'll chime in what little I can. When preparing for F-2, their dashboard began indicating no code while tethered. This persisted after both redeploying code, and re-imaging the cRio.
At this point, the 5th seeded alliances' time-out had run out, and it was time to take the field for the 2nd finals match. The 2nd seed alliance opted to run 2v3, in the hope that 2415 could fix the issue before the 3rd match. 2415 spent the match and subsequent timeout replacing their cRio with a new unit, and then attempting to image and deploy code. Unfortunately this still didn't work, and the 2nd alliance was forced to call a back-up bot for the 3rd match.

2415 was an incredible competitor all weekend, and was a massive part of why the 2nd seeded alliance even reached the finals. They are a class act team with an awesome robot. It's unfortunate that the finals ended the way they did, but at least it's a memorable way to go out. Much of the elimination tournament is about survival, and an incredible alliance ended up coming out on top. 79, 379, and 383 deserve all the credit in the world.

Re: 2013 Washington DC Regional
 

Team 166 would like to thank teams 422, and 2642 for being the best alliance partners we could ask for! And we would like to congratulate teams 79, 379, and 383 on winning the regional. I think the quarterfinal matches we were up against you were the most exciting matches I have seen in a few years!

Re: 2013 Washington DC Regional
 

I'll chime in with what I know of what happened to our team so far.

The issue we had at Peachtree was not the Crio, but a line of code accidentally got deleted....::ouch:: ::ouch::

After F1 we tethered to do a systems check like always and completed one run of systems. During some discussion we decided to run one more to check a motor and thats when no code could be found in the "user command code area" (sorry im not a programmer or computer guy in any way.) We then redeployed code, formatted the crio, and re-imaged the Crio with no success.
After that we quickly got a new Crio thinking the old one had some type of failure and tried again. This had the same symptoms and 116 had to make the call to bring in a backup-robot.

We still have no idea what is going on with our robot, but after long discussions with the FTA after everything, we believe that our drive station may be corrupted and that caused both Crio's to be corrupted. We also believe the corruption may be in the Java virtual machine. We hav already started to port our code to C (based on this theory and other factors, this just gave us the push) to take a factor out. We figure less things running the better. We will shoot a update as soon as we figure out what happened.


Now, I want to say thank you to 116 and 4466 for their awesome play through the eliminations. It was a great run! 4466 may be a roockie, but they have one of the cleanest robots I have ever seen in FIRST. 116 made a huge choice to play F2 2V3 to give us more time to work our issues. Theses guys are a great team and it was a pleasure working with you guys. Thanks so much for selecting us to play with you. Also to the other alliances, these guys came over and offered help to get us back on the field. Class act!

The FTA, refs, robot inspectors, and volunteers were all a pleasure to work throughout the whole event, but even more so durring the troubles of the finals. They never said "you have 30 seconds and we are starting, we dont care what the problem is" like I have got at other regionals....but really worked with us trying to help and get us back on the field.

Thanks again to everyone and cant wait for championships:D

Re: 2013 Washington DC Regional
 

Semi-finals 2 video up here.

I love how 116 fires disks downfield from the feeder station so 2415 can pick them up off the floor. A much discussed strategy which I had not seen implemented until now.

Re: 2013 Washington DC Regional
 

116 was the second seed captan and 2415 was the first pick.

2415 was previously qualified, so their wildcard passes on (I think). 116 was not previously qualified, so their wildcard does not pass on. Wildcards are only given for teams that were previously qualified, not if a team double qualifies at a regional.

Wetzel

Re: 2013 Washington DC Regional
 

On behalf of Team 379, we would like to thank team 79 for giving us the opportunity to join their alliance. You guys had a great strategy and we never veered from it throughout the eliminations. We would also like to thank team 383 for their outstanding game play. Your floor pickup really made a difference by not congesting the feeder station or the playing field.

Also, congratulations to teams 116, 2415, 4466, and 3123. It was one of the craziest finals I've seen or been a part of. It really could have gone either way.

In regards to the wildcards, I believe they were granted to teams 116 and 4466 because 2415 had previously qualified.

This has been team 379's best season to date. With such a young and eager team of students, we are very excited for the future of this team. We hope to see some of our new friends at worlds and thanks again to everyone that helped make this happen.

Re: 2013 Washington DC Regional
 

Re: 2013 Washington DC Regional
 

It's not the very first time it's been played, but it was certainly more successful than our attempt at it.

Can't wait to watch all of these elims on youtube. 612, 2415, and 79 were all on super potent alliances. I think no matter what, 79 + Brazilian Team = Gold.

Re: 2013 Washington DC Regional
 

I had a blast at my last regional as a student, although now we on 422 have to hope that the wait list is kind to us after being eliminated by the eventual champions in the quarterfinals at both regionals we attended. Meeting Woodie Flowers, Dave Lavery, and Dustin Benedict was quite cool, given that the regionals 422 normally attends do not attract very high profile names, and Shan from 612 and Tom from 79 were both kind enough to put up with my ramblings during and after the competition.

We on Team 422 would like to congratulate to team 79, 379, and 383 for their regional championship, and thank them for an extremely exciting set of quarterfinal matches. The scores and defense our alliance put out would have won any other set of quarterfinals, but we could not top your deadly autonomous accuracy and consistency and your blazing fast cycle times.

A thank you to our alliance partners and friends 2642 The Pitt Pirates and 166 Chop Shop – you guys were amazing, and with a little smarter defense and more autonomous shots in QF2-2, we could've gone on to win the whole thing. It was great being on an alliance with both of you, as your drive teams are a blast to compete with. 2642 – you guys were simply amazing. Friendly and high scoring, we couldn't have asked for better partners. 166 – after competing with you in qualification 40, even though we lost by two points that would've made us the #1 seed, we knew that you guys would be our second pick regardless of our first pick. An ungodly 6 CIM drive train with blue nitrile treads and a consistent autonomous and hang coupled with a tough robot and very agressive drivers made a perfect second pick. In Qualification 40, you successfully pinned two robots behind our pyramid for a period of time, and generally made 2974 regret their decision to go mecanum. Great job.

One team I do not see congratulated here yet that undoubtedly deserves it is team 612. After the Virginia Regional, in which my team's drive chains snapping and comm issues kept them from going for gold in a close quarterfinal against teams 1541, 1262, and 1610, they came to DC ready to win the whole thing. Both team 612 and 422 made one significant change to our robots before this event – we added larger pieces of lexan to the feeding slide to our hoppers. In the strategy meeting at the end of day 1, a lot of teams were discussed – Team 79, 2642, and 116's fast cycles, perfect auto scores, and fast hang; Team 2630's full court shooter and adaptability; Team 2415's 7 disk auton and ground pickup – but the one team my scouts placed as the number one contender to win the regional, after analyzing a 3 inch thick binder of data, was team 612. When they put up a triple digit score in Qualification Match 2, everyone at the event knew that they were the team to beat. Because of a servo-shifting problem with their supershifters, they were unable to capture the #1 seeding spot, but still formed a very threatening alliance that averaged 123 points per match in elimination rounds. Because Virginia has not yet moved to a district system, their falling short of the finals has left them without a ticket to championship, and getting a judge's award cannot repay that. Although the trophies from this event didn't stay in the region, 612 has proved that Virginia is a competitive region without a doubt, and for that, I thank them.

- Harrison

Re: 2013 Washington DC Regional
 

I agree about 612, they could have been in the finals. SF2-3 could have gone either way if team 2630's battery cable wouldnt have came unplugged during the match which left them stranded at the feeder station.

Re: 2013 Washington DC Regional
 

Us at Area 53 had similar issues with our cRIO and radio, the cRIO gave an "out of memory" error, and we had to completely reset it. Our radio kept on disconnecting during matches, we're still not sure whether that was due to placement (not a very good call on our part) or what.

Re: 2013 Washington DC Regional
 

Oops. My mistake. The info was even posted earlier in the thread, and I looked right past it.

Re: 2013 Washington DC Regional
 

Congratulations Team 1885 for winning the Washington DC Regional Chairman's award! Team 384 cant wait to see you in St Louis! :D

Re: 2013 Washington DC Regional
 

Exactly what I was thinking of 612. Excellent robot. When they paired with 2630 (which I honestly thought would be picked sooner than 3 - they lost the 3 games they did 'cause of some communication issue, and when they played, it was really goodlike you said above) I was pretty sure the alliance would at least make it to the finals.

Shame 2630's robot stopped working during that 3rd SF game. It was only 6 points at the end, and their robot proved that it could score consistently (they were defended well too, not sure by which robot, but it did a great job).

All said and done, 2630 were already guarenteed to STL after the Israeli regional. Shame 612 could not make it. They really had a good robot. One of the best in DC this year... I felt like they deserved to go :(

And at last, congrats to the winning alliance. They were impressive all through the elim's. Well done also to all the other teams going to STL, if through awards, or if through WC. HAVE FUN!!

Re: 2013 Washington DC Regional
 

Great videos, thanks.

Re: 2013 Washington DC Regional
 

I had a great time at the DC regional, and hope we return next season. The teams that attended were top notch, and I'm looking forward to compete against a few of them again in St. Louis.

To my knowledge, our cRio problems has yet to be solved. Like Andrew said, the issue has baffled students, mentors, and volunteers alike. A big thank you to everyone that came over to help, including members from both our alliance, the opposing alliance and the wonderful volunteers and FTAs. It's a bummer we couldn't get our problems sorted out in time; 2415 would've loved to play with our alliance partners for another two matches.

Speaking of alliance parters, another thank you needs to go out to 116 and 4466. I was honestly shocked that 4466 wasn't picked sooner. The robot looked as if it was made by a seasoned veteran team. Similarly, 116 was a fantastic alliance captain, but that was to be expected. :p

I can't believe I have to trudge through 2 complete weeks of school before St. Louis. Looking forward to seeing some of you there,

-B.

Re: 2013 Washington DC Regional
 

:) And you know what? They were both great teams to work with. The real funny part is that both 1772 and 383 are from the same area of Brazil and do kickoff together.

But, we can't forget about 379 either, without their rain of two pointers we could not have done what we did. (And for the record, in case people missed it, they can shoot 3's but since 383 and 379 both had the same preferred shooting spot for 3's but 379 felt comfortable shooting 2's it was decided to have them run 2's unless the spot was clear).

2415 — I'm sorry about what happened and that we couldn't help get it sorted out. If you need anything you guys know how to reach us.

1885 — Congrats on the RCA win, good luck in St Louis. Your outreach efforts are astonishing.

116 — Great job on the EI and on constructing an incredible alliance, I'm sad we never got to play with both alliances at 100% strength. That would have been some exciting play.

It was a blast meeting new teams in DC this year. I know it'll be a regional 79 always remembers fondly.

Re: 2013 Washington DC Regional
 

That event totally blew the pants off of any other regional I've ever been to. At least 30 of the robots there would make eliminations at any given regional, and I would say at least 16 teams there are Championship worthy. I would like to say a few things.

-This was probably the most competitive regional of the weekend. It wasn't the event with the best teams, but there were so many good robots on the field at once, and high scoring matches were decided by fewer than 12 points (a perfect cycle multiple times. Having 82 and 85 point ties was unbelievable. The fact that scoring 132 points can't give you a close win is insane. I loved it.

-Everyone there was so nice. The volunteers I got to work with (until I coughed up a lung Friday night and was under orders to sleep off my cold), all of the teams, staff, speakers... I guess I'm going to to probably end up at more than 3 events next year, and I'm more than ok with that.

-Even though the tournament winners aren't from the National Capital Region, don't dismiss the National Capital Region. 79, 379, and 383 lit up the court and deserved to win, but it's a crime that 612 isn't going to St. Louis. They can (and have) put up better numbers than over 95% of other teams in the sport. It's unfortunate the Wild Card can't account for a team that excelled all season but couldn't fry the big fish. I hope to see them wiping the floor at some offseason events if the CMP waitlist is unkind to them as much as fate has been.

-I'm really proud of my old team, 422. When I joined the team as a freshman, we went to our away regional and we were just a dozen dudes and some parents on a trip that was a financial impossibility. We had a robot and a prayer. 5 years later, 5 dozen students, parents, grandparents, dedicated mentors, alums, aunts, uncles, brothers, sisters, sponsors both current and potential, VirginiaFIRST board members, and friends traveled up to 3 hours away just to get a glimpse at what the team has done. It doesn't look like there's any real big hardware in store for the team this season, but it's so rewarding to see the jarring evolution of the team over the last five years, and I can't wait to watch the next five. 422 comes from a government and social sciences school in the inner-city of Richmond and it's getting people from all all walks of life to care about what the team does. So many people are investing so much time and money into the 30-odd students because they see their booming potential becoming a reality.

Re: 2013 Washington DC Regional
 

Thanks for the compliment. The bot that defended against 2630 was our robot. (4466)

Re: 2013 Washington DC Regional
 

2415 programmer here in response to why our robot could not compete in the last two matches. I'm trying to figure out the same thing, but here's what we know:

- After our last match we attempted to do a systems check and we noticed that the our robot was communicating (i.e. we could ftp it, and the little light on the driver station that says communication was green), but there was no robot code (the driver station light was red).
> We know that the code was lost between the time of our last match,
> and the next time we turned it on.

- We then tried reimaging the cRIO. It didn't work. We got a spare cRIO from the spare parts table and reimaged that. This time, the code loaded up once and crashed. We were excited because the error we got was IOException, which means there was a file that our code was referencing that we didn't put on it. We loaded our file, rebooted the code, and all of a sudden we couldn't see the code (driver station light was red).
> Now that I think about it, that has to mean that there was an
> issue with our code if it was able to load up once. I'm not sure
> why it worked until now though.

At that point we had to forfeit.

Some other details:

- We use java image version 47.
- We use SmartDashboard. It's been somewhat glitchy, and I've heard
others having issues with it.

If anyone has a clue what could be going on, hit me up. At least writing all of this out helped me think it through.

Re: 2013 Washington DC Regional
 

Team 611 actually had a similar problem to 2415 (albeit not right before a finals match). We discovered about 10-15 minutes before our 4th qualification match that the status light on our cRIO would flash twice every few seconds. After having the imaging tool failing to image our cRIO multiple times while we were queuing, we ended up having a dead robot sitting on the field. After the match, Miles, a volunteer at the DC Regional, helped us repair our cRIO. After a little tinkering with the IP settings in MAX, we were able to reimage the cRIO and recompile our code and everything seemed to be working fine.

We still don't have any idea what caused our cRIO to fail between matches when the robot was powered off.

Regardless, it was a great regional and a great season. I'm actually surprisingly sad to see this one end.

Re: 2013 Washington DC Regional
 

Hey, a 612 student here,

First off, thank you so much to team 422, It was a delight working with you at VCU and DC, and we hope to see you again next year to continue passing on our friendship block...chunk...thing.

And a huge thank you to everyone who recognized our team in other posts in this thread. We had a challenging season, and the DC Regional was a final accumulation of all our hard work. To see you, our fellow FIRSTers recognizing that means as much to us as any award. Your posts have already been shared around our team, and I cannot say how happy they have made us.

That said, there were so many great teams at DC this year, this is a region to watch. 612 had a great time, and we're sad it's over, but the FIRST spirit is still here.