Jump to content

Contributions:Extensions: Difference between revisions

From BCI2000 Wiki
Nluczak (talk | contribs)
No edit summary
Rlellis (talk | contribs)
No edit summary
Line 21: Line 21:
being controlled by the first instance's GUI.
being controlled by the first instance's GUI.
*[[Contributions:ResponseTimeBox]]: A logger that stores event information (button, sound, light, TTL) from the Response Time Box into BCI2000 states.
*[[Contributions:ResponseTimeBox]]: A logger that stores event information (button, sound, light, TTL) from the Response Time Box into BCI2000 states.
*[[Contributions:KeysightGenerator]]: An extension allowing the user to create and execute waveforms on state changes


==See also==
==See also==

Revision as of 18:01, 28 July 2023

A framework Extension is an optional contributed plugin which can affect multiple modules. For example, various manufacturer-specific input-device loggers are provided in the src/contrib/Extensions folder, and these can be optionally added to the BCI2000 framework for SignalSource modules, thereby giving all source modules the ability to log input from the corresponding devices. Selecting a custom Extension, and re-building your modules to include it, requires the use of CMake and a supported C++ compiler: see the Programming Howto:Quickstart Guide for a walkthrough that shows you how to recompile BCI2000 modules.

The following user extensions are available in the Contributions section of BCI2000:

being controlled by the first instance's GUI.

See also

Programming Reference:EnvironmentExtension Class

Programming Tutorial:Implementing an Input Logger