PARTS Outdoor Challenge

PRELIMINARY - SUBJECT TO (BIG) CHANGES

Purpose
- The POC consists of outdoor autonomous navigation events that give robots several excuses each year to take their humans out for a walk and get some air.  The 4 events are staged in increasing order of difficulty.  All events are friendly to newbots but challenging even to sentients.  The format will generally be low-key and flexible, adjusting for changes in weather, number of entries and whatever else is significant on the day of "competition".  The POC shall be easy to plan and execute, so the club will hold several per year.

Challenge Event #1 - Out and Back
Drive from the origin to a point at least 100 feet away and back to the origin and stop. Distance is then measured from the stopping place to the origin.  Shortest distance wins.  It is left undefined what happens if the robot never stops.
Challenge Event #2 - Square
Drive from the origin around a square (typically 100 feet on each side) clockwise or counter-clockwise as instructed by the judge, and stop at the origin.  Distance is then measured from the stopping place to the origin.  Shortest distance wins.

It is legal to cut the corners, pivot 90 degrees, execute a 3-pt turn or whatever it takes to transition from one leg to the next.   Robots are expected to make an honest attempt at traveling the correct distance on each leg but currently this is not judged.

Similarity to the UMBmark procedure developed at Univ. of Michigan by Daniel Borenstein for calibrating the accuracy of odometry and navigation of robots is entirely a figment of your imagination.  
Challenge Event #3 - Out and Back With Obstacles
Identical to event #1 but this time there are obstacles in the way.  

The difficulty level of obstacles and terrain may be scaled to the capability level of robots, or not.
Challenge Event #4 - Gate Crashing
This event challenges the robot to travel several hundred yards toward an unseen finish point with buildings and trees and other objects in the way.  There is a time limit of 10 minutes and the course will be laid out such that the expected path around all the obstacles will be 900 feet, so a robot averaging 1.5 feet per second along a reasonably smart path will finish right on time.

The score has two components:  1) the distance in feet from the finish point at the time limit and 2) the sum of distance penalties from each gate missed along the way.  Minimum score wins.

The aforementioned gates will be placed along the course out of sight of each other.  A distance penalty is incurred for each gate not passed cleanly through.  The gates are made of 2 orange traffic cones 4 feet apart (sorry all you cone-haters).  They will be placed to be noticable along the most likely path.  If more than one path is likely, eg both ways around a building, then gates may be placed along both paths and only penalties for the path chosen will apply.  The organizers will consider that robots prefer not to have to move far out of their normal way or slow down on their way through the gates.  Some organizers will be nicer than others.

A robot with too much knowledge is a dangerous thing, so here we only tell it the location of the start and finish points (Google Earth lat/long points) and literally nothing else.  No other locations, maps, paths or other data about the venue are permitted.  Built-in Google Earth maps with all sorts of preplanned routes for example are not allowed.  The locations of gates will not be known.  At 2 minutes prior to start, a team will receive the start and finish point locations written on a 3x5 index card.  Cards must be handed back before the start.  

If there is enough interest, we hope to add mapping and planning as a feature of future events but you never know....

Robots that lack vision can and should still compete and do well, in spite of gate penalties.  Robots that lack good navigating, obstacle detecting or all-terrain skills will likely get lost or stuck.

It is likely that there will be people and pets on the course and they may constitute serious unplanned obstacles.  Normally this should be taken in stride but in a severe case, the judges may allow a re-run or make a distance adjustment, at their discretion.

Robots must halt at the time limit, either automatically or be halted by their operators.

Robots are expected to be fully autonomous, however there may be special hazards on this course for which a bit of herding or downright steering by the operator is allowed.  This includes avoiding bodies of water, flower beds, cliffs and maybe some others, all at the judges' discretion.  There will likely be a distance penalty assigned by the judges for substantial operator steering or herding.  

There are no limits on instrumentation, size, weight or mode of power other than the safe/sane rule.  Note that remote computers are allowed, although not likely practical due to distances and obstacles.  Flying and swimming are not allowed.  Robots must either roll, walk, hop, slither, run or crawl.  Sauntering, toddling, wandering and roaming are subject to the judge's mood.  

If the event becomes too easy, we will make it harder.  If people start showing up with $100,000 robots and teams of 20 developers, this is great and we will of course split into levels so that "amateurs" still have a challenge they can win.  But we still won't offer $1million prizes.

Venue - The venue for a POC event will be announced by the organizers.  Hopefully, several POC's will be held each year and ideally they would be held at changing locations so that humans can experience different weather, scenery and seasons.  The event can be held at schools, parks, fair-grounds, stadiums, industrial sites and maybe even exotic vacation retreats.  It is not (yet) intended that the POC be held in extreme weather conditions.  Judges may call off the event ahead of time based on severe weather forecasts or on the spot if the weather turns too nasty.  Also it is not intended that robots travel through water deeper than 0.5".  Some other features not intended are stairs, cliffs, pits, interiors of buildings, traffic-bearing roads, active bike paths, and so forth.  These are all regarded as aspects of common sense.

Safety - Robots must be fundamentally safe and sane.  The head judge has the right to scratch at any time before or during the event any robot  deemed risky, unsafe or hazardous.  Robots must have some practical system that allows the operator and/or judge to halt, disable or change the course of the robot if it is about to get in trouble.  Something more subtle than a basebal bat is highly recommended.  See the Liability section below.

Autonomy -  All robots must be autonomous while on the course, with exceptions noted in event #4.

Attempts - There is only one attempt or trial allowed per event, with the rare exception noted for event #4.  

Scoring and Awards - Scoring will be determined for each event and overall by robot.  Awards will not likely be $1 million checks, but you can always dream.  At a minimum, scores and rankings will be posted on the club website.  Great achievements will be duely noted in monthly meetings and great achievers will receive public adulation (but will also be required to pontificate at monthly meetings and publish in scholarly journals).  Honorary Certificates of Artificial Achievement will be liberally bestowed on robots who end an event within a few miles of the finish.  

If the POC is looking like it might become successful, PARTS will establish a ranking system on its website.  Maybe this can eventually extend to a more nationwide system.  That would be nice.  

The robot's score for each event is simply the distance from the robot's stopping place to the finish plus any penalties (tbd).  The overall score is simply the sum of points for all events.  For the purpose of overall score, a robot will receive points for each event not entered equal to the worst score by any robot for that event.

A big fat score of 0 for all 4 events would be a miracle and any robot achieving that will immediately replace the president of the club.

Penalties - No robots will be tortured while on the course, regardless of how many miles of distance penalties they accumulate.

Liability - Each contestant is fully responsible for any damage to person or property caused directly or indirectly by his or her robot.  The Portland Area Robotics Society, the event organizers, judges and other entrants are not responsible for damage caused by any competing robots.  Each contestant must sign a waiver of liability prior to the competition.  A minor must have a guardian present to sign their waiver.  It is not allowed for robots to aim pencil beams of high-intensity infrared laser at obstacles, whether mobile or fixed.  

Whining - Robots are permitted to whine and complain.  People are not.  Please keep the event fun and light-hearted for all, including the organizers and humans.

Judges - One or more judges will officiate the contest. Their prime responsibilities will be to determine that a robot has successfully completed the requirements of a specific challenge, to provide measurements of the robot's stopping position for scoring, and to close their ears to whining.  The decisions of the judges are final.

Thanks - Special thanks goes to David Anderson of DPRG for his organization of the first similar event in Dallas on May 10, 2008.  It is no coincidence that the PARTS Outdoor Challenge events #1-3 are basically a blatant rip-off of dpa's hard work.  Event #4 owes nods to the DARPA Grand Challenge, SRS Robo-Magellan and DPRG's Long Haul in no particular order.  

Originally written by Robert F. Scheer 3/5/2008