- 1 Overview
- 2 Parameters and States
- 3 Input and Output Signal Format
- 4 Error Reporting
- 5 Combining the MatlabFilter with other Signal Processing Filters
- 6 Command Line Options
- 7 Troubleshooting
- 7.1 Debugging Matlab functions
- 7.2 Matlab doesn't find your functions
- 7.3 There is no Matlab engine started up
- 7.4 Changes to M-files appear to have no effect
- 7.5 You get linker errors when rebuilding MatlabSignalProcessing
- 7.6 You get a message window with a "Library not found" message
- 7.7 You get a message window with an "Entry Point Not Found" message
- 8 See also
The MatlabFilter implements a mechanism for using the Matlab engine within the BCI2000 pipeline. The MatlabFilter calls the Matlab engine to act upon signals, parameters, and states. It provides the full BCI2000 filter interface to a Matlab filter implementation.
While BCI2000 is running, each block of data is pushed to the Matlab engine and a well-specified Matlab function (i.e. *.m file) is executed. As explained in more detail in the Programming reference for the GenericFilter Class, all BCI2000 filters consist of a set of functions. The MatlabFilter will, upon execution of each of these functions, contact the Matlab engine and execure the corresponding Matlab function equivalent. Furthermore, the MatlabFilter copies the input signal and the states to the Matlab engine, and copies the output signal and states from the engine after processing the signal.
|BCI2000 function||Matlab equivalent|
Existence of the above-listed Matlab functions is not mandatory, the Matlab 'exist' command will be used to determine whether a given function is available, and will not call the Matlab engine when this is not the case. If either of the bci_Preflight, bci_Initialize, or bci_Process functions is not available, a warning will be displayed to the user.
Most of these Matlab functions do not take input arguments, except for
function [parameters, states] = bci_Construct; function [out_signal_dim] = bci_Preflight( in_signal_dim ); function bci_Initialize( in_signal_dim, out_signal_dim ); function [out_signal] = bci_Process( in_signal );
The most important functions is bci_Process, which is executed every time a new block of data is passed through the pipeline. The bci_Construct function is executed at the beginning and determines the parameters and states. The bci_Initialize function determines whether all requirements are met. The bci_StartRun function prepares the computation that is done during processing (e.g. computing filter parameters). Communication between these Matlab functions is done using global variables.
Parameters and States
Parameters and states are accessible via global Matlab structs called 'bci_Parameters' and 'bci_States'. Parameters may be changed from bci_StopRun and bci_Resting, and will automatically be propagated to the other modules. State values may be modified from the bci_Process function.
To add parameters and states to the BCI2000 list of states, the bci_Construct function may return non-empty cell arrays of strings in its parameters and states return values. The strings constituting these cell arrays are parameter and state definitions.
Your added parameters will appear in the operator module's parameter configuration dialog. Your parameter definition's section name will be used to direct its position in the configuration dialog's register cards:
MyFilter int MyParam= 2 0 0 2 // ...
will display the MyParam parameter on separate register card named MyFilter.
Filtering:MyFilter int MyParam= 2 0 0 2 // ...
will display the parameter on the Filtering register card, inside a group called MyFilter.
Input and Output Signal Format
BCI2000 signals are mapped to Matlab matrices with channel index first, and sample (element) index second. The signal dimension arguments of bci_Preflight and bci_Initialize are integer vectors of size 1x2 with [n_channels n_elements].
To report errors from Matlab functions, use Matlab's error command. Your error messages will be displayed to the user from the operator module.
Combining the MatlabFilter with other Signal Processing Filters
In the BCI2000 binary distribution, the MatlabFilter is shipped inside the MatlabSignalProcessing executable. There, the signal processing chain consists of the SpatialFilter and the MatlabFilter. However, by editing src/core/SignalProcessing/Matlab/PipeDefinition.cpp, you may add as many signal processing filters as you wish.
See Programming Reference:Filter Chain for information about defining a filter chain. Modification of the filter chain requires access to the BCI2000 source code. You will need to rebuild the MatlabSignalProcessing executable.
Command Line Options
By default, the Matlab engine's working directory is set to the signal processing module's working directory at startup. When using the Matlab filter for signal processing, your filter's code will be contained in the bci_Process and associated Matlab functions, which will typically be located inside a dedicated directory. Thus, you may switch between Matlab-based filter implementations by selecting a Matlab working directory at startup. This may be done by specifying the MatlabWD parameter from the command line when starting the MatlabSignalProcessing module:
start MatlabSignalProcessing.exe --MatlabWD="./matlab" 127.0.0.1
will change Matlab's working directory to a directory called "matlab" inside the BCI2000 "prog" directory at startup, and execute bci_Process and associated functions from there.
This parameter must be set from the command line; later changes will have no effect.
Using the --MatlabWD command line option, you may easily switch between multiple Matlab-based BCI2000 configurations. Simply create a separate startup batch file for each configuration, and specify the respective configuration's path on the command line that starts up the MatlabFilter.
By default, the Matlab instance associated with the Matlab engine will be closed when BCI2000 quits. Generally, this behavior is desired to ensure a well-defined BCI2000 system state after each startup. For debugging purposes, though, it is sometimes useful to have the engine's command window available even after BCI2000 has been quit. This behavior is controlled by another command-line parameter, MatlabStayOpen, which may take the following values:
- 0 is the default (no change in behavior),
- 1 keeps the Matlab engine's command window open but clears variables used to transmit information forth and back between BCI2000 and Matlab,
- 2 also preserves intermediate variables (such as bci_Parameters and bci_States) in the Matlab engine's workspace.
To set this parameter to 2, use this command line to start up the signal processing module:
start MatlabSignalProcessing.exe --MatlabStayOpen=2 127.0.0.1
Once the MatlabStayOpen parameter has been set from the command line, it will be listed on the Operator Module's parameter configuration dialog's "system" tab, and may be modified from there. The change will be applied when clicking Set Config.
Debugging Matlab functions
- Start BCI2000. The MatlabFilter will open a Matlab instance in its own window in minimized state.
- Switch to the minimized Matlab instance.
- Type, e.g.,
to open a Matlab editor window connected to the Matlab interactive window.
- In the editor window, set breakpoints as you would normally.
- Execution will be paused, and you may examine variables hovering the mouse over them.
Unfortunately, recent versions of Matlab do not allow interactive debugging of functions executed in the Matlab engine, so the above steps will not work any more. Instead, MathWorks suggests a rather crude approach.
Matlab doesn't find your functions
Make sure to
- either set Matlab's working directory to the directory containing your functions, using the --MatlabWD command line option described above,
- or add the respective directory to your Matlab path.
Generally, the first option is recommended over the second one.
There is no Matlab engine started up
from the command line when logged in with administrative privileges.
Changes to M-files appear to have no effect
Switch to the Matlab engine's command window, and enter
each time you change a Matlab function.
If you get linker errors after editing PipeDefinition.cpp, make sure that all filters' cpp files are part of the MatlabSignalProcessing project.
You get a message window with a "Library not found" message
Make sure that your Windows "%PATH%" variable contains the bin/win32 directory of your Matlab installation.
You get a message window with an "Entry Point Not Found" message
This error is likely to indicate confusion of multiple installations of Matlab on your machine. Check your Windows %PATH% environment variable, e.g. by opening a command console window and typing
When it contains references to more than a single Matlab installation, remove all apart from the reference to the installation you are going to use with BCI2000. Also, make sure to execute
for the Matlab installation you intend to use.
Technical Reference:Core Modules#Signal Processing Module, Technical Reference:Parameter Definition, Technical Reference:State Definition, Programming Reference:GenericFilter Class, Programming Reference:Filter Chain, Contributions:FieldTripBuffer