<div dir="ltr"><div dir="ltr"><div>Final Call for Applications for Participation (deadline Thursday 1 December 2016)<br><br></div><div>RoboCup 2017 Standard Platform League<br><a href="http://www.tzi.de/spl/" target="_blank">www.tzi.de/spl/</a><br>Tuesday 25th July through Monday 31st July 2017 (Nagoya, Japan)<br><a href="http://www.robocup2017.org" target="_blank">http://www.robocup2017.org</a><br><br>RoboCup
is an international initiative that fosters research and education in
Robotics and Artificial Intelligence through a variety of competitions
(RoboCupSoccer, RoboCupRescue, RoboCup@Home, RoboCupJunior) involving
mostly multi-robot systems. RoboCup currently includes a number of
different robot soccer leagues that focus on different research
challenges.<br><br>The Standard Platform League (SPL) is characterized
by the use of an identical robot platform by all the teams.
Participating researchers focus on algorithmic development for fully
autonomous robots, i.e., robots that operate with no external control.
The SPL at RoboCup 2017 will use V5 or older versions of the NAO
humanoid robot manufactured by <a href="https://www.ald.softbankrobotics.com/en" target="_blank">SoftBank Robotics</a>.
The SPL robot soccer team competition games at RoboCup 2017 will be
played between teams of five robots on a 6m x 9m playing surface.<br><br>The RoboCup 2017 SPL will host both a team competition and a mixed teams competition.<br><br>The
team competition will consist of more games for the majority of teams
than in recent years. We expect to qualify 24 teams. A new structure
will be used in the team competition to allow all teams to play more
games against teams with similar skill levels. See Appendix A.3 of the <a href="http://www.informatik.uni-bremen.de/spl/pub/Website/Downloads/Rules2017.pdf" target="_blank">preliminary rulebook</a> for more details.<br><br>Teams
applying for the team competition may also apply for the mixed team
competition. Each mixed team will consist of two teams. Mixed teams will
either play 10v10 games on a middle-size league field or 6v6 games on
the normal SPL field. Only 4 mixed teams will be selected to compete at
RoboCup 2017. See Appendix B of the <a href="http://www.informatik.uni-bremen.de/spl/pub/Website/Downloads/Rules2017.pdf" target="_blank">preliminary rulebook</a> for more details.<br><br>Qualification<br>-------------<br>All
interested teams must submit an original qualification document. In
order for the qualification document to be considered, it must (1) be no
longer than 6 pages and (2) include all of the following information in
sections with the specified headings:<br><br><b>Team Information</b>: the team name, the team leader(s), and the university/company affiliation(s) of the team<br><b>Mixed Teams</b>:
If the team is interested in participating in the mixed teams
competition, indicate the name of the partner team, the proposed mixed
team name, and the proposed mixed team jersey color. Include a short
note about infrastructure plans as well as why this team and the
proposed partner wish to perform as a mixed team.<br><b>Code Usage</b>:
acknowledge the team's use of any other team's code (1) previously from
2015 to present and (2) anticipated at RoboCup 2017. If code is used
from other teams, is this code integrated into a code base that is
mainly designed by the applying team? If not, describe in detail the
'research publishable' advancements the applying team has made to the
other team's code release and what advancements the team is currently
pursuing. If the applying team does not use any other team's code, state
so.<br><b>Past History</b>: provide game results in RoboCup Open
competitions as well as main RoboCup competitions from 2015 onward.
Include opponents and game scores from each competition in a table.
State if the team plans to participate in any RoboCup Open competitions
or friendlies prior to RoboCup 2017.<br><b>Impact</b>: what is the impact of the team's participation and research in RoboCup on (1) the SPL, (2) the team's university/community<br><b>Other</b>: present any other information that you believe supports your application<br><br>The
written material must be complemented by a link to a video (maximum 5
min long, uploaded on the team's web site or on some video server) that
demonstrates the current status of the team. The video is used by the TC
to determine the readiness of the team to compete effectively, and
hence should focus on the team’s ability to play soccer. Teams who did
not participate in the team competition at RoboCup 2016 must include
footage of at least one robot attempting to kick off and score (this
footage must be captured as a single wide shot with no cuts). In cases
where footage from multiple teams is shown (such as game footage),
please include a textual overlay denoting which team is the applying
team. Videos of simulation contributions will also be accepted, but only
when a real robots is unavailable. Preference will be given to teams
that use real robots to show soccer skills in their video.<br><br>Pre-Qualification<br>-------------<br>Teams
that satisfied the pre-qualification guidelines as set forth in the
RoboCup 2016 rulebook will be pre-qualified for RoboCup 2017, if they
submit the following original qualification document. Teams able to
pre-qualify include: Berlin United - NaoTH, B-Human, DAInamite, HULKs,
Nao Devils Dortmund, Nao-Team HTWK, TJArk, UChile Robotics Team,
UPennalizers, and UT Austin Villa.<br><br>The original qualification document must include:<br><br>1. The team name, leader(s), and the university/company affiliation(s) of the team<br>2.
If the team is interested in participating in the mixed teams
competition, indicate the name of the partner team, the proposed mixed
team name, and the proposed mixed team jersey color. Include a short
note about infrastructure plans as well as why this team and the
proposed partner wish to perform as a mixed team.<br>3. A link to a team research report describing their work for RoboCup 2016 (must be posted in a publicly available location)<br><br>For
teams who reached the quarter-finals in the team competition, this team
research report must include a link to publicly release code as
detailed in the 2016 SPL rulebook<br><br>If a joint 2016 team splits, only one team can be pre-qualified for 2017 (please, indicate which one).<br><br>Qualification for Regional Opens Only<br>-------------<br>Teams
may also submit a short intent to participate in a regional open if
they do not wish to participate in the 2017 RoboCup Nagoya competition.
Although teams may participate in regional opens without submitting this
intent to participate, teams who submit an intent to participate and
become qualified will be eligible for special robot pricing as a 2017
RoboCup Event qualified team.<br><br>Teams must submit the following
information by 1 December 2016: (1) The team name, leader(s), and the
university/company affiliation(s) of the team and (2) a short statement
describing the current status/progress of the team. A link to a short
video showing robot soccer behaviors and/or game play (using robots or
in simulation) may be included if available.<br><br>Submission and Evaluation<br>-------------<br>All applications with the (pre-)qualification material must be submitted by 1 December 2016, by email to <a href="mailto:rc-spl-tc@lists.robocup.org" target="_blank">rc-spl-tc@lists.robocup.org</a>. Applications must not be sent to personal SPL TC/OC email addresses and must not contain video attachments.<br><br>Note
that submitting an application serves as a statement of commitment to
participate in the RoboCup 2017 SPL. If you have doubts regarding the
ability of your team to participate (due to funding, visas, ect), please
apply by the deadline but note this in your application. Declining to
participate in any competition after the official early registration
period has opened may negatively affect future applications (the later
you decline, the worse it will affect future applications).<br><br>Teams are encouraged to consider joint participation. Joint proposals will be judged on combined merit.<br><br>Applications will be evaluated to consider a variety of components including:<br><br>1. Potential to play competitive games at RoboCup 2017 (demonstrated ability to play soccer, previous results, ect)<br>2.
Contributions (and potential contributions) to league (code
releases/papers, active in organization, developing own code, ect)<br>3. Diversity (region, team make-up, unique characteristics, ect)<br><br>When
choosing teams and team pairings for the mixed teams competition, we
will pick teams and team pairings that we hope will make the competition
high-quality, competitive, and interesting.<br><br>Qualification
decisions, including alternate lists, will be announced by 20 December
2016. We expect to qualify a total of 32 teams (including some for
Regional Opens only).<br><br>Robot Acquisition<br>-------------<br>SoftBank
Robotics has a special pricing package for teams who qualify for the
2017 RoboCup Events. A list of qualified teams will be sent to SoftBank
Robotics by the SPL Technical Committee after the qualification
decisions have been announced, so teams may contact SoftBank Robotics
after that date to order robots if they choose.<br><br>Orders will have
to be placed to SoftBank Robotics by a set date to benefit from
discounted prices. Teams should contact SoftBank Robotics regarding this
date.<br><br>Discounted RoboCup prices only apply to RoboCup Qualified
Team who will participate to the 2017 RoboCup Event. In case the
Federation informs SoftBank Robotics that a Qualified Team, who
benefited from the discounted RoboCup price, was a no-show during the
2017 RoboCup Events, SoftBank Robotics will invoice the said Team the
additional cost for the regular list price applicable at the time of
purchase. Hence, if a Team purchases any discounted robots and then
decides not to participate, they will be charged the regular price for
all. Teams should contact SoftBank Robotics if they have questions
regarding these policies.<br><br><b>Limit Number</b><br>SoftBank
Robotics agrees to deliver up to 6 NAOs (either new robots or
replacement robots) per SPL Qualified Team at the negotiated price
detailed below. Above this limit of 6 robots, any additional robots can
be purchased at the regular list price applicable at the time of
purchase.<br><br><b>NAO Version</b><br>Softbank agree to deliver the
version V5 of NAO for RoboCup 2017 qualified teams. Any colored panels
besides black are now allowed.<br><br><b>Price (excluding VAT)</b><br>Price of NAO V5* within the Limit Number: 3.900€ OR USD4.900<br>Price of NAO V5* above Limit Number: List Price<br>Additional Charger: List Price<br>Additional Battery: List Price<br>Full Nao V5 Robot replacement of a NAO V4 within the Limit Number **: 3.500€ OR USD4.350<br>Full Nao V5 Robot replacement above Limit Number **: List Price<br>1 Year Warranty Extension for NAO V5 ***: List Price<br>1 Year Warranty Extension for NAO V4 ***: List Price<br>1 Year Warranty Extension for NAO V3.3 and previous versions: not available<br>Other types of replacements (metal gears/arms/head…): not available<br><br><b>Repairs during the RoboCup 2017</b><br>On NAO V5 and NAO V4 during the warranty period: included in warranty<br>On NAO V5, NAO V4 and V3.3 outside the warranty period: quotation on request ****<br>On other versions: not available<br><br>* Includes: 2 years warranty starting at initial shipping date - 1 charger and battery. Does not include: SW suite and shipping.<br><br>**
Includes: 2 years warranty starting at initial shipping date - 1
charger and battery. Does not include shipping of replacement robot,
shipping of replaced robot, shipping possible to local offices –
Paris/Boston/Shanghai - does not include: SW suite. Please note that the
new replacement robot will be shipped after receipt of the replaced
robot by our teams.<br><br>*** The total warranty period shall not
exceed a duration of 4 years after the initial shipping date of the
product, unless otherwise agreed in writing.<br><br>**** Repair at
reasonable price during the RoboCup. In the case of NAO V3.3, quotation
will be done within the limits of available stock of V3.3 spare parts.<br><br>A “Delegation of Signature” document must be signed by the Delegating Official for repair quotations on request during RoboCup.<br><br>Best regards,<br>- RoboCup 2017 Standard Platform League Technical and Organizing Committees</div></div></div>