Contributions:SecondaryBCI2000Controller - Revision history

Mellinger: /* Known Issues */

2025-07-01T14:46:04Z

Known Issues

← Older revision		Revision as of 14:46, 1 July 2025
Line 16:		Line 16:

	===Known Issues===		===Known Issues===
	*Log windows of primary and secondary BCI2000 ~~instance~~ will initially have the same location, hiding each other and possibly leading to confusion. The same applies to operator main windows if ~~the second instance is~~ not hidden by calling "Hide Window" from the secondary batch file.		*Log windows of primary and secondary BCI2000 instances will initially have the same location, hiding each other and possibly leading to confusion. The same applies to operator main windows if secondary instances are not hidden by calling "Hide Window" from the secondary batch file(s).

	==Functional Description==		==Functional Description==

Mellinger: /* Parameters */

2025-07-01T14:44:18Z

Parameters

← Older revision		Revision as of 14:44, 1 July 2025
Line 40:		Line 40:
	Enables/Disables the SecondaryBCI2000Controller.		Enables/Disables the SecondaryBCI2000Controller.

	===~~SecondaryBCI2000TelnetPort~~===		===SecondaryBCI2000Instances===
	~~The telnet port that is used to control the~~ secondary instance ~~of BCI2000~~.		A matrix with one row per secondary instance.

	~~===SecondaryBCI2000StartupScript===~~		The first column contains the telnet port that is used to control the secondary instance of BCI2000.
	The script that is used to start up and configure the secondary instance of BCI2000. An example script is available as <tt>~~BCI2000TwiceSecondaryStartup~~.bat</tt> in your BCI2000 batch directory, and is called by the <tt>BCI2000TwiceStartup.bat</tt> batch file.
			The second column contains the the script that is used to start up and configure the secondary instance of BCI2000. An example script is available as <tt>BCI2000SecondaryStartup.bat</tt> in your BCI2000 batch directory, and is called by the <tt>BCI2000TwiceStartup.bat</tt> batch file.

Mellinger: /* Usage */

2025-07-01T14:41:26Z

Usage

← Older revision		Revision as of 14:41, 1 July 2025
Line 29:		Line 29:
	When the SecondaryBCI2000Controller extension has been enabled in the system at compile time, you will find a <tt>BCI2000TwiceStartup.bat</tt> batch file in your BCI2000 batch folder. Double-click it to start BCI2000.		When the SecondaryBCI2000Controller extension has been enabled in the system at compile time, you will find a <tt>BCI2000TwiceStartup.bat</tt> batch file in your BCI2000 batch folder. Double-click it to start BCI2000.

	Startup configuration of ~~the~~ secondary ~~instance of~~ BCI2000 is done in the ~~file~~ <tt>~~BCI2000TwiceSecondaryStartup~~.bat</tt>.		Startup configuration of secondary BCI2000 instances is done in the files <tt>BCI2000SecondaryStartup.bat</tt>, <tt>BCI2000Secondary2Startup.bat</tt>, etc.
	You may load identical or different configuration parameter files in the ~~two~~ startup batch files.		You may load identical or different configuration parameter files in the startup batch files.

	Data file location is synchronized between ~~the two~~ BCI2000 instances. ~~The second instance uses~~ identical file names to the first one, with an appended <tt>_1</tt> before the file name extension.		Data file location is synchronized between BCI2000 instances. Secondary instances use identical file names to the first one, with an appended <tt>_1</tt>, <tt>_2</tt>, ... before the file name extension.

	==Parameters==		==Parameters==

Mellinger: /* Functional Description */

2025-07-01T13:57:08Z

Functional Description

← Older revision		Revision as of 13:57, 1 July 2025
Line 19:		Line 19:

	==Functional Description==		==Functional Description==
	The extension will start up ~~a second instance~~ of BCI2000, and synchronize data file storage and operation state between the ~~two~~ instances. This is useful to record from two different data sources at the same time, when online processing of ~~one of the~~ data sources is not required. In later analysis, data from the ~~two~~ sources may be aligned in time using BCI2000 time stamps found in the ~~two~~ data files.		The extension will start up one or more secondary instances of BCI2000, and synchronize data file storage and operation state between the instances. This is useful to record from two or more different data sources at the same time, when online processing of secondary data sources is not required. In later analysis, data from the multiple sources may be aligned in time using BCI2000 time stamps found in the data files.

	==Integration into BCI2000==		==Integration into BCI2000==

Mellinger: /* Synopsis */

2025-07-01T13:55:30Z

Synopsis

← Older revision		Revision as of 13:55, 1 July 2025
Line 1:		Line 1:
	==Synopsis==		==Synopsis==
	An extension that controls a secondary BCI2000 ~~instance~~ from the GUI of a primary one.		An extension that controls one or more secondary BCI2000 instances from the GUI of a primary one.

	==Location==		==Location==

Mellinger: /* Known Issues */

2024-09-02T16:45:31Z

Known Issues

← Older revision		Revision as of 16:45, 2 September 2024
Line 16:		Line 16:

	===Known Issues===		===Known Issues===
	*Log windows of primary and secondary BCI2000 instance will have the same location, hiding each other and possibly leading to confusion. The same applies to operator main windows if the second instance is not hidden by calling "Hide Window" from the secondary batch file.		*Log windows of primary and secondary BCI2000 instance will initially have the same location, hiding each other and possibly leading to confusion. The same applies to operator main windows if the second instance is not hidden by calling "Hide Window" from the secondary batch file.

	==Functional Description==		==Functional Description==

Mellinger: /* Parameters */

2024-09-02T16:44:51Z

Parameters

← Older revision		Revision as of 16:44, 2 September 2024
Line 45:		Line 45:
	===SecondaryBCI2000StartupScript===		===SecondaryBCI2000StartupScript===
	The script that is used to start up and configure the secondary instance of BCI2000. An example script is available as <tt>BCI2000TwiceSecondaryStartup.bat</tt> in your BCI2000 batch directory, and is called by the <tt>BCI2000TwiceStartup.bat</tt> batch file.		The script that is used to start up and configure the secondary instance of BCI2000. An example script is available as <tt>BCI2000TwiceSecondaryStartup.bat</tt> in your BCI2000 batch directory, and is called by the <tt>BCI2000TwiceStartup.bat</tt> batch file.


			To tell the second instance that it should refer to the first one for file names, there is a command line parameter:

			===IsSecondaryBCI2000===
			This parameter must be set to 1 in the secondary instance's batch file: <tt>--IsSecondaryBCI2000=1</tt>

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

Mellinger: /* Known Issues */

2024-09-02T16:41:31Z

Known Issues

← Older revision		Revision as of 16:41, 2 September 2024
Line 16:		Line 16:

	===Known Issues===		===Known Issues===
	*When recording into a directory that already contains data files with the same base name, data file name will be out of sync between the first and second instance of BCI2000. Also, run numbers stored within the files will be out of sync.
	*Log windows of primary and secondary BCI2000 instance will have the same location, hiding each other and possibly leading to confusion. The same applies to operator main windows if the second instance is not hidden by calling "Hide Window" from the secondary batch file.		*Log windows of primary and secondary BCI2000 instance will have the same location, hiding each other and possibly leading to confusion. The same applies to operator main windows if the second instance is not hidden by calling "Hide Window" from the secondary batch file.

Mellinger: /* Known Issues */

2022-10-07T13:17:39Z

Known Issues

← Older revision		Revision as of 13:17, 7 October 2022
Line 16:		Line 16:

	===Known Issues===		===Known Issues===
	*When recording into a directory that already contains data files with the same base name, data file name will be out of sync between		*When recording into a directory that already contains data files with the same base name, data file name will be out of sync between the first and second instance of BCI2000. Also, run numbers stored within the files will be out of sync.
	the first and second instance of BCI2000. Also, run numbers stored within the files will be out of sync.
	*Log windows of primary and secondary BCI2000 instance will have the same location, hiding each other and possibly leading to confusion. The same applies to operator main windows if the second instance is not hidden by calling "Hide Window" from the secondary batch file.		*Log windows of primary and secondary BCI2000 instance will have the same location, hiding each other and possibly leading to confusion. The same applies to operator main windows if the second instance is not hidden by calling "Hide Window" from the secondary batch file.

Mellinger: /* See also */

2022-07-08T16:37:24Z

← Older revision		Revision as of 16:37, 8 July 2022
Line 49:		Line 49:

	==See also==		==See also==
	[[Contributions:Extensions]], [[User Reference:Operator Scripting]]		[[Contributions:Extensions]], [[User Reference:Operator Module Scripting]]

	[[Category:Contributions]][[Category:Extension]]		[[Category:Contributions]][[Category:Extension]]