Qualification

Qualification Agent Competition

Qualification Procedures:

Pre-registration is a prerequisite for qualification.
Only pre-registered teams can submit qualification material.

The qualification material consists of:

• Team Description Paper
• Logfile
• Team Travel Support Request (Optional)

Each team should upload the following to their home page by February 21th, 2005.

• your Team Description Paper
• your Logfile

Each team should send the following e-mail to the league chair by February 21th, 2005.

%%----------------------------------------------------------------------

to: kleiner@informatik.uni-freiburg.de

subject: Robocup 2005 Qualification Material

message-body:

Competition=[Agent Competition] 

TeamName=[          ] 

HomePage=[          ]

%%----------------------------------------------------------------------

Teams who do not have a home page should contact the league chair.

• Submission of your Team Description Paper

An important item that every Team must deliver to be able to qualify for RoboCup 2005 is the Team Description Paper. Papers should be in English and formatted to the Springer LNAI format. Papers must be no more than 12 pages in length and should be submitted as a PDF file.

• Submission of your agents logfile

The other important item for the qualification for RoboCup 2005 are two logfile that your agents rescue at the same disaster situation as given by the following two maps:

1. Kobe
2. Foligno

Please use no other kernel than the LATEST KERNEL VERSION 0.46 from source forge: rescue-0_46alpha.

Kernel outputs a logfile by assigning

      logname: rescue.log 

in RUN/config.tex (See READ_ME.txt file in the 0.46 package). Viewers such as Morimoto-viewer or the new 3D viewer, work as logplayers that display rescue operations using the logfile.

• Submission of your Travel Support Form (Optional)

Teams wishing to receive Travel Support must fill the Travel Support Form and send it by e-mail to the league chair. Travel support requests not received by league chair in time, will not be processed.

Qualification Infrastructure Competition Part I

Qualification Procedures:

Pre-registration is a prerequisite for qualification.
Only pre-registered teams can submit qualification material.

The qualification material consists of:

• Team Description Paper
• Official Letter
  
• Team Travel Support Request (Optional)

Each team should upload the following to their home page by February 21th, 2005.

• your Team Description Paper
• Offical letter
  

Each team should send the following e-mail to the league chair by February 21th, 2005.

%%----------------------------------------------------------------------

to: kleiner@informatik.uni-freiburg.de

subject: Robocup 2005 Qualification Material

message-body:

Competition=[Infrastructure Competition] 

TeamName=[          ] 

HomePage=[          ]

%%----------------------------------------------------------------------

Teams who do not have a home page should contact the league chair.

• Submission of your Team Description Paper

An important item that every Team must deliver to be able to qualify for RoboCup 2005 is the Team Description Paper. Papers should be in English and formatted to the Springer LNAI format. Papers must be no more than 12 pages in length and should be submitted as a PDF file.

• Submission of your Travel Support Form (Optional)

Teams wishing to receive Travel Support must fill the Travel Support Form and send it by e-mail to the league chair. Travel support requests not received by league chair in time, will not be processed.

• Submission of an official letter declaring that if the team is selected it will add the source code to the open source development repository of the league under BSD license.

Infrastructure Competition Part II

• An improved version of the Team Description Paper (TDP) which should fulfill the following:
• A minimum size of six pages
  
• Springer LNCS format
• A clear description of what your module will do and why it will be better than the existing tools
• Valid references to related work
  
• A binary of the demo code:
  
• that should be compiled for linux on an i386 architecture
  
• any specific libraries that are required must be named
• Instructions on how to run the program, including a summary of all command-line options.