G10, The Dallas Disable & Crickets Chirping in Manchester

[Jacob Bendicksen]

Originally Posted by Abhishek R

No, they were disabled during the semifinals for supposedly taking too long to set up as well, I believe. I don't recall that rule ever being enforced which resulted in a disable or any warning being given about it prior to when it happened. It was pretty unexpected when it became an issue.

My bad. The finals disable has just been a more visible one than the semis.

Also, when does that 60 seconds start? Right when the gates open? After we're done waiting for the yellow totes to be set back up by referees since teams may not change the position of the autonomous game pieces, so that we can line our robots up with them?

I believe that it starts the moment your robot's wheels touch the carpet.

[Boe]

Originally Posted by Jacob Bendicksen

I believe that it starts the moment your robot's wheels touch the carpet.

If so we are going to be seeing some assembly while two people are holding the robot off the carpet.

[Jacob Bendicksen]

Originally Posted by Boe

If so we are going to be seeing some assembly while two people are holding the robot off the carpet.

I hope not. It was in an email from Kevin Ross (PNW Chairman), and it's not in the Manual, so unless someone has something more official, hopefully this won't happen.

[Brandon Holley]

Along similar lines...Transport Configuration.

I'm curious how it was enforced and implemented in other areas of the country. In South Florida- teams were permitted to exit Transport Configuration once they reached the on-deck queue boxes.

Will this be the norm? Is this how it was done in other venues?

-Brando

[Jacob Bendicksen]

Originally Posted by Brandon Holley

In South Florida- teams were permitted to exit Transport Configuration once they reached the on-deck queue boxes.

Will this be the norm? Is this how it was done in other venues?

-Brando

This was allowed at PNW Oregon City for the entire weekend, and I heard that it was happening at PNW Auburn-Mountainview late Friday since they were running 2 hours behind. PNWFIRST has stated that FIRST approved this as a temporary thing, so don't plan on it for Week 2 events. It could happen at some events, but I think it was a Week 1 thing.

[MrJohnston]

Originally Posted by Jacob Bendicksen

This was allowed at PNW Oregon City for the entire weekend, and I heard that it was happening at PNW Auburn-Mountainview late Friday since they were running 2 hours behind. PNWFIRST has stated that FIRST approved this as a temporary thing, so don't plan on it for Week 2 events. It could happen at some events, but I think it was a Week 1 thing.

An email from Kevin Ross (PNW Chairman) stated that this practice would not be permitted in our week 2 event and that we were expected to strictly abide by the limit. I have also gotten word (indirectly) from the head ref of that event that the 60 second time limit will be enforced.

I really don't think it's a big deal: We knew it would be an issue on day 1 and made design decisions about our robot knowing that the time limit would exist - albeit we did not know how much lenience there would be. If a veteran team creates a robot that simply cannot be assembled in less than, say, 90 seconds, they should be warned, then disabled. We have to play by the rules. If it is a rookie team, perhaps a little more patience would be wise - though not in elimination matches.

[IronicDeadBird]

Has an MC ever managed to damage a robot while introducing the teams?

[AdamHeard]

The 60 second setup time can be brutal, teams often took way longer than that in previous years with no transport config.

[Kevin Sevcik]

Originally Posted by MrJohnston

An email from Kevin Ross (PNW Chairman) stated that this practice would not be permitted in our week 2 event and that we were expected to strictly abide by the limit. I have also gotten word (indirectly) from the head ref of that event that the 60 second time limit will be enforced.

So week 2 teams are supposed to strictly abide by the 60 second limit. So, once (the previous match ends/previous teams exit the field/a team enters the field/sets their robot down/field reset completes) the team has 60 seconds to (finish setting up/exit the field/be behind the alliance wall). Glad Kevin Ross has cleared that up.

[wireties]

Originally Posted by Kevin Sevcik

So week 2 teams are supposed to strictly abide by the 60 second limit. So, once (the previous match ends/previous teams exit the field/a team enters the field/sets their robot down/field reset completes) the team has 60 seconds to (finish setting up/exit the field/be behind the alliance wall). Glad Kevin Ross has cleared that up.

This is another disaster waiting to happen - a classic over reaction. Are all refs gonna start the count at the same time? What are the criteria for starting the count? This is the reason the 60 seconds was in a blue box to begin with - so the ref could exercise discretion, wisdom and GP.

[Jon Stratis]

Originally Posted by Brandon Holley

Along similar lines...Transport Configuration.

I'm curious how it was enforced and implemented in other areas of the country. In South Florida- teams were permitted to exit Transport Configuration once they reached the on-deck queue boxes.

Will this be the norm? Is this how it was done in other venues?

-Brando

The SAFE expansion outside of transport configuration early in the queue is one tool events have this year to help them maintain schedule. Schedule wasn't an issue at Lake Superior this weekend, but it was across the hall at Northern Lights (due to field issues, not team issues). For those two events specifically, we hold an exhibition "Double DECCer" playoff match between the winners of both fields. So while Northern Lights was trying to catch up on Saturday (even playing matches through lunch), Lake Superior was slowing things down so they would both end roughly at the same time.

As I understand it, utilizing this tool is at the discretion of the event, based on the needs of the event. If there's no need, then I doubt it'll be used.

[MrRoboSteve]

At Northern Lights, we didn't end up relaxing the transport configuration rule as we only ran an hour behind and teams were pretty good about setup time. There were some laggards, but we communicated with them and they got better.

Going longer than 60 seconds is a risk, not a rule. During quals, when the event is an hour behind and your robot is in the #3 box -- more likely to be an issue. During practice matches -- less risky.

[waialua359]

A big challenge this year comes in the semifinals.
Teams need time to be able to tether (although I read somewhere you cant?) to reset their robots, fill air tanks and do other software/mechanical checks and setups prior to playing another match.

What happens if you play back-back matches during the round robin 3 matches?
Some teams at IE were rushing to get going again because of this.

[Thad House]

Originally Posted by waialua359

A big challenge this year comes in the semifinals.
Teams need time to be able to tether (although I read somewhere you cant?) to reset their robots, fill air tanks and do other software/mechanical checks and setups prior to playing another match.

What happens if you play back-back matches during the round robin 3 matches?
Some teams at IE were rushing to get going again because of this.

Well 5.6.6 in the game manual says that in the playoffs if an alliance plays back to back matches, the Head Ref WILL issue a field timeout. This doesn't just apply in the finals, but in the semis and quarters as well. So if required to play back to back, there will be a 6 minute field timeout in between.

[DCA Fan]

Originally Posted by waialua359

A big challenge this year comes in the semifinals.
Teams need time to be able to tether (although I read somewhere you cant?) to reset their robots, fill air tanks and do other software/mechanical checks and setups prior to playing another match.

What happens if you play back-back matches during the round robin 3 matches?
Some teams at IE were rushing to get going again because of this.

For these matches we were supposed to take a formal field time out, but we didn't get clarification on this until after the event (we still gave essentially the same amount of time to the teams)- that being said, it's still a very tight turn-around. The tethering is somewhat addressed in the latest game update - with expressed permission from FTA or referee it is allowed.