|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Thank You, Team 217
Does nobody have a problem with the fact that 217 told us specifically to cross them off our list -- with NO ambiguity -- when in fact they were fixable? I understand the point about double checking through our own scout team but that isn't the issue here.
|
|
#2
|
|||||
|
|||||
|
Re: Thank You, Team 217
Quote:
If some members of that team think otherwise, and effect a fix, and do not successfully communicate that fact to the rest of the team, the team has a severe internal communication problem. AFAIK, 217 does not have such an internal communication problem. Therefore, it is to be assumed that while perhaps some members of the team were trying to fix the robot, even they thought that they would not be ready in time for eliminations, and requested that nobody pick them. However, the only way to guarantee not being picked is to decline a pick. If you think someone might be bluffing, call their bluff. If you don't call it, and it bites you, then that's your problem. |
|
#3
|
|||
|
|||
|
Re: Thank You, Team 217
Quote:
Someone earlier said something along the lines of "since when do teams take other team's scouting information?" I forgot to address this, but I have seen teams sharing scouting info all over the place. There are editable google docs for community scouting information, and we had multiple teams in our pit volunteering electronic stats and info throughout this week -- which is great. Why would we have any reason to distrust another alliances scouting info or word? We're all gracious professionals, no? While it may have been advantageous to "call their bluff," we shouldn't have to resort to such measures. |
|
#4
|
||||
|
||||
|
Re: Thank You, Team 217
Quote:
Now, why didn't they decline when they were picked? It would have been the gracious thing to do, right? Unless 1538 told them NOT to say no. Maybe 1538 said "We're going to try to pick you anyways, because if you manage to get fixed you will be the steal of our alliance." After all, the Thunderchickens had an absolutely ridiculous upswing that (obviously) helped make a solid alliance. It might have been worth the risk of having to take a backup bot if there was also a chance of getting the perfect third robot. Maybe 1538's confidence in 217 was a strong enough motivator too. |
|
#5
|
|||||
|
|||||
|
Re: Thank You, Team 217
It should also be pretty much common sense to think along these lines:
217 thought they were done and out beyond repairs. They do in fact tell 1538 and 1986 this and while these two are waiting for the other 7 alliance to be made they are discussing who to pick. When it became obvious to them that 217 would be the perfect choice these two teams decided that between 217's crew, as well as their own teams (Who may I remind you built Robots that went 36-4 and 53-4 respectively at that point) could these crews working together during the hour break diagnose the problem, think of the quickest best solution to get it running and try to maintain and improve it through the competition? My opinion is that between these three teams with 20 Regional/Distict Wins, 5 Championship Division wins, 2 Championship wins, and one of them being in the Hall of Fame as of this year: If anyone could pull this off and make me believe it, these three teams are it Last edited by MARS_James : 28-04-2013 at 10:30. |
|
#6
|
||||
|
||||
|
Re: Thank You, Team 217
I do understand where you are coming from, and I doubt I wouldn't feel the same way, however after playing with 1538 at IE I have a new found respect for them. They were some of the most gracious people there. On the Friday of the regional, we were having some communication issues. The first person that came to help us was, I believe, their mentor and drive coach. After spending at least an hour with us running tests, he couldn't figure it out, but gave us a replacement cRio for the rest of the regional. Even after our qualification match where our alliance broke their arm, they were jovial and seemed not to harbor hurt feelings.
Not also mention not any team can join the hall of fame. |
|
#7
|
||||
|
||||
|
Re: Thank You, Team 217
As a mentor of a team that was an alliance captain 217 did come to us and tell us they were not able to be repaired. They said if you pick us, we will decline.
We then approached a mentor of 217 after the alliance selection and asked how they were able to fix their robot. Their mentor said something to the effect of "we only wanted to play with the number 1 alliance." I wonder if other picking alliances were told this same thing or if was just us. |
|
#8
|
||||
|
||||
|
Re: Thank You, Team 217
I am not implying at all that 1538 and 1986 had any knowledge of this at all. When we worked with both of them they were stand up teams. I do doubt however that the mentor and student going around from 217 told 1538 that "if you pick us, we will decline, because we are broken and cannot be fixed." If they did tell them that and 1538 picked them anyway that was a great risk they took. If they weren't told that and every other alliance captain was, that is not GP in my book. Also for a mentor to directly say they only wanted to be with the number 1 alliance is just not ok.
I would be interested to hear what 217 has to say. Whether or not that was an entire teams strategic decision or just a few students and mentors that decided to do it. |
|
#9
|
||||||
|
||||||
|
Re: Thank You, Team 217
Let me set the record straight. I never ever told any of the teams that we would decline. As a matter of fact, I told every team in the top 15 that we would accept if they picked us but I was certain we could not be repaired. I told the exact same thing to every team including 1538. As a matter of fact, I told them 3 times that we were unable to play.
During alliance selection I was on Galileo watching that selection because I knew we would not be picked based on our robot status. In sure the 1538 mentors i told will corroborate my story. I am 100% positive I told no team that we would decline. Making claims that I said anything otherwise is just false. I was trying to make sure all of the teams in the top 8 knew our status. 1538 had the exact same information everyone else had prior to alliance selection. I believe they took a huge risk picking us. Our auton didn't fire two times during eliminations which was exactly one of the problems we were having when I approached every team in the top 15. To be clear, I was the mentor that approached every team in the top 15. You can blame me and solely me if you think you were misled. My team tried everything they could to get the robot working. Most of our team had no idea what was going on with the robot so I have no idea who you talked to after alliance selection but it wasn't me. Lastly, you do not need to be anonymous. I would be more than happy to discuss the exact circumstances regarding the Newton alliance selection. You have every right to be upset but you have no right to take anonymous shots at my team. You can take shots at me, but you better stand up and be a man (or woman) about it. As you probably know, because you are the one who got Frank Merrick involved, I was approached by Frank and Aiden regarding the situation. They interviewed me and the mentors from 1538 and were completely satisfied with our explanation. In any case, this is my first and last response to this thread. Paul |
|
#10
|
|||
|
|||
|
Re: Thank You, Team 217
Quote:
Unlike 2052 claimed, I can also confirm that our team was told 217 would accept (although I don't entirely understand the reasoning behind this). Finally, I will remain anonymous because of the reasons stated previously. |
|
#11
|
||||
|
||||
|
Re: Thank You, Team 217
I really appreciate Paul posting on this issue and setting the record straight right away.
As a friend, I'm concerned that I continued to perpetuate the rumors thought last night's mentor party. The rumors didn't seem right, but we kept hearing/repeating the same story. I should have just asked right away. Paul / 217, I apologize for not help set the record straight. Congrats on working hard to get the robot working and being division finalists. |
|
#12
|
|||||
|
|||||
|
Re: Thank You, Team 217
I think that the parties involved have set the record straight, and there is no more need for discussion, especially based on anonymous accusations. This thread is now closed.
|
|
#13
|
|||||
|
|||||
|
Re: Thank You, Team 217
This thread has been closed for the time being. The original poster made a improper account to bash a team. That is not allowed.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|