**FIRST EMAIL**/Invitation to Beta test the New Control System

[Jon236]

Since the Beta Test Teams will have a copy of the beta template including sub-vi's, I hope this will be posted so that all of us can become familiar with the code.

[Joe Ross]

I put together a quick map of all the beta test teams.

I think the closest teams geographically are 340 and 1114, but there is that pesky thing called a border between them. Other then that, there seems to be at least around 300 miles between beta test teams.

[Travis Hoffman]

Originally Posted by Joe Ross

Other then that, there seems to be at least around 300 miles between beta test teams.

Originally Posted by rftgnow

we plan to demo at TNT, Mission Mayhem and Robot Rodeo

Originally Posted by garyk

We (668, Apes of Wrath) will be showing the beta system at CalGames, Oct. 25, 2008 at Archbishop Mitty High School, San Jose Calif.

I mentioned this before, but now that the teams have been announced, I think it bears repeating.

My apologies if this is already a part of beta tester plans, but well, I don't know that yet. I expect the beta testers will soon share their plans to deploy information to the rest of us.

I'm sure this is obvious, but the vast majority of FRC teams will not be able to attend local offseason events or any demos or seminars beta test teams may hold at their facilities. Posting videos online, and enabling online access to your most beneficial informational sessions (via live webcast or videoconference, if resources permit; additionally, via video or voice archiving after the fact) would serve the greater community at large.

Joe's map illustrates the large gaps that exist within the beta tester net (all of Illinois, Indiana, and Ohio is one such gap). Such gaps are inevitable given the limited number of control systems available. As beta test teams are out of physical reach of most of the FRC community, I encourage you to use Internet multimedia to bring remote teams closer to you and make the online learning experience almost as good as being there.

Of course, substance is much more important than style, and time is of the essence, so I will forgive y'all if the presentation of the online resources is a bit rough around the edges, as long as the core content is meaningful. You can always "make it pretty" later.

Good luck, and thanks to all who are taking up this challenge for the betterment of all.

[DonRotolo]

Originally Posted by BrianT103

Team 103 is honored to be selected as one of the beta testing teams. Over the coming weeks we will be posting updates, on a separate thread as to what types of meetings and seminars we will be hosting to educate the surrounding teams.

In this case, the people making the decision have chosen wisely.

From my point of view, all it means is that I'll have to drive a bit further to visit. Please be sure to post somewhere a list of when you'll be meeting, and where, as you should expect frequent visitors. Matter of fact, all the beta teams really need to do this.

Some teams won't be able to visit, so beta teams, please post videos, photos, words, whatever - let's stretch communication technology a little here! - so the rest of us can see just how good you really are...

Don

[ATannahill]

We will post information online, including our software (labview). Other useful information like guides and probably media will be posted. From all 18 teams most resources and topics will be covered.

[Karthik]

Just a reminder to all Beta Test teams. In order to get your controller you must sign the FIRST disclosure agreement. This form "indicates your team agrees to disclose information on the new control system when FIRST gives permission to do so during the beta testing process and not before." (Bolding added for emphasis). So before you start making plans on when and where you plan on holding seminars, remember that we have to wait until FIRST authorizes us to release information. I just don't want anyone putting their cart in front of their horse.

[Libby K]

Originally Posted by Karthik

Just a reminder to all Beta Test teams. In order to get your controller you must sign the FIRST disclosure agreement. This form "indicates your team agrees to disclose information on the new control system when FIRST gives permission to do so during the beta testing process and not before." (Bolding added for emphasis). So before you start making plans on when and where you plan on holding seminars, remember that we have to wait until FIRST authorizes us to release information. I just don't want anyone putting their cart in front of their horse.

Karthik's post needs repeating. FIRST is very serious about disclosures, and the beta teams should remember not to put any information out before they're allowed to- or they could lose their test system. That doesn't benefit ANY of us here.

So, remember...
disclose information on the new control system when FIRST gives permission to do so during the beta testing process and not before.

[BornaE]

Originally Posted by Jon236

Since the Beta Test Teams will have a copy of the beta template including sub-vi's, I hope this will be posted so that all of us can become familiar with the code.

We might not be allowed to publish the codes when we get it. But as soon as we have the permission to publish it, I would be happy to do so.

[Aidan F. Browne]

Thanks to the WFA committee for processing a crazy number of beta applications and narrowing it down to a great list of 18 -- it could not have been easy.

And, congrats to the 18 beta teams! If there are gremlins in the system, we, the FIRST community, will deal with them.... you just need to find them for us. Now go forth and test, test, test!