| |
|
|
| |
Participation |
|
| |
|
|
| |
There are 4 stages for
participation in the event. |
|
| |
|
|
| |
Notice of Intent to
Participate |
|
| |
|
|
| |
- Notify Paul Rybski by email about your intent to participate.
His email is on the home page (click the title banner
at the top of the page to return home).
- Subscribe to the email list. This email list will be
used to notify all teams about the event and updates to
the rules. Additionally, teams will be able to participate
in rules discussions as the rules are finalized.
|
|
| |
|
|
| |
Subscribe to the mailing list by clicking
this
link. |
|
| |
|
|
| |
Note, subscribing to the mailing list does
not mean that you will be required to participate in the final
event. |
|
| |
|
|
| |
Pre-Registration |
|
| |
|
|
| |
All teams that seriously intend to participate
need to send a pre-registration email to Paul Rybski (NOTE:
this email can serve as the notice of intent to participate)
. This will ensure that space is reserved for your team
in terms of a work area where only registered teams are
allowed. This is a secure area where equipment and computers
can be safely stored overnight.
This email needs to contain the following information:
- Team name
- Team leader name (e.g. primary contact) with email and
phone number
- Team institution
- Number of estimated team members to participate (can
change later).
- Whether the team will be requesting travel funding (an
exact amount of request is not needed yet).
|
|
| |
|
|
| |
Qualification |
|
| |
|
|
| |
Teams that pre-register are expected to
pass the qualification requirements before they are allowed
to go through full registration and compete at the event.
See the Qualification
section for details.
Teams are highly encouraged to submit earlier
than the listed deadline. There is
no penalty for submitting multiple times. |
|
| |
|
|
| |
Full Registration |
|
| |
|
|
| |
Teams are only allowed to register for
the event once they have met the qualification requirements.
Registration guarantees a team a spot
in the competition as well as allowing the team to be present
at the venue. Typically this just consists of paperwork
but this may change from year to year.
More details on what is required by registration will
be posted after the qualification deadline. |
|
| |
|
|
| |
Back to top |
|
| |
|
|
| |
Qualification |
|
| |
|
|
| |
Teams that wish to participate in the
competition must first qualify. No team will be allowed
to register to attend and participate at the event until
they have qualified.
Teams are STRONGLY recommended to submit their
qualification materials earlier as there is no penalty for
submitting early and resubmitting in the case of a failure
to run the materials (for software league) or for insufficient
description/capabilities (for the robot league).
The results of the qualification procedure will be used
to determine who is eligible to compete at the competition.
Travel funding will be provided to the top qualifying teams,
and so doing well on the qualification results will help
increase eligibility for that funding. If we receive
more qualification entries than we have space for in the
competition, we will be ranking the qualification entries
on a relative scale. There is no pre-set minimum performance
allowed to qualify but instead the ranking is determined
by how well each team's qualification materials/performance
compare to the others and the top N teams (where N is to
be determined) will receive travel funding.
Both leagues are required to participate in a qualification
procedure. The software-only league and the robot league
have different requirements. |
|
| |
|
|
| |
Robot Qualification |
|
| |
|
|
| |
Robot teams are required to submit a
2-page abstract providing a summary of their approach along
with creating a short video of their robot that demonstrates
basic navigation and obstacle avoidance capabilities. This
will ensure that the robots have the basic capabilities
to explore the competition environment safely. |
|
| |
|
|
| |
Software-Only Qualification |
|
| |
|
|
| |
Software teams are required to submit
a 2-page abstract providing a summary of their approach
along with a description of how their software will demonstrate
its performance to the audience during the run. In addition,
the software-only teams need to run their software on one
of the datasets from the competitions below (choose either 2008-06-26, 2008-06-25, 2007-07-25,
or 2007-07-24) and submit the output to the organizers. |
|
| |
|
|
| |
Example image sets |
|
| |
|
|
| |
|
|
| |
|
|
| |
- Dataset 2007-02-07
These images were taken from a Nikon Coolpix 5900
still camera that was mounted on the front of our CMAssist
robot. The libgphoto2 API under Linux was used to automatically
capture these images. Because of the higher quality
of these images, we will be using these for qualification
purposes as well as the contest.
Here are some images that show how the camera was
mounted on the front of the robot.
image1
image2
Here are some photos of the environment with the objects
placed within it. A low table was placed in the center
of the environment and the boundaries are marked with
white tape. These are just to provide a wide angle view
of where all of the objects are placed.
image1
image2
image3
image4
- Dataset 2007-01-05
These images were taken using the top-front camera
of the CMAssist robots. Images are captured at a rate
of 15 fps.
See
the CMAssist web pages for more details
All of the objects in the image are located within
the boundaries of the green carpet. There is a white
line that goes around the boundary of the carpet (it's
actually a robot soccer field for the four-legged league)
and all of the objects in question are found within
it. Here is the list of all objects.
|
|
| |
|
|
| |
Example of the hardest
problem |
|
| |
|
|
| |
The following are a few sets of images
that we took of one of our offices. These image sets are examples
of what might in fact be the hardest sort of environment to
operate within: the cluttered professor's office. Ultimately
we hope that robots will be able to help us find missing objects
in such clutter, but for now, the real competition will be
much more simple.
To repeat:
these are not the difficulty of images
that will be used in this year's competition.
The first image set was taken from a mobile robot equipped
with a 110 degree FOV lens (which has some optical distortions)
and the other was taken with a digital camera. The data
sets can be downloaded here:
The following list of items can be found in the image.
Some are generic classifications of objects and some are
very specific.
Feedback (comments, questions,
requests) about the images are welcome. |
|
| |
|
|
| |
Back to top |
|
| |
|
|
| |
Return to the home page |
|