robocup-ssl / ssl-rules Goto Github PK
View Code? Open in Web Editor NEWOfficial RoboCup Small Size League Rule Book
Home Page: https://robocup-ssl.github.io/ssl-rules/
License: GNU General Public License v3.0
Official RoboCup Small Size League Rule Book
Home Page: https://robocup-ssl.github.io/ssl-rules/
License: GNU General Public License v3.0
In the work of #35, some duplicates in the game event table were overlooked and merged into the master.
e.g.
There are two "Events for scoring goals" table
Difference : for "Possible Goal" event, action for one is "Stop → Kick-Off" and the other is "Halt"
There are two "Unsporting Behavior" event, in "Events for Offenses" table and in "Other events" table
There are two "Double touch" event, in "Events for Offenses" table and in "Other events" table
and so on. Most of duplication is caused by "Other events" table, so I think we need to check them again.
It was brought up on Discord, that there is some confusion in regards of the line thickness:
Current state:
Some relevant quotes from the rules:
The line is usually 1cm thick. The precision of ssl-vision is also about 1cm. So in practice, it should not make a significant difference to take the thickness into account or not.
Point (3) can result in a deadlock:
Because I am currently looking deeper into the Shoot-Out I stumbled over the influence of the Rule 4.4.3. Early Termination At A Score Of 10 onto the Rule 10. Shoot-Out.
The rule Early Termination states that if one team manages to score is tenth goal, the game will be automatically terminated and the team with more goals will be declared the winner, regardless of the current game stage.
This could lead to the problem, that according to the rules, the Shoot-Out would be terminated as soon, as one of both teams manages to score its tenth goal and automatically wins, regardless of the number of tries each team still has left.
Yes this case is rather uncommon but theoretically it could happen, that both teams manage to score a goal at every try, which would lead to the point, that the team that started first, gets its tenth goal and the Shoot-Out would be automatically stopped with the final result of 10-9.
As the Shoot-Out only takes place in elimination matches this would result in a rather unsatisfying situation for the losing team.
Due to the fact that I am currently not sure, whether this is a wanted or unwanted approach, I decided to bring this issue up, so that if it in fact is an unwanted behavior, it can get resolved now and the rules could still be adjusted to make the situation clearer.
Rules say that:
8.1.2. Lack Of Progress
There is a lack of progress if only one team is allowed to manipulate the ball (kick-off, direct free kick, indirect free kick, penalty kick) and does not bring the ball into play in time. The time limit is 5 seconds for free kicks in division A and 10 seconds in all other cases.
Is it means that the time limit for kickoff is 10 sec?
The dimensions of the field lines should be consistent.
The current rules caused some confusion for me on how to measure the distance from a line to a robot.
In a Discord discussion, it was mentioned that TIGERs AutoRef measures from the robot's edge. For exampling the distance to the defense area needs to be 0.09+0.2m according to this.
I'd suggest a clarification along (just like how it's done for distance from lines):
Distances from a robot are measured from its nearest side to the respective measurement point, with an assumed radius of 0.09m.
During stop and free kicks, before the ball has entered play, all robots have to keep at least 0.2 meters distance to the opponent defense area.
There is a grace period of 2 seconds for the robots to move away from the opponent defense area.
If a robot keeps standing too close to a penArea, the foul is counted repeatedly every 2 seconds. As this also applies to STOP, this can quickly become annoying.
The current wording of the penalty marks has caused confusion within our team, and problems during the match in the RoboCup 2022. The penalty marks are defined as follows :
For each field half the penalty mark is on the mid-line (not halfway line), 8 meters (division A) or 6 meters (division B) away from the opponent goal center.
It is clear where the two penalty marks are on each half (8 meters from each goal center), but to whom each penalty mark belongs is ambiguous. Intuition tells me that penalties are taken from the penalty mark closest to the opponent's goal, mainly because this is the case in human soccer. This is however not the case.
I'd like to suggest a clarification of the penalty mark from which to take a penalty :
For each field half, the penalty mark is on the mid-line (not halfway line), 8 meters (division A) or 6 meters (division B) away from the opponent's goal center.
The team taking the penalty has to start at the penalty mark that is on the midline and 8 meters (division A) or 6 meters (division B) away from the opponent's goal.
During a penalty kick, in the rules (5.3.5) it says the following
. The defending keeper has to move to the goal line and keep touching it
However the game controller checks if the keeper is on the goal line and between the goal posts, which is also the requirement in human soccer.
I propose changing the wording of the rule such that it is clear the keeper must stay between the goalposts.
Take a look at the following Situation:
There is a direct Free Kick happening and the Ball is already placed correctly, but Yellow just gathered it's second yellow card with the foul, and therefore wants to remove it's robot automatically.
Sadly our AI confirms perfectly to the rules:
Robots can always be taken in and out during game play without notifying the referee if all the following conditions are met:
The robot is at least partially inside the field margin.
The robot is at a distance from the halfway line that must not exceed 1 meter.
The ball must be at least 2 meters away from the halfway line.
It is therefore not allowed to remove the robot, as the ball is too close to the middle line. I want to point out, this problem will most likely never arise in a real world game, as there is a human ref overlooking the game, but still I feel like it's a bug in the rules that can be fixed rather easily.
I can think of 3 different solutions:
I personally think, triggering a robot substitution is the best solution, as this will also help with other situations that can cause confusion in tournaments: The game is stopped, one team has too many robots, and no one realizes why the game is not continuing. Especially with inexperienced GCOs, Refs and Teams this can happen rather often.
From the rule proposal:
Timeouts waste time. Teams should be encouraged to reduce them to a minimum, while still being able to use them for serious issues.
We do not encourage teams to use timeouts for tuning their parameters.
The number and time of timeouts will not change, but after each timeout, the game will restart from a point in front of the team’s defense area (at least 700mm) and with a direct freekick for the opponent team.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.