| Panel |
|---|
Introduction
The controller allows for experiment session to be run in a quicker, more streamlined and controlled fashion. It resides within the server and its purpose lies in automatically pairing groups (dyads, triads, etc.) of subjects, firing up games and checking for client connectivity throughout the experiment.
...
- The configuration file, the application's only required argument, refers to the name of the configuration file (without extension), residing under gameconfigs.
- The game pool refers to a file containing the settings of pre-recorded games. This is helpful when an experiment spans multiple sessions (e.g., three sessions of 20 people each). If deemed important that all sessions are "indentical," then exposing their subjects to the same games (and not allowing randomness to play a role) is facilitated by using this game pool.
- The minimum number of games refers to how many games every pair of subjects has to play before their session is consider ended.
- Similarly, the maximum number of games refers to how many times each pair of subjects may be allowed to play together throughout the entire session.
Also, keep in mind that you must fire the controller after the server has been started and all clients have connected to it. In a sense, the controller is the final step in starting an experiment.
...