![]() |
Re: [FRC Blog] Einstein Report Released
As I read the report, I've been looking for two specific points of interest:
1. Why was the there a significant amount of failures for just the red alliance teams? 2. Special interest in how much vision tracking contributes to network traffic, as we (beta team)... were concerned of overwhelming traffic from this for teams that wanted to process vision via driver station. I believe point 2 with the network capping addresses this fear for future games... but I would like pursue this with actual numbers (not here in CD obviously). In short I'd want to know if the mjpeg frames cause a significant load in the network traffic, as I want to consider using mp4 compression going forward. I think FIRST action items will address some of this... I'm looking forward to getting these numbers! As for point 1... this is something I observed while watching the Archimedes elimination matches, and the report also reflects this for the Einstein matches. I've observed that red alliances usually have won (e.g. 90%) this year in our 2 regionals (I wonder how true that is for other regionals). There may be some correlation of this and the higher seed being on the red team. I noticed for Archimedes elimination, an overwhelming victory from the blue alliances. I don't want to talk about the political stuff but just want to throw some general things out there... 1. Is there a scapegoat political agenda going on? 2. No one can keep a secret as all will be revealed to those who want to know about it... it is just a matter of time. Why? friends tell friends, and those friends tell friends... and well you get the picture... just like FB itself. (P.S. I do not want to know... I'm an engineer not a politician) |
Re: [FRC Blog] Einstein Report Released
Quote:
After Finals Match 1 on Newton we took the robot out to be examined. we noticed that the Ethernet cable was slightly loose, so we re-zip tied it to the radio. After that we ran fine in Finals Match 2. I'm not saying that this was 100% the reason why we lost control, but it does appear to be so, at least to me. I'm leaving this here as a reminder to all teams, rookies to veterans, to double check EVERYTHING before going onto the field, you never know what could go wrong. |
Re: [FRC Blog] Einstein Report Released
Quote:
|
Re: [FRC Blog] Einstein Report Released
Quote:
|
Re: [FRC Blog] Einstein Report Released
Quote:
47R/95 for Alamo = 49.5% Red wins 31R/76 for Dallas = 40.8% Red wins Disclaimer: I only counted once, so I may be off by a percent or two. Perhaps someone can crunch the numbers for all the regionals? |
Re: [FRC Blog] Einstein Report Released
Quote:
|
Re: [FRC Blog] Einstein Report Released
Yup. There should be a fairly strong Red bias in Elims, especially so in the QFs.
Side note of interest, at ON2 (GTR-West) this year, 2056 played their first Elimination matches at a regional on the blue alliance. Every other regional, they've won from the #1 seeded alliance, who never plays with blue bumpers. |
Re: [FRC Blog] Einstein Report Released
To those that believe that the team of the INDIVIDUAL should hesitate to come forward, let's think about our culture for a minute.
In my experience, FIRST is about accountability and responsibility. We have an accountability to others, both for our good decisions and our bad. We have a responsibility to make the world a better place than when we arrived in it. This means we hold ourselves accountable for our mistakes and celebrate our successes. On my team I've made mistakes. We all do. We don't hide them from others. We learn from them. We discuss them. We are accountable to ourselves but also those within our community. I know for a fact at certain points during my time on the team many mentors would have called me an arrogant jerk, and they'd be right. But the culture of our team and of FIRST allowed me to accept my mistakes and grow. Now those same mentors have hired me at their companies and have given me great recommendations because I made myself accountable for my actions and learned from them. Now about this individual. I do believe that they are beyond being forgiven. Their actions have a malicious intent that I believe is clearly illustrated by the actions of FIRST in dealing with them. FIRST doesn't reserve that kind of action for an accident. The individual's actions were deeply hurtful to everyone who has even been touched by FIRST, and I believe that they don't really care given, 1.Their actions 2. A lack of an apology thus far That said they will only be anonymous for so long. Eventually the community will have a name and a number to go with it. My opinion is that team should come forward. Help the community heal and acknowledge that a team member turned out to be a different person than you thought. Don't help protect this person for your own anonymity. That can only last so long. If you truly did nothing wrong no one who matters and has half a brain would hold you accountable for something that you are not to blame for. Don't protect someone who chose to make a decision that terrible. Address the situation in a manner befitting the quality of the community we are all a part of. The teams targeted are some of the best. Ever. They have worked to excel to a point that most of us will never reach. They should be celebrated for reaching that level and helping inspire others to do so. I honestly think they deserve commendation for simply maintaining a positive attitude despite the malicious actions of some idiots over the years (and yes they are idiots, no apologies). They deserve an apology and an explanation. Anyone in their place does. In short, to everyone. Be accountable. Acknowledge success and mistakes, and grow from them. Just my thoughts on a bad situation that had a fortune to be dealt with by some amazing people. |
Re: [FRC Blog] Einstein Report Released
1 Attachment(s)
Quote:
The usual caveats about the FRC Twitter data feed apply. |
Re: [FRC Blog] Einstein Report Released
Quote:
Everything else is spot on. |
Re: [FRC Blog] Einstein Report Released
Quote:
Ether: Thanks for this data... it confirms what 1075guy and I have observed in regards to the red bias in elims. From this global scope xls document everything is probably as we'd expect. However, the FRC report itself does show a significant amount of failures for red alliance teams. Also, there was one match in particular that we played where we observed 2 simultaneous red alliance failures that got me thinking about this during the rest of the competition. |
Re: [FRC Blog] Einstein Report Released
Quote:
It should be self-explanitory... if not then please just disregard. |
Re: [FRC Blog] Einstein Report Released
Quote:
If you were that team, wouldn't you want to admit that, like Alex said, this person had a different character than you thought... rather than get called out on a public forum before you get your chance to speak for yourself? I don't approve of a witch-hunt for the person involved, but I do believe the team should get a chance to step forward before those with the torches and pitchforks get them first. |
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). |
Re: [FRC Blog] Einstein Report Released
I'm happy for the FMS Whitepaper.
|
| All times are GMT -5. The time now is 23:34. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi