The Small Size League wiki has moved. Up-to-date information is available at the new wiki.
Information for Teams
Three technical challenges will be held at RoboCup 2014, out of which the Double-Size Field technical challenge is compulsory for teams to proceed beyond the round-robins.
These challenges are designed to encourage SSL teams to develop technical contributions and to test ideas that can evolve the league towards the RoboCup goal of 2050. In order to motivate more teams to participate in the challenges, there is no qualification constraint, and the Committees encourages all the participating teams to compete in the challenges.
For a team to qualify beyond the round robins, they must successfully participate in the double-sized field technical challenge. Successful participation is declared after scoring at least 2 points. Points will be awarded for the demonstrating the following skills on the double-sized field, where each skill is scored only once:
In addition to these points, additional bonus points will be awarded to teams that play on the double-sized field for actual competition matches:
Procedure for the Double-Sized Technical Challenge:
This challenge will test the accuracy of a team’s autonomous referee software. Software entered in this challenge does not need to be capable of autonomously running an entire game; rather, the intent of this technical challenge is to demonstrate building blocks and provide a solid foundation on which others can build more advanced autonomous referee systems.
A team will be awarded the specified number of points after the software correctly identifies the specified event for the third time (no further points are awarded for additional detections, nor for two or fewer detections of a particular event):
Any software that identifies one of the above events when it did not, in fact, occur will lose one point per false positive identification.
To participate in this challenge, all autonomous referees must be designed to receive SSL-Vision and referee box packets from the network to identify game state, and must be configured to avoid sending any packets onto the network.
To avoid any unfair benefit, all participants will simultaneously judge a single live RoboCup game. All autonomous referees will be attached to the field network. A neutral third party will monitor each autonomous referee computer’s display; teams are responsible for making their autonomous referee software easy enough to explain to this third party. Please consider the use of a scrolling log format (this could be as simple as writing messages to standard output), for ease of reading and re-examination of past output. The neutral third party will record each instance of an event identified by the autonomous referee, along with whether the positive identification was true or false.
For the purposes of this technical challenge, a positive identification is considered true if and only if the human referee on duty at the game makes the same call. As the purpose of this challenge is to detect specific events, not to run a complete game, the referee will be requested to announce all relevant events, including those (s)he would not normally call due to e.g. the precedence rules or anticipated benefit rules set out in section 5.2 if the Laws of the Game. The referee will also be requested to consider input from his/her assistant when announcing these events, as some events may happen outside the referee’s line of sight.
In order to be declared as successfully participating in this technical challenge, a team’s autonomous referee software must: