**FRC EMAIL**/Announcing Beta Test Teams

[Beth Sweet]

Joe, that map is really interesting. The "greens" (Java) seem to be east and west coast, while "blues" (C++) seem more concentrated in the upper mid-section (only US analysis). Wonder why that trend is? (I'm sure it's based on who applied for what, but it's interesting...)

[blayde5]

Hello from Team 115, many of us are actually really surprised we got it but nevertheless, we'll help FIRST to the best of our abilities.

It's also weird we're the only NorCal team for beta testing...

Good luck to all teams !!

[biojae]

Now, which teams get to beta test the hardware?
How many devices will be distributed to the beta teams?

[Chris is me]

Originally Posted by biojae

Now, which teams get to beta test the hardware?

All of them.

How many devices will be distributed to the beta teams?

Probably a complete (beta) driver's station / cRIO / etc, if it's anything like last year. We didn't get to keep them though (we even had to return the jumpers and Ethernet cables!) without paying for all of the non-FRC-legal beta parts.

[Joe Ross]

Originally Posted by biojae

Now, which teams get to beta test the hardware?
How many devices will be distributed to the beta teams?

Originally Posted by Bill's Blog

Some of these Beta teams will be tapped to test hardware as soon as the elements become available.

I believe this will be different then last year. Teams already have a cRIO and all the required hardware. Some teams will be asked to test any new hardware (classmate PC, and anything else), and some will only be testing software. They have not said yet how the teams that will test hardware will be selected.

[Chris is me]

*notes down that post as my Bi-Weekly Chief Delphi Mistake*

I'm wondering exactly what software wise we could test without an (accurate) DS for C++ that we otherwise wouldn't know from 2009 build. That is, unless they activate stuff we didn't have access to on the cRIO last year...

I guess that means my team's spare cRIO will be shared between a swerve chassis group and a beta group then.

[biojae]

Originally Posted by Chris is me

I'm wondering exactly what software wise we could test without an (accurate) DS for C++ that we otherwise wouldn't know from 2009 build. That is, unless they activate stuff we didn't have access to on the cRIO last year... .

The drivers station should not require a huge amount of change on the cRIO side, the change is hopefully transparent
if not, then a trip to the closest team with the new DS may be in order

[alivemyst]

A couple of thoughts:
This year Beta test teams won't have much to test in the way of new hardware, and will be mostly concerned with making sure new and existing libraries work appropriately. I was a bit disappointed with the fact that FRC expects teams to recycle the cRIO--while understandable because of its enormous cost, it will incapacitate older robots which veteran teams like to maintain for demonstration purposes.

Also, unlike last year's beta test, this year the Java Beta test involves software that is entirely opensource, and can actually be acquired by anyone at this point in time, should you know where to look. Sure they are prerelease, but I can confirm that they work.
At the very least having the documentation available to all teams as it is(once again, loook around carefully--its easier to find than the source), should give everyone interested in using java plenty of opportunity to train on the system.

[lynca]

Originally Posted by blayde5

It's also weird we're the only NorCal team for beta testing...

I would also like to see how they mapped out the teams. In Texas we have two teams from Houston as Beta testers.

Has anyone made a map of all the different Beta teams ?

Random sidenote:
The DiscoBots (2587) applied but were not accepted. I believe this is because the high # teams get much less respect in FIRST. I would be interested in the number of +2000 number teams that applied for Beta.

[ATannahill]

Originally Posted by lynca

I would also like to see how they mapped out the teams. In Texas we have two teams from Houston as Beta testers.

Has anyone made a map of all the different Beta teams ?

Random sidenote:
The DiscoBots (2587) applied but were not accepted. I believe this is because the high # teams get much less respect in FIRST. I would be interested in the number of +2000 number teams that applied for Beta.

2974 Team WALT and 3006 West High FIRST Robotics were accepted as rookies. I do not think that FIRST discriminated against teams by number. 2753 were on Einstein this year and did great. Numerous teams under 500 did poorly this season. If a team is not selected they should be active on the First Forums and learn as much as they can about the system from the beta testers.

[Chris is me]

Originally Posted by lynca

Random sidenote:
The DiscoBots (2587) applied but were not accepted. I believe this is because the high # teams get much less respect in FIRST. I would be interested in the number of +2000 number teams that applied for Beta.

I doubt it is based on number, but a lot on notoriety and history with demonstrations, quality robots, reliability, etc. FIRST tends to know Hall of Fame teams, long standing veteran teams, etc. will be able to do this (not saying Disco Bots can't, I'm sure FIRST just didn't realize how you guys could help the beta test program). If there is someone with more notoriety in those areas very close to your team's region then they were probably picked over you.

Pardon me for tooting my team's horn, but my team has a long history of building reliably-programmed robots (not necessarily competitive :/) and does hundreds of demonstrations a year, plus my team had a successful year beta testing in 2008, so that's probably why my "high number team" got picked. Other teams likely have much the same story; notoriety in these fields makes them more likely to be picked. It's a shame as there are excellent teams that get overlooked (right off the bat I know team 2502 would be perfect for beta testing).

The short version is that teams don't get respect by their number, but by their reputation. Low number teams just have had more time to establish themselves.

[Akash Rastogi]

Originally Posted by Chris is me

I doubt it is based on number, but a lot on notoriety and history with demonstrations, quality robots, reliability, etc. FIRST tends to know Hall of Fame teams, long standing veteran teams, etc. will be able to do this (not saying Disco Bots can't, I'm sure FIRST just didn't realize how you guys could help the beta test program). If there is someone with more notoriety in those areas very close to your team's region then they were probably picked over you.

Pardon me for tooting my team's horn, but my team has a long history of building reliably-programmed robots (not necessarily competitive :/) and does hundreds of demonstrations a year, plus my team had a successful year beta testing in 2008, so that's probably why my "high number team" got picked. Other teams likely have much the same story; notoriety in these fields makes them more likely to be picked. It's a shame as there are excellent teams that get overlooked (right off the bat I know team 2502 would be perfect for beta testing).

The short version is that teams don't get respect by their number, but by their reputation. Low number teams just have had more time to establish themselves.

It was not about history. It was about the application, the mentors available, the skills available (hell, 1089's main mentor IS a JAVA teacher XD), and resources available( this usually comes with age). History was a small part of this but clearly not a priority.

Lynca, I too am a little surprised your team was not chosen based purely on proven skill of mentors/students and resources but perhaps this wasn't represented in your application, who knows. But then again, a lot of others were surprised as well. You would have been a great Beta Tester btw.

[lynca]

Originally Posted by Chris is me

The short version is that teams don't get respect by their number, but by their reputation. Low number teams just have had more time to establish themselves.

I agree with your statement. However, if you have two teams with equal reputation, most people will give the lower number team the benefit of the doubt.

Sorry about by random sidenote turning into a major discussion point on this thread. My team is very happy to have two Beta Testers selected in our area (Houston), much better than zero Beta testers last year !

Back to my original question ?

Originally Posted by lynca

Has anyone made a map of all the different Beta teams ?

[ttldomination]

I agree that it's tough for higher number teams but I mean there are teams that have done it.

2974 Team WALT
3006 West High FIRST Robotics

But it is harder for higher number teams because it's harder for them to properly establish themselves.

[rfolea]

Originally Posted by ttldomination

I agree that it's tough for higher number teams but I mean there are teams that have done it.

2974 Team WALT
3006 West High FIRST Robotics

But it is harder for higher number teams because it's harder for them to properly establish themselves.

Hey ttlD - you are welcome to come over and help ...