Category: Rescue Robots

Haiti and Kobe, Japan

Haiti and Japan

Tomorrow is the anniversary of the 1995 Kobe Earthquake. The irony that I am in Kobe accepting the Motohiro Kisoi Award for Academic Contributions to rescue engineering instead of in Haiti does not escape me. There is always a gap between possibility and reality, but gaps about high definition TVs seem trivial compared to gaps in life saving and recovery.

Yesterday Ms. Ikuko Tanimura from the International Rescue Systems institute took me to the Hyogo Perfectural Emergency Management and Training Center and the full-scale earthquake testing facility at the National Research Institute for Earth Science and Disaster Prevention. Suffice it to say that the Japanese have the technology to shake entire 6 story buildings and bridges in three dimensions and understand collapses. Recently, they shook to pieces a wooden house and let the IRS researchers apply their technologies (I am so envious!) Dr. Akiko Yoshimura, an architect, designed a clever facility where teams can practice victim management in wet, confined spaces designed to tax the ergonomic constraints of responders. As I travel the world, I see so much good science, good ideas, good inventions!

The Japanese researchers from IRS are sanguine about progress and the time it takes to go from research to the field. IRS director Prof. Satoshi Tadokoro started what became IRS in 1995 in response to the Kobe earthquake and the loss of Motohiro Kisoi, a promising graduate student in his department. I also started in 1995, motivated by the Oklahoma City Bombing. The research directions Satoshi and I initiated back in those days are a little embarrassing in retrospect- we didn’t understand disasters and there was little data or experience base. Now as we’ve profited from being engaged in exercises and actual responses, being able to apply cognitive work analysis methods, and collect performance data on machines and people, the community is beginning to isolate and address more meaningful issues that will lead to truly useful technology that will be easy to use and maintain.

But as we discussed last night at the reception, good science isn’t sufficient to help a disaster like Haiti. We need industry to (cheaply) manufacture the devices, agencies and NGOs to accelerate adoption.

But what we really need are early adopters and caches all over the world, so that even it doesn’t take 3 days for response teams to bring in the sensors and robots (and comms and power), that the local responders can make the most of the critical 72 hours.

Brazil Mudslide: rescue robots for mudslides

The sad news of the mudslide in Angra dos Reis, Brazil, brings up memories of our deployment to the 2005 La Conchita, California, mudslides. Rory Rehbeck, then a captain with LA County Fire Department, invited CRASAR out to assist Ventura County Fire Department. There really aren’t survivors of a mudslide- the mud is a liquid, penetrates like water, and covers everything. The best you can hope for is survivors from the collateral damage. The houses on the slope of La Conchita were either buried, squished as if inside a giant trash compacter, or untouched. We attempted to use the new Extreme robots we had purchased through a NSF grant to search some of the damaged houses as a family of 6 was still missing (they were on vacation) and the canines were giving some ambiguous hits.

Our journal article “Rescue robots for mudslides: A descriptive study of the 2005 La Conchita mudslide response” Journal of Field Robotics, vol 25 no 1-2 (Jan 2008) p 3-16  gives the details of what Sam Stover and I experienced: the robots did not do well in the mud and vegetation when we tried to go under a house to get in it nor work in deep shag carpeting when we entered another house through the garret window. See the Media Gallery for photos. But being there did identify the need for remote sensor networks dropped off by UAVs to continously monitor for further slides (geologists checking manually every 6-8 hours isn’t good enough)- sensor networks for advanced placement already exist, they just don’t get used. We’re looking forward to combining the UAV work here with Prof. Dez Song’s work in sensor networks.

The families in Brazil are in our prayers and hearts.

Robotics Rodeo at Ft. Hood

RIMG0149

RIMG0159

RIMG0149

I had the good fortune to attend the Robotics Rodeo at Ft. Hood last week- a rodeo of unmanned ground robotics hosted by U.S. Army Tank Automotive Research, Development and Engineering Center (TARDEC) and Fort Hood III Corps (go Phantom Warriors!). A wonderful experience and many thanks to the CO Gen. Ricky Lynch (he has MS in robotics from MIT).

Some pictures are above and some thoughts about the commercialization of robotics…

According to a good friend, Bill Kearns, at the turn of the last century, there were over 200 car manufacturers in North America. (His family’s business was one of them.) Each manufacturer had something special, a starter motor, independent suspension, what have you. An amazing array of advances, some redundant, many brilliant.

But the problem was, they weren’t on the same car. Who wanted the latest, greatest engine on a car that you had to use with a hand crank?

Durant and Ford were credited with manufacturing but sometimes it is missed that they it wasn’t just that they mastered mass production, they mastered mass production of the right thing. They were among the first to view the cars as the sum of its parts. The superior technology of a component (usually invented by the owner) was not the reason for existence but rather a marketable feature of a desirable whole. As was stressed in one of my mechanical engineering courses, automobile companies are manufacturing companies, which make things for people to buy, not engineering companies, which create or investigate ideas for someone else to make into things for people to buy. Automotive companies at the turn of the century were really about engineering, not about the car. A similar pattern of scattered developments which were consolidated into systems happened in the aerospace industry.

The Robotics Rodeo reinforced my opinion that ground robotics is in the same state. Interesting pieces, some brilliant engineering, lots of duplication, and few useful systems.

One conclusion is that this is the Natural Order of Things and will sort itself out over time. This line of reasoning is: perhaps some duplication will result in lesser technologies occasionally trumping superior technologies and some dollars will be wasted. But this should be tolerated since the duplication and competition is usually efficient overall and reduces purchase prices, right? Besides, premature standards or regulations can kill off an emerging technology.

The Natural Order of Things philosophy has problems. In asymmetric warfare, do we have time or dare risk being beta-maxed by an adversary? And in days of trillion dollar deficits, will we be able to afford the cost of duplication? Remember, the government is subsidizing the UGV market (either through DoD or law enforcement) whereas automotive industry was private capital. There is no real consumer market for these devices. Is UGV development is in fact regulated by the invisible hand of capitalism or being de facto regulated by current defense acquisition processes. If so, is that a good or a bod thing? I don’t know…

Wildland firefighting, UGVs, and UAVs

I think UAVs for wildland firefighting is a good thing, honest!

I’m at the AUVSI North America conference– yesterday I gave two papers, one on the wildland firefighting descriptive analysis that we did with Lockheed Martin on the use of ground robots and one on our Rollover Pass, Texas, response. The wildland firefighting paper made the Flight Global Daily newsletter today (probably as the token application du jour that didn’t involve weaponization). I’m quoted giving a list of problems with UAVs for wildland firefighting- that was the list of problems from the focus group of subject matter experts.

There may be a killer UAV with my name on it… please, please, call them off. I love UAVs, honest!

The list of problems is based on what they’ve seen in UAVs to date, not what’s possible or what is even available. Sadly the disconnect between what exists and what the response community has access to remains depressingly high. Bob Roth and Tom Zajkowski with the Forestry Service are working hard, with Greg Walker’s group at Alaska and Brian Argrow’s team at Colorado combining research and fieldwork.

But the poor firefighters often only see and interact with vendors who come out of nowhere at a disaster and claim to have the best technology; while well-meaning, the technology is often a poor match because there is no understanding of what the responders really need. Trust me, it’s not covered in any of the movies, you actually have to talk with them. Before a disaster. During, they are way too busy and are justifiably deeply suspicious of anything outside of their network of relationships..

Which reminds me about the time a group of technologists were told by an agency that their technology wasn’t needed, but showed up at the disaster anyway (I warned them not to do that), and were jailed and their gear impounded. Yep, interfering with a response is an offense. And the incident commander makes the call as to what constitutes interference.

Mismatched technology plus bad manners = deep abiding negative view of robots.

Anyway, ground robots good, aerial robots good, all good for wildland firefighting when applied appropriately! But we’ve got to educate the firefighters about what’s out there and ourselves about what they need. Don’t shoot the messenger 😉

Beyond Asimov; The Three Laws of Responsible Robotics

IEEE Intelligent Systems just printed our (David Woods, OSU, and my) article about “Beyond Asimov: The Three Laws of Responsible Robotics” and put “Beyond Asimov” as one of the articles on the cover… and the hate mail has started!

So what does Asimov and his Three Laws of Robotics have to do with rescue robotics? The Three Laws are being taken seriously as a framework for discussing human-robot interaction. Rescue robotics has humans behind the robot and humans in front of the robot- it’s about as human-centric as you can get. I became one of the early drivers of the human-robot interaction community (I co-chaired the seminal 2001 DARPA/NSF study) precisely because I found through my fieldwork that the poor interaction was the limiting factor. No matter how bad the rescue robots were in terms of locomotion, communications, sensing- the horrible mismatch between the robots and the human cognitive abilities for the environment was the limiting factor. It isn’t just interfaces, it is the set of fundamentally, pervasively wrong assumptions about how people interact with robots.

Whenever I hear some grad student talking about wanting to design robots which meet Asimov’s Three Laws and thereby provide perfect human-robot interaction I get ill. One year I heard a researcher telling the press that their robot met the First Law of Robotics (a robot may not injure a human) because it was able to avoid people. Except that it was simply avoiding heat sources and people happen to be warm.

To say AI researchers tend to be technological optimists is an understatement.

The paper came about when I began to read Moral Machines (David texted me that I had to stop whatever it was I was doing and go read it now, he was so put out by the book). I next-day-ed the book, and between that and the Living Safely with Robots tome, shouted “enough with the Asimov’s Laws already as some sort of gold standard for robot ethics. It was a literary device. Let it go!” My family tends to find things to do away from the house at time like that. I thought the Moral Machines actually made a strong, though unintentional, argument for why Asimov would get sued if he were a robot manufacturer.

So I whipped up a draft on alternative laws one Saturday morning. Leila Takayama and Victoria Groom from Cliff Nass’ group at Stanford read it, make great suggestions, and included in their HRI workshop. I sent it to David to read and he came back with excellent ideas, tons of experiences and examples of how autonomy and automation fails, and way better prose. I insisted that we stay with three laws and that they had to be symmetric with Asimov’s– sticking with literary convention to make a point. I agree with David, if you really want laws, it’d be better to start over. Anyway, we put a version in an IEEE ICRA workshop (thanks Cindy for presenting!) and continued to refine. We ran it past Robert Hoffman who saw the possibilities of getting a more informed discussion going and after a rapid edit cycle and a discussion with Jeff Bradshaw, it’s in print. (I’m sharing names in a Good Way, please don’t go yell at them if you hate the paper.)

Hopefully, besides hate mail, we’ll get a real intellectual discussion going instead of extreme quotes in the media. AI robotics is capable of so many things, I hate to handicap true progress by adherence to a cute literary devices designed to create problems.

RoboCup Rescue

robocup competitors

I’m in Graz for the RoboCup Rescue- my talk on Friday was well-received and it was great to see so many students doing such great work!

I finally got to meet Amir Soltanzadeh, my Facebook buddy, and leader of the AriAnA team- the team gave me their uniform- thanks! Iran has always been very active in RoboCup Rescue and AAAI rescue competitions- it’s certainly a practical application given the earthquakes in that area, though the real “killer app” is using robots to remove land mines. I was very impressed with how quickly the US and Iran set aside differences to allow the US international team to help at the 2003 Bam earthquake. Colleagues in Iran tried to arrange for CRASAR to attend but it would have taken 2 days by commercial air- too late to be of much help and too expensive to just check things out- and we could only get permission from the State department to fly with the military over, not back.

robocup testbed

The competition was well attended by about 20 teams from Europe and Asia (none from the US)- you can check out robocup.org for more details. The competition arena designed by Adam Jacoff at NIST has to satisfy many constraints- it has to be cheap, shippable to different venues, repeatable so everyone can build their own, open and visible so that spectators can see, and still present a challenge! In the early years of the competition when it was held at IJCAI, Chief Ron Rogers of Florida Task Force 3 was involved and put up tarps to black out areas and created some water hazards. More realistic, but quite the barrier for new teams to get involved and hard on the spectators!

I haven’t been to RoboCup Rescue in several years. There was a surprising homogeneity between platforms. Almost all of the ground platforms have converged to a Packbot or Talon style with flippers and treads and a similar size, with manipulator arms. I didn’t see any innovative platforms such as snakes, legs (such as RHex), or even the wheel/leg combinations you see from Case Western. Most of the platforms were large enough to be mistaken for bomb squad or law enforcement robots.

Another common touch was the addition of a camera on a mount behind the manipulator arm (if there is one). This is to give the operator exproprioceptive information and compensate for the lack of sensing in robotics. Rescue robots always have a camera- that provides exteroceptive sensing- sensing of the world around the robot. Usually they have proprioceptive sensing- sensing of the robot’s internal position- but not always, the lack of proprioception on the mine crawler at the Crandal Canyon Utah mine disaster was a big problem. Many of the Operator Control Units had icons representing the relative position of the flippers, taking advantage of the proprioception. But there’s a third category of sensing- exproprioception: where is the body relative to the world? Am I stuck? About to fall over? Is my arm under a rock? Exproprioception is clearly important. And extremely difficult to do without a “skin” and good spatial reasoning.

So the teams are trying to get exproprioception through exteroception. That’s common in bomb squads and I’ve heard it referred to as the “we’ll just stick another camera on it” non-solution. That leads to challenges in the operator’s attention and situation awareness- which camera to look at, when? Also note that the higher the camera, the better the view. But the higher the camera, the less likely it can be used for a real response where the voids are less than 1m high and anything that sticks up or out snags. It’s a tough problem and hopefully one of these groups will find a more optimal solution.

Sadly, I saw perhaps 2 women total on the teams. We had hoped that the societal relevance of rescue robotics would help attract women to computer science and engineering but there was no evidence here. Hopefully, the lack of women is a fluke.

Collaboration at a Distance! TU Delft

What a great phrase from the researchers at TU Delft that captures a major aspect of emergency informatics: collaboration at a distance! Given that robots and embedded sensors provide a remote presence into places that people can’t get to (or get to quickly enough), the question is how to use it? Which leads to collaboration at a distance!

As we noted in a recent article (see “From Remote Tool to Shared Roles,” in IEEE Robotics and Automation Magazine, special issue on New Vistas and Challenges for Teleoperation, 15:4, Dec.08, pp. 39-49), the real human-robot ratio isn’t having 1 person controlling a 1,000 robots but rather having a 1,000 people be able to use the data from a robot, without necessarily knowing that it’s from a robot. And certainly those 1,000 people won’t all know each other and may be working independently (and at cross-purposes), which David Woods at Ohio State calls polycentric control. Plus in order to use the data, we expect some ad-hoc teams to form and that they will use the visual data as a common ground (as per Jenny Burke’s PhD).

I was at the Technical University of Delft (TU Delft) on Wednesday to attend Maarten van Zomeran’s MS defense, as I had been invited to serve on his committee. Maarten did a great job with the Rubbleviewer and his MS was well attended- I am very proud. His thesis was chock full of interesting information beyond the Rubbleviewer, including a comparison of US FEMA search methods and information representation with United Nations INSARAG. Maarten has participated in two full scale exercises, one with the Czech team and one with the Netherland team in an exercise in Dubai- plus with the responders at Disaster City. An amazing grounding for his work in better representations and visualization!

It also gave me an opportunity to meet in person the research team there- they don’t focus on emergency response but that’s becoming an area of interest. A lot of great work in artificial intelligence, HCI, and especially software agents. Prof. Dr. Catholijn Jonker, head of Man Machine Interaction dept (and another right thinking woman!) proposed a way forward for continued work on the Rubbleviewer and collaboration in general. TJ de Greef was a great host (few things are better than great conversations over Dutch white beer in an outdoor plaza!) and I admire his industrial research expertise and research savvy. What a great group of people! Check out http://mmi.tudelft.nl/index.php

I sat in on a undergraduate student capstone project presentation and was impressed not only by the topic and competence, but also that it was delivered in perfect English.

All that remains… return to Cologne

cologne site jun 09

I’m on travel this week in Europe. My first start was Cologne to meet with the gang from the Franhofer Institute and to present plaques to them and the Cologne Fire Department, thanking them for allowing us to participate in the State Archive Building Collapse. Hartmut, Sebastian, and Thorsten came down from Bonn for dinner and a walk by the collapse site, now leveled, waiting the conclusion of lawsuits, new officials, etc. It is hard to believe that it has only been 3 months. Not only has it only been 3 months, but the city had erected a temporary roof (like those used at stadiums) and removed it.

BTW, I was told the oldest, most valuable manuscripts were among the 20% forever lost.

awards

Prof. Thomas Christaller was receiving a prestigious medal, so the timing was bad, but Harmut arranged a “mini-symposia” at the Franhofer Institute with Capt. Rorhle and me giving talks. All of Capt. Rorhle’s slides were in English, so despite him talking in German, it was totally fascinating. Perhaps the most fascinating was to see the timeline of events, from getting a call 2 minutes before the collapse throughout the first hours. The flow of information (and mis-information) is apparently the same there as it is in the US– which really emphasizes the need for emergency informatics.

Prof. Stefan Wrobel attended and my hats off to him and Thomas for an amazing place! It’s a lovely combination of old (a castle) and new (the buildings and especially the robotics high bay lab) with an artistic and eco sensibility (“green” roofs).

So looking at the cleared site, similar to the WTC site, it is hard to tell that two people lost their lives there, that a physical connection to the past was lost as well. But given that Cologne appears in some ways defines itself by the bombings from WWII, I suspect every resident can feel the tortured earth and have added it to their long memories.

Summer Institutes and being an Alpha Geek

Summer Institute-1

While it’s been longer than I realized since my last post. Part of the delay was the usual end of the semester scrambling, but also much more exciting event our first mini Summer Institute On emergency informatics at Disaster City. A Summer Institute as created by David Woods at Ohio State is and amazing innovation workshop, where the various stakeholders in a system — in this case academics responders, agencies, and industry, give together to learn each other’s language, conduct hands-on missions, and participate in envisioning exercises. We had 35 participants from TEES, TEEX, and our academic and industry partners. Faculty from 5 engineering departments (CE, CSE, ECE, ME, and ENTC) plus Architecture participated along with Carnegie Mellon, Ohio State, and TAMU Corpus Christi. TCAT led the industry affiliates program discussion- attended by 4 industries (Lockheed Martin, AirRobot, SA Technologies, and Velodyne), and the US Army Research Lab. One major outcome was a model of information flow and structural inspection tasks– none of this had any idea how much rescue, recovery and reentry hinges on the structural specialist, building inspectors, insurance adjusters, and contractors. Look for a publication with the model soon!

But the other big news is that Damon Tabor at WIRED did a short piece on us under the Alpha Geek heading. Click here to see. Nice job- he spent over a year on it, we had wanted him to embed with us but couldn’t work it out.