Slashdot Mirror


DARPA Announces 2005 Grand Challenge Semifinalists

Mockingbird writes "DARPA announced 40 semifinalists for the 2005 Grand Challenge autonomous robot race today. Notable remaining teams include the Carnegie Mellon University Red Team, Stanford Racing and a high school team, the Palos Verde Road Warriors. 78 teams missed the cut. The race, which will take place on Oct. 8, 2005 features a $2 million prize for the first team whose robot crosses 175 miles of the Mojave in under ten hours. The robots must be fully autonomous, with no team intervention allowed once the vehicle is launched. The first race was held in 2003, when the most successful team managed to log only 7.4 miles."

132 comments

  1. Team ENSCO! by sH4RD · · Score: 1

    Yeah...I've seen their machine. It's pretty freakin' sweet. I do love the Linksys equipment glued (or something) to the top. At least they have good taste in technology :P

    --
    WASTE - The Secure P2P
    1. Re:Team ENSCO! by JMUChrisF · · Score: 0

      Same here! I work with two of the non-ENSCO employees. Awesome video of their truck doing their course. REALLY Freaking cool. Good sounding engine in that beast. I'd love to make it into a daily driver.

      Go ENSCO!

    2. Re:Team ENSCO! by notsoanonymouscoward · · Score: 1

      I went with some co-workers to watch team axion qualify near UCSD. Except for a bump with a trash can, it did pretty damn good. The driving control is much more rough than a human driver ever would, but I think they can pull it off.

      --
      I ate my sig.
  2. Stanford's got this in the bag. by Chess_the_cat · · Score: 1, Interesting

    And it's street legal! As far as I know, the first such vehicle to make that claim.

    --
    Support the First Amendment. Read at -1
    1. Re:Stanford's got this in the bag. by CyborgWarrior · · Score: 2, Funny

      As if a DARPA authorized vehicle is actually going to get pulled over by the police? Haha, I can see the cop walking up beside that one now.....

      --
      If you can't say something nice, make sure you have something heavy to throw.
    2. Re:Stanford's got this in the bag. by NitsujTPU · · Score: 1

      We move ours in an old U-Haul when going between test sites.

    3. Re:Stanford's got this in the bag. by Anonymous Coward · · Score: 1, Informative

      Several other teams are street legal. Team DAD (IIRC) for one actually drove to the challenge with the team inside the car. PVRW may be as well. Team Tormenta is also street legal, if you disengage the steering controller.

    4. Re:Stanford's got this in the bag. by Xerotope · · Score: 4, Funny

      Team DAD's vehicle was street legal last year. It created a pretty funny situation. They brought it to the raceway the first day and were told they had to impound the vehicle for the duration of the QED. They asked "How are we going to get back to the hotel?" DARPA rented them a car.

    5. Re:Stanford's got this in the bag. by yincrash · · Score: 1

      it's good to note that it was RED TEAM that made it the furthest last year.

      woo cmu!

    6. Re:Stanford's got this in the bag. by brilinux · · Score: 1

      Yeah, damn thing almost ran me over in the Morewood parking lot. I hope they win.

    7. Re:Stanford's got this in the bag. by Anonymous Coward · · Score: 0

      We have cornell as well which is the real RED time.

    8. Re:Stanford's got this in the bag. by Animats · · Score: 2, Informative
      No, they had to get a ride out of the California Speedway to a car rental place and rent their own car.

      I've met the Team Dad people. I'm very impressed.

    9. Re:Stanford's got this in the bag. by zurmikopa · · Score: 1

      I'm the Axion team. (One of the teams that qualified) Our vehicle is street legal.

    10. Re:Stanford's got this in the bag. by SpyPlane · · Score: 1

      My team's (AVS) vehicle is a street legal (although mean looking Humvee) and got pulled over by police. They mostly wondered what the hell we were doing wondering around in a military Humvee on usually unused roads with tank-stopper obstacles in the bed. They were impressed with our explanation, wished us luck, and went on their way.

      --
      "We need a fourth law of Robotics: Stop Fingering My Wife"
    11. Re:Stanford's got this in the bag. by Anonymous Coward · · Score: 0

      To my knowledge, Golem Group's vehicle was street legal last year, and Team Caltech's vehicle is street legal this year. Please don't make claims like this without doing a little research first.

  3. iRobot by Anonymous Coward · · Score: 5, Funny

    The Roomba actually only made it 4 miles, but it cleaned up the competition...

    (groan)

  4. Dont bother competing by Timesprout · · Score: 2, Funny

    I have entered my Terminator this year as I think he needs to interact with other machines more, I still expect him to destroy all the other competitors but a day out and some challenge-response kaboom action will probably do him no harm. Also if your name happens to be John Conner I would recommend staying away from the competition site.

    --
    Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
    What truth?
    There is no dupe
    1. Re:Dont bother competing by Rei · · Score: 3, Insightful

      Hey, don't joke too much: DARPA's end goal with challenges like this is to build fully robotic semi-autonomous armed combat vehicles.

      May I propose a new slogan for the contest: "DARPA Grand Challenge: Because An Army of Kill-Bots Will Make Them Like America Again!"

      I think that the first autonomous kill-bot that we make should have a big "We've Come To Bring You Freedom!" sign placed directly beneath its main gun turret, for the irony. ;)

      --
      We should start dealing in those black-market beagles.
    2. Re:Dont bother competing by rdwald · · Score: 1

      Actually, as I understand it, DARPA isn't looking for fully robotic semi-autonomous armed combat vehicles as it is looking for fully robotic semi-autonomous armed supply vehicles. That way, all the humans who now are driving the supply vehicles can drive the combat vehicles instead. Alternatively, this would allow one human in a Jeep to drive and guard a whole supply convoy.

    3. Re:Dont bother competing by SomeGuyTyping · · Score: 1

      ONE human? Sounds like a single point of failure. That guy gets capped and a whole buttload of supplies are stolen. How bout if no humans were in the convoy - that makes more sense.

      --
      My posts are definitive. Reality is frequently inaccurate.
    4. Re:Dont bother competing by DNS-and-BIND · · Score: 3, Insightful
      Don't be an asshat. The end goal is to build automated supply convoys.

      You really think that the armed forces would allow their budgets to be threatened by unmanned combat vehicles? Commanders only think about how many men they command.

      Oh, and your reference to killbots reminds me of the Simpsons, where Kent Brockman used ridiculously overhyped language to try and scare viewers. The Simpsons was making fun of the attitude you display in your post.

      --
      Shutting down free speech with violence isn't fighting fascism. It IS fascism!
    5. Re:Dont bother competing by Kafka_Canada · · Score: 2, Insightful

      "DARPA Grand Challenge: Because An Army of Kill-Bots Will Make Them Like America Again!"

      I don't want our enemies to like us, I want them dead.

      --
      Fuck it
    6. Re:Dont bother competing by rastachops · · Score: 1

      So you're going to kill most of the world?

    7. Re:Dont bother competing by Anonymous Coward · · Score: 0

      How about "Eat burning Freedom!"

    8. Re:Dont bother competing by Anonymous Coward · · Score: 0

      I like ;)

    9. Re:Dont bother competing by Anonymous Coward · · Score: 0

      WTF...I have beeen in and out of the DARPA website to see a list of the teams that didnt make to the semi finals...Just couldnt findem.

      can Any one here help out..?

  5. A Real Challenge by Anonymous Coward · · Score: 0

    7.4 miles, eh? I bet they'd all be broken down, wrecked or stolen in a few blocks* if they had to deal with Chicago rush hour.

    * It takes an hour to go a few blocks in Chicago rush hour. Nothing like starting your commute, only to find out on the radio it will take you 2.5 hrs to escape the city. Yuck!

  6. Yeah, but... by MrAnnoyanceToYou · · Score: 1, Redundant

    Do they all run Linux?


    *duck*

    1. Re:Yeah, but... by Anonymous Coward · · Score: 1, Informative

      our's ran netbsd, which caused us some problems (ie, no native threading until 2.0, problems with large shared memory blocks)

      which is not to say that the OS kept our team out of the qualifiers, we had plenty of problems besides that.

    2. Re:Yeah, but... by Anonymous Coward · · Score: 1, Informative

      The Golem Group runs Linux. Can't speak for the others.

    3. Re:Yeah, but... by Anonymous Coward · · Score: 0

      Someone should make a Beowulf cluster out of them...

    4. Re:Yeah, but... by sceptre15 · · Score: 1

      Team Cajunbot runs Fedora Core 2.

    5. Re:Yeah, but... by osusparta · · Score: 1

      The OSU WAVE team is using a combination of Linux and FreeBSD boxes. -James

    6. Re:Yeah, but... by zebbo · · Score: 2, Informative

      Team Jefferson uses Fedora Core 3 and Java, even embedded java (http://jstamp.com/) http://teamjefferson.com/

    7. Re:Yeah, but... by Anonymous Coward · · Score: 0

      Team AVS http://www.autonvs.com/ runs linux and QNX.

    8. Re:Yeah, but... by Anonymous Coward · · Score: 0

      Team Caltech ran Slackware last year, and is running Gentoo this year.

  7. oh yeah?! by Anonymous Coward · · Score: 0

    my lego mindstorms robot will rock these guys anyday. its solar powered and has a gauss rifle that can be used to disable the enemy.

    1. Re:oh yeah?! by aklix · · Score: 1

      That sounds pretty sweet. I thought I was the only one who hooked up a solor panel to my Mindstorms RCX (I asked around). Gauss Rifle sounds pretty freakin sweet too, of coarse lugging that around will make your mindstorm go pretty slow.

    2. Re:oh yeah?! by kyle90 · · Score: 2, Funny

      Solar powered Gauss rifle? That must take what, like several years to build up enough charge?

      --
      Real_men_don't_need_spacebars.
    3. Re:oh yeah?! by BlogPope · · Score: 3, Funny
      Solar powered Gauss rifle? That must take what, like several years to build up enough charge?

      Legos are very patient.

      --
      My other car is a Popemobile
  8. hmm.. rtfa? by lonb · · Score: 1

    "The vehicles must travel approximately 150 miles
    over rugged desert"

    Where did the 175 number come from?

    --
    "Ain't I a stinka..." - Bugs
    1. Re:hmm.. rtfa? by heli0 · · Score: 3, Informative
      http://www.darpa.mil/grandchallenge/overview.html
      The route will be no more than 175 miles over desert terrain featuring natural and man-made obstacles. The exact route will not be revealed until two hours before the event begins.
      --
      Whenever the offence inspires less horror than the punishment, the rigour of penal law is obliged to give way...
    2. Re:hmm.. rtfa? by lonb · · Score: 1

      Yea, actually I found that in the overview after I posted. =) C'est la vie.

      --
      "Ain't I a stinka..." - Bugs
    3. Re:hmm.. rtfa? by heli0 · · Score: 1

      Last year's route was 148 miles so I would expect something similar this year.

      --
      Whenever the offence inspires less horror than the punishment, the rigour of penal law is obliged to give way...
    4. Re:hmm.. rtfa? by heli0 · · Score: 1

      142 miles, sorry.

      --
      Whenever the offence inspires less horror than the punishment, the rigour of penal law is obliged to give way...
  9. Two Indiana Entries by SeventyBang · · Score: 4, Interesting


    Today's Indianapolis Star. The mention of Scott Jones - the guy who invented voicemail - has a good project background.

    People have been coming from all over the state (literally) to work on the project (just down the road a piece) on a very regular basis, just for the fun of it.

    I've talked to several people who have been tinkering with it and are having a good time. Sometimes, bordering on obsession.

  10. Jumping for joy... by rice_burners_suck · · Score: 1

    I'm jumping for joy--This puts my team one step away from winning, and on top of that, it's all over Slashdot!!!

  11. code for winning robot by SQLz · · Score: 4, Funny

    while(true) { follow_road(); }

    1. Re:code for winning robot by Anonymous Coward · · Score: 1, Funny

      while(1) {
      if(!on_road()) {
      get_on_road();
      } else {
      petal_to_the_metal_grandma();
      }
      if(crash()) {
      if((rand() % 2) == 1) {
      run();
      } else {
      give_middle_finger();
      run();
      }
      }
      if(being_p ulled_over()) {
      chassis_type(BRONCO);
      chassis_color(WHITE);
      f loor_it();
      }
      }

    2. Re:code for winning robot by Spy+Hunter · · Score: 5, Funny
      petal_to_the_metal_grandma();

      Unfortunately the race was lost when, due to a tragic typo, the robot drove off-course to deliver flowers to a statue of an old lady.

      --
      main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
  12. Gravity has this one in the bag. by Anonymous Coward · · Score: 1, Funny

    "The race...features a $2 million prize for the first team whose robot crosses 175 miles of the Mojave in under ten hours."

    The winning design: Hummer + cinderblock.

    ;)

    1. Re:Gravity has this one in the bag. by Ingolfke · · Score: 1

      The winning design: Hummer + cinderblock.

      This would actually work if it wasn't for the fact that the Hummer can only make it 163.5 miles on a single tank of gas.

    2. Re:Gravity has this one in the bag. by timbo234 · · Score: 1

      Hummer can only make it 163.5 miles on a single tank of gas Surely that's a typo - 1.6 miles a tank seems right for the hummer.

      --
      Pre-canned Evolution Links for all those Slashdot holy wars.
    3. Re:Gravity has this one in the bag. by Animats · · Score: 1

      CMU tried that last year. Crashed three times in eight miles.

    4. Re:Gravity has this one in the bag. by Anonymous Coward · · Score: 0

      Hummer can only make it 163.5 miles on a single tank of gas Surely that's a typo - 1.6 miles a tank seems right for the hummer.

      Maybe 163.5 miles is for the disel version.;)

  13. A few questions... by BiggerIsBetter · · Score: 2, Interesting

    I'm a coder, not an AI or image-processing geek, so these might be dumb questions... but...

    Why the need for so many sensors? I can understand a use for them in low-visibility, eg dust or darkness, but the current models seem excessive to a layman. I mean, can one not use steroscopic cameras (scanning the field, as our eyes do), run edge and shade detection over the frames, and generate 3D terrain models in real time?

    How does a vehicle determin terrain density and route selection? Can terrain texture be estimated based on reflection or image matching, so the vehicle can decide not to drive over some water or a bog, for example?

    Even a good human driver is going to get stuck in the deset without learning how to handle a truck offroad. Is it feasible to train a neural-net system to select a likely course, possibly with a set of hardwired rules as a base? Eg, make your own way, but don't sink the car.

    I've no doubt this stuff is Hard, but much of this appears to be done via brute force...

    --
    Forget thrust, drag, lift and weight. Airplanes fly because of money.
    1. Re:A few questions... by neuroinf · · Score: 5, Interesting

      You need to look at the footage from the last attempts that showed how easily they become stranded on top of fence-posts. You wouldn't think it was possible to destroy a heavy vehicle like that, but a human will back off when hearing the gearbox squeal - not a computer. The vision stuff is an absolute nightmare - any sensor is better than vision. It sure is a serious challenge. I expect maybe 30 miles this time?

    2. Re:A few questions... by Asterixian · · Score: 1

      IANAAIE (AI expert), but my intuition says that maintaining control of a large vehicle at 20+ MPH on rugged terrain requires one hell of a real-time sensor system. The system doesn't understand patterns as well as humans do just from stereoscopic images, so it has to compensate by gathering many other kinds of information in real-time. Also consider that the algorithms we normally use to process such information accurately can take a long time - longer than your average human reaction time.

      In theory, you're right, a good driver wouldn't necessarily be able to do this task, which means anyone who wins this challenge might have created a car that drives better than we do. :)

    3. Re:A few questions... by BiggerIsBetter · · Score: 4, Interesting

      There's a zillion ways to destroy a heavy vehicle, or parts thereof. Drivetrain seems to be a weak point in many offroad vehicles.

      Your post just says to me, add some mics and some audio processing! When you drive, you listen to the car. You learn what's normal for a given speed or condition, and any waveform that's out of sync flags an error. You stop, look around, back up, and try something else. I had to explain this to friend of mine the other day - it had never occured to her to listen to a engine (or transmission) to hear the load.

      If you really don't like audio, run a calc against axle speeds, engine RPM, clutch slip, figure out how much torque is where, and back off when something's close to breaking.

      --
      Forget thrust, drag, lift and weight. Airplanes fly because of money.
    4. Re:A few questions... by Anonymous Coward · · Score: 0
      anyone who wins this challenge might have created a car that drives better than we do

      Obviously, you've never driven in LA, else you'd realize that it's already the case...

    5. Re:A few questions... by Zackbass · · Score: 3, Insightful

      For those that don't know, it's quite amazing how much the average car does this already. As mentioned, things like RPM, individual wheel speeds, clutch slip, internal pressure sensors, temperature sensors, and just about anything else you can think of that could be remotely useful is monitored by the computer which can kick the drivetrain into various "limp home" modes and set off that damn check engine light.

      --
      You gotta find first gear in your giant robot car
    6. Re:A few questions... by Anonymous Coward · · Score: 2, Insightful

      If it wasn't a Challenge, anybody could do it.
      2004 was Alpha. 2005 is Beta. 2006 will be Release.

      Even Microsoft takes 2-3 tries to get something right.

      Different teams are taking different approaches, but the more and different sensors you have, the more info you have to determine your environment.

      Some of it is Brute Force, for this problem. But, it still takes Smarts to finish at a decent speed. And last year, people finally got a clue as to how much Smarts it can actually take.

      So this year, it really will be more of a software problem. How fast can you process the sensors you do have, understanding limits of those sensors, tell the vehicle to change it's trajectory, and then perform the actions; all while following a course to an end goal.

      It has been amusing to read all the other recent posts from half-dots (those who toss off 1/2 a thought without even a smidgen of researching or thinking through, but have got to pump an opinion out) The lines of code being used, the processing to be performed, and the harsh computing environment are just some of the variables that make this so darn interesting.

      The Baja drivers DARPA hired to check the course and follow the vehicles, they talk about how difficult the problem is for them on this (relatively) easy terrain and constrained environment. To do it at the speed necessary to complete the course is hard. 17 mph average gets you there. 30 mph wins big, but is a much much harder driving task.

      Sure, no one finished the race last year. That shows how hard the problem is! The Whining Armchair Quarterbacks(TM) can't seem to even imagine how you learn from failures and try try again. Sure seem to be more bunches of negative nabobs out there this year, even on /. Hell with 'em. They got no idea of the gumption or stamina these teams are putting in, and the problems they are tackling every day.

      This is pushing the state of the art in robotics. And I for one am tickled to be doing my small part in the whole thing, and supporting one team as best I can.

    7. Re:A few questions... by LoraxLorax · · Score: 1

      You're better off doing audio - you only need one input device instead of a whole bunch of different sensors. And you have a really good point about how humans drive, in that out of place sounds inform us to all sorts of malfunctions.

    8. Re:A few questions... by sfcat · · Score: 1
      Why the need for so many sensors?

      For the visual sensors, because sensors don't rotate or change focus like eyes so different angles are needed, different viewing distances, etc. For other types of sensors such as radar are needed for handling situations such as very dusty conditions, blinding light, low light, etc.

      How does a vehicle determin terrain density and route selection?

      Well the route is handled with GPS and maps and the route is at least somewhat navicable so it just follows the route, but only to an inexact level of granularity. After that, visual sensors take over with the smaller adjustments for avoiding potholes and other obsticals.

      Is it feasible to train a neural-net system to select a likely course, possibly with a set of hardwired rules as a base?

      You seems to have alot of faith in neural nets. They aren't the magical end all be all of AI you seem to think. All they can do is learn a function, but for higher level planning they tend to not do so well. Also, for reasoning under incomplete information they tend to not do so well. Usually, these systems use multiple algorithms at multiple levels of reasoning and vote between different algorithms solving the same part of the problem. This is alot harder than you seem to think and I assure you that brute force techniques aren't being used, and further more aren't even possible. This is because a brute force technique would try all possibilities, but in this problem you must make a prediction and live with the results, just like real life.

      --
      "Those that start by burning books, will end by burning men."
    9. Re:A few questions... by hhawk · · Score: 1

      Audio feedback came to my mind right away as well... I would add temp sensors for detecting above normal opperating temps.. I wonder what else is possible?

      --
      http://www.hawknest.com/
    10. Re:A few questions... by timeOday · · Score: 3, Insightful

      See, it's pretty easy to fix the bug that destroyed your vehicle last year. What's 1000x harder is to anticipate the bug that will destroy your vehicle this year.

    11. Re:A few questions... by BiggerIsBetter · · Score: 1

      For the visual sensors, because sensors don't rotate or change focus like eyes so different angles are needed, different viewing distances, etc.

      Ah OK. I imagined focusable, rotatable cameras, on an isolated platform. I'm sure smarter folks than me have considered this, but I figured it would make sense to model terrain that way. Because that's how I do it. Maybe it's too slow.

      For the visual sensors, because sensors don't rotate or change focus like eyes so different angles are needed, different viewing distances, etc.

      Yeah, that's pretty much what I figured. Much the same as a person would do it. I was more getting at "optical ground recognition" with that question. Thinking about how people recognise a bog or ice or water without actually standing in it ("ooh, that ground's shiny/dark/textured/etc"). I guess you have sensors that can measure ground density or something.

      You seems to have alot of faith in neural nets. They aren't the magical end all be all of AI you seem to think.

      Not at all. I'm just using it as an example, although much of offroad driving is little more than function(scenario)=action. Of course there's higher level planning needed, for course mapping and so on, but I think that most of the details *can* be reduced to a functional level.

      Take your Mom out in a truck, and tell her to drive through a small bog. She'll probably drive in, and get stuck. Now tell her about the diff-locks. She'll either get through, or drive in, get further, then get completely stuck. So you say, "Hey, it's 4wd, but still... how about finding an alternative?" So she drives around the bog. Now she can weigh up the "severity" (texture, size) of the bog against an approach to it - drive through locked up, or drive around. NN or Fuzzy Logic just seemed like relatively easy ways to learn substract rules.

      I read some teams are using 7 or 8 fast CPUs here, and I wondered if maybe that was an indication of a) this is *really* hard, or b) too much information is being processed the wrong way.

      --
      Forget thrust, drag, lift and weight. Airplanes fly because of money.
    12. Re:A few questions... by cr0sh · · Score: 1
      Exactly - another thing you tend to do when you drive a car is "feel" - so much about the road (and where it is coming from) can be felt through the steering wheel, the gas (and brake) pedals, the gearshift and clutch (if you aren't driving an automatic), and the seat of the vehicle - to let you know about various road conditions, etc - as you drive the vehicle.

      So, maybe a series of microphones, strain gauges, and other similar force sensors (beyond the usual inclinometers and such) on various portions of the chassis and suspension might be a good idea on these vehicles.

      Ultimately, what is being asked to be constructed is analogous to pack animal of sorts. While most teams have given their animals eyes and a sense of location and orientation, they have probably left out hearing and "touch", as well as proprioception - this last is something that you must do in a legged robot if you wish it to walk, but would it be shocking at all to find out you must do it in a wheeled robot to get it to correctly navigate rough and unfamiliar terrain?

      Ask a person with a severe case of FMS (fibromyoalgia) whether proprioception matters or not (even in familiar tasks and conditions!)...

      --
      Reason is the Path to God - Anon
    13. Re:A few questions... by Anonymous Coward · · Score: 0

      I worked on Virginia Tech's entries into the Grand Challenge, specifically on the vision system. We use a Bumblebee stereoscopic camera for depth perception and image processing. (http://www.ptgrey.com/products/bumblebee/)

      Our entries (Cliff and Rocky, both of which are among the 40 finalists) use scanning laser rangefinders (LRFs) and the aforementioned Bumblebee stereoscopic camera. The laser rangefinder technology is nearly foolproof in many ways. The results are real (except sometimes when interacting with puddles) and the I/O interface is simple. The problems with LRFs are that they can be spoofed by dust and rain, cannot tell a piece of shrubbery from a boulder, and will miss important information like a chain link fence.

      The problem with a stereoscopic camera used solely for stereo processing is the sheer intensiveness of the process. Depth perception (both range and accuracy) depend entirely on the number of pixels used in the processing. The amount of computational power a team of 40 or so engineering students can fit on a club car is limited. Better depth perception means longer refresh times, which means that boulder that was 30 meters away when you took the pictures is probably lodged in your engine by the time you send the processed data to whatever program is running your path planning. (We used a behavioral-based approach of obstacle avoidance on Cliff, and the A* algorithm (http://upe.acm.jhu.edu/websites/Benny_Tsai/Introd uction%20to%20AStar.htm) for Rocky.)

      The way that our genius programmer - not me - approached the problem was to use a whole bunch of other algorithms using a single image to identify likely road areas, and then only process that area in stereo. It worked very well on a noisy test course at 10 mph, though that's still too slow to complete the challenge. Anyway, go Hokies!

    14. Re:A few questions... by bluGill · · Score: 1

      You mean you don't test on anything other than what stopped you last year? When I test my code (which doesn't run cars across deserts) I create every situation I can think of to see what will happen. (This includes everything someone else has told me about that I remember/wrote down)

      You know where you failed. You know where your peers failed. You test for that. Then you test it again, because it might be luck that got you by. Then you build your own playground and start testing. I know of many miles of trails to test on. From minimum maintenance roads (the township has them on the map, but they don't send trucks down it most years), to deer paths (which may not be legal to travel). Don't forget all the jeep meets, which are held in places where driving is hard - you go the week before/after and see what happens.

      Of course it will be years before you get all the glitches out. However you can work out enough that you can finish, if not this year, next. (I think this year is a little too aggressive, though you should make a good showing, you will know of many bugs in the system that you pray don't strike)

    15. Re:A few questions... by BiggerIsBetter · · Score: 1

      I was thinking that too. I'd even go as far as splitting the code up, and doing test-driven development.

      * Define a data model for the IO and AI.

      * Utilise an existing VR engine, and get a team working on the route navigation stuff. It doesn't have to be "real world" as the software doesn't know any different. Use topo maps or whatever, and work it until your virtual robot can navigate from A to B within the capabilities of the car and the world you give it, on the assumption that the IO system can produce the data model.

      * Go find some test tracks, and work out the vehicle control details with a human in control. Ensure that the IO is what's needed for the AI to manage the car.

      * Procure or produce the IO systems. Drive-by-wire is off-the-shelf. Most of the imagining is too, with some home-brew image processing on the top.

      * Let a human plot the general course, then teach the car how to drive. Start with A to B stuff (gas+steering+brakes). Throw in a bog or a rock-field that needs to be analyzed further, add a hill that needs engine braking on the descent, etc. Make new tests that it can't do, then make it pass them.

      * Rinse and repeat until happy.

      * Profit!?

      How about an OSDN Entry next year? ;-) Of course, the OSS development process might give some clues to the competition...

      --
      Forget thrust, drag, lift and weight. Airplanes fly because of money.
    16. Re:A few questions... by janwedekind · · Score: 1
      There's an interesting paper on how to do SVD-correspondence for (corner-)features.
      One can determine optical flow from this and it would be useful for sensing the motion of a flying robot f.e.

      Another interesting paper is about using correlation to estimate speed in an incremental way.

      You can see, that the problem gets feasible as soon as you restrict the domain sufficiently. Restricting the domain is crucial in computer-vision. Otherwise you'll end up searching for the holy grail of computer-vision ;-)

    17. Re:A few questions... by Gruneun · · Score: 1

      can one not use steroscopic cameras (scanning the field, as our eyes do)
      Is that heat coming off the desert road in front of us or water running across it?

      I've no doubt this stuff is Hard, but much of this appears to be done via brute force
      As much as this is a contest, it's also a massive brainstorming session. If nobody makes the finish line, but one team creates an elegant routing algorithm or one team designs an innovative rollover solution, DARPA wins. The prize money is peanuts compared to the money they would have to (and do) dump into contractors to get those results.

      The only reason this contest exists is because someone finally realized that bragging rights and a loose leash are very powerful motivators.

    18. Re:A few questions... by Anonymous Coward · · Score: 0

      The short reason why cameras alone generally don't work is that vision is notoriously fickle, you can easily have situations of high saturation on the camera, glare or simply dust. That said, there are good algorithms that work on "road detection". However, even the best of this software at best gives a "confidence level" on where the road edges are. This in turn reduces the reliability overall in the sensor. This isn't a "killer" but it starts to give you a sense of why a vision system alone is not generally enough.

      One other topic you bring up is the idea of creating a 3D terrain model. The problem inherent in this is that the 3D terrain models output by stereo are generally "fuzzy". Meaning that you are not able to accurately know "exactly" where an object is, especially at farther distances.

      These two items combine to make vision, though a good option, not necessarily the only option you want to run with. It takes a ton of work to do it right, and this is before you have dealt with any of the system level issues of controlling a vehicle. Which includes everything from performance control loops that perform well in hills to how you will feed in trajectories for the robot to follow. This is why at least most teams are going for the simpler option of using laser, and working on the other problem (vision) as a side or a secondary methodology.

    19. Re:A few questions... by BiggerIsBetter · · Score: 1

      That highlights something I have trouble getting my head around, whether or not vision is used.

      Even we (as drivers) don't know exactly where something is. The edge of a track in the desert is a good example - you take your best guess based on ruts or defoliage, and feel the response from the car when you get off the ruts. You make a correction to keep the ride as "smooth" as you can... still no good? You slow down, or try to find another route.

      You *don't* need to know every rock on the road, just those big enough to cause problems. Another post talked about reducing the domain... that's what we do everytime we drive. We learn what the car can do, and ignore anything below a certain threshold. Check it out at your supermarket judder-bars - boys in low cars slow down, moms in suvs don't. The boys are processing more because their cars need them to. The moms aren't because their suvs soak it up for them. Neither of them calculates based on vehicle approach angle, they just learned what height and grade they can ignore. Better chassis + good domain reduction = easier task.

      --
      Forget thrust, drag, lift and weight. Airplanes fly because of money.
  14. [OT] Your sig by cduffy · · Score: 1

    What does preventing the government from making a law abridging freedom of speech have to do with reading at -1?

  15. Is the motorcycle running this year? by Anonymous Coward · · Score: 0

    IMHO it was the coolest; but I'm too lazy to look it up.

    1. Re:Is the motorcycle running this year? by georgewilliamherbert · · Score: 2, Informative
      IMHO it was the coolest; but I'm too lazy to look it up.
      Yep.

      Blue Team

  16. Many of the robots are street legal by Anonymous Coward · · Score: 1, Informative

    Team DAD and The Golem Group to name only two.

  17. No flying allowed? by Anonymous Coward · · Score: 0

    Seems like we've had GPS navigating cruise missiles for quite a while.

    1. Re:No flying allowed? by Anonymous Coward · · Score: 0

      Real Cruise Missiles dont use GPS. They are totally autonomous, I know, I write the software that routes them.

  18. Re:Don't bother competing by Animats · · Score: 2, Interesting

    Of course. The purpose of the military is to kill people and break things. Ask any Marine. If you can't accept that, you shouldn't be in the arms business. Entering the DARPA Grand Challenge is being in the arms business.

  19. Go Golem! by shadowmatter · · Score: 3, Interesting

    The Golem I last year finished fourth, travelling 5.2 miles. It had the lowest budget of only $35,000 dollars (whereas some other teams' have a reputed budget of over a million...). And based on this image here, what I believe makes it uber-awesome is that they are cheating the competition by installing an elf under the hood and letting him drive.

  20. First race was March 13, 2004 by KFury · · Score: 2, Informative

    Not 2003...

  21. Who was cut by Rufus211 · · Score: 1

    I'm somewhat curious as to who the 78 teams are that were cut from this.

    1. Re:Who was cut by Chris84000000 · · Score: 1

      GCART@RIT for one =.(

      --
      Please stop misusing Catch-22 to describe chicken-egg problems or other paradoxes that are not Catch-22.
    2. Re:Who was cut by XkbaX · · Score: 1

      teams from princeton and MIT were also cut

    3. Re:Who was cut by locokamil · · Score: 1

      Princeton University with a staff of 5 and a budget of under $5K. We made the list for alternate semifinalists, though.

    4. Re:Who was cut by redrocknomad · · Score: 1

      We, MIT, blew out our steering motor three hours before our demo with DARPA and don't have funding to have replacements for everything (CMU) so we had to withdraw before showing what we had

    5. Re:Who was cut by lopgok · · Score: 1

      Team Robomonster was cut.

      I was the real software lead, despite what is on their web page. After I tried to explain that Z course was hard (follow a Z gps path, but with 2 trash cans placed by darpa that had to be avoided). I wrote soem basic gps parsers, but they decided not to use them.

      The technical guy in charge, Pete, tried to get all the code from the net, and found some visual basic gps following code. They tried to update their servo's, but flashed a bad program, and as a result, at the site visit, the car didn't move a millimeter under its own power.

      They also had (as far as I know) no sensors hooked up to the software to avoid the trashcans. Perhaps they wanted to run them over?

      I tried to explain that the software was what kept anyone else from winning last year, as the hardware was likely up to the task. They didn't seem to understand that.

      I told them I was withdrawing from the team, due to differences of opinion (like I wanted to test the software, but they thought that getting it to compile was some form of testing). I had unit tests for all of my code, but the test data I had from the GPS only had one satellite. (You need 3 satellites for lat & long, and you need 4 for elevation.)

  22. I have to say... by Krater76 · · Score: 1

    I think this is probably just about impossible. The plain fact is that you have to get 150 miles in 10 hours. That's an average of 15 miles per hour minimum. You obviously need to go faster than that.

    So I'm going into geek mode now and say that most of the time you need to be going 30 mph. So in one second (if i did my math right) you need to be able to see something ~14 meters in front of you. You most likely need at least a 5 second headstart since you have to break or turn. So about 60 meters sound right? The more the better. You need sensors/image processing that are powerful enough to be accurate out that far and then you need to process it. Don't forget AI so you know what to do.

    Don't get me wrong, I think this is very cool and would love to try to do this, but I'm realistic. If someone suceeds this time I will be very surprised.

    --
    "Is life so dear, or peace so sweet, as to be purchased at the price of chains and slavery?" - Patrick Henry
    1. Re:I have to say... by sharkb8 · · Score: 1

      Last year, CM's red team used Lidar, or laser radar. They flipped their Hummer the night before the race, crushing about $400K worth of Raytheon equipment, and it all had to be replaced in one night. Lidar lets you build a pretty good 3d image of the stuff in front of you. CHeck out computer vision on the internet, the simple stuff isn't too difficult to do. I believe one team last year kept having their vehicle mistake bushes for mountains though.

    2. Re:I have to say... by RickRussellTX · · Score: 1

      That's why they call this the "DARPA Grand Challenge", not the "DARPA Mediocre Challenge" or the "DARPA Wussy Challenge". DARPA set the goal knowing that it would be nearly impossible in the first competition to create excitement.

      And by all accounts, it seems to have worked, since there are many thousands more researchers (ranging from PhD engineers to talented gearhead hobbyists) working in the field of auto-navigated land vehicles than before the challenge.

      And, for the record, I want the Golem Group to win :-)

    3. Re:I have to say... by Anonymous Coward · · Score: 0

      For the record, the parent post isn't correct. CMU flipped their vehicle at least a week before the race, not the night before.

  23. Palos VerdeS by Ecko7889 · · Score: 0

    I think they made a spelling mistake. It is "Palos Verdes High School". That's cool that they made the news. This is just their second year as a new high school and they seem to being doing great. I wonder why my school hasn't gotten into this...oh well we kicked their ass in football.

    --
    $sig$
  24. Why 3D Computer Vision is HARD by TERdON · · Score: 5, Insightful
    Ah, coder? Do you have good knowledge of math too? Then YOU could possibly make the breakthrough in 3D Computer Vision.

    I'm studying a course in 3D Computer Vision right now, at TUHH. It's part of the Erasmus exchange program I'm having here - the eigth and last semester (excluding the thesiswork) of my master of engineering in automation and mechatronics at Chalmers in Gothenburg. I can easily say this course is the most difficult one of all I've been taking for all of my study time, hopefully the three weeks I have between that exam and the last of my others, will be enough to learn what doesn't stay in my head during the lectures...

    In fact, I have the course book right beside me. To begin, the description of it would be more or less along the lines "an orgy in linear algebra, mathematical statistics, with some flavouring of image processing, geometry, optimization and algorithms". Basically, it's 30-40% mathematical formulas, 650 pages, some containing things not even all MSc even learn like tensor notations etc. Not something I'm even sure is a good thing to recommend to very many slashdotters, even. You'll get its name though - "Multiple View Geometry in Computer Vision", by Hartley & Zisserman. ISBN 0-521-54051-8.

    What I see as problems in the book, is that almost everything is working on corner detection. This is great, if you want to make 3D-models of houses or other man-made objects (at least half of the examples in the book are architectural, I would say). It's not so great if you want to image bushes, rocks and other things with not so obvious corners on them. Also, the process involves quite heavy processing - both image processing, finding all those corners, statistical processing (to sort out outliers, which there will be), and optimization to find the best fitting backprojection of the image planes). I don't have a sure grip on the needed processing power but I doubt, when considering realtime demands in a car, that it'll hardly be easy to get it working.

    Also, it's still to a big deal itself an area under research. The situation with using 5+ images (from different cameras och just consecutive images from the same, moved camera), isn't very well known. Using more images, of course would mean a bigger chance to get a decent 3D model of the scene...

    And still, you would at least need two cameras to do anything useful. You can't reconstruct 3D space without having at least two images of the object to reconstruct. And probably you will need more - you would probably want to reconstruct all the way around (ie more cameras on the sides and backwards), and add extra sensors like radar etc for extra checks.

    And then you really haven't solved the problem of driving the car. You have only built a decent mapping of the 3D surroundings of it. You have to add AI/some kind of steering logic, which only in itself is a demanding task. Just look at all FPS games out there - if it would be easy to construct good AI, with a known 3D-world, tailormade for the figures, would we really be seeing that many games with crap-AI? I'm happy I ain't taking an AI course too, for sure!

    --
    I have a really elegant proof for Fermat's last theorem. If this sig was only a bit longer...
    1. Re:Why 3D Computer Vision is HARD by osusparta · · Score: 1

      We were hoping to get the bumblebee for this competition, but the team in all its wisdom decided that the order of buying things is sensors->more sensors->less expensive sensors->gps->sensors->cameras->COMPUTERS! If you guys want, I do have a slightly old version of the OSU WAVE team's AI. https://sourceforge.net/projects/tkrpathplanner/ -James

  25. Isn't that kinda hard? by drewzhrodague · · Score: 1

    Isn't that kinda hard for our current excuse for technology? This has never been done before, right? I welcome our new killbot overlords.

    --
    Zhrodague.net - I do projects and stuff too.
  26. Wired Mag on previous race results by Anonymous Coward · · Score: 2, Informative

    Wired magazine has an pretty funny article on the results of the 2003 race with a description with what went wrong for each team.
    http://www.wired.com/wired/archive/12.05/start.htm l?pg=15

  27. No, they want to kill people. That's life. by typical · · Score: 1

    Don't be an asshat. The end goal is to build automated supply convoys.

    Automated supply convoys? Dude, you're dumber than a bag of bricks.

    A friend of mine does robotics work at CMU. He was building a "autonomous search and rescue vehicle" for the DoD, went through all the vision and mapping and what-have-you work and was appalled when he was supplied with the final control system and discovered that it sported a big red "Weapon" button.

    Nobody in the military is going to ask for funds to build an autonomous bloody kill-bot, for the obvious political reasons. However, once you *have* an autonomous platform and a human-tracking system (so, you know, you don't "accidentally drive into your soldiers", or so you can "find them on search and rescue missions"), you stick a couple of servos and a gun on top and you have a basic version of your kill-bot. Once you have *that* done, it's a much smaller political step to request funding for improvements to "help ensure that none of our boys get accidentally shot", or something along those lines.

    Remember the unmanned Predator? Yeah, that "unarmed", "reconaissance" aircraft? The one we stuck a Hellfire air-to-ground-missile to and used to assassinate some al Quaeda suspect (and a couple of people that happened to be in his car) in Yemen, waaay back in 2002? Once you have a vehicle platform, sticking weapons on it is not hard.

    You really think that the armed forces would allow their budgets to be threatened by unmanned combat vehicles?

    Naturally, you mean *other* than the abovementioned Predator (and the other unmanned aircraft that can serve as weapons platforms). And other than cruise missiles. Come on, man. Face reality. They've been doing this for a long time.

    Commanders only think about how many men they command.

    Wow. You have one heck of a simplistic view of the people in the military. If that was true, we wouldn't have most manpower-reducing military hardware we do today -- just lots and lots of infantry.

    If I'm a general, and someone offers me something that means that I don't have to send people out into a meat grinder, suffer political pressure, pay death benefits, pay to replace someone, deal with photos of dead soldiers making their way into the press...no, I'd have to say that I'd be pretty quick to look into those kill-bots.

    That doesn't mean that it's necessarily *bad*, having robots do killing for the United States. We just have to be aware of what we're getting into, and be sure that this is a path that we want to take. Occupations of a country may someday consist of just dumping robotic sentry vehicles all over it, things that shoot on sight anyone that isn't carrying the appropriate radio identification device (or is moving outside of their prescribed limits). No American soldiers need be killed, but we have to consider what happens when wars are cheap and easy to fight, and the media doesn't stir up the public over them.

    --
    Any program relying on (nontrivial) preemptive multithreading will be buggy.
  28. Give the NSF the DARPA funding by typical · · Score: 1

    Of course, if you *don't* build arms, you don't get the funding to do competitive bleeding-edge robotics work. Bit of a Catch-22, eh? If the NSF got the funding that the DoD is provided with to make tomorrow's killing mechanisms, we wouldn't have these kind of dilemmas, would we?

    --
    Any program relying on (nontrivial) preemptive multithreading will be buggy.
  29. Right... by cr0sh · · Score: 3, Insightful
    If this doesn't make you think they will slap the winning code into such a 'bot, nothing will.

    DARPA, and the DOD would *love* to have semi to full autonomous "kill bots" - in a way, today, they already have them for some tasks - they are called "cruise missles", which can be launched, told to stay on "hold" above possible targets, then commanded to strike on located targets. I would assume "located" likely means some form of lat/lon coordinates or painted with a laser (either by troops or from the air).

    The exact same thing could be done with a kill bot: send it to a predetermined position, and tell it to "hold fire" unless acted upon agressively, or if non-friendly comes into position (at which point it could bark a series of commands in different languages to the offender - think of it as an active landmine with intelligence that can move on command), which if not heeded, shoots a warning, then if continued, shoots to kill. Friendlies are identified by RFID or similar tags. Equip them with the ability to identify each other, as well as to flock or coordinate efforts with one another. Other commands could be something like "fire on ident", where they could be set up, then when a target is painted with a laser (perhaps from a troop's rifle), it fires on that target.

    You better bet that the DOD and DARPA would be all over such a system if it was proven field safe (to our troops) and easy/quick to use, and rugged. They are half way there with the TALON robots already, they just lack the rest of the package, which the Grand Challenge is dealing with...

    Of course, one can also easily see the potential of scaled up versions - robotic Humvees and M1A tanks, as well as robotic quads, and perhaps legged versions...

    BTW - this last was actually funded by DARPA back in the 1980's, which culminated in the Odetics, Inc. (now known as Iteris, Inc. - based in Anaheim, California - interesting the strange things going on at this company, whatwith name changes, etc - plus, they are developers of an "electronic highway" concept - I am sure there is no relation to the Grand Challenge - wink, wink) ODEX-1 legged walker - a very unique leg design that proved to be fairly robust and strong, while keeping outboard weight (on the legs) to an absolute minimum by moving all the electric motors inward toward the torso of the machine.

    Think about it - if you could, in addition to GPS coordinates, vision systems, etc - also bury in the ground or nearby some form of active or passive "locator" beacons, such as what Odetics - oops, I mean Iteris - is developing - wouldn't the problem become just a little bit simpler...?

    Nah - DARPA hasn't been thinking about this, not at all, not at all...

    --
    Reason is the Path to God - Anon
    1. Re:Right... by Iriel · · Score: 1

      Yes, the military has had ideas about the application of technology that could create 'kill-bots', however, one has to realize that using sensors to determine terain is still a long way off from enemy/ally recognition. What's the use of making some Mechwarrior-type missle launching autonomous robot if it can only recognize moving targets? Anyone can be killed by that.

      Besides, not everything is black and white as a lot of people would like to make it seem. There are offensive capabilities granted by autonomous machines, but there are also defensive/rescue/supply/whatever options to explore as well.

      Just because we can make something autonomous for one task doesn't mean we automatically have Gundams on autopilot destroying entire nations. The technology will most likey integrate with the military tech we already have, not replace everything overnight.

      --
      Perfecting Discordia
      www.stevenvansickle.com
  30. Re:Don't bother competing by earthforce_1 · · Score: 1

    Last year's DARPA challenge was very good for breaking things. Killing people might happen if they stand anywhere around the course, and the robotic drivers decide you are just a sagebrush.

    --
    My rights don't need management.
  31. Re:No, they want to kill people. That's life. by DNS-and-BIND · · Score: 1
    Do you know any Navy commanders? I do. They care about two things, how much budget, and how many men.

    Please stop calling it a kill-bot. Hello...Simpsons?

    --
    Shutting down free speech with violence isn't fighting fascism. It IS fascism!
  32. Money... by Daniel294 · · Score: 1

    "The race...features a $2 million prize for the first team whose robot crosses 175 miles of the Mojave in under ten hours.".
    Too bad most teams have already spent more than that. Oh well, it's the experience I guess. It makes my FIRST robot seem like legos! Personally, I will be rooting for PV high (1) because they are a high school team and (2) they are 5 miles away from me. However, it won't be done. I predict a maximum of 20 miles.

  33. Re:No, they want to kill people. That's life. by Anonymous Coward · · Score: 0

    Idiot, "kill-bot" is from Futurama, not the Simpsons. :)

  34. Re:No, they want to kill people. That's life. by ilmdba · · Score: 1

    keep dreaming...

    http://www.navy.com/navyofthefuture/ddx

    "Crew: Many of the functions performed by crews on conventional destroyers will be automated on the DD(X). That means a reduction in crew size - 330 fewer sailors than the Spruance class destroyers and 200 fewer sailors than the Oliver Hazard Perry class frigates. The crew will also focus on fighting versus ship maintenance."

    http://www.navyleague.org/sea_power/apr_05_46.php

    "Part of the 1,200-man reduction in the size of a carrier crew planned for the CVN 21 next-generation carrier will be accomplished by installation of the new launching system and arresting gear."

  35. but by nounderscores · · Score: 1

    Everyone knows that a clone army will respond more creatively to situations that would stump a droid army.

  36. Re:Don't bother competing by SeventyBang · · Score: 1


    No, the purpose of the competition is to find a replacement for UPS.


    (see the newer /. story)

  37. OSU WAVE Team by osusparta · · Score: 1

    Hey all. I'm in charge of the actual pathplanner software for the OSU WAVE team. All of you should probably know that this whole DARPA thing is a joke. They don't want people to succeed. MIT, Princton, and even Ford didn't make it, but somehow my school did. Don't get me wrong, our software is freakin' amazing, but it was never used. The dumbest technology known to man that got lucky and passed 1/3 of the site visit tests got us through. I'm happy to be a part of this whole thing, but this whole thing is weird.

    1. Re:OSU WAVE Team by Qrlx · · Score: 1

      that doesn't really tell us anything we don't know. its darpa. its weird. film at ii?

    2. Re:OSU WAVE Team by redrocknomad · · Score: 1

      I'm curious what the dumbest technology known to man actually is...

    3. Re:OSU WAVE Team by osusparta · · Score: 1

      Sorry, I'm a little pissed at them and forgot to actually give any details. What they used was a knee-jerk reaction type technology. They use a couple of low-tech sonar units (kind of like what we used in high school physics) and have the car randomly turn left or right when that happens. There is a basic "global path planning" that follows GPS waypoints, but it isn't as reliable as luck.

  38. bring your diazepam by mbius · · Score: 1

    There's a zillion ways to destroy a heavy vehicle, or parts thereof.

    SNAAAAAAAAAAAAAAAAAAAAAKE!

    --
    you can have my violent video games when you pry them from my cold, dead hands.
    Prime UID Club
    1. Re:bring your diazepam by BiggerIsBetter · · Score: 1

      Badger badger badger.

      --
      Forget thrust, drag, lift and weight. Airplanes fly because of money.
  39. The U.S. Military In 15 - 20 Years ... by MS_leases_my_soul · · Score: 1

    The U.S. Military is going to a model where the "heavy lifting" of combat will be done by autonomous or semi-autonomous units. It is all about reducing training costs and the "political cost" of human lives.

    The Air Force is going to this model with the http://www.fas.org/man/dod-101/sys/ac/ucav.htm/UCA V. You will F-22 fighters for Air-to-Air Superiority to control the skies as F-35 Joint Strike Fighter squadrons augmented with UCAVs take out ground targets. The UCAVs get the dangerous missions and the F-35s do clean-up work. Targets are found and designated by UAVs like the Predator and the Global Hawk. 80% of the Air Force's costs are training and personnel. Even when you get to hard equipment costs, the UCAV is 1/3 the price of a JSF and 8 - 9% the cost of a F-22.

    The Army and the Marines will have the "packbot" and Talon robots to engage "hardened targets". Ground robots will still require human guidance and will most likely be an extension of the eyes, ears, and rifle instead of autonomous soldiers.

    As a veteran of the Gulf War and a former paratrooper of the 82nd Airborne, I can not even begin to describe the advantages of a highly mobile force that can air-deployed or sea-deployed in 1 - 3 days anywhere in the world. The 82nd Airborne can have 1/3 of the Division anywhere in the world in 18 hours or less of the President saying "Go." Imagine them having that same deployability but now having that same size force able to employ more firepower than the entire Division thanks to robotic augementation.

    The problems here are still those of logistics and command and control. You still need boats and planes to put your forces on site. Commanders still need to be able to get an assessment of the tactical situation from the field and give orders to their forces. Robots put that much more of a strain on command and control and logistically are yet another thing that must be transported to the front, kept running, and repaired as needed.

    I wonder what the MOS of a robot repairman is in the Army?

  40. Re:Don't bother competing by Anonymous Coward · · Score: 0

    "The purpose of the military is to kill people and break things."

    It's obvious you know nothing about war history or the military in general. Just stop posting, makes you look much less stupid.

  41. My favorite vehicle did not make it by reed · · Score: 1

    I was rooting for a somewhat local team but they didn't qualify, probably will enter next year though.

    Their vehicle is pretty awesome, hope they can get some good navigation software worked out by next year. The vehicle can just drive over lots of obstacles that seem to get the various trucks and jeeps hung up, which gives it a good advantage, but they will probably need to "armor" it a bit from branches, posts, and loose rocks.

    Videos of the vehicle here: http://www.howeandhowe.com/videos.htm

  42. Re:No, they want to kill people. That's life. by Pollardito · · Score: 1
    A friend of mine does robotics work at CMU. He was building a "autonomous search and rescue vehicle" for the DoD, went through all the vision and mapping and what-have-you work and was appalled when he was supplied with the final control system and discovered that it sported a big red "Weapon" button.

    yup, i saw Real Genius too

    it's a much smaller political step to request funding for improvements to "help ensure that none of our boys get accidentally shot"

    you're pretty caught up in your viewpoint here, but i thought i'd point out that the vehicle doesn't have to be autonomous to be unmanned. Wired had a recent article describing how the Air Force is requiring that vehicles like the predator be flown by trained pilots, so it'd seem to be moving in the other direction if they were suddenly this much more miserly about the resources operating their vehicles.

    otoh, throw some level of autonomy onto a vehicle that is being piloted remotely for the most part and you've got the ability to continue operation past the point where you're communications are jammed. the knowhow that goes into operating autonomously could also be used as a system to doublecheck the actions of the operator.

    anyway, these killbots already exist, it's just that there's someone with a little joystick operating them now. there will probably always be someone targetting their weapons.

  43. Uhhh... by Anonymous Coward · · Score: 0

    I actually used to live where they are doing the testing (Near Fort Irwin, CA) and have drove in that terrain with absolutely ZERO visibility (I'm not kidding, no stars, no moon, no headlights, all you can do is "use the force" and drive slow) and its quite the task.

    Of course, 'bots in computer games can easily traverse terrain such as this, wonder why Bungie didn't have a submission...

  44. NN and pregen data? Pretentious gibberish follows by Anonymous Coward · · Score: 0

    Seems to me that a bunch of collaborative systems wouldn't be the worse way to go. Use a terragen/landscape generator and some scripts to create thousands of images of vaguely representative terrain. Run the images through a software representation of the visual sensors (including any feature detection/compression routines) to generate visual inputs.

    Get some neural networks working on that input and matching it to a number of factors - visible surfaces, object recognition, material recognition, anything you can think of. Hook all of these into a neural guesser that tries to determine the overall 3D-nature of the surroundings (including objects (static and moving) and likely materials).

    Connect the output from that to a path plotter. See if the result can naviagate the virtual landscapes in a virtual vehicle without stranding it. NN for two abilities - shortest reasonable path and road-following. Train it to avoid obstacles and dodgy terrain.

    Use sound and vibration and pressure and heat and light level and GPS and shock and other sensors to determine the state of the vehicle and immediate surrounds. Limit the vehicle to 0.1mph and load your software. Have it prowl semi-randomly around the desert for a couple of weeks, calibrating its distance-guesses on the nature of the terrain against close-up sensor readings.

    Throttle it up to 1mph and implement a time-dependent reward/rating sytem, setting a pair of goalpoints at semi-random locations and running the vehicle back and forth between them a couple of dozen times, then resetting the goal points and so on, until the fastest method is determined. Have the vehicle sensors constantly monitoring for potential damage and marking certain sensor/state patterns as potentially dangerous.

    Ramp the speed limit up to 5mph and run a third set of trials. Measure fuel consumption vs different driving/environment patterns.

    Ramp the speed limit up to 20mph. See if you can get the vehicle to tip over. Run over rough terrain, make notes of any damage or temporary inaccuracy of the sensors (via vibration, shock etc) vs speed and surrounds. Implement a goal of sufficient sensor/evaluation accuracy to allow undamaged travel over easy-to-rough terrain, plus a generous buffer.

    Ramp up the limit to 50mph (and have at least three different remote-stopping systems at this point). Have the vehicle find a speed point over various terrain types that minimizes damage, fuel use and time taken while maximizing sensor/evalutaion accuracy.

    Tweak the algorithms and hardware for speed and accuracy of evaluation under a wide variety of conditions. Abridge the NN. Make sure it's mostly only evaluating the terrain along the most likely courses. Increase the raw speed of the computers and shockproof them. Beowulf them, if you have to.

    With luck, the safe max speed will be above 20mph on flat terrain. Without luck, you may have to settle for either getting the furthest in 10 hours without finishing, or flooring it.

  45. Re:No, they want to kill people. That's life. by DNS-and-BIND · · Score: 1
    "Just miles from your doorstep, hundreds of men are given weapons and trained to kill. The government calls it the Army, but a more alarmist name would be... The Killbot Factory."
    --Kent Brockman

    Child, go away, don't bother me. This was a quote five years before Futurama ever got on the air.

    --
    Shutting down free speech with violence isn't fighting fascism. It IS fascism!
  46. LINK PLEASE? by wskellenger · · Score: 1
    How about a link to the actual press release??

    Something like five URLS in the story and not a single link directly to the semifinalists?