User Reference:BCI2000Launcher

From BCI2000 Wiki
Jump to: navigation, search


The BCI2000Launcher program provides a convenient user interface for organizing BCI2000 applications and parameter files. The Source, SignalProcessing, and Application modules are selected from a list, and multiple parameter files can be loaded.


Using BCI2000Launcher

Organizing BCI2000 Modules

On the first launch, BCI2000Launcher examines the contents of the BCI2000/prog directory, looking for executable programs. Known programs are sorted appropriately, e.g., the gUSBampSource.exe program is placed in "Acquisition" column. If a program is not recognized, it is placed in the "Others" column. Right-clicking on a module brings up a context menu that allows it to be moved to another column. Programs that are rarely used can be moved to the "Others" column to keep them out of the way. BCI2000Launcher stores across sessions which modules are selected, using a BCILauncher.ini settings file.

Selecting Parameter Files

A very useful feature of the BCI2000Launcher is the ability to load multiple parameter fragments. One or more fragments can be added to the list to be loaded by pressing the "+" button, and selecting the *.prm files. Files can be removed from the list using the "-" button. If more than one prm file contains the same parameter, files lower on the list will have precedence over those higher on the list.

Entering Recording Parameters

The SubjectName, SubjectSession, and DataDirectory parameters may be entered directly in the BCI2000Launcher dialog. These values take precedence over the parameters' values in one of the specified parameter files.

Starting a BCI2000 Session

Select the desired modules from each column, and click the "Launch" button in the bottom right corner. You can also select multiple programs to be started from the "Others" column at the same time. Additionally, you can deselect modules by pressing the "Clear Selection" button, and select individual programs to launch and connect to the Operator, without starting all required modules. This is useful for debugging new programs, since the new program can connect from a debugging session, and the others will start as normal.