Slashdot Mirror
A Programming Language For Self-Organizing Swarms of Drones
New submitter jumpjoe writes: Drones are becoming a staple of everyday news. Drone swarms are the natural extension of the drone concept for applications such as search and rescue, mapping, and agricultural and industrial monitoring. A new programming language, compiler, and virtual machine were recently introduced to specify the behaviour of an entire swarm with a single program. This programming language, called Buzz, allows for self-organizing behaviour to accomplish complex tasks with simple program. Details on the language and examples are available here. Full disclosure: I am one of the authors of the paper.
I'm the lead researcher in this project. Thanks for your questions! I'll try to address all of them.
Q. Why an external language?
A. Robot swarms are a special kind of system. It's not just a collection of computers (like a network would be), but a collections of autonomous devices that occupy space and form networks with very volatile topology. Sure one could use C/C++/Java/Python to program them, but it gets fast very complex, due to the large number of interactions among robots. We believe that it's much better to have a language that natively provides you with the right kind of abstraction, and hides whatever is not necessary for swarm-level coordination.
Q. It looks like C.
A. It's directly inspired by JavaScript and Lua, which in turn look like C. We wanted this, so people can get productive faster and don't need to learn a whole new syntax from scratch. The entire point of our effort is to make something people would want to use.
Q. Why not flex/bison/LL parser ecc.
A. No specific reason. These are just development tools - we could have used Lemon, we found it easier and more fun to make our own thing. The fact that the VM is custom is a necessary feature - it weighs only 12KB, and this means that we can put it on very resource-limited robots.
Q. There's no BNF available.
A. I'll publish it, it's just not on the website yet. We just went public, there's lots of work to still. Good suggestion!
Q. Semantics are vague.
A. That means the paper was not written clearly enough. If you have more precise feedback on this, I'd be happy to hear you.
Q. Unknown symbols are cumbersome and potentially confusing.
A. I see your point, and I agree. I am currently working on a way to make the debugger aware of this issue, because I think that having robot-specific symbols is an interesting idea. You raise a good point, though.
Once more, thanks for your feedback!
I'm the lead researcher on this project. Thanks for your question!
We gave your concern quite a bit of thought.
In brief, we found no language with the features we wanted that would fit <16KB or <32KB. We wanted a dynamic language with closures, with a VM powerful enough to work in a networked environment with highly volatile topology, and that would be easy to modify to accomodate features such as swarm management and virtual stigmergy. We considered Python and Lua at first, but Python is just too complex to fit the requirements (I studied TinyPy for a week, and it's too limited) and Lua VM makes it hard to fit networking the way we wanted it.
In the end, we thought that a dedicated language with the right features might be a good choice. After all, Python does nothing C++ doesn't do - but the level of abstraction that Python offers makes developers way more productive. With Buzz, we hope to offer a tool that makes people more productive when the problem is coordinating hundreds of robots. There's obviously lots of work to do towards this goal, and the current implementation of Buzz is just a step in that direction.