<div dir="ltr"><div class="gmail_quote">The pre-registration deadline for RocoCup2017 Soccer Simulation 2D League</div><div class="gmail_quote">is approaching.</div><div class="gmail_quote">The pre-registered teams are listed in<br></div><div class="gmail_quote"><br></div><div class="gmail_quote"><span style="color:rgb(68,68,68);font-family:roboto,helvetica,arial,sans-serif;font-size:13px"> <a href="https://goo.gl/9TvuuQ">https://goo.gl/9TvuuQ</a></span><br></div><div class="gmail_quote"><br></div><div class="gmail_quote"><div class="gmail_quote">If you cannot find your team in the list or you intend to participate the competition, please send</div><div class="gmail_quote">the pre-registration infomation to <a href="mailto:akym@fukuoka-u.ac.jp">akym@fukuoka-u.ac.jp</a> by Feburuary, 26th.</div><div><br></div></div><div class="gmail_quote"><div>----------</div><br><div dir="ltr"><div><div>Call for Participation<br></div><div><br></div><div>Soccer Simulation League - 2D Simulation Competition, RoboCup 2017</div><div>July 27 - July 30, 2017 (Nagoya, Japan)</div><div><a href="http://www.robocup2017.org/" target="_blank">http://www.robocup2017.org/</a></div><div><br></div><div><br></div><div>Introduction</div><div>------------</div><div>The RoboCup 2D Simulated Soccer League is the oldest of the RoboCup</div><div>Soccer Simulation Leagues. It is based on the RoboCup Soccer Simulator</div><div>that enables two teams of 11 simulated autonomous robots plus an</div><div>autonomous coach agent to play a game of soccer with very realistic</div><div>rules and game play. Due to its stability the RoboCup Soccer Simulator</div><div>is a very good research and educational tool for multiagent systems,</div><div>artificial intelligence and machine learning.</div><div><br></div><div>We would like to invite you to participate in the RoboCup 2017 Soccer</div><div>Simulation League, 2D competition, which will take place July 27 -</div><div>July 30 2017, in Nagoya, Japan. To pre-register all teams have to</div><div>provide a Team Description Paper, and in case they are based on</div><div>another team under a license they have to publish the agent source</div><div>code. The teams will also have to provide a binary file and logfiles</div><div>showing the team game play quality.</div><div><br></div><div><br></div><div>Schedule</div><div>--------</div><div>Team Pre-Registration Deadline: February 26, 2017 (Sunday) - 23:59 UTC</div><div>Materials Submission Deadline: March 12, 2017 (Sunday) - 23:59 UTC</div><div>Qualification Notification: March 28, 2017 (Tuesday)</div><div><br></div><div><br></div><div>Qualification</div><div>--------------</div><div>In RoboCup 2017 up to 24 teams will be allowed to participate in the</div><div>2D Simulation competitions. Qualification is based on the quality of</div><div>the TDP, and the team's current performance based on provided logfiles.</div><div>Previous achievements in RoboCup and scientific contributions to the</div><div>RoboCup community in past years are also relevant for qualification.</div><div>There are several general rules on which the qualification processes</div><div>as well as the tournaments are based:</div><div><br></div><div>1. One-Fourth-Rule: Only one fourth of the participating teams may be</div><div>from the same country. With 24 places in RoboCup 2017 only 6 teams per</div><div>country are allowed. If a team is situated in more than one country,</div><div>the bound location counts. Teams infringing this rule will be ignored</div><div>in the ordered list of qualified teams. False statement results in</div><div>penalty. See Appendix A.1 for further explanations.</div><div><br></div><div>2. One-Team-Per-Research-Institut<wbr>ion:</div><div>Each university or research institute may only qualify one team. If a</div><div>team is affiliated with more than one institution, the unbound</div><div>affiliation counts. Teams infringing this rule will be ignored in the</div><div>ordered list of qualified teams. False statement results in penalty.</div><div><br></div><div>3. Plagiarism-Penalty:</div><div>If a team commits plagiarism, the team and its members will be banned</div><div>from participation for this and next year's RoboCup. The term</div><div>plagiarism comprises any use of external knowledge without proper</div><div>referencing, i.e. copying or using the thoughts, ideas, texts or</div><div>language in general and presenting them as their own. This applies for</div><div>Team Description Papers as well as logfiles, team code and binaries.</div><div>All kinds of licenses and copyright have to be respected. This applies</div><div>for the qualification process as well as the RoboCup tournaments.</div><div>Please be aware that when a team is found guilty of committing</div><div>plagiarism it is disqualified and banned at any time. This may also be</div><div>in the middle of the tournament.</div><div><br></div><div>4. No-Show-Penalty:</div><div>If a team qualifies for RoboCup 2017, but is not able to participate,</div><div>it has to cancel its participation ONE MONTH before the RoboCup-2017’s</div><div>final registration deadline for the TEAM (by an email to Hidehisa Akiyama</div><div>akym at <a href="http://fukuoka-u.ac.jp" target="_blank">fukuoka-u.ac.jp</a>, in order to give the next-ranked team the</div><div>chance to take its place. If a team fails to observe this rule</div><div>('no-show'), the team and its members will be banned for RoboCup-2018</div><div>competition.</div><div><br></div><div>5. Academic-Fairness-Rule:</div><div>If any team breaches general academic fairness in any other way, it</div><div>has to face penalties as well.</div><div><br></div><div>6. Automatic-Qualification-Rules:</div><div>The top four teams from last RoboCup (i.e., Gliders, Helios, Ri-one,</div><div>and CSU_Yunlu) are automatically qualified (after pre-registering</div><div>their teams and submitting appropriate materials). The remaining teams</div><div>will be selected through the qualification process.</div><div><br></div><div><br></div><div>Pre-Registration</div><div>----------------</div><div>All teams wishing to qualify need to pre-register before the deadline</div><div>(26 February 2017). To pre-register, send an e-mail to akym at</div><div><a href="http://fukuoka-u.ac.jp" target="_blank">fukuoka-u.ac.jp</a> with the subject '2017 Pre-registration TeamName'.</div><div>The e-mail should contain the following information:</div><div><br></div><div>1. Team-Name:</div><div>2. Country:</div><div>3. Affiliation:</div><div>4. Team-Leader:</div><div>5. Team Members:</div><div>6. Contact e-mail:</div><div>7. Base-Team:</div><div>8. Dependencies:</div><div><br></div><div>You should receive a confirmation e-mail for your pre-registration.</div><div>Affiliation is the team's organization, institute or university.</div><div>Dependencies should include all dependencies of your team binaries</div><div>from the standard repositories (so every team binary should be executable</div><div>at the tournament). Under Base-Team each team using another team as base</div><div>for their agents, has to specify this team. Please note that you have to</div><div>provide correct and full information and giving false or incomplete</div><div>statement will be penalized with banning of the team and its members.</div><div>Please be aware that with respect to gentlemanly play, we will NOT allow</div><div>any team name changes from the pre-registration to the competition in</div><div>RoboCup 2017. If a team has based its agent on external code or libraries</div><div>published under certain licenses or copyright, it has to observe the</div><div>according rules. In most cases this will be the GNU General Public License,</div><div>i.e. a proper disclaimer has to be included in Team Description Paper and</div><div>source code and the source code has to be submitted as well. After</div><div>official RoboCup competitions the binaries will be published, i.e. the</div><div>rules of the corresponding license have to be respected as well. For</div><div>GPL this also implies publishing the code.</div><div><br></div><div><br></div><div>Qualification Materials</div><div>-----------------------</div><div>All teams who wish to qualify need to send their qualification</div><div>materials by the deadline (12 March 2017). To send the</div><div>qualification materials, send an e-mail to akym at <a href="http://fukuoka-u.ac.jp" target="_blank">fukuoka-u.ac.jp</a></div><div>with the subject '2017 Qualification Materials TeamName'. The e-mail</div><div>should contain the following information and files:</div><div><br></div><div>1. Team-Name:</div><div>2. Country:</div><div>3. Affiliation:</div><div>4. Team-Leader:</div><div>5. Team Members:</div><div>6. Contact E-Mail:</div><div>7. Base-Team:</div><div>8. Dependencies:</div><div><br></div><div>Attachment Files:</div><div> 9. Team Description Paper ('TDP_TeamName.pdf')</div><div>10. Team Binary (and also source code depending on the base code license)</div><div>11. Links to logfiles (stored as a single file, 'Logfiles_TeamName.tar.gz')</div><div><br></div><div>In order to participate in qualification, a team has to send as</div><div>attachments a Team Description paper, the team current binary as well</div><div>as links to logfiles showing the team's game play quality. The deadline for</div><div>submission is March 12th, 2017.</div><div><br></div><div><br></div><div>Team Description Paper</div><div>----------------------</div><div>Each team has to submit a team description paper (in English)</div><div>describing the focus and ideas as well as recent advancements</div><div>implemented in the team. This paper must have a length of 4 to 6 pages</div><div>in Springer LNCS style and has to be submitted as PDF (to be named</div><div>'TDP_TeamName.pdf'). Please note: A team can only be qualified if the</div><div>quality of its TDP is appropriate!</div><div>The Team Description Paper (TDP) should comprise, among other things:</div><div>the scientific focus of the team; team's current efforts; progress</div><div>since last TDP/competition; team base code and description how the</div><div>team is different from the base code; originality of the team's</div><div>approach; results (team results or ideally results achieved using the</div><div>team's main scientific contribution(s)); related work (at least 5 and</div><div>ideally more than 10 references comparing the work with related work</div><div>developed by other teams).</div><div>Please be aware that the TDP has to describe the team's very own</div><div>scientific efforts and explicitly illustrate whether a team has used</div><div>external knowledge (ideas, code, agent base or the like) to build</div><div>upon. If a team did use knowledge not evolved by this team, the own</div><div>achievements have to be outlined in contrast to this. This also</div><div>applies if one or more team members have switched from another team or</div><div>a new team is created on the base of another even though the involved</div><div>persons have not changed. If external knowledge is used but not</div><div>referenced, explained and differentiated from in the TDP, the team and</div><div>its members will be penalized with banning for this and next year's</div><div>RoboCup.</div><div><br></div><div><br></div><div>Team Binary/Source Code</div><div>-----------------------</div><div>Teams should send an attachment with a working binary. Depending on</div><div>the base code license teams should also provide the team's complete</div><div>source code. Team binary or source code should be compressed in a</div><div>single file named ('Binary_TeamName.tar.gz' or</div><div>'Source_TeamName.tar.gz').</div><div><br></div><div><br></div><div>Logfiles</div><div>--------</div><div>In order to assess the team's performance and evaluate its scientific</div><div>efforts in the context of game play, teams have to submit one logfile</div><div>against one of the top teams of last year's RoboCup</div><div>(<a href="http://chaosscripting.net/files/competitions/RoboCup/WorldCup/2016/2DSim/binaries/" target="_blank">http://chaosscripting.net/fil<wbr>es/competitions/RoboCup/WorldC<wbr>up/2016/2DSim/binaries/</a>)</div><div>and one logfile against the latest agent2d</div><div>(<a href="http://sourceforge.jp/projects/rctools/downloads/55186/agent2d-3.1.1.tar.gz/" target="_blank">http://sourceforge.jp/project<wbr>s/rctools/downloads/55186/<wbr>agent2d-3.1.1.tar.gz/</a></div><div>or later). Logfiles comprise both rcg and rcl in version 5</div><div>(server::game_log_version = 5) generated with compression</div><div>(server::game_log_compression = 1 and server::text_log_compression =</div><div>1) on using the most recent version of the Soccer Server. These</div><div>logfiles have to prove that the team is competitive enough to</div><div>participate and demonstrate the team's characteristics.</div><div><br></div><div>Due to the size of logfiles, it is recommended to store your files online</div><div>and send only the link(s).</div><div><br></div><div><br></div><div>Qualification Results</div><div>-----------------------</div><div>The TDPs and logfiles of all teams will be peer reviewed by experts in</div><div>2D RoboCup Simulation League nominated by the OC. The reviewers will</div><div>evaluate the qualification materials and rank the teams. The ranks</div><div>will be averaged into a global ranking and the top teams on that</div><div>ranking will be qualified for the RoboCup 2D simulation competition.</div><div>Qualification results will be announced on March 28 2017. Please</div><div>note that the submitted materials of all qualified teams will be</div><div>made publicly available during the announcement of qualification</div><div>results.</div><div><br></div><div><br></div><div>Appendix</div><div>--------</div><div>A.1 Explanations to General Rule 1</div><div>"If a team is situated in more than one country, the bound location</div><div>counts." General rule 1 defines an upper bound of 6 teams from the</div><div>same country. If 6 qualified teams already originate from country A</div><div>and there is a team XY originating from country A as well as country</div><div>B, team XY is not allowed to participate in RoboCup despite the fact</div><div>that the quota for country B may not be reached.</div><div><br></div><div>A.2 Explanations to General Rule 2</div><div>"If a team is affiliated with more than one institution, the unbound</div><div>affiliation counts." General rule 2 defines that only one team per</div><div>institute may participate in RoboCup. However, if a team XY is</div><div>affiliated with institution A as well as institution B and there is</div><div>already a team affiliated with A, the team XY may participate.</div><div><br></div><div>==============================<wbr>====================</div><div><br></div><div>Best regards,</div><div>Hidehisa Akiyama</div><div><br></div><div>On Behalf of Organizing Committee of Soccer Simulation 2D</div><div>Competition, RoboCup 2017 Nagoya</div></div><div><br></div>
</div>
</div><div><br></div>
</div>