Go to Post Please don't act embarrassed if your designs didn't work out; join the club. You are learning and will get better every year. - Gary Dillard [more]
Home
Go Back   Chief Delphi > Competition > Rules/Strategy
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Closed Thread
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 12-01-2011, 10:54
GaryVoshol's Avatar
GaryVoshol GaryVoshol is offline
Cogito ergo arbitro
no team
 
Join Date: Aug 2005
Rookie Year: 2000
Location: Royal Oak, MI
Posts: 5,762
GaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond reputeGaryVoshol has a reputation beyond repute
A fix creates a problem ...

Post Team Update #1:
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).
Quote:
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)
(emphasis mine)


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.
__________________
(since 2004)
  #2   Spotlight this post!  
Unread 12-01-2011, 11:08
mathking's Avatar
mathking mathking is offline
Coach/Faculty Advisor
AKA: Greg King
FRC #1014 (Dublin Robotics aka "Bad Robots")
Team Role: Teacher
 
Join Date: Jan 2005
Rookie Year: 1999
Location: Columbus, OH
Posts: 642
mathking has a reputation beyond reputemathking has a reputation beyond reputemathking has a reputation beyond reputemathking has a reputation beyond reputemathking has a reputation beyond reputemathking has a reputation beyond reputemathking has a reputation beyond reputemathking has a reputation beyond reputemathking has a reputation beyond reputemathking has a reputation beyond reputemathking has a reputation beyond repute
Re: A fix creates a problem ...

Quote:
Originally Posted by GaryVoshol View Post
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.
  #3   Spotlight this post!  
Unread 12-01-2011, 11:40
AllenGregoryIV's Avatar
AllenGregoryIV AllenGregoryIV is offline
Engineering Coach
AKA: Allen "JAG" Gregory
FRC #3847 (Spectrum)
Team Role: Coach
 
Join Date: Jul 2008
Rookie Year: 2003
Location: Texas
Posts: 2,569
AllenGregoryIV has a reputation beyond reputeAllenGregoryIV has a reputation beyond reputeAllenGregoryIV has a reputation beyond reputeAllenGregoryIV has a reputation beyond reputeAllenGregoryIV has a reputation beyond reputeAllenGregoryIV has a reputation beyond reputeAllenGregoryIV has a reputation beyond reputeAllenGregoryIV has a reputation beyond reputeAllenGregoryIV has a reputation beyond reputeAllenGregoryIV has a reputation beyond reputeAllenGregoryIV has a reputation beyond repute
Send a message via AIM to AllenGregoryIV
Re: A fix creates a problem ...

My interpretation is that the MINIBOT can move autonomously or by the power of the HOSTBOT before deployment but once deployed it can't have any energy imparted on it by the HOSTBOT. The rules does not state the how the MINIBOT must move while attached to the HOSTBOT just how it most move after.

The Q&A will be the final wording but that is how I few this rule change.

So in this case the HOSTBOT could lift the MINIBOT to the DEPLOYMENT LINE but then the MINIBOT would climb off the HOSTBOT and continue up the pole after DEPLOYMENT.
  #4   Spotlight this post!  
Unread 12-01-2011, 12:42
Taylor's Avatar
Taylor Taylor is offline
Professor of Thinkology, ThD
AKA: @taylorstem
FRC #3487 (Red Pride Robotics)
Team Role: Teacher
 
Join Date: Jan 2006
Rookie Year: 2006
Location: Indianapolis, IN, USA 46227
Posts: 4,605
Taylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond reputeTaylor has a reputation beyond repute
Re: A fix creates a problem ...

I know during the animation it was said that minibots should not be deployed before the endgame begins, lest the tower become disabled. I cannot for the life of me find that rule in the manual.
Would one of you be so kind as to point me that way?
__________________
Hi!
  #5   Spotlight this post!  
Unread 12-01-2011, 12:48
Jared Russell's Avatar
Jared Russell Jared Russell is offline
Taking a year (mostly) off
FRC #0254 (The Cheesy Poofs), FRC #0341 (Miss Daisy)
Team Role: Engineer
 
Join Date: Nov 2002
Rookie Year: 2001
Location: San Francisco, CA
Posts: 3,082
Jared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond repute
Re: A fix creates a problem ...

Taylor,

<G17>
  #6   Spotlight this post!  
Unread 12-01-2011, 13:16
earlybird's Avatar
earlybird earlybird is offline
They tried to ship me 2 competition
AKA: Robbie Oehrli
FRC #2849 (Team Ursa Major)
Team Role: Mentor
 
Join Date: Jan 2010
Rookie Year: 2009
Location: Columbia, MD
Posts: 30
earlybird is a jewel in the roughearlybird is a jewel in the roughearlybird is a jewel in the rough
Re: A fix creates a problem ...

Quote:
Originally Posted by AllenGregoryIV View Post
So in this case the HOSTBOT could lift the MINIBOT to the DEPLOYMENT LINE but then the MINIBOT would climb off the HOSTBOT and continue up the pole after DEPLOYMENT.
According to <G19> the mini bot would have to be latched on to the pole at the deployment line. My interpretation of the rule is that once it is in contact with the tower or possibly even breaks the plane the hostbot can't move the minibot in a vertical direction at all with out risking a penalty, even if it just lifts the mini bot up to the deployment line.

<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).
Violation: The TOWER on which the MINIBOT is DEPLOYED is disabled. If the MINIBOT is
DEPLOYED on something other than a TOWER, then the ALLIANCE’S TOWER upon which
the highest RACE SCORE was earned will be discounted.

<G19> means that HOSTBOTS are not allowed to launch the MINIBOT up the pole
at the TARGET, or otherwise contribute to the vertical movement of the MINIBOT.
Energy for vertical movement may not be stored in the MINIBOT before
DEPLOYMENT (except that which is contained within the battery and excluding
incidental kinetic energy stored in the motors or wheels, but NOT, for example, in a
flywheel).
Closed Thread


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 04:13.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi