User Reference:BCI2000Certification - Revision history

Wengelhardt: /* See also */

2024-09-03T17:59:40Z

Wengelhardt at 19:19, 21 June 2024

2024-06-21T19:19:03Z

@@ Line 301: / Line 301: @@
 There are two ways to connect the output of the gTRIGbox to the g.USBamp, “Analog” or “Digital”, as indicated in the figure below. Pins connected by a  <span style="color:#f97e00">orange</span> dotted line denote connections that are necessary to measure the amplifier latency.
 [[File:Usbampconnections.png|800px|thumb|center|upright=2.5|Connectors schematic.]]
 ====Digital Configuration====
@@ Line 313: / Line 315: @@
 [[File:F15pin_d-sub_connector.jpg|600px|thumb|center|upright=2.5|15 Pin D-Sub Connector with Breakout Board.]]
 <!--
 {| class="wikitable"

Nluczak: Added Video

2021-03-01T23:24:26Z

Added Video

← Older revision		Revision as of 23:24, 1 March 2021
Line 15:		Line 15:

	This document serves as the BCI2000Certification manual. As an example, this page will describe the certification procedure for the g.USBamp with visual and auditory stimuli triggered with the g.TRIGbox. At the end of the page, the certification results for using BCI2000 with three biosignal amplifiers (the g.USBamp, EGI GTEN 200, and Nihon Kohden JE120-A) are provided. A discussion and derivation of the specific system latencies are found [https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3161621/ here].		This document serves as the BCI2000Certification manual. As an example, this page will describe the certification procedure for the g.USBamp with visual and auditory stimuli triggered with the g.TRIGbox. At the end of the page, the certification results for using BCI2000 with three biosignal amplifiers (the g.USBamp, EGI GTEN 200, and Nihon Kohden JE120-A) are provided. A discussion and derivation of the specific system latencies are found [https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3161621/ here].
			==Video Demonstration==
			<youtube alignment="center">https://youtu.be/yh7ifhCh2v0</youtube>
	==Compiling the BCI2000Certification Programs==		==Compiling the BCI2000Certification Programs==
	The BCI2000Certification procedure actually consists of two separate programs, including a graphical user interface that simplifies the task of selecting and starting tests, and a program that performs the data analysis and returns results. These programs are compiled automatically with the other BCI2000 programs. Compilation is only supported in BCI2000 v3.0 with the Visual Studio or MinGW compilers. Instructions can be found at [[Programming_Howto:Building_BCI2000]]. At the point where you start CMake, be sure to check BUILD TOOLS in the BUILD menu.		The BCI2000Certification procedure actually consists of two separate programs, including a graphical user interface that simplifies the task of selecting and starting tests, and a program that performs the data analysis and returns results. These programs are compiled automatically with the other BCI2000 programs. Compilation is only supported in BCI2000 v3.0 with the Visual Studio or MinGW compilers. Instructions can be found at [[Programming_Howto:Building_BCI2000]]. At the point where you start CMake, be sure to check BUILD TOOLS in the BUILD menu.

Swiftj: /* Loading Configuration Files */

2021-02-25T16:58:34Z

Loading Configuration Files

← Older revision		Revision as of 16:58, 25 February 2021
Line 37:		Line 37:
	# In the BCI2000Certification tool, select <code>File->Open *.ini</code>		# In the BCI2000Certification tool, select <code>File->Open *.ini</code>
	# Navigate to the folder <code>BCI2000/tools/BCI2000Certification</code>.		# Navigate to the folder <code>BCI2000/tools/BCI2000Certification</code>.
	# Load the file named <code>BCI2000Certification_16ch_100ms.ini</code> if using a 16-channel system~~, or <code>BCI2000Certification_32ch_100ms.ini</code> if using 32 channels~~. (This tutorial assumes a 16-channel system).		# Load the file named <code>BCI2000Certification_16ch_100ms.ini</code> if using a 16-channel system. (This tutorial assumes a 16-channel system).
	# If using more than 16 channels, then the amplifier parameter files must be modified.		# If using more than 16 channels, then the amplifier parameter files must be modified.
	## Navigate to <code>BCI2000/tools/BCI2000Certification/parms/</code>, and open the file <code>Certification_gUSBamp_24.prm</code> in Notepad.		## Navigate to <code>BCI2000/tools/BCI2000Certification/parms/</code>, and open the file <code>Certification_gUSBamp_24.prm</code> in Notepad.

Swiftj: /* Compiling the BCI2000Certification Programs */

2021-02-19T20:15:52Z

Compiling the BCI2000Certification Programs

← Older revision		Revision as of 20:15, 19 February 2021
Line 17:		Line 17:

	==Compiling the BCI2000Certification Programs==		==Compiling the BCI2000Certification Programs==
	The BCI2000Certification procedure actually consists of two separate programs, including a graphical user interface that simplifies the task of selecting and starting tests, and a program that performs the data analysis and returns results. These programs are compiled automatically with the other BCI2000 programs. Compilation is only supported in BCI2000 v3.0 with the Visual Studio or MinGW compilers. Instructions can be found at [[Programming_Howto:Building_BCI2000]].		The BCI2000Certification procedure actually consists of two separate programs, including a graphical user interface that simplifies the task of selecting and starting tests, and a program that performs the data analysis and returns results. These programs are compiled automatically with the other BCI2000 programs. Compilation is only supported in BCI2000 v3.0 with the Visual Studio or MinGW compilers. Instructions can be found at [[Programming_Howto:Building_BCI2000]]. At the point where you start CMake, be sure to check BUILD TOOLS in the BUILD menu.

			[[image:CMakeBuildTools.png\|frame\|none\|Check the BUILD TOOLS box to build the certification tester and analysis tool.]]

	==Using the BCI2000Certification Procedure==		==Using the BCI2000Certification Procedure==

Abelsten: /* Procedure for Assembling Cable */

2021-02-16T19:37:32Z

Procedure for Assembling Cable

← Older revision		Revision as of 19:37, 16 February 2021
Line 390:		Line 390:
	=====Procedure for Assembling Cable=====		=====Procedure for Assembling Cable=====
	# Strip the ends of five wires with safety connectors at one end, leaving a quarter-inch exposed (if you want to measure amplifier latency, strip one additional wire).		# Strip the ends of five wires with safety connectors at one end, leaving a quarter-inch exposed (if you want to measure amplifier latency, strip one additional wire).
	# Start with the D-Sub connector. Connect each of the pins in ~~‘’’gTRIGbox Output ‘’’ column of~~ the ~~table above~~ to its own piece of safety connector wire.		# Start with the D-Sub connector. Connect each of the pins as shown in the connector schematic to its own piece of safety connector wire.
	# If you also want to measure amplifier latency, a voltage divider is necessary to bring the 5V output at the gUSBamp's digital output at pin 5 down to a voltage less than 250mV (the max input range on the gUSBamp's analog inputs). Selecting a <math>R_1</math> and <math>R_2</math> such that the following equation is satisfied would result in a 100mV signal at the analog inputs:		# If you also want to measure amplifier latency, a voltage divider is necessary to bring the 5V output at the gUSBamp's digital output at pin 5 down to a voltage less than 250mV (the max input range on the gUSBamp's analog inputs). Selecting a <math>R_1</math> and <math>R_2</math> such that the following equation is satisfied would result in a 100mV signal at the analog inputs:
	<math>0.02 = \frac{R_2}{R_1+R_2}</math>		<math>0.02 = \frac{R_2}{R_1+R_2}</math>

Abelsten: /* Latest gTRIGbox */

2021-02-16T19:25:32Z

Latest gTRIGbox

← Older revision		Revision as of 19:25, 16 February 2021
Line 296:		Line 296:
	The plug is assembled next, similar to the. Solder the signal wire from Pin 3 (Digital Out 1) on the digital I/O connector to the signal connector on the female mono plug, and solder the ground wire to the outer ground connector on the plug. The below figure shows this; in this figure, the red wire is the signal wire, and the brown wire is the ground.		The plug is assembled next, similar to the. Solder the signal wire from Pin 3 (Digital Out 1) on the digital I/O connector to the signal connector on the female mono plug, and solder the ground wire to the outer ground connector on the plug. The below figure shows this; in this figure, the red wire is the signal wire, and the brown wire is the ground.
	===Latest gTRIGbox===		===Latest gTRIGbox===
	There are two ways to connect the output of the gTRIGbox to the g.USBamp, “Analog” or “Digital”, as indicated in the figure below.		There are two ways to connect the output of the gTRIGbox to the g.USBamp, “Analog” or “Digital”, as indicated in the figure below. Pins connected by a <span style="color:#f97e00">orange</span> dotted line denote connections that are necessary to measure the amplifier latency.
	[[File:Usbampconnections.png\|800px\|thumb\|center\|upright=2.5\|Connectors schematic.]]		[[File:Usbampconnections.png\|800px\|thumb\|center\|upright=2.5\|Connectors schematic.]]

Line 310:		Line 310:

	[[File:F15pin_d-sub_connector.jpg\|600px\|thumb\|center\|upright=2.5\|15 Pin D-Sub Connector with Breakout Board.]]		[[File:F15pin_d-sub_connector.jpg\|600px\|thumb\|center\|upright=2.5\|15 Pin D-Sub Connector with Breakout Board.]]
			<!--
	~~The necessary connections between the device’s pins are shown in the following figure. Pins in~~ <~~span style="color:#f97e00">orange</span> denote connections that are necessary to measure the amplifier latency.~~
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 334:		Line 333:
	\| style="color:#f97e00;" \| 1 & 5		\| style="color:#f97e00;" \| 1 & 5
	\|}		\|}
			-->
	=====Procedure for Assembling Cable=====		=====Procedure for Assembling Cable=====
	# Cut 3 pieces of wire, each the same length (about 3 ft should be sufficient).		# Cut 3 pieces of wire, each the same length (about 3 ft should be sufficient).
Line 353:		Line 353:
	# One 7 pin Digital Pin Connector from g.tec		# One 7 pin Digital Pin Connector from g.tec
	# One Additional Safety Connector Wire (to USB amplifier input)		# One Additional Safety Connector Wire (to USB amplifier input)
			# Two resistors for Voltage Divider
	# Soldering Iron and Solder		# Soldering Iron and Solder

	If you use the D-Sub connector with a breakout board and do not want to measure amplifier latency, you will not need to do any soldering, making assembly quite easy. Below is a table of what pin connections must be made. The connections shown in <span style="color:#f97e00">orange</span> are necessary to measure amplifier latency.		If you use the D-Sub connector with a breakout board and do not want to measure amplifier latency, you will not need to do any soldering, making assembly quite easy. Below is a table of what pin connections must be made. The wiring diagram above provides a guide for what pins need to be connected.
			<!--
			The connections shown in <span style="color:#f97e00">orange</span> are necessary to measure amplifier latency.
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 385:		Line 387:
	\| style="color:#f97e00;" \| 1		\| style="color:#f97e00;" \| 1
	\|}		\|}
			-->
	=====Procedure for Assembling Cable=====		=====Procedure for Assembling Cable=====
	# Strip the ends of five wires with safety connectors at one end, leaving a quarter-inch exposed (if you want to measure amplifier latency, strip one additional wire).		# Strip the ends of five wires with safety connectors at one end, leaving a quarter-inch exposed (if you want to measure amplifier latency, strip one additional wire).
	# Start with the D-Sub connector. Connect each of the pins in ‘’’gTRIGbox Output ‘’’ column of the table above to its own piece of safety connector wire.		# Start with the D-Sub connector. Connect each of the pins in ‘’’gTRIGbox Output ‘’’ column of the table above to its own piece of safety connector wire.
	# If you also want to measure amplifier latency, ~~strip~~ and ~~solder~~ the ~~additional safety connector to~~ pin 5 on the digital I/O connector.		# If you also want to measure amplifier latency, a voltage divider is necessary to bring the 5V output at the gUSBamp's digital output at pin 5 down to a voltage less than 250mV (the max input range on the gUSBamp's analog inputs). Selecting a <math>R_1</math> and <math>R_2</math> such that the following equation is satisfied would result in a 100mV signal at the analog inputs:
	# If assembling the digital I/O connector, it may be helpful to insulate the wires from the casing using either a piece of black electrical tape or an insulating gel, like silicone. If a gel is used, be sure to let it set for several hours or overnight. It is also probably a good idea to check the electrical connection with a multimeter prior to insulating.		<math>0.02 = \frac{R_2}{R_1+R_2}</math>
			# Assemble this voltage divider by soldering the resistors, pin 5 on the digital I/O, and additional safety connector together as detailed in the connectors schematic. You can also use a bread board to avoid soldering.
			# When assembling the digital I/O connector, it may be helpful to insulate the wires from the casing using either a piece of black electrical tape or an insulating gel, like silicone. If a gel is used, be sure to let it set for several hours or overnight. It is also probably a good idea to check the electrical connection with a multimeter prior to insulating.
	# Next, attach the rubber sleeve over the end of the part with the female threads, as shown in the panel.		# Next, attach the rubber sleeve over the end of the part with the female threads, as shown in the panel.
	# Slide the smaller metal sleeve over the wires, then slide the larger rubber sleeve over the wires.		# Slide the smaller metal sleeve over the wires, then slide the larger rubber sleeve over the wires.

Mellinger: /* Analyzing Data */

2021-02-16T17:16:49Z

Analyzing Data

← Older revision		Revision as of 17:16, 16 February 2021
Line 202:		Line 202:
	# When the parameters have been correctly configured, press "Run" to start the analysis, which can take several minutes. Note that debug builds run very slowly, so you should always use a release build for analysis.		# When the parameters have been correctly configured, press "Run" to start the analysis, which can take several minutes. Note that debug builds run very slowly, so you should always use a release build for analysis.
	# When finished, the analysis tool will display results at several levels of detail. On top, a summary is displayed, then a list of requirements is shown, with a global result for each requirement. Further down, results are shown for individual files.		# When finished, the analysis tool will display results at several levels of detail. On top, a summary is displayed, then a list of requirements is shown, with a global result for each requirement. Further down, results are shown for individual files.
	# To store results for documentation, you may press ''Save and Open...'' to save results to a text file, which can be found in the ~~BCI2000 Certification~~ folder. The file name will have the format <code>results_(date)_(time).txt</code>. Additionally, this contents of this file will be opened automatically at the end of the process in a new window.		# To store results for documentation, you may press ''Save and Open...'' to save results to a text file, which can be found in the folder choosen at the bottom left, defaulting to the data folder. The file name will have the format <code>results_(date)_(time).txt</code>. Additionally, this contents of this file will be opened automatically at the end of the process in a new window.

	===Interpreting Analysis Results===		===Interpreting Analysis Results===

Mellinger: /* A Note on "Pass/Fail" */

2021-02-16T17:14:42Z

A Note on "Pass/Fail"

← Older revision		Revision as of 17:14, 16 February 2021
Line 221:		Line 221:
	====A Note on "Pass/Fail"====		====A Note on "Pass/Fail"====
	The values that determine whether or not a task passes or fails are determined somewhat arbitrarily. For example, we determined that an audio output latency of more than 65 ms is unacceptable for psychophysical research, e.g., BCIs. In the example shown, the audio output latency was ~62 ms for all tasks with audio, and thus these tasks registered as a "pass." However, it is ultimately up to the researcher to determine what is acceptable system timing; this method provides a method of quantifying the system latency values to simplify the process of making these decisions.		The values that determine whether or not a task passes or fails are determined somewhat arbitrarily. For example, we determined that an audio output latency of more than 65 ms is unacceptable for psychophysical research, e.g., BCIs. In the example shown, the audio output latency was ~62 ms for all tasks with audio, and thus these tasks registered as a "pass." However, it is ultimately up to the researcher to determine what is acceptable system timing; this method provides a method of quantifying the system latency values to simplify the process of making these decisions.

			You may move the slider near the top of the window in order to display the original GUI elements you saw before clicking "Run". When clicking the checkbox close to "Override requirements", a small editor window appears, containing code for all requirements applied to the data. You may modify requirements there, as you see fit.

	====Visualizing Certification Test Results using GNUPlot====		====Visualizing Certification Test Results using GNUPlot====

Mellinger: /* See also */

2021-02-16T17:09:54Z

← Older revision		Revision as of 17:59, 3 September 2024
Line 443:		Line 443:
	[[User Reference:Module Command Line Options]], [[User Reference:Operator Module]]		[[User Reference:Module Command Line Options]], [[User Reference:Operator Module]]

	[[Category:Performance Measurement]][[Category:Data Analysis Tools]]		[[Category:Performance Measurement]][[Category:Data Analysis Tools]][[Category:Video]]

← Older revision		Revision as of 17:09, 16 February 2021
Line 399:		Line 399:
	[[User Reference:Module Command Line Options]], [[User Reference:Operator Module]]		[[User Reference:Module Command Line Options]], [[User Reference:Operator Module]]

	[[Category:Performance Measurement]][[Category:Data Analysis]]		[[Category:Performance Measurement]][[Category:Data Analysis Tools]]