[robocup-small] Proposed Rule Changes for SSL 2006
tomwoe at 163.com
tomwoe at 163.com
Thu Dec 15 07:51:39 EST 2005
>>>>> "David" == David Ball <dball at itee.uq.edu.au> writes:
Hi all
Here is ZjuNlict's opinion.
David> INCREASE FIELD SIZE.
Fine
David> WALLS
Fine
David> LOCAL VISION
Fine
David> RESTART RULES
Fine
David> OFFICIAL COLOURS
Fine.
David> GOALS
Fine.
David> BALL
Fine.
David> VIRTUAL ENERGY BUDGET
Fine.
David> PHYSICAL ENERGY BUDGET
Fine
David> INCREASE NUMBER OF ROBOTS
A
David> CHIP KICKING
B.2
David> LENGTH OF PERIODS / TIMEOUT / HALFTIME:
B
David> RED CARDS / SAFETY ENFORCEMENT:
David> Implementation:
David> 1) When a yellow card offense occurs, the game is stopped. (as per normal)
David> 2) A yellow card signal is sent from referee box to team host computers. (as per normal)
David> 3) The team host computer that received the yellow card must move a robot to the field
David> peripheral so that it can be physically removed by the robot handler.
David> 4) The game continues as per normal
David> 5) The robot must sit out for at least X minutes (current proposal is 2 minute). On the
David> next game stoppage after X-minute, the robot may be placed back by the robot handler
David> (no signal from referee box will be given). The yellow card status will be checked only
David> at the instance stoppage occurs. For example, if a stoppage occurs 1 minute 55 second
David> after a stout, the robot cannot be put back in 5 seconds into the stoppage. This is to
David> prevent teams from delaying stoppages so that they can get their robot back in.
David> Note: The referee box needs to be modified so that it can keep tracks of all yellow card
David> status.
David> Suggestions for offenses worth a time penalty:
David> ----------------------------------------------
David> You could give a time penalty when
David> - The two defender rule is applicable
David> - a robot bumps into another "on purpose"
David> - a team couldn't take a free kick for the third time in a row
David> - a robot enters the 50mm radius at free kicks (restarts) for
David> the third time so the free kick need to be restarted
David> - a robot kicks the ball from the throw-in directly or almost
David> directly off the field repetitive, so the game gets stuck.
David> - a robot loses parts bigger than a screw
David> Advantages over yellow/red card system only:
David> --------------------------------------------
David> - The decision for a time penalty is easier to make for the referee. It penalizes
David> misdoings without taking the
David> chances for the affected team to win. - After the penalty is over. The misdoing is
David> forgiven, no further discussion
David> - For the case of a wrong decision, there is no need for discussion since the time
David> penalty is quite short and won't turnaround the game (If a team has a lot of misdoings
David> then this would be a disadvantage for the team and that would be okay then)
David> - The game could get more fluently since you take out a robot and don't have to stop the
David> while game, with all robots taking their
David> best position again. (Sometime you will have to stop the game because the robot that
David> has to halt is in the way, but then you
David> could "halt" the game and restart it without a "stop" so that all robots are still at
David> their positions when the game goes on
Fine.
We suggest to implement this rule by the refer box. When the
misdoing team receive the "Yellow Card" signal,they must
react to the signal and drive one of their robots out of the
field and hold there still. After the penalty time finished
,when the first "Stop" signal is sent,the refer box should
also send a "PENALTY TIME OVER" signal to the punished team.
And the punished team can react the signal and drive the
robot in the field.
If the punished robot moves in the field during the penalty
time, a "Yellow Card" should be given again.
David> FREE KICK/KICKOFF PROCEDURE:
Fine.
We suggest all restart should be 50mm inside the field.
Regards
Yonghai Wu
ZjuNlict
More information about the robocup-small
mailing list