Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Rules/Strategy (http://www.chiefdelphi.com/forums/forumdisplay.php?f=6)
-   -   Blocking 2 ball autons (http://www.chiefdelphi.com/forums/showthread.php?t=147499)

headlight 21-04-2016 16:40

Re: Blocking 2 ball autons
 
Quote:

Originally Posted by BenHildy (Post 1576706)
I like this! However you do run the risk of having the robot intake both balls and being charged for forcing a penalty on another team. Also, if the balls collide, the the robot, however unlikely, may still pick up the ball launched at their original target. However, both of these issues are quite minor and unlikely. This solution is innovative and certainly would be entertaining to witness! I hope we do!

Its kind of an interesting situation, I wonder if it would really be considered forcing a penalty. On one hand, you didn't load the ball into their robot or otherwise force the ball upon them. On the other hand, you're taking advantage of a pre-programmed behavior to cause their robot to commit a foul.

If this was during teleop there would be no question, the robot that intakes two balls gets the penalty, putting the balls close together is in no way an attempt to cause the other robot to get a penalty. Is autonomous judged differently?

Pretzel 21-04-2016 16:40

Re: Blocking 2 ball autons
 
Quote:

Originally Posted by jspatz1 (Post 1576718)
"G13 During AUTO, ROBOTS may not enter the volume above the MIDLINE.
Violation: FOUL. If contact is made with an opponent ROBOT beyond the MIDLINE (either direct
contact or transitive contact through a BOULDER), an additional FOUL is assessed and the
opponent ROBOT is immediately awarded the CROSSING of the closest DEFENSE from the point
of contact."

The ball has half of it's volume on each side of the midline. This means you do not need to cross it to move it out of position. If the first thing you do in the autonomous mode is simply nudge the boulder, you run very little risk of making transitive contact through a boulder since you will not be touching the boulder by the time the second robot makes a grab for it.

In addition, if you make first contact with the boulder it would be the other team incurring the foul for contact, not you. If your robot is touching a boulder and the 2-ball auto team tries to intake it, they would be making transitive contact through a boulder with you, not the other way around (you are not making transitive contact if you get there first).

In a way I could see this becoming a new kind of canburglar arms race, where teams try to touch the boulder first. From the way the rules appear to be written it seems that if you touch the boulder before the 2-ball auto bot tries to intake it, they're making contact with you and they will be fouled. If they make contact first, then you nudging it will be considered a foul. Thus, the speed at which you can get to that essential (for a 2-ball auto) boulder will become more important as the stakes get higher.

Littlepchan 21-04-2016 16:44

Re: Blocking 2 ball autons
 
Assuming one of the two balls is taken, we would have to look at the next step and whatever defense is in position 1. If the defense in position 1 something that can be easily crossed like the rough terrain then a team could supposedly cross and shoot (best case scenario). Worst case scenario, the opposing team gets 5 extra points and another life point off a defense.

Hitchhiker 42 21-04-2016 17:34

Re: Blocking 2 ball autons
 
Quote:

Originally Posted by willpflem (Post 1576697)
It seems to me that doing this, and therefore starting in front of the secret passage, would prevent you from running a profitable auto yourself (minimum of a cross). In my opinion any winning alliance will have an auto for each one of its alliance members. So the question to me boils down to, 'Is blocking their 10 points more profitable than gain 10 of your own?'

Yes, because you are helping stop their capture (by not letting them score) in addition to denying them the points.

Kevin Sevcik 21-04-2016 17:34

Re: Blocking 2 ball autons
 
Quote:

Originally Posted by Abhishek R (Post 1576723)
Well, it's possible that you start with no ball, grab the ball the two-baller intends to take, then score that ball by crossing over the nearest defense and shooting. The risk you run in that case is "are you fast enough to grab the ball before the other team does?" Because if you don't get the ball, you won't score any balls in auto.

Oh man, not this again. At least it's optional this time and not as likely to end with two robots semi-permanently attached...

Seriously, though, it seems like everyone is dropping a ball off by the wall. Instead of a drag race, it seems like you would be better off outtaking your own ball at the dropped ball to disrupt its position and cause a hiccup that way.

I actually think this is the only viable option, since it's really unlikely you can successfully start between the midline and your opponent's secret passage. Here's what the auto would look like:
Setup: In front of defense 1 lined up to intake ball 2 (one down the line from the one you opponent's intaking).
1.Rotate to face your opponent's dropped ball, outtake at high speed.
2.Rotate straight, intake mid-line ball.
3.Cross defense in front of you.
4.Score ball in auto.

Super simplified, of course. You can skip 2 and 4 if you're already not scoring a ball in auto, though. I think it'd be doable, the question is whether you can hit the dropped ball accurately enough and hard enough to disrupt things. And whether you'll get a foul for using a boulder to make a defense harder if one or both carom into the low-bar and jam things up there.

Donut 21-04-2016 17:51

Re: Blocking 2 ball autons
 
Quote:

Originally Posted by jspatz1 (Post 1576718)
"G13 During AUTO, ROBOTS may not enter the volume above the MIDLINE.
Violation: FOUL. If contact is made with an opponent ROBOT beyond the MIDLINE (either direct
contact or transitive contact through a BOULDER), an additional FOUL is assessed and the
opponent ROBOT is immediately awarded the CROSSING of the closest DEFENSE from the point
of contact."

In my interpretation, transitive means direct contact. Once I release a boulder from my robot I can no longer be in transitive contact with an opposing robot through that boulder. I do not think that an opposing robot will get to the mid-line ball faster than the ball reversed out of the defensive robot will. Transitive is not defined in the game manual glossary, so it is open to interpretation.

Quote:

Originally Posted by Kevin Sevcik (Post 1576748)
I actually think this is the only viable option, since it's really unlikely you can successfully start between the midline and your opponent's secret passage. Here's what the auto would look like:
Setup: In front of defense 1 lined up to intake ball 2 (one down the line from the one you opponent's intaking).
1.Rotate to face your opponent's dropped ball, outtake at high speed.
2.Rotate straight, intake mid-line ball.
3.Cross defense in front of you.
4.Score ball in auto.

This is more along the lines of what I think would work, but for a mid-line block rather than finding the opposing dropped ball. There is no rule that a robot start with bumpers parallel to the field walls, a robot could start angled so that it can immediately release its intake ball to knock the mid-line ball off course. Then it can either cross or (in your more daring method) attempt to intake a mid-line ball itself before crossing. I think the strategy only really makes sense if your robot has little to no chance of scoring a high goal in autonomous (low goal only bot, defense bot with less shooting capability), in which case the extra mid-line ball after defending the 2 Ball auto is a pretty low benefit for the effort involved.

Caleb Sykes 21-04-2016 18:58

Re: Blocking 2 ball autons
 
Quote:

Originally Posted by Kevin Sevcik (Post 1576748)
Seriously, though, it seems like everyone is dropping a ball off by the wall. Instead of a drag race, it seems like you would be better off outtaking your own ball at the dropped ball to disrupt its position and cause a hiccup that way.

That sounds like a G39 violation to me.

However, I should make it clear that I'm not a ref, so I don't even have the right to comment. :rolleyes:

apm4242 21-04-2016 19:13

Re: Blocking 2 ball autons
 
Quote:

Originally Posted by Caleb Sykes (Post 1576782)
That sounds like a G39 violation to me.

However, I should make it clear that I'm not a ref, so I don't even have the right to comment. :rolleyes:

Yeah, this may be a dumb question, but how do all 2-ball autos not violate G39?

G39 ROBOTS are prohibited from launching BOULDERS unless they are in contact with the opponent’s TOWER or carpet in the opponent’s COURTYARD, and not in contact with any other carpet.

Isn't launching defined as intentionally imparting any momentum to the ball? Therefore, wouldn't intentionally dropping the 2nd ball be launching?

Similarly, how does the 2-ball auto defense by launching a boulder to disrupt the pickup not violate G-39?

EDIT: This was all I could find on Q&A:

Q533
Q. Can you further clarify the definition of "launching" as it applies to G39? Would either of these actions be considered a G39 violation if performed while in contact with the Neutral Zone or a team's own Courtyard: A. A robot very weakly ejects a BOULDER through an upward-facing mechanism normally used for shooting, such that it rises a minimal height required to clear the mechanism and then drops to the ground. B. A robot forcibly ejects a ball at ground level, rolling it across the field.

A. Good question. Releasing a BOULDER such that it is not shot in the air, but dropped from a certain height is not launching. A ROBOT that "forcibly ejects a ball at ground level" would be considered "launching," and this will be clarified in Team Update 03.

Although, I still think it's vague

jspatz1 21-04-2016 20:37

Re: Blocking 2 ball autons
 
I think it is very unlikely for an "arms race" of speed to the first ball to become a thing. Firstly, there are only a handful of robots, out of hundreds at CMP, that have demonstrated the 2-ball auto. The odds of meeting one in a match and being prepared to reach this ball faster than them (< 0.5 seconds?) in a match where they decide attempt it is extremely small. Can burglars in 2015 were much, much more common.

Secondly, the space available between this first ball and the berm on the defensive side is very narrow. Most robots would not fit in this space facing the ball. We once tried to place a dead partner in this space, and could not fit them there even sideways. Any movement required by the defensive bot is unlikely to win a race to the ball, the 2-baller has a significant set-up advantage.

Caleb Sykes 21-04-2016 20:44

Re: Blocking 2 ball autons
 
Quote:

Originally Posted by jspatz1 (Post 1576821)
Secondly, the space available between this first ball and the berm on the defensive side is very narrow. Most robots would not fit in this space facing the ball. We once tried to place a dead partner in this space, and could not fit them there even sideways. Any movement required by the defensive bot is unlikely to win a race to the ball, the 2-baller has a significant set-up advantage.

Starting the match partially inside of the secret passage is perfectly legal.

jspatz1 21-04-2016 21:05

Re: Blocking 2 ball autons
 
Quote:

Originally Posted by Caleb Sykes (Post 1576824)
Starting the match partially inside of the secret passage is perfectly legal.

I only meant that this area is not clear and is obstructed by the berm.

Donut 21-04-2016 21:09

Re: Blocking 2 ball autons
 
Quote:

Originally Posted by apm4242 (Post 1576788)
Q533
Q. Can you further clarify the definition of "launching" as it applies to G39? Would either of these actions be considered a G39 violation if performed while in contact with the Neutral Zone or a team's own Courtyard: A. A robot very weakly ejects a BOULDER through an upward-facing mechanism normally used for shooting, such that it rises a minimal height required to clear the mechanism and then drops to the ground. B. A robot forcibly ejects a ball at ground level, rolling it across the field.

A. Good question. Releasing a BOULDER such that it is not shot in the air, but dropped from a certain height is not launching. A ROBOT that "forcibly ejects a ball at ground level" would be considered "launching," and this will be clarified in Team Update 03.

Well scratch my idea off the list. Under this strict interpretation any reversing of an intake with decent speed while in the Neutral Zone should be called as a launching violation. This was not something we were watching for when I was reffing and I would not have called a penalty for that without having this Q&A brought up.

The other Gabe 21-04-2016 21:10

Re: Blocking 2 ball autons
 
Quote:

Originally Posted by apm4242 (Post 1576788)
Yeah, this may be a dumb question, but how do all 2-ball autos not violate G39?

G39 ROBOTS are prohibited from launching BOULDERS unless they are in contact with the opponent’s TOWER or carpet in the opponent’s COURTYARD, and not in contact with any other carpet.

Isn't launching defined as intentionally imparting any momentum to the ball? Therefore, wouldn't intentionally dropping the 2nd ball be launching?

Similarly, how does the 2-ball auto defense by launching a boulder to disrupt the pickup not violate G-39?

Actually, based on the information you currently have, not a dumb question at all. my guess would be that the refs are only considering it "launching" if you're trying to score a boulder in a goal. otherwise, teams potentially wouldn't be able to do two rather important things:
1. eject boulders that are improperly loaded into their machines
2. eject a second boulder if they accidentally pick up 2 of them
without being subject to a G39

now as for how this relates to autonomously blocking their autos, I see this as very grey area. there's certainly nothing outright prohibiting it, but there's nothing that out rightly allows it either

personally, I think they should allow it. I'd like to see these battles happen :P

(I don't have any official weight behind what I say here, just how I think it's being/should be interpreted)

apm4242 22-04-2016 07:50

Re: Blocking 2 ball autons
 
Quote:

Originally Posted by The other Gabe (Post 1576837)
personally, I think they should allow it. I'd like to see these battles happen :P

I agree. Anyone else think it's odd that dropping a boulder and having it hit your bumper which causes it to roll across the floor is ok but rolling a boulder across the floor is not?

I'm definitely not against 2-ball autos - they're undeniably awesome and should be allowed. It just seems like this Q&A response is written to specifically allow them...

Anyway, just a thought.

BoilerMentor 22-04-2016 08:05

Re: Blocking 2 ball autons
 
Quote:

Originally Posted by JesseK (Post 1576714)
There is no way to push a ball out of the way in auton without pushing it towards the outer works that the opponents are consistently crossing. This means that in teleop, if those balls are near those outer works they are effectively the opposing alliance's balls. At that point, for you to retrieve them you run the risk of contacting the opponent when they're in the outer works.

I'd argue having the boulders against the outer works that you're trying to cross is actually a larger obstacle to most teams than it is an aid. If the boulders are in that position care must be taken in crossing, because a poorly positioned boulder plus a hasty crossing can equal a tortuga, or at a minimum a robot getting tied up with a ball for some portion of teleop.

******Qualification: What follows below is probably not a particularly gracious or professional choice in the strategy department and I wouldn't endorse it. I'm simply observing that it could be a possibility*******

In fact, that may become a part of the strategy. If an alliance were to push the boulder into the opponents outer works while they're trying to complete a secondary auto crossing they could end up tied up for the rest of the match, eliminating significant scoring potential and making breach difficult (if a defense is obstructed by the incapacitated robot) and capture an impossibility


All times are GMT -5. The time now is 17:50.

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