Dispatcher

Description
The Dispatcher reads a schedule file and runs the tasks listed in it one at a time. It also keeps a list of how many subjects have run the schedule, and how many sessions they have each run.
The tasks that are currently run by the Dispatcher all have a similar set of characteristics. They all accept a common set of parameters, including a timeout for the task (after which it dies) and a filename to store the results in.

Topics

How to Run It	The PenSUSOPS Setup program creates an icon for the Dispatcher in the group that it creates on your desktop. It will automatically find the directory that contains your schedules so that you can select the one you want. Run the Dispatcher by double clicking on its icon. When it starts you will see this window:
Schedule File	The schedule file is described in the Schedule Editor documentation above. It lists the tasks to be run, the length of time each should run, and any task-specific parameters.
Sessions File	The sessions file keeps track of which subjects have run this schedule, and how many times they have run it. In the normal course of things you will not need to edit it. It is kept up-to-date by the Dispatcher.
Rolling Back A Session	A run of a schedule may die part way through if there is some problem with the computer or the subject. It is assumed that you will merely start another session, and later discard the partial data.

How To Run It

Description
The PenSUSOPS Setup program creates an icon for the Dispatcher in the group that it creates on your desktop. It will automatically find the directory that contains your schedules so that you can select the one you want. Run the Dispatcher by double clicking on its icon. When it starts you will see this window:

Click on the Experiment button and choose a schedule to run. Then click on the Subject button to pick one of the existing subjects or to add a new one.

Then Click on the Run Script button to run the schedule. You will see the screen go white, and then you will see a small window asking you to click to start.

You can now give the computer to the subject and let them run the tasks. When the tasks are all complete another window will appear saying that all tasks are done.

Schedule File

Description
The schedule file is described in the Schedule Editor documentation above. It lists the tasks to be run, the length of time each should run, and any task-specific parameters. Refer to Schedule Editor for more information.

Sessions File

Description
The sessions file keeps track of which subjects have run this schedule, and how many times they have run it. In the normal course of things you will not need to edit it. It is kept up-to-date by the Dispatcher.
The session file is kept in the schedule directory, and has a name ending in ".ses".

For example if a schedule is named "xyz" then the session file is named ".../Results/xyz/xyz.ses".

There is one line per subject. The line contains the subject identifier (a three letter or number code for the subject), the number of times the subject has run the schedule (the session count), and an optional "real name" for the subject.

Here is a sample session file.
```
 	     jch       2       Jeff Hunter
	
```

Rolling Back A Session

Description
A run of a schedule may die part way through if there is some problem with the computer or the subject. It is assumed that you will merely start another session, and later discard the partial data.
You may however wish to remove the partial session results, and re-run a session. There is no automated way to do this.

If you really wish to remove a session here are instructions. You can only do this immediately after the aborted session. Once the subject has completed another run its too late.

Pick any editor to edit the files with. The Notepad is handy, but will not work for really big data files.

Edit the session file. Find the line for the subject. Decrease the session number by one. (Be sure not to remove the TABs between the the columns of data.)

Look for data files with names ending in the subject identifier. (For example if the schedule is "xyz" and the subject ID is "123" then the data will be in files with names like "xyzLRT.123" and "xyzSTM.123".

Go to the end of each file and delete all the records with the session number that you are want to remove. The session number is the third field in each line.