Team Update 8

combined updates link: https://firstfrc.blob.core.windows.net/frc2017/Manual/TeamUpdates/TeamUpdates-combined.pdf

I am excited that Idle Loop and the GDC were able to improve player station balancing. read the FRCand Idle Loop blog posts for more info. It turns out it was more complicated than I originally thought, so I’m glad they took the time to work it out.

the other note is a rope clarification.

I04-G - if frayed, knotted or looped, the total diameter does not exceed 10 in. (~25 cm) (D)

Time to haul out the old “I’m a frayed knot” punchline…

I’m knot sure if you could have delivered that pun any better.

Let’s rope these puns in before it gets out of hand.

Two other things:
to give full credit, it was not my idea that player station balancing would be important. I can’t find the right thread here to give credit to the right people, but it was a CD thread that made me look up how MatchMaker works (because i thought it did balance stations). I just knew who to poke to get it looked at.

Second, I’m knot 'frayed of a pun thread.

This update is good to see.
Are we asking too much by asking that the playoff alliance captain get to choose the alliance station positioning?

Because as it stands, this system sure is making teams stay in the same proximity to the boiler for the entirety of playoffs. (unless you count switching between alliance colors) And I can’t really think of a good reason for this except “because FMS”

It is also interesting that your method of allowing the alliance to pick spots is EXACTLY what they will be allowingin subdivison playoffs … this is for subdivision playoffs at Houston and St. Louis.

ALLIANCES may start with any three (3) of the four (4) ROBOTS on their ALLIANCE during Subdivision Playoff MATCHES and during the Championship Playoffs. The list of three (3) Teams participating in the MATCH and their selected PLAYER STATIONS is called the LINEUP

T11. The ALLIANCE CAPTAIN must report the LINEUP to the Head REFEREE, or their designee, in writing prior to end of the preceding MATCH (e.g. the LINEUPS for Quarterfinal 2 must be submitted before the end of Quarterfinal 1). If there is no preceding MATCH, the LINEUP is due no later than two (2) minutes before the scheduled MATCH time.

Not sure why this method is NOT what we will be doing for District and Regional Play. It would be nice if it could at least be used for the District Championships.

The assignment of field positions will be even more critical in District and Regional play because of the smaller number of teams to pick from.

FYI, this has been a rule at Champs since at least 2014. Search for LINEUP in the document.

Given that this is the first year where the alliance station assignments matter so much to the game play, I’m not surprised that FIRST hasn’t updated the rules regarding District Champs. I wouldn’t expect them to change the rules, but I’ve been wrong before :slight_smile:

Another thing to consider is that at District Champs/Regional Tournaments, there are only 3 team alliances with the provision for a backup robot. The backup robot concept doesn’t exist at Champs, given that each alliance contains 4 teams. What that means is that the capability for assigning teams to specific spots is built into FMS for Champs. What I don’t know is if it’s feasible to change FMS to allow to player station assignments - I don’t know what kind of changes are made to the FMS configuration between the last event and Champs.

Food for thought. I don’t disagree with you, but I think it’s important to look at the issue from multiple perspectives.