Our recent overhaul of Player has given us the opportunity to do some
new and interesting things. I'd like to know: what do you want?
All ideas welcome, but I'm looking for relatively significant
enhancements. More like new transport mechanisms and less like a
driver for the latest laser range-finder.
I'll assemble the responses into a prioritized wish list and post it
at the project website. I'll also incorporate the items from the SFU
wiki on ideas for a Google Summer of Code project.
Here are a few ideas to get things going (feel free to comment on them):
- New transport layers, getting away from the client-server model.
Candidates include CORBA, ACE, Reid Simmons' IPC...
- Standard implementations of multi-robot algorithms. Whereas now we
have implementations of single-robot algorithms like AMCL and VFH, we
could implement multi-robot SLAM, auction-based task allocation, etc.
- Support for structured "client-to-client" communications. Right
now, this is totally ad hoc, with everybody reinventing the wheel.
We could take ideas from the old lifomcom driver and new relay driver
to provide more fully-featured communication links among control
programs (which, depending on the transport mechanism in use, will
not necessarily be "clients")
- Standard tasks to try in simulation, with instrumentation to
provide automatic evaluation. Richard's going in this direction with
Playerstage-users mailing list