|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||||
|
||||||
|
Re: Team Update 16 (2016)
1: Red, Red, Red
2: Red, Red, Blue 3: Red, Blue, Blue 4: Red, Blue, Red 5: Blue, Blue, Red 6: Blue, Blue, Blue 7: Blue, Red, Blue 8: Blue, Red, Red |
|
#2
|
||||
|
||||
|
Re: Team Update 16 (2016)
Quote:
We figured out it was one of the many cases where somebody probably copy-pasted 2015 to 2016 and this case did not have a lot of instances where this would have happened until this week. 1v8 and 2v7 will always send a red alliance to semis and 3v6 and 4v5 will always send a blue alliance to semis. 1/8v4/5 will always send red to finals and 2/7v3/6 will always send a blue team to finals, just like in the olden days. I feel really bad because everyone at the event did their jobs right (our drive coach read the rule to the head ref, the head ref agreed with him, and the FTAs tried to accommodate based on the rules, and field staff communicated the changes as fast as possible) but we all ended up contributing to a loss of about 20 minutes of time (the event still finished on time though, which was AWESOME) |
|
#3
|
||||
|
||||
|
Re: Team Update 16 (2016)
Quote:
I can't find the video of it, but I saw this happen at a week 1 event - a red robot drove across the midline and pushed a stationary blue robot several inches transitively through a boulder (no direct robot contact). Only 1 foul was called due to how the rule had been written. I was a ref in week 2, and we discussed this scenario prior. We decided since R13 did not mention transitive contact, we would enforce it the same way as was done in week 1. I'm glad to see the loophole closed, as it preserves the intent of the violation. |
|
#4
|
|||||
|
|||||
|
Re: Team Update 16 (2016)
I'll be honest, a lot of teams were not just doing this because 254 or 1678 were using overhead cameras on poles. Some teams at the Arizona North Regional were doing it because they specifically knew there was no height restriction. Now that this rule is implemented, a lot can agree the safety is definitely more concerning than the advantage over another.
|
|
#5
|
|||
|
|||
|
Re: Team Update 16 (2016)
Quote:
|
|
#6
|
||||
|
||||
|
Re: Team Update 16 (2016)
Quote:
https://youtu.be/oiMaHpT7bvg |
|
#7
|
||||
|
||||
|
Re: Team Update 16 (2016)
Well it would appear that our periscope will now be modified to be 8'8". Benefits of using a pool slimmer pole is that it allows us to adjust height easily.
|
|
#8
|
|||||
|
|||||
|
Re: Team Update 16 (2016)
This is a good change.
|
|
#9
|
|||
|
|||
|
Re: Team Update 16 (2016)
I don't think boulder wars is the genesis of the G13 change. I am guessing this is more likely the problem:
Two opposing robots line up on each side of a boulder. At the start of Autonomous, One robot drives in the wrong direction, and hits the boulder, which then hits the other robot. The other robot was not going after the boulder, but was going for a cross. The other robot is now knocked off it's path and cannot complete the crossing. Since the offending robot did not "touch" the other robot, there was not a G13 - Contact of opponent robot foul. |
|
#10
|
||||
|
||||
|
Re: Team Update 16 (2016)
This is exactly the change Travis spoke about the very first time I saw him setting up your camera pole.
Whether 11'8" is an optimal solution, it is a solution none the less. I'd say objective achieved! |
|
#11
|
||||
|
||||
|
Re: Team Update 16 (2016)
As the person who typically files the medical incident reports in the Dome, I am pleased.
|
|
#12
|
||||
|
||||
|
Re: Team Update 16 (2016)
Seems the height limit was chosen to be the same as the top of the flag on top of the tower. So, those on the field will have a nice, handy visual reference to know if your camera is too high!
|
|
#13
|
||||
|
||||
|
Re: Team Update 16 (2016)
What are these flags you speak of? None in sight on the towers at AZ North.
|
|
#14
|
|||||
|
|||||
|
Re: Team Update 16 (2016)
Quote:
Apparently they were a tad late getting out to the fields. |
|
#15
|
||||
|
||||
|
Re: Team Update 16 (2016)
And a tad broken... the solenoids on ours were tripping circuit breakers.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|