Jump to content

Contributions:External Interfaces: Difference between revisions

From BCI2000 Wiki
Mellinger (talk | contribs)
No edit summary
Mellinger (talk | contribs)
No edit summary
 
Line 3: Line 3:


*[[Contributions:BCPy2000]]: Signal processing and application module for calling custom Python functions.
*[[Contributions:BCPy2000]]: Signal processing and application module for calling custom Python functions.
*[[Contributions:BCI2000Automation]]: A Windows COM component that allows controlling BCI2000 from .NET or other COM compatible software, e.g. Matlab for Windows.
<!--*[[Contributions:BCI2000Automation]]: A Windows COM component that allows controlling BCI2000 from .NET or other COM compatible software, e.g. Matlab for Windows.-->
*[[Contributions:BCI2000Command]]: A command line tool that connects to a BCI2000 instance and executes scripting commands. This allows scripting BCI2000 from any command line shell environment.
*[[Contributions:BCI2000Command]]: A command line tool that connects to a BCI2000 instance and executes scripting commands. This allows scripting BCI2000 from any command line shell environment.
*[[Contributions:BCI2000PresentationLink]]: An extension to the [http://www.neurobs.com/ NBS Presentation] software that allows controlling BCI2000 from Presentation, and to record Presentation time stamps in BCI2000.
*[[Contributions:BCI2000PresentationLink]]: An extension to the [http://www.neurobs.com/ NBS Presentation] software that allows controlling BCI2000 from Presentation, and to record Presentation time stamps in BCI2000.

Latest revision as of 20:23, 19 June 2025

External Interfaces are provided to enable interoperability with other software. Most of these interfaces use Operator Scripting to control BCI2000, and to log information provided by the external software.

See also

Programming Reference:BCI2000Remote Class, Programming Reference:SignalSharingDemo Signal Processing