|
Re: A fix creates a problem ...
Quote:
Originally Posted by GaryVoshol
Post Team Update #1:
(emphasis mine)
Quote:
<G19> MINIBOTS must remain completely autonomous and move up the POST solely through electric energy provided after DEPLOYMENT by the permitted, unaltered battery and converted to mechanical energy by the permitted unaltered motors (and associated, appropriate circuitry).
DEPLOYMENT – the act of positioning a MINIBOT on a TOWER. DEPLOYMENT starts when the MINIBOT breaks the vertical projection of the TOWER BASE circumference during the END GAME. DEPLOYMENT ends when the HOSTBOT is no longer in contact with the MINIBOT. (Related form, DEPLOY, verb)
|
So now the MINIBOT can't begin to move upwards until after it is no longer in contact with the HOSTBOT. Moving upward to break that contact is not valid.
|
I think that this is another very good question for the Q&A. Can the robot not start moving up until after deployment ends? Or until after deployment starts? If the former, this is a pretty nasty (but not uninteresting) restriction. I am reminded of a set of field orders I read once at Quantico, about something not being allowed until after engagement. Some of the platoons involved interpreted the orders one way (waiting until the engagement was completed), the rest another (as soon as the engagement commenced).
__________________
Thank you Bad Robots for giving me the chance to coach this team.
Rookie All-Star Award: 2003 Buckeye
Engineering Inspiration Award: 2004 Pittsburgh, 2014 Crossroads
Chairman's Award: 2005 Pittsburgh, 2009 Buckeye, 2012 Queen City
Team Spirit Award: 2007 Buckeye, 2015 Queen City
Woodie Flowers Award: 2009 Buckeye
Dean's List Finalists: Phil Aufdencamp (2010), Lindsey Fox (2011), Kyle Torrico (2011), Alix Bernier (2013), Deepthi Thumuluri (2015)
Gracious Professionalism Award: 2013 Buckeye
Innovation in Controls Award: 2015 Pittsburgh
Event Finalists: 2012 CORI, 2016 Buckeye
Last edited by mathking : 12-01-2011 at 11:11.
|