|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools |
Rating:
|
Display Modes |
|
#31
|
||||
|
||||
|
Re: 2014 Central Valley Regional
973 looked like they were having growing pains switching to a new drive coach combined with pretty poor partners throughout. Regardless, it looks like they are getting those issues figured out(look at their last match) and have really good synergy(973 being good at assists, and 254 being good at shooting with a great auto). It doesn't hurt that they won champs with each other and are great friends too.
|
|
#32
|
||||
|
||||
|
Re: 2014 Central Valley Regional
Does anyone know: Is there an FRC-wide policy (applicable to all FRC competition events) regarding the process for filling the "extra slots" in the schedule? Or is the policy a local decision? For example, at CAMA there were 83 Qual matches. 83*6=498 "slots" to assign teams to. But there were 45 teams. 498 div 45 = 11 rem 3. So, 3 "extra slots". Who decides which teams fill those 3 extra slots? For example, are they assigned automatically by the scheduling program? And what if one of those selected teams cannot, for some reason, participate in one of these "surrogate" matches - are they penalized in some way? Or do the organizers at the venue ask for volunteers? |
|
#33
|
|||
|
|||
|
Re: 2014 Central Valley Regional
973 pick looks very fishy to me. Smells of collusion, but would the judges ever do anything? Don't think so.
|
|
#34
|
|||
|
|||
|
Re: 2014 Central Valley Regional
I haven't been able to keep up with the regional...but if you are accusing 973 of intentionally sandbagging, the Greybots are not a team that would do something like that.
|
|
#35
|
||||
|
||||
|
Re: 2014 Central Valley Regional
Quote:
What do you think is illegal, dishonest,or deceitful about it? |
|
#36
|
||||
|
||||
|
Re: 2014 Central Valley Regional
Quote:
|
|
#37
|
||||
|
||||
|
Re: 2014 Central Valley Regional
Quote:
2. Do you really want judges to be able to "do anything" to a team based on an alleged fishy looking hunch? What action could possibly be appropriate for a judge to take here? |
|
#38
|
||||
|
||||
|
Re: 2014 Central Valley Regional
Don't take records as seriously this year as you have in previous years. Since winning matches this year requires your whole alliance to be good, teams are getting screwed out of matches that in previous years they may have been able to win by themselves. There's such a value to teamwork this year that having bad teammates can make your record a lot worse than you really are. Not saying this is definitely what happened to 973, but it's a pretty good assumption I think.
|
|
#39
|
||||
|
||||
|
Re: 2014 Central Valley Regional
Quote:
Quote:
|
|
#40
|
|||
|
|||
|
Re: 2014 Central Valley Regional
Quote:
|
|
#41
|
|||||
|
|||||
|
Re: 2014 Central Valley Regional
Quote:
If they were sandbagging we would have been trying to pick them with the 23rd pick, not the 1st pick. Last edited by Cory : 09-03-2014 at 17:59. |
|
#42
|
|||||
|
|||||
|
Re: 2014 Central Valley Regional
Quote:
Personally, I'd assume that team numbers are not taken into account in the algorithm, and since that's the only team-specific information that the match scheduler takes in, every team should have an equal chance of being a surrograte. |
|
#43
|
|||||
|
|||||
|
Re: 2014 Central Valley Regional
Quote:
Quote:
|
|
#44
|
||||
|
||||
|
Re: 2014 Central Valley Regional
Quote:
- Is this policy a local decision or an FRC-wide policy* - Who decides which of the participating teams will play surrogate matches* - Any particular rationale for the 3rd match being the surrogate? - If for some reason a team cannot play their last match, does their "surrogate" match become official? * Karthik & AllenGregoryIV answered in previous posts Last edited by Ether : 09-03-2014 at 18:03. |
|
#45
|
|||
|
|||
|
Re: 2014 Central Valley Regional
I don't know for sure, but I would imagine that you want it be as early as possible to prevent using it to easily manipulate standings but late enough to minimize the likelihood that the surrogate team will have any chance of having not passed inspection or otherwise be non-functional (obviously damage can happen in any match and render the robot inoperable for the next match).
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|