|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: [FRC Blog] Einstein Report Released
Quote:
The longer the secret is kept, the better. If the team name never is revealed other than mumblings at regionals(ie. "Yeah I hear it was that mentor for team XXXX"), then that is even better. Also, has anyone considered the possibility that the team themselves don't even know about it, and that the perpetrator is passing it off as leaving for other reasons? Part of me wants to view that as a case, but part of me has reasons why that wouldn't work (how would FIRST get into contact with the individual other than through the main team contact? unless that person kept it a complete secret/between them and the perpetrator). |
|
#2
|
|||||
|
|||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
Quote:
Quote:
|
|
#3
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
I hope that hailstorm doesn't come to them. To what you did say, of course they will be mad, and justified in being so. Last edited by Ekcrbe : 15-07-2012 at 00:38. |
|
#4
|
|||||
|
|||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
|
|
#5
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
I challenge the FIRST community to be above this and avoid putting this stigma on an unfortunate team and consider everyone in this team's influence innocent until proven guilty. There's no guarantee the perpetrator acted alone, but it would be even sadder and stranger to find a cast of co-conspirators. I doubt this will be the case.
|
|
#6
|
|||
|
|||
|
Re: [FRC Blog] Einstein Report Released
Did anyone from 1717 get to formally investigate with FIRST the cause of their issues during division eliminations?
Seems logical to look into their case as well as other communication issues during eliminations at Champs, albeit, probably without inviting all teams to Manchester it might be difficult. At least it would give these other teams piece of mind as well knowing that it is not solely some issue with code/electronics that caused their issues during elims. Last edited by Akash Rastogi : 15-07-2012 at 01:55. |
|
#7
|
|||
|
|||
|
Re: [FRC Blog] Einstein Report Released
Quote:
And does anyone else think it might be beneficial(or in some ways detrimental) to have two topics of discussion for this ne political, one technical. Or would that just draw too much attention to the political stuff/become a battleground?Last edited by Steven Donow : 15-07-2012 at 01:12. Reason: Android chief Delphi is not kind |
|
#8
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
Suppose the perpetrator leaves the team because of graduation? The "individual" was not identified in the FIRST Einstein Investigation Report as being a mentor nor student. Wouldn't the FIRST community would be more forgiving if this was more like a teenage "stunt" rather than an attack on sportsmanship and GP by a team leader? If a mentor did this, the team involved likely would suffer irreparable damage to their reputation. Last edited by David Brinza : 15-07-2012 at 06:31. Reason: Grammar |
|
#9
|
|||||
|
|||||
|
Re: [FRC Blog] Einstein Report Released
Good work on FIRST and all volunteers and afflicted team's parts with their swift and thorough analysis.
Good work on catching the issues with smart dashboard. Good work on 118's part in identifying their own issue with their gyro reset loop. Good work on 118's and volunteers parts again for working to identify the issue with their vxworks network buffer being overrun following the cessation of normal crio code activity. Good work on all parts reminding us that its probably best that our cRios never run at 100% utilization, and that its perfectly plausible to not hit 100% doing all sorts of complicated logic, whether you're running c++, java, or labview. Good work on deciding to limit team bandwidth moving into the future, our applications are only going to get greedier with time and we need to have a cap. Good work spotting all wiring problems that were in fact present with several of the playoff teams. And good work and god speed in all future efforts in securing the field against any external interference, be it intentional or not. The only secure network is one that's disconnected, but we can all (and I'm sure will all) do our best to improve the quality of experience for all FIRST teams. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|