> I'm currently working on making a very simple GUI, written in python > (pyGTK), that provides the ability to run simple simulations. It hopefully > will help people get started with TOSSIM but WILL NOT BE DEVELOPED FOR > COMPLEX SIMULATIONS. To do complex simulations you will have to go back to > writing the simulation in python. The GUI inherits the TOSSIM objects and > extends them with some basic features like x,y coordinates for the motes. > When I get a chance I'll write a quick abstract for the GUI and post some > current design notes. As soon as I get a stable version up I'll post it. > Currently I have an unstable version working with topology for the motes, > radio communication, variable speed for running the simulation, log > filtering and the ability to view variables on each mote working. > http://www.cs.chalmers.se/~dcs/seminar/ is a link to what looks to be > someone else developing a GUI for TOSSIM. They do not say what version > there developing it for. I'm glad to hear someone (or two) is working on this. It would be nice if these projects were easier to track down. (These is something gratifying (to me) with seeing physical representations.) At this point I hope it's not for TOS 1.x... (yes, I'm a zealot trying to get people to switch)
> This is another extension I'm working on. It is a new object for TOSSIM-T2 > that will provide the ability to set a sensor value in your python script > and read it in your motes. It will also read a stream from a file pointer > passed to it. It is going to be very simple with get/set functionality with > NesC objects calling gets to read the values and Python sets to configure > the values. This actually sounds like it is almost entirely the task I've been doing this little inquiry research on. Is the code available anywhere? This seems like it'd be a rather useful feature. I'd much rather just report that this feature has currently been implemented and work on something else. How do you handle time synchronization with the motes/execution environment and data? (Just the stream makes it sound like it simple reads the next value in the stream.) With a full C/python Read interface it seems like the data could be any generic f(t), continuous or otherwise. > I made it very specific so far making it only work with the > HamamatsuS1087Par sensor rite now. I'm currently reading trying to find a > way to imbed it more with the ADC to allow for a more dynamic design for > more platforms. Is there a reason it needs to be sensor-specific if it uses the Read interface? If not, what am I missing? Thanks Paul _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
