Slashdot Mirror
Grand Challenge 1, Competitors 0
Ivan writes "According to the DARPA Grand Challenge Status Board, 2 bots were withdrawn before the race started and the remaining 13 were all disabled. Red Team and SciAutonics II tied at 7 miles, a bit short of the 142 miles required." CNN has coverage and interviews.
There were engineered obstacles, such as barbed wire and the like. And the deserts out here are not like the Sahara. They have washes and rock formations and various natural obstacles. Finally, a lot of the problems were mechanical or technical-brakes locking up and such. So it isn't as simple as it sounds.
If my answers frighten you, stop asking scary questions.
Hate to break it to you but the desert is far from a "completely barren plan, with very few obstacles".
Even with a previously traveled path and prepared track it's not uncommon for VERY well financed race teams to fail to finish in a desert race. Most desert racers consider it a win just to make it to the finish line and that's with a driver!
Look into the SCORE side of this challenge a bit more and you'll find a LOT of info about just how challenging desert racing is with drivers - let alone trying to do it autonomously.
--- Juggle juggle@hitesman.com
The first tanks could only go a thousand yards before breaking down, and they had a 7 man crew.
it didn't take long for things to change.
http://dgc.gi.alaska.edu/Overview_2_1_04.htm Section 2.4.1
Don't mod this cut-n-paste troll up anymore.
...
"I wouldn't make such an analogy anywhere other than slashdot, but I could feel that the load average on my brain was as high as it could be." Such an analogy is actually perfectly appropriate. Cognitive load is a term used by human factors psychologists to describe what you're talking about. As a driving researcher I have a suspicion it's going to be a while before a machine can match a human in handling the cognitive load for a task like driving - particularly in a wartime situation.
I was lucky enough to have a press pass. We had to get to Barstow at 5:00am (driving up from LA) which was rough. Driving in the dark along the highway leading to the start, we topped a rise and in the valley below portable lights had been strung up creating an oasis of light. As we got closer we could see the satelite uplink trucks, grandstands, police, and military.
After registering and getting our fancy orange safety vests, we went to the starting line and were able to get some great pictures as the bots prepared to start the race. Red Team (from Carnegie Mellon) had the best qualifying time so they were first out of the gates. Their 3 million dollar hummer started off fast and was quickly out of sight. The four helicopters filming from the air were flying dangerously close to each other trying to get a good shot so it was easy to track where the vehicle was.
SciAutonics II was the next bot out of the gate, the also had a good start and proceeded out of view. About this time we heard the good news, Team Red was seven miles down the course. Soon after we got the bad news, Red Team's vehicle had died. The odds on favorite was eliminated by a mechanical failure after only 7 miles.
Several of the rest of the bots failed to get past the first turn, and the rest either withdrew or failed within a few miles. The six wheeled ENSCO lost control, ran up the embankment, and overturned. Of the 100+ teams who built bots, 25 were invited to qualify, 15 of those were allowed to race, and only 7 of those made it more than a mile.
All in all it was an excellent experience. My suggestions for next year (or for the openchallenge, etc) would be to do the race in segments like the WRC does. Divide the 200 mile race into 10 mile segments, teams get points based on their performance for the stage. If you fail a stage you're not eliminated, you just fall in the rankings. Teams are allowed an hour of maintenance between stages to fix any problems they think they can fix. This would make it both a lot more interesting, and a lot more satisfying.
Here's a very good
From http://www.grandchallenge.org/gallery/Day6.html
.5 miles, the vehicle was disabled.
Preliminary Data from DARPA Grand Challenge
As of 11:00 a.m. PST, March 13, 2004
Vehicle 22 - Red Team - At mile 7.4. Vehicle went off course, got caught on an obstacle and rubber on the front wheels caught fire, which was quickly extinguished. Vehicle has been disabled.
Vehicle 21- SciAutonicsII - At mile 6.7. Vehicle went into an embankment and became stuck. Vehicle has been disabled, and the team is recovering it.
Vehicle 5 - Team Caltech - At mile 1.3. Vehicle went through a fence, and couldn't come back through. Vehicle has been disabled, and the team is recovering it.
Vehicle 7 - Digital Auto Drive - At mile 6.0. Vehicle was paused to allow a wrecker to get through, and, upon restarting, sensors were not able to determine the proper route. After sensors tried unsuccessfully for three hours, vehicle was disabled.
Vehicle 25 - Virginia Tech - Vehicle brakes locked up in the start area. Vehicle has been removed from the course.
Vehicle 23 - Axion Racing - Vehicle circled the wrong way in the start area. Vehicle has been removed from the course.
Vehicle 2 - Team CajunBot - Vehicle brushed a wall on its way out of the chute. Vehicle has been removed from the course.
Vehicle 13 - Team ENSCO - Vehicle flipped in the start area, experienced a fuel leak, and the team needed to shut off the fuel. Vehicle has been removed from the course.
Vehicle 4 - Team CIMAR - At mile 0.45. Vehicle ran into some wire and got totally wrapped up in it. Vehicle has been disabled.
Vehicle 10 - Palos Verdes High School Road Warriors - Vehicle has been removed from the course - it hit a wall in the start area.
Vehicle 17 - SciAutonics I - At mile 0.75. Vehicle went off the route. After sensors tried unsuccessfully for 90 minutes to reacquire the route, without any movement, vehicle was disabled.
Vehicle 20 - Team TerraMax - Got to mile 1.2. Vehicle then started backing up and after
Vehicle 15 - Team TerraHawk - Withdrew prior to start.
Vehicle 9 - The Golem Group - At mile 5.2. Vehicle stopped. Vehicle had a throttle problem while going up a hill. After trying for 50 minutes, the vehicle was disabled.
Vehicle 16 - The Blue Team - Withdrew prior to start.
The preliminary results have been posted on the day 6 media gallery. Since it is a word document I'l post it in full.
.5 miles, the vehicle was disabled.
Preliminary Data from DARPA Grand Challenge
As of 11:00 a.m. PST, March 13, 2004
Vehicle 22 - Red Team - At mile 7.4. Vehicle went off course, got caught on an obstacle and rubber on the front wheels caught fire, which was quickly extinguished. Vehicle has been disabled.
Vehicle 21- SciAutonicsII - At mile 6.7. Vehicle went into an embankment and became stuck. Vehicle has been disabled, and the team is recovering it.
Vehicle 5 - Team Caltech - At mile 1.3. Vehicle went through a fence, and couldn't come back through. Vehicle has been disabled, and the team is recovering it.
Vehicle 7 - Digital Auto Drive - At mile 6.0. Vehicle was paused to allow a wrecker to get through, and, upon restarting, sensors were not able to determine the proper route. After sensors tried unsuccessfully for three hours, vehicle was disabled.
Vehicle 25 - Virginia Tech - Vehicle brakes locked up in the start area. Vehicle has been removed from the course.
Vehicle 23 - Axion Racing - Vehicle circled the wrong way in the start area. Vehicle has been removed from the course.
Vehicle 2 - Team CajunBot - Vehicle brushed a wall on its way out of the chute. Vehicle has been removed from the course.
Vehicle 13 - Team ENSCO - Vehicle flipped in the start area, experienced a fuel leak, and the team needed to shut off the fuel. Vehicle has been removed from the course.
Vehicle 4 - Team CIMAR - At mile 0.45. Vehicle ran into some wire and got totally wrapped up in it. Vehicle has been disabled.
Vehicle 10 - Palos Verdes High School Road Warriors - Vehicle has been removed from the course - it hit a wall in the start area.
Vehicle 17 - SciAutonics I - At mile 0.75. Vehicle went off the route. After sensors tried unsuccessfully for 90 minutes to reacquire the route, without any movement, vehicle was disabled.
Vehicle 20 - Team TerraMax - Got to mile 1.2. Vehicle then started backing up and after
Vehicle 15 - Team TerraHawk - Withdrew prior to start.
Vehicle 9 - The Golem Group - At mile 5.2. Vehicle stopped. Vehicle had a throttle problem while going up a hill. After trying for 50 minutes, the vehicle was disabled.
Vehicle 16 - The Blue Team - Withdrew prior to start.