|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Denying an Alliance Selection
Has your team ever denied one of the top seeds picking you? Have you ever witnessed another team denying a selection? If so, I imagine these teams were in the top 8 as well, right? Why do you deny in that case?
Just wondering, because I've never seen a team deny, and it seems like it would be very ungracious. |
|
#2
|
|||||
|
|||||
|
Re: Denying an Alliance Selection
Check the responses in the Great Lakes thread. It also happened at Midwest this year, and at Detroit a year or two ago. There are a variety of reasons for declining to participate in an alliance, and most of them are GP.
|
|
#3
|
||||
|
||||
|
Re: Denying an Alliance Selection
i believe it happened in jersey a few years ago, and 25 and 103 ended up together (correct me if im wrong, i know i have seen it once), but this is not unGP at all. If your team is lucky/good enough to be in the top 8 then you have earned the opportunity to pick who ever you want. The team that declines would only do so if they thought that the teams they had in mind to pick would be a better fit. While scouting i encourage looking for the bot that flys under the radar, that sleeper pick that tends to take your alliance from good to great.
|
|
#4
|
||||
|
||||
|
Re: Denying an Alliance Selection
As said above, it's largely GP. If your robot fails, you can deny to prevent yourself from hampering the alliance. That's the only reason I've ever though of, although I'm sure there are more.
I'm sure you understand that denying does prevent you from joining any alliances afterwards though. I think it's largely used as a formal withdrawal from competition, since it is necessary for teams to send representatives to the field. |
|
#5
|
|||||
|
|||||
|
Re: Denying an Alliance Selection
Yeah, it has happened in FLR and GTR this past year. If you are a low seeded team and not picked by the top 2/3 teams, there is a real good plan to deny teams 4-6 to make your own alliance. It's not always the case of being non GP, it's still all about survival in the elimination rounds. If you feel the other team doesn't fit in a plan you have or compliment your robot more then others out there, then go right ahead and deny the pick. Also something happened at GTR, that I have never witnessed before. Team 03 knew coming into the later half of the day that their drive system was on the verge of breaking. They had announced before the alliance pickings that they might be fully operational and requested not to be picked. I felt that was a really professional announcement from a professional team. I can only wish other teams take that and do it as well instead of being selected and then announce to the alliance that they are not full functional.
|
|
#6
|
||||
|
||||
|
Re: Denying an Alliance Selection
I once saw a team, not in the top 8, deny an alliance selection because they didn't understand the rules. They wanted to partner up with a different team not the #1 seed. They were told that denying this selection would forfeit them from the elimination rounds & they still denied. Then when the team they wanted to pair up with called their number they were happy & came running out to accept. They were told again that they could not accept. Lets saw the behavior I witnessed after that announcement was not GP, for that matter it wasn't even PG.
|
|
#7
|
||||
|
||||
|
Re: Denying an Alliance Selection
In 2006 at Nationals (Newton Field), 176 was denied twice. It was part of a strategy by the #1 seed to break up any "super alliances". 176 was not one of the best robots on the field, but had been doing fairly well and had a nice match schedule. They ended up being the only undefeated team in the division and ultimately took the 1 seed.
The seeding was... 1. 176 2. 987 3. 25 4. 254... 176 knew that 987 was likely to select 25, due to their success together at Las Vegas that year and they also knew that 25 would deny a selection. They knew 25 would deny because there were a decent amount of teams that were considered better than 176. They also chose 254 for the same reason. 987 could then not select 25 or 254. 25 also could not select 254 as well. Ultimately they chose 111 and got to the Division Finals. You could argue that if they hadn't played that strategy, they wouldn't have made it past semis. So to answer the question...a good amount of times denying a team/blocking a team has a lot to do with strategy. However there are a decent amount of times where the seeded team is just not up to snuff for some teams to pair with. Last edited by Corey Balint : 01-04-2008 at 10:41. |
|
#8
|
||||||
|
||||||
|
Re: Denying an Alliance Selection
Quote:
If picking, and the team is a top seed:
Last edited by Travis Hoffman : 01-04-2008 at 10:53. |
|
#9
|
|||||
|
|||||
|
Re: Denying an Alliance Selection
For a team to deny in the top 8 is okay. Many strategies are pre-planned going into the alliance pickings, some of which tell the person picking that they will not accept an invitation to be allied together. It's all part of the "game" or FIRST would have a rule not allowing this to happen.
For a team to deny out of the top 8 is also okay. If a team has a robot that may have a broken something-or-other and does not want to keep an alliance from having an alliance partner that is at "100%" instead, it's very gracious for them to deny the selection. As for what happened at GLR this past weekend, I saw it as an immense strategy put into place, and it worked very effectively. |
|
#10
|
||||
|
||||
|
Re: Denying an Alliance Selection
Strategy is an integral part of the robotics competition and the alliance selections are a part of that. If you think of the importance of strategy in games that you are familiar with - apply that to the entire process of build and competition, from design through alliance selections, and throughout each match, with alliances working with each other.
I'm linking you to the conferences that will be available at the Championship. There are those who will not be attending the Championship, I understand, but I would like you to look at some of the topics and note who some of the presenters are. A few of the presentations discuss strategy. If there is any way for folks to attend these, I would highly recommend it. http://www.usfirst.org/uploadedFiles...dule_32008.pdf The game, strategy, drivers continuing to improve throughout the competition(s), alliances working with each other - each of these elements continue to deepen and develop, as does our understanding. It's pretty spectacular. |
|
#11
|
|||||
|
|||||
|
Re: Denying an Alliance Selection
If the Los Angeles selections for 2008 ever come up on video, there were four declines to partner with one team. All four came from inside the top 8. Then one of those teams was picked and accepted and #9 came up...only to be sent back after the FTA reminded the person running the selection (not the MC in this case) that you can't accept after declining.
My team went into those knowing that if we were picked (by some fluke) we would decline. I also remember one instance--not sure if it's something my dad told me or something I saw--but a team declined because they were going to miss their flight home if they participated in the elimination rounds. And then there are the "breaker" declines. I won't go into those, as others have done it already. |
|
#12
|
||||
|
||||
|
Re: Denying an Alliance Selection
It's pretty simple really, the seeding process is not perfect. Sometimes teams get lucky match selections and seed higher than the level their robot is performing at. When this happens seeded teams can sometimes get stronger partners by choosing their own alliance.
|
|
#13
|
|||||
|
|||||
|
Re: Denying an Alliance Selection
Travis,
This is what I tell rookie teams at each regional on Saturday morning... "Be sure to have a list of your top 5 #1 picks and top 5 #2 picks ready for alliance selection. Make sure you give the list to your team captain before alliance selection. If you find yourself in a position to be picking you want to be prepared and if you are picked you want to help your alliance partner pick another robot that will fill out your capabilities. If you choose someone in the top eight and they decline, do not feel bad, just move on to your next choice. They either think they have a better chance with another robot; they think they would like to play you; or they think your robot would be a better fit with another robot you have not thought about. Remember that this might be their and your last chance to bring home some hardware this season. Everyone wants to play on Saturday afternoon. Finally, remind your student to keep an eye on the available team list on the big screen. You don't want to pick someone that is already in an alliance, you don't want to look like a rookie out there." I know there have been other threads about picking teams you know will decline so they cannot ask another team in the top eight. My $0.02 on this subject is Shame On You! |
|
#14
|
|||||
|
|||||
|
Re: Denying an Alliance Selection
On a side note, I have seen teams accept an invitation when they shouldn't have. If you don't think your team matches up well then it's more than OK to say "thanks but no."
|
|
#15
|
||||
|
||||
|
Re: Denying an Alliance Selection
Quote:
Consider this hypothetical situation where one mediocre team is ranked #1 overall, followed by several excellent robots: 1. 9999 2. 1114 3. 39 4. 103 5. 968 6. 1625 7. 3000 8. 4000 Let's also assume 9999 is marginally better than teams 3000 and 4000. 9999 should start picking at 39 (NOT 1114) 39 declines 103 declines 968 declines 1625 declines now 9999 picks 1114. Consider 1114's position: What is the BEST POSSIBLE ALLIANCE that can be formed at the regional now? That's right, it ACTUALLY is 9999 and 1114, because the rest of the field is now forced to pick robots 3000, 4000 and below. 1114 should DEFINITELY accept, and they WILL form the strongest alliance at the regional. The strategic power of the 1st rank seed as a "so-so" robot should not be trifled with. Unfortunately, we RARELY ever see it used to its maximum potential. The truth is, some (actually MOST) teams can only build okay robots. Some of these teams are consistently higher performers by just finding a way to win (in a GP way of course). Can they really be faulted for this? To me, this process is easily just as inspiring... Last edited by Mr. Lim : 01-04-2008 at 12:02. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| New alliance selection method | Bharat Nain | Rules/Strategy | 5 | 08-01-2006 22:16 |
| [OCCRA]: CMP Alliance Selection | Alex Golec | OCCRA Q&A | 1 | 14-11-2005 18:20 |
| Alliance Selection 2005- Like it? | OneAngryDaisy | Rules/Strategy | 42 | 14-03-2005 14:59 |
| Selection process for Alliance Partners in the Finals | Ken Loyd | Rules/Strategy | 17 | 02-05-2002 00:13 |
| Alliance Selection Clarification | Bill Beatty | Off-Season Events | 1 | 11-11-2001 07:11 |