FIRST is really looking into the Einstein problems

[Steven Donow]

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.

Yeah, as people already said, I don't think that's an accurate conclusion to jump to. It could easily be, "We think we may have found the issue, but we're not certain that's the issue, so we don't want people to say it's the issue, then have everyone get their pitchforks out when that's not the issue" or something along those lines.

[Jon Stratis]

When we have an issue in production, my manager doesn't just want to know what happened. He wants reliable, reproducible testing AND a fix proving we identified the correct answer before he'll disseminate information to other parts of the organization. Saying you found the issue and coming back a week later and saying "just kidding" is about the worst thing an operations team can do.

[Al Skierkiewicz]

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.

Jim,
This could not be further from the truth. I just managed to get my preliminary reports (qty. 14) filed yesterday afternoon. They were likely the easiest to compile but were needed by others to complete their work.

[Peter Matteson]

Originally Posted by Jon Stratis

When we have an issue in production, my manager doesn't just want to know what happened. He wants reliable, reproducible testing AND a fix proving we identified the correct answer before he'll disseminate information to other parts of the organization. Saying you found the issue and coming back a week later and saying "just kidding" is about the worst thing an operations team can do.

We are the same way where I work. We review with a team of engineering fellows along the way to make sure we haven't gotten off track at each step during the DIVE process. (Define, Investigate, Verify, Ensure)

If you during your investigation that you don't verify the cause of the problem you can't ensure it won't reoccurr. I would want to make sure my data supported the conclusions before they were published, and preferably have a working solution.

[qzrrbz]

Originally Posted by Peter Matteson

We are the same way where I work. We review with a team of engineering fellows along the way to make sure we haven't gotten off track at each step during the DIVE process. (Define, Investigate, Verify, Ensure)

If you during your investigation that you don't verify the cause of the problem you can't ensure it won't reoccurr. I would want to make sure my data supported the conclusions before they were published, and preferably have a working solution.

If you look at this as an "academic problem", you will come to a similar conclusion. It is very much looked upon badly if you publish in "the popular press" before you do so in a refereed technical journal!

[EricVanWyk]

Earlier this week it took me a little bit too long to realize that the reason my pen wasn't writing correctly was that it was actually a screwdriver. I'm going to have to ask for a few nights of honest sleep before signing off on a report.

[Astrokid248]

Originally Posted by EricVanWyk

Earlier this week it took me a little bit too long to realize that the reason my pen wasn't writing correctly was that it was actually a screwdriver. I'm going to have to ask for a few nights of honest sleep before signing off on a report.

Ouch! Yeah, go catch some sleep, get a massage, have a few adult beverages. No need to kill yourself over this. Just remember that for all our whining and complaining, we actually do appreciate all your hard work and incredible effort. (That goes for anyone else present at the testing too.)

[JaneYoung]

In some ways, I think it's easier to be a NEM (non-engineering mentor) in this situation and to trust and support the process that has begun, lacking the technical expertise to fuel impatience and frustration. I have great respect for everyone involved and everyone that has to patiently wait for news and updates.

We'll get through this as a community, this we know.

Jane

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