Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Robotic Airplane Flies In Tight Spaces (mashable.com)
83 points by gagan2020 on Aug 13, 2012 | hide | past | favorite | 22 comments


What's cool here other than the fact that it seems to react really quickly is that it has no universal conception of location, like GPS.

My limited understanding of the topic is thus:

For localizing, they use a particle filter, which is basically a method that helps you figure out latent variables (in this case location) based on multiple observations.

Using the data, it creates a model of how the aircraft moves. In each "tick", you make a prediction about where the aircraft will be in the future (let's say, based on how fast you know the motor goes and which way the rudders are tilted etc). Then, you actually compare it to the data you got from your sensors (in this case a laser rangefinder) and update your model. Thus, your model is better.

The more traditional formulation of this is the Kalman Filter, which is everywhere in classical controls systems. I think the particle filter is just simpler for large numbers of variables whereas for Kalman filters, complexity increases exponentially.

edit:

Another way to look at it is that this is how robots deal with the "real world" where sensors are noisy and slightly off, actuators are unreliable and can't produce smooth and constant output etc. Instead of trying to guess all these factors, it automagically accounts for these on the fly by looking at how the robot behaves and how you expected it to behave.

edit2:

Corrections abound! Read replies below!


The difference is not really about the number of variables but the dynamics of the plant...

The classical formulation of Kalman filters assumes gaussian distributions for the variables. This makes the computations much faster since the posterior distributions is a few matrix operations away. This works fine when the model for the plant is linear (since a linear transformation of a gaussian variable is gaussian). In situations where the plant model is not linear estimates can go awry quickly.

In the case of particle filters you sample the prior distribution, simulate the non-linear plant with these initial conditions and then construct the posterior distribution by incorporating the measurements. This process is computationally more expensive than classical Kalman filtering but is more accurate for non-linear plants.


Obligatory link to "Probabilistic Robotics" -- generally considered the #1 reference on the subject, written by top roboticists (Thrun, Burgard, and Fox): http://www.amazon.com/Probabilistic-Robotics-Intelligent-Aut...


  What's cool here other than the fact that it seems to react really quickly is that it has no universal conception of location, like GPS.
Nit-picky robotics engineer chiming in: it's not reactive. The planning is done ahead of time, and they expect there to be no dynamic obstacles in the environment.


D'oh! That's not what I meant to imply. Should have made that clearer.


The udacity class does an awesome job of teaching kalman filters, particle filters etc.

http://www.udacity.com/view#Course/cs373/CourseRev/apr2012/U...

In the course you go step by step implementing these things in python. The course far exceeded my expectaion from an online course.


This is fricking genius! Thanks for the link!


If I remember correctly, a big advantage of particle filters over Kalman filters is that the particle filters can model complex, multi-modal distributions, whereas the Kalman filter just updates the mean and covariance of a single high-dimensional Gaussian (albeit optimally). This is nice for localization problems because it allows you to keep track of multiple competing hypotheses about your current location.



Thank you, this is much better.


Original story from MIT News Office w/ video: http://web.mit.edu/newsoffice/2012/autonomous-robotic-plane-...


This is a much better link and admin should change the story link to this one.


The big "what stopping this from being mainstream" part of this is the need for a prior map. It's absolutely analogous to Google's autonomous vehicles needing to be manually driven through the area in which they're planning to later operate autonomously.

This is great work, but it's not onboard SLAM, only onboard localisation. All up, it's great to see more of the autonomous ground vehicle work becoming small and lightweight enough to go on aerial vehicles. Traditionally the low payload capacity has been a showstopper for UAVs, and laser range finders are often heavy, hence why so many UAVs have used vision-only localisation techniques.


For us civilians, slam is Simultaneous Localization and Mapping, which is the equivalent of walking around and exploring an unknown area and committing it to memory (mapping) while also still maintaining your own bearings in there (localization).


Some relevant videos on autonomous catastrophic flight recovery by Rockwell Collins:

Continuous AI flight after blowing off one wing:

http://www.youtube.com/watch?v=xN9f9ycWkOY

Continuous AI flight after catastrophic wing loss (showing manual/AI difference):

http://www.youtube.com/watch?v=dGiPNV1TR5k



I am always so happy to see a navigational demonstration that doesn't rely on external positioning, e.g. GPS. Having tried both sides (dead reckoning/sensing and external positioning), I have come to feel like so many GPS-based projects are essentially trivial GPS demos.


What happens when it hits a dead end? At least a helicopter can stop and return on exactly the track it came in on.

Presumably one of the reasons for the prebuilt map is so that it doesn't enter a dead end, which some parking garages have.


On a sidenote I'd like to add that rc flying is a ton of fun. Especially if you couple it with FPV (first person view) cams, goggles etc...


That plane thinks it's Han Solo! (Never tell me the odds!)


Cool, but I'd trim "genius" from the title.


If we can put a rover the size of a VW beetle on Mars, we can definitely put a couple of these on it too.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: