Go to Post Gosh, I wish that we would've named IndianaFIRST after a candy. - Andy Baker [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 11-01-2014, 19:49
RRLedford RRLedford is offline
FTC 3507 Robo Theosis -- FRC 3135
AKA: Dick Ledford
FRC #3135 (Robotic Colonels)
Team Role: Mentor
 
Join Date: Jan 2010
Rookie Year: 2009
Location: Chicago, IL USA
Posts: 286
RRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond repute
Re: G12 Update clarification

This still does not clarify whether positioning lower goal blocking robot extensions sufficiently across (but outside) their faces, and then leaving them statically positioned while an opponent tries to score the ball past them, would be considered a defensive trapping violation.

If the defensive blocker remains static, the ball's contact with their defensive elements is 100% initiated by the offense bot's pushing of the ball, so IMO it should not be a trapping foul.

If it is not a foul, then many bots will be able to easily prevent any balls being scored at a lower goal with minimum deployment(s) of lower goal blocking elements. It will also raise another concern for when a goal blocking element might be deformed by the ball pushing against it to point of passing inside the plane of the goal face. Since the offensive bot would be causing it to happen, it should not be a foul, but what if ball then gets wedged against inside of goal, against a deformed blocking element such that ball cannot pass further inward or be pull back outward.

That would put scoring on permanent hold for the offensive team, yet it would seem they caused their own demise by trying to force the ball past the goal blocking element. Yet the defender may have intentionally designed their blocking elements to specifically cause this kind of a result.

-Dick Ledford
__________________
FTC 3507 RoboTheosis
FRC 3135 Robotic Colonels

Last edited by RRLedford : 11-01-2014 at 20:02.
  #2   Spotlight this post!  
Unread 11-01-2014, 19:56
Zuelu562's Avatar
Zuelu562 Zuelu562 is offline
Ready for WPI District!
AKA: Jake Janssens
FRC #3623 (Terror Bots)
Team Role: Mentor
 
Join Date: Jan 2010
Rookie Year: 2008
Location: Massachusetts
Posts: 340
Zuelu562 is a splendid one to beholdZuelu562 is a splendid one to beholdZuelu562 is a splendid one to beholdZuelu562 is a splendid one to beholdZuelu562 is a splendid one to beholdZuelu562 is a splendid one to beholdZuelu562 is a splendid one to beholdZuelu562 is a splendid one to behold
Re: G12 Update clarification

Quote:
Originally Posted by RRLedford View Post
This still does not clarify whether positioning lower goal blocking robot extensions sufficiently across (but outside) their faces, and then leaving them statically positioned while an opponent tries to score the ball past them, would be considered a defensive trapping violation.

If the defensive blocker remains static, the contact with them is 100% initiated by the office bot, so IMO it should not be a trapping foul.

If it is not a foul, then many bots will be able to easily prevent any balls being scored at a lower goal with minimum deployment of of lower goal blocking elements.

-Dick Ledford
I feel this is completely legal. The tradeoff is not being able to block both low goals at once (unless you have 2 robots doing this....) and without proper design, the ball will almost instantly go into the low goal the second the defensive mechanism is retracted if the ball is stuck upon the mechanism.

My question is, if the ball is on your mechanism or you attempt to move with an opponent's ball stuck in between your defensive extension and the wall and the ball travels with you, is it possession?
__________________
Team Resume
562 "S.P.A.R.K." - Student Programmer 2008-2011, Field Coach 2011
3623 "Terror Bots" - Technical Mentor, Field Coach 2012 - Present

Volunteer Resume:
BattleCry@WPI 12, 13, 15, 16 - Queuing
BattleCry@WPI 14 - Field Reset
Granite State District Event 2014 - Team Queueing
NEFIRST District Championships '14,'15,'16 - Team Queuing
  #3   Spotlight this post!  
Unread 11-01-2014, 20:17
PVCpirate's Avatar
PVCpirate PVCpirate is offline
FRC Data Nerd
AKA: Anthony Jennings
FRC #1058 (PVC Pirates)
Team Role: Alumni
 
Join Date: May 2010
Rookie Year: 2009
Location: Londonderry NH
Posts: 669
PVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud of
Re: G12 Update clarification

Quote:
Originally Posted by RRLedford View Post
If it is not a foul, then many bots will be able to easily prevent any balls being scored at a lower goal with minimum deployment(s) of lower goal blocking elements. It will also raise another concern for when a goal blocking element might be deformed by the ball pushing against it to point of passing inside the plane of the goal face. Since the offensive bot would be causing it to happen, it should not be a foul, but what if ball then gets wedged against inside of goal, against a deformed blocking element such that ball cannot pass further inward or be pull back outward.

That would put scoring on permanent hold for the offensive team, yet it would seem they caused their own demise by trying to force the ball past the goal blocking element. Yet the defender may have intentionally designed their blocking elements to specifically cause this kind of a result.

-Dick Ledford
(Emphasis Mine)

I think in the situation you described here, the defending team has caused the ball to be stuck in the goal. This would not be the fault of the offensive team, they are just trying to score. If I were a ref(which I'm not), I would probably call trapping here. The ball is "trapped" inside the goal, and this situation is being caused by the defensive team. Additionally, if the defender is unable to pull free, they could be subject to an additional technical foul and/or red card.
__________________
My accomplishments with 1058:
2010 - Granite State Regoinal Winners, Galileo quarterfinalists, IRI quarterfinalists
2012 - GSR Chairman's Award winners
An incredible four years I will never forget
  #4   Spotlight this post!  
Unread 11-01-2014, 21:16
Brandon Ha Brandon Ha is offline
Registered User
FRC #0302 (Dragons)
Team Role: Electrical
 
Join Date: Mar 2012
Rookie Year: 2011
Location: Michigan
Posts: 48
Brandon Ha is on a distinguished road
Re: G12 Update clarification

The easiest way to determine possession is if that drive team changed directions to impact the ball. Or went OUT OF HIS WAY to get to the ball.
Strategically speaking a team might not be fouled for a possession once, but this is not the only time they are seeing you. You should get a good idea of what the robot will be capable of doing by the second match. So if the refs think this is the second time they have seen that same idea it might turn on some ideas.
__________________
We all make mistakes.
I make one everyday.
The important thing is.
( \_/ )
(^_^)
('') ('')
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 00:56.

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