The files for the scene application are under the Scene folder.

1) Create a new directory called 'Scene' under /opt/tinyos-1.x/apps.

2) Place the files Beacon.nc, BeaconC.nc, Monitor.nc, MonitorC.nc, Scene.nc, SceneM.nc, and SceneMsg.h into this 'Scene' directory:.

3) To be able to use the SceneMsg message type, create a new directory called 'scene' under the following directory:

/opt/tinyos-1.x/tools/java/net/tinyos/message/

4) Add SceneMsg.class and SceneMsg.java to this 'scene' directory.

5) Open a cygwin command prompt, cd to /opt/tinyos-1.x/apps/Scene.

6) Issue the command 'make pc'. 

NOTE:

Before the 'make pc' command, the constants, TIMER_INTERVAL (in MonitorC.nc and BeaconC.nc) and step (in the Python script) should be set to the following values matching the desired client speed:

0 mph => TIMER_INTERVAL = 2000, step = 0.3
2 mph => TIMER_INTERVAL = 1000, step = 0.3
4 mph => TIMER_INTERVAL = 500, step = 0.6
8 mph => TIMER_INTERVAL = 250, step = 1.2

7) Issue the command tinyviz -script sceneScript_<name of file>.py. This will run the simulation in TinyViz.

NOTE: Replace the <name of file> part above with the relevant part for running the below scripts:

The sample Python script, sceneScript_VisualGrid.py, demonstrates visually the application for a 4 mph client mobility (step = 0.6) grid layout and it does not write to any log files.

The sample Python script for 2 mph client mobility and a grid layout, sceneScript_Grid4.py (with step = 0.3), creates and writes to a file called log_Grid4.txt.

The sample Python script for 2 mph client mobility and a random layout, sceneScript_Random4.py (with step = 0.3), creates and writes to a file called log_Random4.txt.

You can automate the simulation process using a script, such as simscript. Then, the command to use would be 'source simscript' at the cygwin command prompt.