Not yet a member? No problem!
Sign-up just takes a second.
Forgot your password?
Recover it now.
Already signed up?
Log in now.
Forgot your password?
Recover it now.
Not yet a member? No problem!
Sign-up just takes a second.
Remember your password?
Log in now.
8 Comments
Reefiesays...I for one am glad our new robotic overlords won't take much effort to subdue when the humans are ready to rise up.
eric3579says...DARPA Robotics Challenge
https://youtu.be/8v18eAtRiCI
Sarzysays..."Derpa" tag.
https://media.giphy.com/media/b9aScKLxdv0Y0/giphy.gif
notarobotsays...Sigh.
noimssays...Don't be cruel. We've all been there.
Paybackjokingly says...To be fair, their programming was done by the same guy who created QWOP.
NaMeCaFjokingly says...Yeah, the robot apocalypse is gonna take a few decades to get right
MilkmanDansays...Late to the comment party here, but Slashdot had an interesting explanation of *why* so many of the robots had trouble like this:
"DARPA deliberately degraded communications (low bandwidth, high latency, intermittent connection) during the challenge to truly see how a human-robot team could collaborate in a Fukushima-type disaster. And there was no standard set for how a human-robot interface would work. So, some worked better than others. The winning DRC-Hubo robot used custom software designed by Team KAIST that was engineered to perform in an environment with low bandwidth. It also used the Xenomai real-time operating system for Linux and a customized motion control framework. The second-place finisher, Team IHMC, used a sliding scale of autonomy that allowed a human operator to take control when the robot seemed stumped or if the robot knew it would run into problems."
http://hardware.slashdot.org/story/15/06/10/038224/why-so-many-robots-struggled-with-the-darpa-challenge
Discuss...
Enable JavaScript to submit a comment.