User Reference:Operator Module
The operator module is the user interface seen by the experimentator. It allows to view and edit system parameters, save and load parameter files, and start and stop system operation.
Main Window

Operation Buttons
The main window contains four large buttons. These buttons correspond to the tasks that need to be performed during an experiment:
- Config
- opens the configuration window,
- SetConfig
- applies the current set of parameters to the system,
- Start
- starts system operation,
- Quit
- exits the system once the experiment has finished.
Not all buttons are functional all the time; availability of a function depends on system state, and is indicated by the button's state.
Function Buttons
There are four function buttons that execute Operator Scripts. Scripts and button captions may be configured freely from the preferences dialog.
Status Area
The status area, at the bottom of the main window, contains four fields. System status is displayed on the left, and module status is displayed in the three rightmost fields, in the natural order of core modules (Data Acquisition, Signal Processing, Application).
Main Menu
File
- Preferences...
- opens the Preferences Dialog.
- Exit...
- terminates BCI2000 after displaying a confirmation message. This menu entry is always available, even if the Quit button is dimmed.
View
- States...
- displays a window that lists the state variables currently available in the system.
- Operator Log
- toggles visibility of the log window. The log window becomes automatically visible when there are error or warning messages; for informative messages, and debugging output, it is necessary to make it visible using this menu entry.
- Connection Info
- toggles visibility of the connection information window. This window displays information whether connections between operator and core modules are established, network addresses, and the number of messages that have been transferred so far.
=Help
- About...
- displays extensive information about the operator module's version number, the source code revision it was built from, and the time of the build. This information is also kept inside the OperatorVersion parameter on the system tab, and written into data files along with all system parameters.