2013 Washington DC Regional

[santosh]

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

[Akash Rastogi]

Originally Posted by santosh

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

I gotchu Santosh.

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

[Bochek]

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.

[bearbot]

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

[mizscience]

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

[mizscience]

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

[buildmaster5000]

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.

[Lil' Lavery]

Originally Posted by mizscience

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

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

[ttldomination]

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.

[ToddF]

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.

[Jared Russell]

How does a cRIO suddenly lose its image?

[ToddF]

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.

[mrmummert]

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.

[ToddF]

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...

[Sam C.]

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.