DARPA Announces Grand Challenge 2005
An anonymous reader writes "The Grand Challenge 2005 Date has been announced for October 8, 2005. Check out DARPA's official webpage for details. Already several teams from last year are gearing up: Carnegie Mellon Red Team, D.A.D., and Cal Tech. Also, several new teams are entering, among them Stanford, and Florida Tech. Should be a very interesting Challenge next year!"
"Should be a very interesting Challenge next year!" ...more so if anyone finishes
a big garage, a spare '67 IH Scout 800, a laptop I could trash, assorted robotics parts, and a month or two paid time off (or better yet- sponsored by my work)... I just *know* I could get out of the parking lot...
As a proud dropout of Florida Tech, I'd just like to point out that the "Florida Tech" link goes to an article about the University of Florida. If Florida Tech is competting, I wish them all the best luck. Here's the correct link to their website: www.fit.edu
the same spooks that want to identify terrorists by how they walk?
No, they're the ones who created the Internet. You know, that thing you're using right now. Plus, they happen to be a huge supporter of scientific research and development. Given the fact that industry has slashed R&D in favor of raising the quarterly reports by a half a percentage point or giving the members of the Board an ivory backscratcher as an annual bonus, let's not be too quick to insult one of the few remaining patrons of science.
GMD
watch this
I can't wait to see all the new automated field medic designs. Wait, why does that one have a big gun sticking out of the top....
I Am My Own Worst Enemy
First off, returning teams already have a foundation to build upon, both in existing hardware and in technical experience. Writing software for a race like this is almost impossible to do without testing it on a working vehicle (i.e. testing in simulation only works out major problems, but does not translate well to desert racing). For example, Caltech spent 6 months getting actuators and drivers to work well enough to hand over the vehicle to the software team. As soon as that happened, we noticed several problems interfacing the actuators to the software (e.g. updating actuator positions too fast locked them up and made them stop responding). Ultimately our vehicle was not even waypoint following accurately until late February. Most teams were in the same state we were in - racing the clock, plagued by bad hardware (sensors and actuators) and inexperience. BUT we were very close to being very good. If they re-ran the race mid-summer this year the results from all of the teams would be very different. Looking to next year, teams have working vehicles which means 1 full year of onsite testing instead of 2 months.
Another thing that is interesting about the next race is the timing relative to academic calendars. A lot of teams are university driven and it was very difficult for students to devote enough time to the project while still handling their school requirements (definitely true with a Caltech workload). The next race is at the very end of the summer which means that a crew can work on the vehicle full time for three months before the next race.
Whether or not someone wins the next race is entirely up to DARPA. By next year there will be 5+ teams that could navegate last-race's course in
Anyway, good luck to all teams...especially new teams - you have quite a hurdle in front of you. See you in 1 year.