Quick links:
Famous tasks:
www.whiskercontrol.com/WhiskerServer_v1_screenshots.shtml
WhiskerServer v1.0 screen shots
The installation logo
Views of the server as a whole
| (click thumbnail to enlarge) | |
| The main server screen, showing some of the lines attached to the computer, and which client is using them. |  |
| A summary of the clients currently connected, and their status. |  |
| The server's status view, summarizing the network status and monitoring the computer's performance. The menu illustrates some of the commands that pertain to the server as a whole. |  |
| Configuring the digital I/O hardware. |  |
| The server's event log. |  |
| Configuring 'fail-safe' outputs to help ensure critical equipment cannot be powered on when the server is not running. |
|
Some views of an individual client
| (click thumbnail to enlarge) | |
| Status of a particular client. |  |
| The lines that this client is using. As with the main line display, you can force a line on/off for testing purposes. |  |
| The names (aliases) that the client has given its lines. One very easy way to implement yoking is to give the same alias to two or more lines. One way to implement counterbalancing is to give several aliases to one line (as in this example). |  |
| The timers that the client is using at the moment. The menu illustrates some of the things you can do to clients that are running. |  |
| For debugging, you can switch on an event log and a full communications log for the clients. Here is an example of the event log. |  |
| This is a snapshot of the communications log, which lists every message that passes between the client and the server. This form of detailed information is occasionally very helpful in testing new tasks. |
|
The system in action: an overview
| (click thumbnail to enlarge) | |
| Here, five tasks are running (each controlling a second-order schedule of i.v. cocaine reinforcement, and each in a slightly different phase of training). |  |
| Or you can minimize them all and go for a coffee. |  |
