Quote:
Originally Posted by squirrel
Perhaps the refs or inspectors can ask you to demonstrate that the MINIBOT is entirely below the horizontal plane after DEPLOYMENT...that should be possible before/after a match?
I'd like to see the alternative interpretation, how does it work?
|
Alternative interpretation...
(I wrote this over the past hour while I was watching television and did not see Bruceb post which made basically the same argument)
Defined terms in the rules:
DEPLOYMENT – the act of positioning a MINIBOT on a TOWER. DEPLOYMENT starts when the MINIBOT breaks the vertical projection of the TOWER BASE circumference. DEPLOYMENT ends when the HOSTBOT is no longer in contact with the MINIBOT. (Related form, DEPLOY, verb)
DEPLOYMENT LINE – located on the POST, approximately 18 inches above the top surface of the BASE.
No where in the manual does it define a cylinder of extending from the deployment line.
Elsewhere in the manual, it describes cylinders for violations but not for this case.
My copy of the rules from Jan11 did not have this form of deployment as a violation. This violation was added in Update #2. The GDC decided to change <G21> instead of just changing <G22>.
(They also did not add a cylinder explanation for this changed rule).
The spirit of the rule is the minibots need always remain completely below the deployment line while in contact with both the hostbot and the pole.
And that, at first contact with the pole, the minibot must be completely below the deployment line.
Do you really think the GDC specifically wanted to preclude this type of deployment? I think it is just that it was they just used the fewest words to to make up for their omission that the minibot needed to start completely below the deployment line. Maybe they were concerned about minibots very close to the pole and still above the deployment line and the potential difficulty it would cause to referees making a ruling.
BTW, my team doesn't violate this rule: we move our minibot horizontally.
There are at least a couple good lessons here:
1) Read the rules and the updates AND all the GDC Q&A
2) Post your progress here on CD and get good advice BEFORE you get officially inspected and get surprised
Writing requirements and manuals is usually a thankless job. The GDC does an excellent job. Bruceb and team have days to create an alternative deployment if Q&A does not work for them.
It's really nice that everyone is willing to be helpful.