[robocup-small] REMINDER (LAST DAY): SSL Pre-registration and Qualification Procedure for Singapore 2010

[alfredo at itam.mx]

--------------------------------------------------------------------------
LAST DAY TO PREREGISTER
--------------------------------------------------------------------------

Dear SSL Robocuppers,

Please find below the SSL Pre-registration and Qualification procedure for
Singapore 2010.
Please note that all dates are final and similar for all leagues.

This information is also available on the league web site:
http://small-size.informatik.uni-bremen.de/robocup2010:qualification

See list of currently pre-register teams at:
http://small-size.informatik.uni-bremen.de/robocup2010:teams

Best wishes to all,

Alfredo Weitzenfeld
On behalf of the SSL Organizing Committee for Singapore 2010

********************************************************

Singapore 2010 SSL Pre-registration and Qualification Procedure
This page describes the pre-registration and qualification procedures for
the Small Size League for RoboCup 2010. The pre-registration and
qualification procedures are similar to those in recent years.
Important Dates
•       Team Pre-Registration Deadline: 15 Jan 2010
•       Team Qualification Deadline: 15 Feb 2010
•       Early Registration: 1 Mar - 31 Mar 2010
•       Regular Registration: 1 Apr - 30 Apr 2010
•       Team Setup: 19 Jun - 20 Jun 2010
•       Competitions: 21 Jun - 24 Jun 2010
•       Symposium: 25 Jun 2010
The organizing committee (OC) will assess the qualification material and
report the results by March 1st, 2010.
Pre-registration
Submit by email to the organizing committee (OC) (small-size-oc at tzi.de)
your intent to participate in RoboCup by Jan 15th 2010. The e-mail subject
should be: 2010 Participation Intent (YourTeamName).
Qualification Criteria
Every team that wants to participate has to attend the following actions
by February 15th, 2010 (11.59 PM, GMT+1):
•       The team must have completed the preregistration procedure.
•       The team must submit a Team Description Paper (TDP).
•       The team must submit a Team Video.
Please pay attention to the following points:
•       In past competitions, there have been teams that registered but
failed to compete at the competition (turning up does not count). This
behavior is unfair to the many other teams that could have competed in
their place. Any team that registers for a competition and fails to
compete will be barred from qualifying for the following competition year
(unless the circumstances are exceptional). This rule was introduced for
RoboCup 2004 and will be enforced for RoboCup 2010.
•       Most communication will be done by e-mail using the Small Size
mailing list. Pay attention to these e-mails and answer the OC's
questions. A team that does not reply risks losing its qualified place.
•       We understand that new teams may struggle meeting all of the
qualification criteria below. We encourage new teams to submit
qualification video material demonstrating their true current
capabilities, while stating in their Team Description Paper (TDP) what is
expected to be completed by June 21st, 2010. However, teams not meeting
minimum required criteria will be considered for inclusion in competitions
only after all teams submitting compliant qualification materials.
•       Each team that passed the qualification or is in the waiting list
must submit a message to the organizing committee to confirm whether the
team has enough financial support to attend the competition. This message
must be sent before March 15th, 2010 (11.59 PM, GMT+1). If a team in the
qualified list cannot attend the competition, a team from the waiting list
will be selected in the waiting order.
Submission of your Team Description Paper (TDP)
The Team Description Paper should focus on one or two main components of
your developed system. We recommend you to choose topics that you feel are
especially novel, important, or different from how other teams approach
the problem, and/or other teams would be interested in reading about.
It is especially important to have clear and focused explanations. You can
assume that the audience is familiar with general Small Size League topics
and can thus devote most of the TDP to the important issues. In
particular, you should explain the technical details of how your approach
works so that other researchers can repeat your results. In this way,
other researchers can gain from your experience, as you will gain from
theirs, and together we can achieve the goals of the RoboCup Initiative.
At the last competitions, there had been robots that did not comply with
the Small Size rules. To sensitize all teams for regarding these rules,
the following information should be included in the Team Description
Paper: the height of the robot, the maximum diameter of its projection to
the ground, and the maximum percentage of ball coverage (as defined in the
Small Size rules).
New teams should clearly state their current robot capabilities and what
is expected to be completed by June 21st, 2010.
Submission Information:
•       The length of the TDP is limited to 12 pages.
•       Please use the same Springer LNAI format as the symposium
submissions (see RoboCup Symposium instructions).
•       Papers should be sent as a zipped pdf or postscript file via
e-mail to the organizing committee.
•       The e-mail subject should be: 2010 TDP (YourTeamName).
Submission of your Team Video
Your team video must be at least 1 minute of unedited continuous footage.
The qualification video can be either of the following types, although
preference will be given to item 1 (then 2 and last 3):
1.      A video of your robots participating in a RoboCup standard game
(i.e. a game at RoboCup or one of the local regional competitions). The
video should show obstacle avoidance, shooting and passing skill. The game
should be based on contemporary rules (2004 and afterwards).
2.      A video of your robots (there *must* be at least two moving
robots) engaging in two or more of the following activities: a) One or
more robots competing against an active robot goalkeeper. b) Two or more
robot field players actively going to the ball and playing against one
another. c) At least two robots playing cooperatively against 5 static or
moving obstacles.
3.      A video showing one or more robots partially demonstrating
capabilities listed in item 2.
The team video is used by the OC to determine the readiness of a team to
compete effectively and is part of the criteria in ranking teams in the
qualification process. Teams are advised to submit a video that best
demonstrates the readiness of the team to compete in an international
competition.
Submission Information:
To submit the video footage, you must send an e-mail to the RoboCup Small
Size mailing list and cc: it also to the organizing committee. The mail
should contain the following information:
•       Subject: 2010 Qualification Video (YourTeamName)
•       The URL of the location of your video, which should be available
via ftp or http.
Please pay attention to the following points:
•       Please submit a single video file.
•       The video must be stored on your own server or any reliable online
video hosting service (it is better to provide more than 1 link to the
video).
•       Do NOT send the video as an attachment to the mailing list nor to
the organization committee!
Special Requirement for Top 8 Teams from RoboCup 2009
One of the best ways to provide a good start point for the new and young
teams in small-size leagues is Learning from the Best. From this
viewpoint, All small-size league committees agreed with the new procedure
for selecting the seeded team1) in the competition schedule as follows
•       To be ranked as seeded teams, all top 8 teams from last year must
submit the materials providing additional information about their system.
•       The additional materials are Extended Team Description Paper
(ETDP) and the presentation at the competition event.
•       ETDP is an extended version of TDP which has no limit on number of
pages (at least 20 pages). The submitted ETDP should be written in the
same format as the TDP.
•       In order to maximize the effectiveness of ETDP, all 8 teams are
also needed to provide the presentation of their ETDP at the competition
event.
•       The evaluation of the ETDP is based on the Contribution to the
Community criteria. This means the other teams (old, young or new) should
learn something from the contribution and able to reproduce or use the
information in the ETDP.
•       As the evaluation is based on the qualitative quantities, all top
8 teams from last year which pass the qualification procedure should
submit the ETDP as soon as possible. The reason is to allow the committees
to have enough time to evaluate the ETDP and give back the feedback to the
teams before the final decision is made.
•       The topics of the ETDP is available here
•       The due date of the ETDP is April 1st, 2010 (11.59 PM, GMT+1)
•       Papers should be sent as a zipped pdf or postscript file via
e-mail to the organizing committee.
•       The e-mail subject should be: 2010 ETDP (YourTeamName).
“In the past, the top eight teams of the previous RoboCup have always been
seeded for the round robin state of the competition, i.e. the top four
became the heads of the four round robin groups, the other quarter
finalists have also been distributed evenly. This is done to avoid an
early elimination of potentially strong teams.”








-- 
La información contenida en este mensaje de datos es confidencial,
constituye un secreto industrial y/o profesional en términos de la
legislación vigente y se encuentra dirigida exclusivamente al
destinatario indicado en dicho mensaje. Si usted recibe esta información
por error o si usted no es el destinatario del mensaje, favor de
notificar al emisor, y destrúyalo.

The information contained in this electronic message is confidential,
it constitutes a professional and/or industrial secret in terms of the
current legislation, and is intended for its recipient only. If you
receive this message by mistake and/or if you are not the recipient
thereof, please notify the sender and destroy it.