|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools |
Rating:
|
Display Modes |
|
#61
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
Quote:
Quote:
|
|
#62
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
After thoroughly reviewing the report, I have come to two conclusions:
1) FIRST did an incredible job of researching all of the factors that went into what happened on Einstein. 2) Any team, regardless of experience and ranking can have those simple little problems that could contribute to larger problems such as what happened on Einstein. Regardless of whether or not the code and electrical problems were the root cause of the Einstein failures, each and every team should review this document and ask themselves whether or not they might have similar electrical/programming problems. Loops without sleeps and bad crimps are problems that are easy to look for in your robot, but not necessarily easy to diagnose. If teams add these to their list of things to check on their robots during the build season, we can help ensure that robots are running to the best of their ability. Should any further malicious behavior take place, removing these problems as a potential source will assist in troubleshooting as well. |
|
#63
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
|
|
#64
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
While I still read, I think I should note to anyone who has hard feelings against 1114 or another successful team: what the heck are you gaining by beating someone else down? What would inspire you to go out of your way to see someone fail (the real kicker being you get nothing in return save for some personal satisfaction)? A bully beating up a bunch of kids in the FIRST playground is frankly depressing. I don't visit FIRST and FRC affiliated web sites to become depressed.
To make things a bit more light-hearted, I hope this act doesn't delay any development of SimPhone on Android. My Galaxy Nexus is a tame soul. It's letting me thumb through the report and push the link to some students on other teams. |
|
#65
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
Furthermore, we should set the bar pretty high for characterizing an individual's intent to be "malicious". The words in the report and Jon Dudas' letter are insufficient to support that conclusion. We don't know the individual's motive or intent. |
|
#66
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
Also, since there were issues outside of Einstein it sort of makes sense that there could be other ways this might happen that aren't quite so badly intentioned. Last edited by techhelpbb : 13-07-2012 at 20:47. |
|
#67
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Oh man, I have never seen someone roasted so hard on CD.
Just stop and think for one second. You know there's an issue, and you know the people who can fix it. But, instead of acknowledging the issue, they tell you to go away? Then, you're determined to show them that this issue is real, and that it matters. All you can think of is proving them wrong and proving yourself right. So then you take actions that aren't good, but in your mind, they will serve a greater good. In my short few years being around people, I've met a handful of people who are utterly brilliant but they have no social awareness and a lack of ability to see consequences. These people are nailed as socially awkward, but in their mind whatever they are doing, however they are doing it, is perfectly right. Did this person interfere intentionally? Yes. Do I believe that this person had malicious intent at heart? No. Do I believe that the person has been adequately punished? Yes. Additionally, I cannot even begin to imagine how team 1114 and their alliance partners currently feel, however, I believe that making a public apology is not the right path. The internet is the internet, and FIRST is FIRST. By publicly revealing himself/herself and the team, they leave themselves open to emotional, and possibly physical, harassment. I am not condoning these actions, I am not condoning this person. However, without knowing all of the facts, I cannot support any action that would possibly bring this person any more harm. - Sunny G. |
|
#68
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
|
|
#69
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
There could also have been some other factor at work and let's hope it's one of those acknowledged within the report because a large amount of cost and effort went into this after the fact. |
|
#70
|
|||
|
|||
|
Re: [FRC Blog] Einstein Report Released
Quote:
Some friend of his found a flaw in the City of Toronto's (IIRC, big metropolitan centre anyway) traffic light control system. Tried to tell city council and they ignored him, blew him off. So he turned every traffic light red in the city for several minutes. When they came after him? He said "Be thankful I didn't turn them green." |
|
#71
|
|||
|
|||
|
Re: [FRC Blog] Einstein Report Released
Quote:
I'm impressed with the detailed report and the handling of the situation by FIRST. Can't wait to get my hands on the FMS white paper! As to the "interferer", I see his actions "accidentally intentional". From my understanding of the report, he simply tried to connect to the robot and provided an incorrect network password. I've seen robot networks on my mobile device many times, and tried connecting to it in the shop out of curiosity. Nothing really happened in that environment, but I'd give him the benefit of the doubt and call it a case of curiosity killed the cat. After all he did come forward. Last edited by Brandon_L : 13-07-2012 at 21:17. |
|
#72
|
|||||
|
|||||
|
Re: [FRC Blog] Einstein Report Released
I'm going to keep my personal feelings on the shelf for a while. I need to give it some time before I address more... unsavory... aspects of the situation.
But, what I am overjoyed to say, is FIRST did an amazing job at covering the situation. When I opened the document, I expected a 4/5-ish page summary report of what FIRST had been doing with the Einstein teams the past few weeks. I was pleasantly surprised to find an extremely long, fully detailed report of EVERY test and analysis run by FIRST. Bravo, FIRST. Bravo. You owe us nothing. Yet you went through everything for us. You guys rock! I'll leave it with this. Do we really need a pound of flesh? Just sayin'. |
|
#73
|
||||
|
||||
|
Re: [FRC Blog] Einstein Report Released
Quote:
We can't assume that the person involved is any more guilty than a hypothetical weird wiring issue on the field. We don't know if they were the only one doing this at all. We don't know if they fully understood what they were doing. We don't know how it was if they were trying to fix it they were dismissed. I can't feel the need to ruin what could be some person's life when these teams will continue and have more chances to make it that far. Besides this is perhaps one of those stranger and more memorable moments where the memory of the participation is more valuable than the dusty trophy. I'm sure a great number of us won't soon forget what happened. Last edited by techhelpbb : 13-07-2012 at 21:15. |
|
#74
|
|||||
|
|||||
|
Re: [FRC Blog] Einstein Report Released
Imagine the chaos if FIRST allowed any random person to walk in and give their suggestions while trying to diagnose the issue during Einstein. They'd be flooded with every person out there who has a theory (take a look at the numerous Einstein threads filled with people bickering about what they think happened to get an idea of how many people that would be) to step in.
Also, the document indicates that this individual was observed doing this multiple times and continuing throughout the match. If they were just doing some unauthorized (and incredibly harmful) troubleshooting, why didn't they stop after forcing a robot to lose connection the first time? Why did they take their phone out after explicitly being told not to? Because of those facts, I think it's hard to say that the intent was not malicious. My heart goes out to The Eh Team. Nobody doubts that they were an amazing alliance of 2 of the best teams (and one very promising up and comer). When people look back on Rebound Rumble, they will not only remember that 16, 25, and 180 won, but that 1114, 2056, 4334, 987, 233, 118, 548, 2194, and 207 were all outstanding teams whose robots excelled at the game. Quote:
Quote:
Last edited by Alexa Stott : 13-07-2012 at 21:35. |
|
#75
|
|||
|
|||
|
Re: [FRC Blog] Einstein Report Released
Im really really glad FIRST took their time to put together an awesome report! BUT.... after reading the whole things twice, I'll admit I don't quite have the technical experience to understand the report in its entirety.
Could someone summarize and explain the more detailed aspects of the Robot Testing and Failed Client Authentication Testing? Specifically, what intentional interference actually happened, how did it cause problems, and what are they planning to do to fix the issue? Thanks! |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|