Go to Post If you do mentor FIRST, be an asset to your team, but know that your students will admire you all the more if you set an example and finish your own homework. - Eugenia Gabrielov [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

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #9   Spotlight this post!  
Unread 15-04-2013, 11:02
J_Miles's Avatar
J_Miles J_Miles is offline
FiM Referee
AKA: Jared Miles
no team (EngiNERDs)
Team Role: Alumni
 
Join Date: Feb 2009
Rookie Year: 2009
Location: Ann Arbor, MI, USA
Posts: 128
J_Miles is a splendid one to beholdJ_Miles is a splendid one to beholdJ_Miles is a splendid one to beholdJ_Miles is a splendid one to beholdJ_Miles is a splendid one to beholdJ_Miles is a splendid one to beholdJ_Miles is a splendid one to behold
Re: A "Dangerous Situation"

Interesting...

(Disclaimer: I was a referee under Mark Garver (The MSC Head Ref) this season at Waterford, and am not a current member of 2337)

There is quite the logical conundrum here. I am personally of the opinion that putting oneself in the position where committing a foul is a possibility places the burden of the foul on that team (in this situation, your team's robot); HOWEVER, it is clearly stated in rule G18-1 that

"Strategies aimed solely at forcing the opposing ALLIANCE to violate a rule are not in the spirit of FRC and are not allowed. Rule violations forced in this manner will not result in assessment of a penalty on the target ALLIANCE .

Violation: TECHNICAL FOUL"

With THAT said, Mark and the rest of the Refs at Waterford discussed this very rule in a situation that arose at Hub City involving 1986, 16, and 2848:
http://www.youtube.com/watch?v=spyRub7z1Bw
The action of 16 forced 2848 into the pyramid. Consequential contact with the pyramid is a foul for the team making contact (Here, 2848); however, per rule 18-1, forcing a team into a foul is a rules violation. The conclusion of our discussion was that NO FOULS would be assessed in this situation because we judge that team 16 was pushing 2848 not to try and force a foul, but rather to attempt to move 2848 out of the way so that 1986 might be able to shoot unhindered.

This seems quite similar to the situation you described. Ultimately, though, it is up to the head referee to make that call. I would expect that 2337 forcing your machine into 67's would not be considered a foul, but if 67 initiated the contact, a foul WOULD be assessed - a technical foul if the contact was deemed "Purposeful or Consequential." Again, ultimately this is up to the head referee to decide, but there are arguments to both the decision made at MSC and a "no-call" philosophy.

My advice would be to ensure that you clarify this same question with the head referee on your field at championships and adjust accordingly.

(As a side-note, getting in between a FCS defender and the FCS robot is not necessarily match-ending because it simply forces the defender to circle around and push from behind. Yes, there may be a delay, but certainly not match-ending because there is no point at which the team attempting to block can safely "sit" to effectively cause a stalemate)
__________________

 


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 06:37.

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