Hi Chris,<div><br></div><div>I would like to clarify the rule regarding "catching" chip kicks in the following scenario: </div><div><br></div><div>Scenario:</div><div>1. Yellow robot 0 chip kicks the ball towards blue goal.</div>
<div>2. Blue goalie (blue robot 0) touches the ball, and the ball bounces off its front.</div><div>3. The ball, bouncing off the front of blue goalie, hits the back of blue defender robot 1.</div><div>4. The ball, after hitting the back of blue defender robot 1, enters the blue goal.</div>
<div><br></div><div>Would this scenario result in a goal for yellow team?</div><div><br></div><div>-Joydeep</div><div><br><div class="gmail_quote">On Sun, Mar 17, 2013 at 2:01 AM, Christopher Head <span dir="ltr"><<a href="mailto:chead@chead.ca" target="_blank">chead@chead.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA256<br>
<br>
Dear teams,<br>
I’m happy to announce that the technical committee, with some<br>
much-appreciated input from the organizing committee, has prepared the<br>
new rules for use at RoboCup 2013. As always, these rules are available<br>
on the league’s wiki, at <<a href="http://robocupssl.cpe.ku.ac.th/rules:main" target="_blank">http://robocupssl.cpe.ku.ac.th/rules:main</a>>.<br>
Other than small grammatical and formatting tidying, I’d like to bring<br>
your attention to the following major changes (I suggest following<br>
along in the “Changes from 2012 to 2013” document, so you can see what<br>
was removed as well as what was added).<br>
<br>
In subsection 3.1.3, text is added indicating that goalie interchange<br>
requires the referee, and from there the teams (via the refbox), to be<br>
notified of the goalie’s pattern number (a new refbox including this<br>
feature is almost ready for release and will use the Protobuf packet<br>
format as discussed a while ago on this mailing list).<br>
<br>
Subsection 3.1.4 has been removed because the rules about card handling<br>
have been coalesced and rewritten later on.<br>
<br>
In subsection 9.3, the phrase “other than due to a forced restart” has<br>
been added to the double touch rules. In my opinion, it makes no sense<br>
to apply the double touch rules to a forced restart because both teams,<br>
and multiple robots per team, can touch the ball at the same time;<br>
there is no specific “kicker” who should not be allowed to double<br>
touch. The original occurrence of the phrase “neutral restart” has been<br>
replaced by “forced restart” for clarity, as that is what it is called<br>
in the referee box.<br>
<br>
In subsection 9.3 further down, a line has been added making it<br>
absolutely clear that a forced restart has only happened and teams may<br>
only approach the ball after the referee indicates the forced restart.<br>
<br>
In subsection 12.1, the broken robot rule has been removed (as it now<br>
awards an indirect, not a direct, free kick; this was intended all<br>
along but accidentally put in the wrong section). The two defenders<br>
rule was deleted from this section and placed in subsection 12.2<br>
regarding penalty kicks; having it here was pointless as two defenders<br>
could never happen except inside the defense area.<br>
<br>
In subsection 12.2, a new two defenders rule was added that now only<br>
awards a penalty kick if the second defender and the ball are both in<br>
the defense area at the same time, or if the second defender touches the<br>
ball while inside the defense area (the defender might be straddling<br>
the line of the defense area, so the second defender could touch the<br>
ball while the ball itself is not actually in the defense area—this is<br>
still a penalty). This objective metric should reduce confusion about<br>
whether the second defender materially affected gameplay.<br>
<br>
In subsection 12.3, the broken robot rule removed from 12.1 has been<br>
inserted, and the chip goal rule has been updated. I have summarized<br>
the new chip goal rule in a separate paragraph below, as it affects many<br>
parts of the text.<br>
<br>
In subsection 12.4.1, the yellow card handling rule has been rewritten.<br>
As the rule was previously written, it would in theory have allowed a<br>
robot to be sent off with a yellow card but then be interchanged for<br>
some other robot immediately; of course, we never played that way,<br>
rather taking a yellow card to decrease the number of robots allowed on<br>
the field without affecting any specific robot. The new rule doesn’t<br>
actually change how we play, it just updates the text to reflect<br>
reality.<br>
<br>
Subsection 12.4.2 makes the same update for red cards.<br>
<br>
Decision of the Technical Committee #7 of Law 12 only applied to the<br>
old chip goal rules, so it is deleted.<br>
<br>
Subsection 13.2 updates the outcomes of direct free kicks for the new<br>
chip goal rule.<br>
<br>
Subsection 14.4 updates the outcomes of penalty kicks for the new chip<br>
goal rule.<br>
<br>
Law 15 indicates what happens if a throw-in is kicked directly into a<br>
goal. The previous rules simply stated that this was not permitted,<br>
without indicating what happened in result. This would mean that the<br>
ruling would degenerate to the ball crossing the goal line without<br>
scoring, which would grant a goal or corner kick to the opponent of the<br>
last team to touch the ball. However, there is a problem with this<br>
interpretation: throw-ins are signalled to the teams as indirect free<br>
kicks, but actual indirect free kicks award a goal kick to the kicking<br>
team if they get the ball directly into the goal. Therefore, with the<br>
rules as previously written, the same signal would sometimes make a<br>
direct kick into the goal a good thing (indirect free kick) but<br>
sometimes a bad thing (throw-in)! The two added clauses make the<br>
throw-in follow the same rules as the indirect free kick, thus removing<br>
this confusion.<br>
<br>
Subsections 16.1 and 17.1 update the outcomes of goal and corner kicks<br>
for the new chip goal rule.<br>
<br>
Subsection A.3 is added and explains the semantics of an abandoned<br>
(forfeit) match.<br>
<br>
Subsection A.4 is added and dictates that round-robin games shall end<br>
early if the score difference between the two teams reaches ten points.<br>
<br>
Throughout various sections, text has been updated for the new chip<br>
goal rules. The new chip goal rules are intended to simplify the rules<br>
and encourage more chipping. The fundamental principles of the new<br>
rules are as follows:<br>
<br>
(1) Chip goals are usually permitted. However, as a goalie in actual<br>
soccer would be allowed to catch a high-flying ball with his or her<br>
hands, so a goalie in SSL will be allowed to “catch” a ball. Of course,<br>
the robot does not actually have any way to catch the ball. Therefore,<br>
the chip goal rule dictates that if the ball flies above 150 mm, touches<br>
the goalie, and then goes directly into the goal without touching any<br>
other robot, then the goalie is considered to have caught the ball; no<br>
goal is awarded, and instead the defending team is given an indirect<br>
free kick. This rule only applies if the last robot to touch the ball<br>
before the goalie is an attacker; it does not apply if the ball touches<br>
a defender, then touches the goalie, then enters the goal.<br>
<br>
(2) Chip goals directly from restarts of play (other than neutral<br>
restarts, i.e. Force Start) are not permitted; they are generally<br>
handled the same as a goal scored from an indirect free kick, but only<br>
for the kicker’s opponent’s goal—these rules do not apply to own goals.<br>
Specifically:<br>
(a) A direct chip goal from a direct free kick awards the kicker a goal<br>
kick (just like any direct goal on an indirect free kick).<br>
(b) A direct chip goal from an indirect free kick awards the kicker a<br>
goal kick (this is true for ANY direct goal from an indirect free kick,<br>
so no rule is needed).<br>
(c) A direct chip goal from a goal kick causes the goal kick to be<br>
retaken.<br>
(d) A direct chip goal from a corner kick awards the kicker a goal kick.<br>
<br>
(3) Chipping shall not be used for penalty kicks. If the kicker chips<br>
on a penalty kick and the ball rises above 150 mm before it touches the<br>
goalie or the goal structure, the penalty kick is forfeit—no goal is<br>
awarded if the ball goes in, and the kick is not retaken.<br>
<br>
Please feel free to contact this list with any questions or concerns<br>
or, for confidential matters, the Technical Committee (at<br>
<<a href="mailto:rc-ssl-tc@lists.robocup.org">rc-ssl-tc@lists.robocup.org</a>>) or me personally (at <<a href="mailto:chead@chead.ca">chead@chead.ca</a>>).<br>
<br>
Christopher Head<br>
RoboCup Small Size League Technical Committee Chair<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2.0.19 (GNU/Linux)<br>
<br>
iF4EAREIAAYFAlFFXE4ACgkQnfE3lq0v9Iw2EAD/WFeHlerMj6uNsdWe1RQ/ajCT<br>
4Tg77VmhhrpFMA3tbPwA/jG87Ewo6HVJNEgsUbdH3fBfVYK0pml5C35628s8Dy8V<br>
=Yz6W<br>
-----END PGP SIGNATURE-----<br>
_______________________________________________<br>
robocup-small mailing list<br>
<a href="mailto:robocup-small@cc.gatech.edu">robocup-small@cc.gatech.edu</a><br>
<a href="https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small" target="_blank">https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small</a><br>
</blockquote></div><br></div>