Neubertify

Podcasts

Until three months agothis was all I knew about podcasts:

When I needed to ask one of my coworkers a question and their reaction was to pull out their headphones and then looked for the pause button on their headphone cord, they were listening to music. When they were searching for the pause button first and then pulled their headphones out, they were listening to a podcast. 

In the fall of 2012 (seven years after Apple added native support for podcasts to iTunes and eight years after they thought they had a trademark on “pod”) everything changed. “This American Life” was the gateway prog that kept my brain busy during hours of circuit board assembly. This American Life’s branded Android app works about as well as discussing weight loss with our cat, which lead to the historic event in November 2012: I installed a podcast manager.

Here’s the subscription list I have assembled so far.

This American Life

According to their own stats, 750,000 people listen to the podcast of this show alone (i.e. not including the radio listeners across pretty much every NPR station in the US and CBC in Canada). Listen to the program for five minutes and it’s immediately clear that this is a high quality no-nonsense radio production. There are now awkward pauses, nobody ever misspeaks and nobody ever sounds nervous on This American Life. The soundscaping is present but blends in perfectly. Nothing distracts from the speech. Even material recorded when cold calling sources is edited to make every person sound like they are coming right from their public speaking coach.

You’ll notice this as a common theme, so I’ll insert it as an interjection here: I find the production quality of a podcast more important than the content. Your program could contain tomorrow’s best performing stock, if  your levels weren’t normalized and your speech wasn’t steady, I wouldn’t subscribe. 

This American Life’s content is mostly in the investigative journalism category. The stories are always non-fiction except when Mr Daisy gets to make the program). Some stories are non-stories (like last weeks story on how hog rectums might or might not be used as fake Calamaries). 

Snap Judgement

I don’t know about this one. The shows’ producer won a radio talent contest with the concept of producing a story telling show. I didn’t know this, but story telling appears to be a performance art like stand up. I guess the comedian whose show I went to in London many years ago and consisted of him talking about how his Dad just died was actually a story teller. 

Snap Judgement’s tag line is “story telling with a beat” and the beat is something that takes some getting used to. There is music mixed into the stories, music between the stories, and none of it quite blends in. And then there are the jokes (?) that make up the credits at the end of the show. I rarely get those. This show makes me feel like a stranger (which I technically am). I subscribe to it for the selection of stories ranging from eye opening to moving.

Fun fact: Snap Judgement’s website’s FAQ contain info on how to get started producing a story that they would air.

From Scratch

From Scratch, unlike TAL and Snap Judgement, is not nationally syndicated. It does, however, run on NPR Berlin of whose existence I had no idea of until half a minute ago. Anyone reading this who listens to NPR in Berlin? 

From Scratch is a series of interviews with people who started something, usually one or more businesses and sometimes a non-profit. This week’s guest was the initiator of the Highline Park in NYC. Today I listened to the interview with the founder of Tumblr (guess when I decided to write this post). Many guests are from the New York area which gives the program a local touch.

Initially the interviews felt very scripted with the presenter (Jessica G. Harris) sounding undynamic. After listening to tens of episodes I’ve come to appreciate that though because it shifts the focus to the guest. The inquisitive questions about the guests’ families and personal relationships sometimes make me feel like I am listening to something that’s none of my business, I genuinely hope they go over those before the recording.

This Developer’s Life

I’m pretty sure I know how these two gentlemen came up with the title of their podcast… As far as I can tell this is a private production and they are doing a pretty good job at imitating their namesake. In addition to very clean production, they have access to a surprisingly large number of people and stories. I particularly enjoyed listening to the story with and about Bill Hill, the co-inventor of ClearType.

Something I am grateful for is that they chose “developer” over the totally abused “engineer”. What they mean is “person involved in the creation of software”.

The Amp Hour

This is the odd one out. I’m pretty sure they record the show by recording a Skype conversation and then posting it unedited. They go off on tangents from which they only recover after 10 minutes. And Dave says “oh boy” at least 10 times each episode. I think I am not insulting anyone when I write that Dave and Chris don’t know much about producing radio, but they definitely know their s*** about electrical engineering. Dave deserves a medal or knighthood or something for his instructional videos on the EEVBlog and Chris probably the same for his videos which I should start watching one of these days.

Half of the shows consist entirely of completely unorganized chatting between Dave and Chris about industry news. For reasons beyond my comprehension they devote 10 minutes of each show to repeating the evers-same discussion about Kickstarter.com. 

The other half of the shows involve a guests. This is where the style of the program comes to fruition. Most guests quickly realize that nothing has been prepared and relax into storytelling mode. I learned all I know about manufacturing in China from Scott Miller, and got a basic understanding of how those black boxes I solder to circuit boards come to life thanks to the CEO of Touchstone Semiconductor.

Others

I can also recommend NPR’s Planet Money, made by the same people as This American Life, talking about fun things like starting their own shell company in Belize. The Robots Podcast is a good source of information on robotics but takes some energy to listen to. Currently in my playlist and waiting to be heard is The Moth, which I hear is another famous storytelling podcast similar to Snap Judgement.

What am I missing?

Do you know of other podcasts I should try out? Drop me a comment below, or send me a tweet @jonemo, or email me at [my-two-letter-initials]@jonasneubert.com.

Manufacturers are also just Middle Men

Any market where unnecessary middlemen stand between customers and their successful use of a solution is about to be disrupted.

This quote is from an article by Box.net founder Aaron Levi on FastCompany.com. It got me thinking about how bad life must be as a Middle Man.

In the article, Levi mentions Amazon and Ebay as examples for simplicity through disintermediation. Both companies drastically improved processes by removing intermediate parties, aka “Middle Men”. Ebay did it with private sales, and Amazon did it with book sales, then sales of everything, then server commissioning, then book authorship, and so on. Today the trend to kill middle men keeps most of the world’s tech startups busy: Uber, Exec, Spotify, 23andMe, etc—everybody is trying to kill some sort of middle man. Who are these unfortunate people in the middle?

Today’s endangered middle men live at the top of the supply chain. They are retailers, distributors, medical professionals, taxi dispatchers. In the supply chain, they are between the producers and the consumers. They have in common that some or all aspects of how they add value is in the process of being replaced by a cheaper and/or better technology that enables self-service.

What’s quite interesting is that a new batch of middle men is already getting in line for disintermediation. They are the manufacturers. You read that right: Manufacturers are also just Middle Men. In the supply chain, they currently live between the designer and the soon-to-be-gone distributors and retailers mentioned above.

Manufacturing is often regarded as solid future-proof business because its value-added is physical. Middle man assassins today stop at manufacturing because making stuff is hard. Enter 3D printing (which really just is a catch-all term for a group of novel manufacturing methods). Suddenly the assumption that manufacturing is hard is as outdated as the assumption that you can earn money by stocking dead trees on shelves.

The time when you can have an affordable machine in your home that can fabricate many of the objects we are used to buying from a store will be here sooner than you think. Five years in, it will increasingly seem ridiculous to have finished objects transported from a far-away production facility to your house. Who needs free UPS Second Day shipping with Amazon Prime when you can buy a blueprint from the designer and have it fabricated in your home within an hour or two? There will be a new group of startups ready to remove the manufacturing middle men and to cash in on this change. 

To pacify the skeptics I should mention that the change I am describing will be gradual and incomplete, just like the current wave of middle men assassinations.  Some things will never be fabricated at home (Higgs Bosons, dark matter, etc). Many items will remain more economical to produce in factories for a long time. And there will always be people who prefer doing things the old fashioned way (your parents, progress deniers, the Amish). None of that invalidates my main point though: Manufacturers are middle men.

One more thing: Remember how I wrote that manufacturers are middle men between designers and consumers? There is no reason to assume that designers aren’t next in line to play the role of the unloved middle man. Once manufacturing has been disintermediated, designers are just the middle men between ideas and and consumers. First attempts at design automation are old news even today…

Why I stopped using Gmail

I am a fan of Google products. When Google Voice first came out I went around begging people to invite me and have been using it ever since as my primary number. I can’t even remember how I read RSS feeds before there was Google Reader. And Gmail! I was a little hesitant when it was first released but for the past years Gmail was the first browser tab I opened in the morning and the last one I closed at night. The list goes on. According to my Google Accounts page I use 30 different Google services.

Things were good. Google made more and more great products. Whenever one came along that I found useful, I started using it. Payment was easy: I gave them my data, they used my data to show me relevant ads. Sometimes I clicked the ads and bought something. I was happy. I thought Google was happy. I was wrong.

Google does not want me to love their products. Google wants me to love Google. All of it. As Larry Page himself points out: “This is the path we’re headed down – a single unified, ‘beautiful’ product across everything.” (Source: Pando Daily)

Examples of  “unified, beautiful”  have been cropping up everywhere on Google for months now:

1. The grey bar on top of Gmail has been there in one form or another for a long time. It’s a time sink. I am distracted easily. A constant reminder that Google Reader exists and that somebody whose name I remember added me to a circle is the last thing I need—even if the reminder is beautiful and unifying.
2. During my occasional visits to Google+, an artificial intelligence suggests I should invite my boss and other professors I work with to Google+. Nobody told the artificial intelligence that it’s above my pay grade to invite professors to social networks. And anyway: What does the frequency of emails I sent people through Gmail have to do with Google+? Nothing. Beautiful and unified. But mostly annoying.
3. For years you could sign up for Google Analytics with any email address. A while ago, you had to merge that separate login into your Google Account. Your client’s websites that you track in Analytics have nothing to do with the cat videos you share on Google+? Too bad, now the cat videos and your clients are beautiful and unified. 
4. When I google my name, as suggested by Google, the first “search result” informs me that my Google+ profile is 30% complete. Beautiful and unified. And irrelevant. 
5. There was a time when you could sign up for Google products, and sign off from Google products. Today, you are merely informed when you automatically become user of new Google product like Google+. Compare how many Google products you use today, to the number of Google products you can individually remove from your Google account.

This should give you a taste of things to come. I haven’t even mentioned the filter bubble created by “Search, Plus Your World” or the beautiful unified privacy policy yet.

There was a time when users had needs, and chose tools to satisfy those needs. Need to hang a picture? Select a hammer. Need to make pancakes? Select a pan. Need ubiquitous access to your email? Select a webmail provider. Everyone had their own set of tools. Every lumberjacks has their own preference of chainsaw. Every code monkey has their own preference of text editor. Some like Stihl, some like Husqvarna. Some like Vim, some like Emacs. On the internet, these times are over.

We aren’t selecting individual tools any more. We choose from a small selection of beautiful unified tool boxes. If you want Gmail, get the Google tool box including a Google+ profile you never asked for and personalized search results that shape your picture of the world. Some fear that this will lead to incompatible online service ecosystems: Separate world wide webs owned by big companies. I fear more practical issues:

1. Google locks people out of their accounts. All the time. I recently lost my Google Adsense account for no clear reason and without a chance for appeal. With a unified Google both your chances of unintentionally triggering an account lockdown increase and the damage caused increases.
2. Unexpected interactions between tools you never use and your uninformed actions will result in your data being exposed like it happened with Google Buzz. If you care about your privacy, you will have to understand the entire Google ecosystem to protect it, not just the Google products you use.
3. It will be even harder to focus. Google Talk and Google+ and the Google Toolbar are already there today to distract you in Gmail. This will get worse.

I want to continue using the Google tools I love without the risk of losing my online identity by doing something I didn’t know was prohibited (I am still not sure why that Google Adsense account is gone), without the work involved in understanding the entire Google ecosystem to manage my privacy, and without constant distraction by the latest gadgets Google came up with. Dropping Gmail is how I achieve this. 

Why Gmail? Of all Google services, Gmail holds the most information about about me, and also the most private information. My mother’s maiden name, my SSN and what medication I took for an inflammation three years ago, it’s all somewhere in my Gmail. By taking that data out of the beautiful unified Google ecosystem, I dramatically decrease the risk of privacy debacles. Gmail is also the Google service I interact with most. By leaving it, I achieve the biggest reduction in beautifully unified distraction. Not using Gmail should also reduce the chances of losing access to the tools I rely on—doing less things inside the ecosystem seems like a good strategy for doing less things that can cost me my key to the ecosystem. And finally: As opposed to other Google products, there are good alternatives to Gmail. 

Farewell Gmail. And kudos for your IMAP access, the “archive” concept, threaded conversations, and generally how you disrupted the freemail market!

Klout Scoring Algorithm Revealed

Imagine walking down the street absent-mindedly, and suddenly someone walks up to you and starts scoring your gait. They don’t just do it with you, they score everybody’s walking.

Initially you don’t care but a few days later you notice how people start experimenting with different gaits. “That surely must be a short-lived fashion thing!”, you think.

Secretly you also try to set your steps in a slightly different manner. And then your daily score goes up a little. Was that because of the way you bent your big toe just a tiny little bit that day? Or was it the little change in the angle you set right foot that did the trick? Before long, you find yourself trying to do bigger steps with a little more springiness in your ankle. And that’s before you find out that the highest scoring walkers get free perks!

Of course, this post isn’t about walking around. It’s about a not-quite-so-new-anymore website named after the formerly underused term “clout”.  Klout is one of those companies where you, the user, aren’t the customer but the product. Klout scores your daily communication. FastCompany ran an insightful article about Klout’s business model in their July/August 2011 issue (read a shortened online version here).

In short: Klout turns communicating with other people through social media sites like Twitter and Facebook into a game. The first prize in each category is the grand chance to help a big company (Klout’s customer) with their marketing for free. Of course, winning is easy because there are infinitely many categories!  

By the way: If you don’t like playing games, that’s too bad. Klout is a game where everyone has to play (nobody is forced to win, yet). If you want to communicate through Twitter, you have to play Klout. If you want to walk through the park, you have to let other people score your walking. I’m sure you get the idea.

I almost forgot, the title of this blog post is “Klout Scoring Algorithm Revealed”. That’s right, I figured out the Klout scoring algorithm. It happened by accident. Here’s how.

I’ve secretly been trying to increase my Klout score. Trying to tweet more outrageous false news to get more retweets one week, trying to @-reply a lot some other week. Tweeting (and reading tweets) usually happens during small breaks throughout my workday (and worknight).

On October 16 this stopped. That day I went from normal work days into two weeks of unnormal work days. A few unfriendly entries in my calender prompted me to increase my productivity to a level that cannot be sustained long and required a full day of distractions on October 28. Here is my Klout chart for this time period:

Do you see it? It’s clear as day! Klout never looks at your Twitter and Facebook profiles - ever! Your Klout score is simply the inverse of your productivity! 

The secret is out: Klout claims to rank the reach and impact of your communication, when in truth their secret scoring algorithm simply measures how much work people get done! 

The motivation to write this post comes out of a Twitter conversation with @natedogreimer and @LittleAnimation who also produced this comic on the same topic.

WebOS developer relations writes you a recommendation to move to Windows Phone 7

HP announced it will no longer produce webOS devices. That’s old news and it sucks because webOS is the only mobile platform I know how to develop apps for. I’ve got better things to do than write about that though, instead I have a fun side story that developed around the whole webOS hubub. 

Brandon Watson, who has a job title including “senior” and “director” at Microsoft and is basically a developer evangelist for Windows Phone 7 tweeted today:

That’s yet another clever marketing move by Brandon after betting $1,000 that the Dilbert creator will like Windows Phone 7 and offering free devices to various hackers including the guys who first jail broke Windows Phone 7 (read more about it at WinRumors). 

While Brandon’s move isn’t a big surprise, this entry in the HP webOS developer forums sure is one:

You’ll be forgiving to think this is some sort of prank. But “webOSdev” is in fact the account of Chuq van Rospach, the developer community manager answering developer questions in the HP webOS forums. 

anyone who wants to take Microsoft up on their offer, I’ll write you a letter of recommendation to help you qualify. 

(I’m not joking. I get that developers have to pay the rent.)

In summary: The developer relations guy for webOS is offering webOS developers help in transferring over to Windows Phone 7. You make up your mind if that is a good sign for the webOS platform or not.

How to enable developer mode on a HP TouchPad

This might be a no-brainer for developers who developed for webOS phones in the past. But if you are getting started programming for webOS with a HP Touchpad and the (relatively) new Enyo framework like I am doing right now, you’ll have a hard time figuring out how to test your app on the actual device.

Step 1: Put your device in developer mode

In “Just Type” enter webos20090606. If you happen to have a lot of time on your hands you can also enter upupdowndownleftrightleftrightbastart (the Konami Code). Both secret phrases will result in a otherwise hidden button appearing:

Press the button, switch the “Developer Mode” switch on, and follow the straightforward onscreen instructions. Your life will be a lot easier if you leave the password empty, but that also means that anyone who gets your Touchpad and connects it to a computer, has Novaterm and knows what he or she is doing can get root access to your Touchpad. You decide.

When you’re done you should see this screen:

Step 2: Restart

I am not sure this step is really needed but on the internets I read reports of things not working if you skip this step. To restart your Touchpad, press and hold the main button and then press and hold the on/off button. Keep holding them until the flashing HP logo appears. 

Step 2: Connect Touchpad to computer

Plug the USB cable into the Touchpad and into the computer where you are developing the app. On the Touchpad you’ll see a notification popup offering you to connect the Touchpad as a USB drive. Don’t do it. 

Step 3: Load your app onto the Touchpad

The assumption here is, that you have the Enyo SDK installed on your computer (if you used the emulator to test your app, you have the SDK). Open your command line (or terminal if on a Mac) and use the following command:

palm-package [directory where your app sourcecode is goes here]

This packages your app into an ipk archive named after the app name you gave the app in appinfo.json.

palm-install -d usb [filename of your compiled app archive goes here]

The app will apear under “Downloads” in the Launcher. Done.

Appendix 1: Dear Microsoft

Notice how this howto did not include a two week process of getting approved by one of your shitty partner companies and how it did not cost me 75 Euros to gain the right to test three apps on my device for one year.

Appendix 2: Dear Apple

Notice how this howto did not require going to the store to buy a Mac. Also note, that no NSA style encryption and security certificates were involved.

Appendix 3: Dear Blackberry

Notice how it was possible to test the app on the actual device.

My ICRA2011 notes - compiled in absentia

ICRA stands for International Conference on Robotics and Automation. It’s one of the three big worldwide robotics conferences every year (next to IROS and RSS). What’s “big” for robotics conferences? Big for robotics conferences is just over 200 technical session with up to 6 talks each, plus a few video and poster sessions, plus a bunch of keynotes, plenaries and a trade exhibition. Obviously, not everything is relevant or interesting to everyone. Here are my personal notes from this year’s ICRA.

Just to be clear from the beginning: I didn’t go to ICRA this year. But it’s 2011 and there is magical stuff like the internet and online conference programs. Much less magical is the fact that I spent last Saturday digging through just under 1000 abstracts in an attempt to find potentially interesting papers. 

Things that fly

Free Flight Simulations and Pitch and Roll Control Experiments of a Sub-Gram Flapping-Flight Micro Aerial Vehicle

Lindsey Hines and colleagues from the Nanolab at the CMU Robotics Institute describe how to control the flight of a sub-gram (!) flapping wing machine. Like other flapping wing flying machines the wings are passively rotating which results in aerodynamics whose analysis is somewhere between difficult and impossible (to my knowledge). I think the machine in the paper is the same as the one shown on their website. The abstract says it doesn’t fly (yet), but the research is primarily concerned with inducing the torques necessary to steer during flight.

Levitation Control of Experimental Wing-in-Ground Effect Vehicle along Z Axis and about Roll and Pitch Axes

Already widely reported in popular news is the aero-train described in a paper by Yusuke Sugahara and colleagues from various Japanese universities. AeroTrain is basically a train shaped vehicle that hovers a little above ground, a concept known as Ground Effect Vehicle. My first thought was: “Why is this in a robotics conference?” Answer: Because the paper deals with the control of the vehicle during flight. And that is aerial robotics. See a video of the (not quite train sized) prototype:

The Flying Machine Arena as of 2010

This is a video submission (i.e. instead of a presenter talking for 15 minutes, a video is shown) and my guess is that the video shown at the conference is equal or similar to this Youtube video:

The Flying Machine Arena looks like it used to be a normal atrium at ETH Zurich. Outfitted with safety nets and gymnastics mats by Professor D’Andrea and his team it’s now a test arena for, you guessed it, flying machines. I have no doubt that this “arena” makes for a far better test environment for flying robots, than the Duffield Atrium where Cornell engineers let their flying contraptions rise all the way up to the roof where they (supposedly) trigger the fire alarm. Previous output of Flying Machine Arena includes robots juggling, playing piano and dancing. 

A Flying Inverted Pendulum

A quadrotor balancing an inverted pendulum is the latest output of the Flying Machine Arena. If you fancy a challenge, you can download the math behind this demo from the author’s website. Or just watch the video:

Modular Robots at ICRA2011

Control of Multiple Heterogeneous Magnetic Micro-Robots on Non-Specialized Surfaces

This paper by Eric Diller et al. from the CMU RI Nanolab (previously mentioned above) describe new work on Mag-µBots, a flock of non-identical millimeter-sized robots that can be controlled in 2D through applying magnetic fields. The same authors (in different order) have another paper about the same robots in the conference. There’s also a project site and a Youtube video:

Simulating Multi-Million-Robot Ensembles

Dynamic Physical Rendering is a project at Intel Research Pittsburgh. One Intel researcher and two CMU students wrote this paper about a physics based simulator for millions of robotic modules. The abstract says: “Our approach is shown to run 108x faster than a previous scalable simulator.” The software is a fork of an (unspecified) existing physics engine and simulates distributed software running on and interactions between up to 20 million modules. That’s pretty impressive, now we just need to build a modular robotic system with such a number of modules :-)

A New Self-Reconfigurable Modular Robotic System UBot: Multi-Mode Locomotion and Self-Reconfiguration

Researchers from the Harbin Institute of Technology (that’s in China if you were also wondering) present a new self-reconfigurable robotic system named UBot. The modules are cube shaped with two rotational degrees of freedom and four connecting surfaces each. Since the abstract mentions that quadruped, chain and loop configurations are possible, it’s safe to assume that this is a chain type modular robot (not a space filling lattice type). All in all this sounds very similar to other chain type robots such as MTRAN, Polybot. Some pieces of information such as the size of modules and electronics implementation details are not mentioned in the abstract and I’ll have to wait for the full paper to appear in IEEExplore (which—for unknown reasons—usually takes several months).

Cross-Ball: A New Morphogenetic Self-Reconfigurable Modular Robot

Yet another new self-reconfigurable modular robot platform is presented by researchers from the Stevens Institute of Technology, University of Surrey and Honda Research: Cross-Ball “provides several flexible 3D reconfiguration capabilities, such as rotating, parallel, and diagonal movements […] for modular robots using more complex self-reconfiguration algorithms”. And apparently every module is mobile on its own. Unfortunately, no pictures yet. The first author (Professor Yan Meng) also lead a workshop at ICRA under the title “Morphogenetic Robotics: A New Emerging Field of Self-Organizing Robotic Systems”.

Load Balancing for Multi-Robot Construction

More on the theoretical side of things in modular robotics is work by Nils Napp and adviser Eric Klavins whose more recent work has been related to the Factory Floor concept. Think of it as a construction site where a bunch of workers cooperate to build a structure under uncertain material supply and without central control. Their ICRA paper presents a load balancing algorithm for proper load distribution in assembly of modular structures.

Making Self-Disassembling Objects with Multiple Components in Robot Pebbles System

Kyle Gilpin and his adviser Daniela Rus have been working on the concept of robot dis-assembly for a while, initially with their Miche modular robots and lately with the much smaller scale Pebbles. The novelty in this paper is a (distributed?) algorithm that allows multiple objects to be made from one initial block of pebbles through disassembly.

Robots that are going to replace you

DustCart, an Autonomous Robot for Door-To-Door Garbage Collection: From DustBot Project to the Experimentation in the Small Town of Peccioli

Researchers from Pisa are about to revolutionize the garbage collection industry with their robot DustCart. At least for a small Italian village. Think you’ve seen this before? Indeed, this went through the blogs in 2009.

Donut As I Do: Learning from Failed Demonstrations

There’s been lots of work on teaching robots by demonstration. That’s nice, assuming you can do what you want the robot to do. But what if you want the robot to do something, you can’t do? Like flipping pancakes? This issue is addressed in this paper by researchers from the Learning Algorithms and Systems Lab at EPFL. They also have a video on their website.

An Autonomous Ice-Cream Serving Robot

For this video submission, a KUKA robot was used to serve ice cream. Maybe we can get one of these for when the Cornell Dairy Bar re-opens? Two interesting aspects of this implementation is how the fragile ice cream cone is gripped and the use of a time-of-flight camera.

Grasping with Application to an Autonomous Checkout Robot

This paper by researchers in Oussama Khatib’s Lab in Stanford presents a robot that does the job of a checkout assistant. Just like its human counterpart this robot can work with cluttered arrangements of products and previously unseen products. Unlike its human counterpart the robot uses a 3D sensor. Also unlike its human counterpart, the robot costs 400k but once that’s paid it doesn’t ask for a monthly salary. Here’s the video:

Following and Interpreting Narrated Guided Tours

If you think you are safe from being replaced by a robot, think again. A group led by Professor Seth Teller developed a robot to complete a task that many thought would remain exclusive to humans for eternity: Following guided tours. That’s right, this robot is your perfect tourist! “The tour-taking behavior is demonstrated in a multi-floor office building and evaluated by assessing the comfort of the tour guides, and by comparing the robot’s map partitions to those produced by humans.”

Everything else

1. The prize for best paper title at ICRA2011 goes to Gian Diego Tipaldi and Kai Oliver Arras from the University of Freiburg. The title: “I want my coffee hot!”
2. Again from the Harvard Microrobotics Lab comes a thin, transparent, “hyper-elastic” keypad. This is one of those papers where I really wish I could see more than the abstract right now. The keypad seems to be electrofluidic with fluidic microchannels across which resistance changes. But why is it a “keypad” and not a “keyboard” or “touchscreen”? I suspect that there is some scalability issue. If this is scalable, can I please have the walls in my appartment covered with it?
3. It’s 5.5 grams heavy, can walk (actuated by four Shape Memory Alloy coils), communicate wirelessly and has a camera - MEDIC is the work of the Biomimetic Millisystems Lab at Berkeley.
4. This robot does not actually climb walls. But the authors argue convincingly that their air hockey table setup is equivalent to a vertical wall sans gravity. What makes ParkourBot (named after the crazy sport where people run and jump and fly through cities) special is, that it climbs walls dynamically (as opposed to statically). The IEEE’s Automaton blog has the details (and the Youtube video).
5. This paper probably won’t hit the blog circuit but sounds potentially very insightful: It’s a comparison of four common methods used to model contact in multi-body simulations.
6. The Harvard Microrobotics Lab shows a centimeter-scale inchworm robot with bidirectional claws. It walks on ceilings! I can’t wait to see a video of this.
7. New results on how fish swim are presented by researchers at the AILab at the university of Zurich. In a nutshell: Fish with joints of varying stiffness swim faster than those with constant stiffness in all their joints. It’s true for real fish, now we know it works for robot fish as well.
8. A robot that can climb any tree - like a squirrel. Presented by the Advanced Robotics Lab at the Chinese University of Hongkong. And here is the Youtube video.
9. My personal award for the paper with most authors goes to a group from German DLR who present a human-inspired hand arm system. To me this looks like the best replication of the human arm to date. Want to read more? You have the choice between a technically comprehensive review on the IEEE Spectrum blog orthe usual robots-will-kill-us-all BS on Engadget. There is another paper in the Space Robotics session that seems closely related.

ICRA in other blogs

IHeartRobotics has a small collection of videos from ICRA2011 and Travis Deyle bloging at Hizook.com wrote up a list of talks he is looking forward to before ICRA even began, and the “Robot Perception and Learning lab at CSIE, NTU, Taiwan” has the full list of Best Paper nominees and winners.

Fluidinfo API: Likes & Dislikes

I spent the last two weekends¹ working with the Fluidinfo API (here is why). Using Fluidinfo is pretty easy, I found two weekends enough to discover most of what is possible with Fluidinfo.² Here’s my collection of likes and dislikes which accumulated while working with Fluidinfo. In the spirit of a true pessimist, I start with dislikes.

Dislikes

1. Among the very first things I learned while playing with Fluidinfo: You can delete your root namespace but you can’t re-create it. If you sign up with the username skillshelv.es your root namespace will be skillshelv.es (big surprise) meaning that all your tags will be in the format skillshelv.es/tagname or skillshelv.es/subnamespace/tagname. Because you have the ability to manage subnamespaces under your root namespace, Fluidinfo exposes the ability to delete namespaces. When I first tried out the Python Library, the first thing I managed to do successfully was delete my root namespace skillshelv.es. Trying to recreate it results in a permission error. That’s why all Skillshelv.es related tags now live in the alternate namespace skillshelves which I obtained after creating a second account. 
2. There is no results pagination and no way of limiting the result count. The heading of the docs chapter on query results limits sounds promising, but only talks about hard limits imposed by Fluidinfo, not limits set in the query. Try querying for the titles and author names of all O’Reilly books stored in Fluidinfo. You get 2373 book titles and their respective authors, totaling half a megabyte of data. If you only want to show the first ten, you’ll still have to query all of them.   
3. Fluidinfo (sometimes) is slooooooooow. The query mentioned above takes somewhere between 8 seconds and forever to return results. That’s a long time if you know that your user is waiting for a page to display. It’s an even longer time if you are using Google App Engine: GAE has a hard limit of 10 seconds on how long an outgoing HTTP request may wait for a response. On Skillshelv.es I work around long load times by running all Fluidinfo GET queries in Javascript. That way I can display a loading indicator while the Fluidinfo data is loading. This gives the user something to see and shifts the blame to Fluidinfo :-) More generally, though, it means that Fluidinfo shouldn’t be the datastore you query when generating pages. A potential solution might be allowing to limit the result count (see #2) which might reduce processing time on the Fluidinfo side and reduces the amount of data to be transferred.
4. Object IDs can’t be used in queries. It’s easy to get a list of all tag names that are attached to an object. It’s not so easy getting the values of all those tags. Fluidinfo only provides a clear method to retrieve exactly one tag value associated with a specific object at a time, e.g. the title of a certain O’Reilly book. If you want multiple tag values at the same time, you’ll have to use the /values API endpoint, like in this example which gives you title and price of all O’Reilly books whose title contains “PHP”. Fluidinfo gives you a pretty neat query language to define which objects are included in the response of a query to /values, but querying for an object ID isn’t part of that query language. Therefore, you can’t retrieve multiple tag values for a single object at a time, unless you already know one tag value that uniquely identifies this object. For O’Reilly books the contents of oreilly.com/id seem to be unique and Skillshelv.es uses it equivalently to a primary ID. Update: I mentioned this in the Fluidinfo IRC channel and apparently this is now a ticket and might become a feature in future.
5. While this Fluidinfo blog post suggests that Fluidinfo’s matches operator for text matching works like MySQL’s LIKE, it doesn’t actually. matches only matches full words. That’s not unsurprising but was a little disappointing when I tried building an auto-complete feature that pulls data directly from Fluidinfo.

Likes

1. First class user support! When I reported #1 of the dislikes above via Twitter, Fluidinfo’s CEO replied within a few hours acknowledging the issue. Later I figured out that most the action is going on in Fluidinfo’s IRC channel where the folks behind Fluidinfo seem to always be hanging out waiting for people to approach them with their problems. When one of my (valid) queries wouldn’t work one day, the problem was fixed in no time and on top I got a ton of useful advice. 
2. Fluidinfo Explorer. This tool didn’t seem very useful to me at first but then I discovered the context menu and the login button :-) Once you have some data in Fluidinfo and you want to quickly check or change a few entries, nothing beats this tool.
3. There are a million lots of ways to access Fluidinfo. Libraries are available for Adobe AIR, Clojure, Go, Java, Javascript, Lisp, .NET, Perl, PHP, Python, Ruby and Smalltalk. And Fluidinfo supports JSONP and CORS. It’s really nice to be able to hit the ground running in whatever language you like best. Compare this to some big companies who have tens of APIs, each with libraries available in another random selection of two or three languages.

Footnotes:

[1] Like every good grad student I did not devote the entire weekend but also did some real research work on these weekends. 

[2] I realize that I could be suffering the Dunning-Kruger Effect: I could have missed those 99% of Fluidinfo’s functionality that take three years to learn. But my lack of knowledge about Fluidinfo leads me to the erroneous conclusion that I learned the usage of Fluidinfo in two weekends. Unfortunately, I would have no way of realizing this.