From: Radu B. R. <ru...@cs...> - 2006-06-07 07:46:41
|
You might want to check the CVS repository, as I committed working interfaces and code for mica2,mica2dot,rcore,particles,m1,m1-mini and m300 (check the wsn and rfid interfaces). I also have some automatic feature extraction plugin using PCA, ICA, Wavelets, Fourier (with the possibility to use the output of one as the input of another) and then combining them to calculate classical features like mean, variance, power spectrum, etc. This one is not committed yet though, as we lack a proper interface for that. I am currently using opaque in my own projects. Best, Radu. Mirko Bordignon wrote: > hi, > > as others said, I'd say service discovery; then I think some > infrastructural redesign -or, meanwhile, a simple extension- could > better address interoperation with simpler wireless sensor networks (I > think about TinyOS related stuff), > btw, isn't Player dubbed as a "Free Software that enables research in > robot and sensor systems" ;-) ? > > the following excerpt made me think about it, although incorporating > part of the zigbee stack is surely something more kernel/os related > > 4. Code for a Linux-based 802.15.4 access point. A Telos Mote plugged > into a Linux PC acts as an 802.15.4 access point and routes packets to > the Internet. > (from > http://mail.millennium.berkeley.edu/pipermail/tinyos-devel/2005-August/000767.html) > > > maybe it's just because my instructor makes us work with bots and > motes in the lab, but I think p/s should address the thing more > clearly, even if it's already possible (with the proper os hacking and > player driver development) to work out something > (in fact I'm lobbying for p/s in the lab PCs as a mean to interface > not only with the robots but with the sensor nodes too...) > > cheers > > Mirko Bordignon - University of Padova, Italy > > mirko[dot]bordignon[at]ieee[dot]org > > > > Il giorno 06/giu/06, alle ore 22:03, Brian Gerkey ha scritto: > >> hi, >> >> 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 >> the Zoo. >> >> brian. >> >> >> _______________________________________________ >> Playerstage-users mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-users > > > ------------------------------------------------------------------------ > > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > -- | Radu Bogdan Rusu | http://rbrusu.com/ | http://www9.cs.tum.edu/people/rusu/ | Intelligent Autonomous Systems | Technische Universitaet Muenchen |