FIRST is really looking into the Einstein problems

[daniel_dsouza]

connection problems happen to even the most prepared...

http://www.youtube.com/watch?v=znxQO...feature=fvwrel

if you are in a hurry, go to 1:33.

[qzrrbz]

Originally Posted by daniel_dsouza

connection problems happen to even the most prepared...

http://www.youtube.com/watch?v=znxQO...feature=fvwrel

if you are in a hurry, go to 1:33.

And they figured out what was happening ... ~500 wi-fi base stations in the crowd, and the phone couldn't handle that. When they had the crowd "dim" the base stations, it worked. Hmmm...

[Jim Wilks]

It's now been over a month since the re-enactment of the Einstein saga. Not a word from FIRST since the last email stating they "needed a few weeks" to analyse data.

I maintain that if they had found something concrete they would have shared something about it.

[Mark McLeod]

Frank mentioned it again last week.

Originally Posted by FRC Blog

Thursday, July 5, 2012

Where’s the Einstein Report?


Hello Teams,

I’m sure you’re wondering what the status is of the Einstein report. I can tell you that our internal staff, with a great deal of support from our outside experts and the Einstein teams themselves, have been working very hard on this. The current draft report is over 20 pages long, and includes lots of detail. Getting all these details right is taking some time, but we hope to have a final version ready for release shortly.

I did want to share with you a photo taken during Einstein Weekend, June 9-June 10th. That’s a great deal of talent represented in one place at one time, all working on a common cause!

Frank

[CalTran]

Originally Posted by Mark McLeod

Frank mentioned it again last week.

It's good to hear that they're making progress. Probably not the progress some people are looking for, but they're not going to bust the entire wireless problem in 2 days of official testing.

[Al Skierkiewicz]

Everyone,
The report is getting very, very close. Bill's departure has added to the workload a little at HQ.

[linuxboy]

Originally Posted by Al Skierkiewicz

Everyone,
The report is getting very, very close. Bill's departure has added to the workload a little at HQ.

Excuse me while I go obsessively check the FRC Blog every few minutes.

[billbo911]

This is from the introduction to the PDF containing the results of the testing.

Additionally, Einstein match play suffered from an intentional act of interference.

I'm too stunned to say more!

[Alexa Stott]

Thread about the report here: http://www.chiefdelphi.com/forums/sh...d.php?t=107285

[Jim Wilks]

Read the report in detail.

Lots of "might haves" and "possiblys". No real root cause whatsoever identified. The mystery lives on.

[Zach O]

Does anyone have information on what "custom electronics" 118 had an issue with?

Edit: Got the answer. I assume it's the BeagleBone.

[Alexa Stott]

Originally Posted by Zach O

Does anyone have information on what "custom electronics" 118 had an issue with?

Edit: Got the answer. I assume it's the BeagleBone.

That's all in the report. And, yes, some of it was the BeagleBone. Some of it was a bad gyro. The two worked together to create something of a perfect storm for a communication failure.

[Bruceb]

This from FIRST

Dear FRC Teams:



Thank you for your continued support as we conduct our examination of issues surrounding the Einstein matches from Championship.



This past weekend we duplicated, to as great an extent as possible, conditions as they were on Einstein in St. Louis. All Einstein robots and one to two representatives from each team were present. Matches were run in the same order, with teams in the same driver stations, as at Championship. In addition to 1-2 representatives from each team and FIRST staff members, highly respected independent experts and key volunteers participated in and contributed to the evaluation. Additional specialized tests were also conducted.



The FIRST staff were in awe of the Gracious Professionalism exhibited by all participants. At each turn, teams illustrated camaraderie – loaning parts, helping carry and set up others teams' robots, and even helping drive competitors’ robots when necessary.



We have learned a great deal, and have much more to learn. With the large data set to be analyzed, and a few additional tests still planned to be run, it will be several more weeks before we are prepared to draw and share our initial conclusions.



We have asked all weekend participants not to disclose details concerning weekend testing until our additional testing, results and initial conclusions are available to the entire community. The FIRST Engineering staff, with support of the external experts and the FIRST community experts are working with all deliberate speed on their analysis and recommendations. We understand everyone's desire to hear initial results and appreciate your continued patience.



Please continue to provide your experiences, thoughts, questions and concerns as we move through this process. We are checking the 2012frcfeedback@usfirst.org in-box and teams' input has already played an important role, including being the inspiration for some of the specialized testing we performed this past weekend.



Sincerely,



Jon

[Jim Wilks]

Originally Posted by Bruceb

This from FIRST

We have asked all weekend participants not to disclose details concerning weekend testing until our additional testing, results and initial conclusions are available to the entire community. The FIRST Engineering staff, with support of the external experts and the FIRST community experts are working with all deliberate speed on their analysis and recommendations. We understand everyone's desire to hear initial results and appreciate your continued patience.

I always see the "not to disclose details" card played when things didn't go well. I guess there was no aha! moment when the problem showed itself again. If there was truly good news, it would be shared immediately.

Just my $.02 worth.

[IKE]

Originally Posted by Jim Wilks

I always see the "not to disclose details" card played when things didn't go well. I guess there was no aha! moment when the problem showed itself again. If there was truly good news, it would be shared immediately.

Just my $.02 worth.

Or if you have a few likely contributors that you are trying to sort out. Or if you have a problem that you can have a solution to shortly. Or if you have a problem with no current solution and feel you need a proposed solution before you scare teams into not competing or...

There are a whole lot of reasons to not prematurely release ideas/data/anedotes. This reminds me of a neat story I read in WIRED a few years back.