Exercise:Logging Devices - Revision history

Jhill at 23:32, 13 November 2012

2012-11-13T23:32:10Z

← Older revision		Revision as of 23:32, 13 November 2012
Line 18:		Line 18:
	* To log the joystick, use <code>--LogJoystick=1</code>		* To log the joystick, use <code>--LogJoystick=1</code>
	* To log the 5DT Data Glove Ultra, use <code>--LogDataGlove=1</code> . '''Please be gentle with the data glove'''.		* To log the 5DT Data Glove Ultra, use <code>--LogDataGlove=1</code> . '''Please be gentle with the data glove'''.
	* To log the Nintendo Wiimote ~~(support for which is currently still unofficial but will be released soon)~~:		* To log the Nintendo Wiimote:
	*# Ensure that a Bluetooth dongle is attached.		*# Ensure that a Bluetooth dongle is attached.
	*# Press the (1) and (2) buttons simultaneously on the Wiimote. Lights will flash for several seconds, during which the Wiimote is receptive to pairing.		*# Press the (1) and (2) buttons simultaneously on the Wiimote. Lights will flash for several seconds, during which the Wiimote is receptive to pairing.
Line 27:		Line 27:
	*# The flag you need when starting your source module is <code>--LogWiimote=1</code>		*# The flag you need when starting your source module is <code>--LogWiimote=1</code>

	~~Support~~ for ~~the Tobii eyetracker will also be released soon~~.		The BCI2000 platform also supports Tobii eyetrackers via the EyetrackerLogger and various forms of EEG-synchronized audio and video acquisition via the AudioExtension and WebcamLogger. See our [[Contributions:Extensions\|contributed extensions]] page for more details.

	What other hardware devices do you think it would be useful for BCI2000 to support? If you have custom hardware you wish to integrate into BCI2000, you may be interested in the [[Programming_Tutorial:Implementing_an_Input_Logger\|programming tutorial on implementing an input logger]].		What other hardware devices do you think it would be useful for BCI2000 to support? If you have custom hardware you wish to integrate into BCI2000, you may be interested in the [[Programming_Tutorial:Implementing_an_Input_Logger\|programming tutorial on implementing an input logger]].

Jhill at 23:58, 14 May 2011

2011-05-14T23:58:42Z

← Older revision		Revision as of 23:58, 14 May 2011
Line 1:		Line 1:
			This exercise walks you through the process of connecting a human-interface device or other measurement device, and "logging" its output as state variables, synchronized with the brain signals you are recording.

	# Copy one of the existing batch files and use it as a template to write your own batch file.		# Copy one of the existing batch files and use it as a template to write your own batch file.
	# In your new batch file, open the Operator, SignalGenerator, DummySignalProcessing and DummyApplication.		# In your new batch file, open the Operator, SignalGenerator, DummySignalProcessing and DummyApplication.
Line 9:		Line 11:
	What sorts of neuroscientific questions could you address, by recording signals from human-interface devices, synchronized in real-time to brain signal recordings? What sort of experiments would you imagine doing? Which state variables would be relevant, and how would you process them?		What sorts of neuroscientific questions could you address, by recording signals from human-interface devices, synchronized in real-time to brain signal recordings? What sort of experiments would you imagine doing? Which state variables would be relevant, and how would you process them?

	Now we need a way of visualizing the state variable(s) you find most interesting. The exact way you do this may depend on the state you are interested in. A simple preliminary way might be to use the shell in the ''MatlabSignalProcessing'' module to repeatedly examine the variable <code>bci_States</code> or similarly, <code>self.states</code> from the shell of one of the Python modules. One of the most flexible ways would be to use, the [[ExpressionFilter]], which has been built into ''DummySignalProcessing'' for the purposes of ~~the workshop: states~~ can be drawn into the signal pipeline by entering their names into the '''Expressions''' parameter (found in the config dialog's '''Filtering''' tab). This also allows you to view the signal, if you fill the '''VisualizeExpressionFilter''' checkbox in the '''Visualize''' tab.		Now we need a way of visualizing the state variable(s) you find most interesting. The exact way you do this may depend on the state(s) you are interested in. A simple preliminary way might be to use the shell in the ''MatlabSignalProcessing'' module to repeatedly examine the global variable <code>bci_States</code>, or similarly, <code>self.states</code> from the shell of one of the Python modules. One of the most flexible ways would be to use the [[User_Reference:ExpressionFilter\|ExpressionFilter]], which has been built into ''DummySignalProcessing'' for the purposes of this exercise. State variables can be drawn into the signal pipeline by entering their names into the '''Expressions''' parameter (found in the config dialog's '''Filtering''' tab). This also allows you to view the signal, if you fill the '''VisualizeExpressionFilter''' checkbox in the '''Visualize''' tab. If the signals are out of the range of visualization, the ExpressionFilter allows arithmetic expressions that can be used to compensate for this. For example, <code>(MousePosX-1000)/1000</code> is a valid expression.

	The following devices are supported on the workshop installations. You can log as many devices simultaneously as the CPU and number of available USB ports will allow (just keep appending the flags). For whichever device(s) you choose, check to see which states are added.		The following devices are supported on the workshop installations. You can log as many devices simultaneously as the CPU and number of available USB ports will allow (just keep appending the flags). For whichever device(s) you choose, check to see which states are added.
Line 26:		Line 28:

	Support for the Tobii eyetracker will also be released soon.		Support for the Tobii eyetracker will also be released soon.

			What other hardware devices do you think it would be useful for BCI2000 to support? If you have custom hardware you wish to integrate into BCI2000, you may be interested in the [[Programming_Tutorial:Implementing_an_Input_Logger\|programming tutorial on implementing an input logger]].

Jhill at 23:48, 14 May 2011

2011-05-14T23:48:55Z

← Older revision		Revision as of 23:48, 14 May 2011
Line 6:		Line 6:
	# Edit your batch file such that the source module (in this case SignalGenerator) is started with the [[User Reference:Module Command Line Options\|command-line option]] <code>--LogMouse=1</code>		# Edit your batch file such that the source module (in this case SignalGenerator) is started with the [[User Reference:Module Command Line Options\|command-line option]] <code>--LogMouse=1</code>
	# Relaunch BCI2000 using the updated batch file, and check the States again. Note that there are now additional state variables, in accordance to what the [[User_Reference:Logging_Input\|documentation on the mouse and joystick loggers]] tells us to expect.		# Relaunch BCI2000 using the updated batch file, and check the States again. Note that there are now additional state variables, in accordance to what the [[User_Reference:Logging_Input\|documentation on the mouse and joystick loggers]] tells us to expect.
	# '''~~TODO~~''': ~~Work out a way to visualize one~~'s ~~chosen state (ExpressionFilter + visualizations~~, ~~Matlab, Python, ..~~.)
			What sorts of neuroscientific questions could you address, by recording signals from human-interface devices, synchronized in real-time to brain signal recordings? What sort of experiments would you imagine doing? Which state variables would be relevant, and how would you process them?

			Now we need a way of visualizing the state variable(s) you find most interesting. The exact way you do this may depend on the state you are interested in. A simple preliminary way might be to use the shell in the ''MatlabSignalProcessing'' module to repeatedly examine the variable <code>bci_States</code> or similarly, <code>self.states</code> from the shell of one of the Python modules. One of the most flexible ways would be to use, the [[ExpressionFilter]], which has been built into ''DummySignalProcessing'' for the purposes of the workshop: states can be drawn into the signal pipeline by entering their names into the '''Expressions''' parameter (found in the config dialog's '''Filtering''' tab). This also allows you to view the signal, if you fill the '''VisualizeExpressionFilter''' checkbox in the '''Visualize''' tab.

	The following devices are supported on the workshop installations. You can log as many devices simultaneously as the CPU and number of available USB ports will allow (just keep appending the flags). For whichever device(s) you choose, check to see which states are added.		The following devices are supported on the workshop installations. You can log as many devices simultaneously as the CPU and number of available USB ports will allow (just keep appending the flags). For whichever device(s) you choose, check to see which states are added.

Jhill at 23:27, 14 May 2011

2011-05-14T23:27:28Z

← Older revision		Revision as of 23:27, 14 May 2011
Line 10:		Line 10:
	The following devices are supported on the workshop installations. You can log as many devices simultaneously as the CPU and number of available USB ports will allow (just keep appending the flags). For whichever device(s) you choose, check to see which states are added.		The following devices are supported on the workshop installations. You can log as many devices simultaneously as the CPU and number of available USB ports will allow (just keep appending the flags). For whichever device(s) you choose, check to see which states are added.

	* To ~~use~~ the mouse or trackpad, use <code>--LogMouse=1</code>		* To log the mouse or trackpad, use <code>--LogMouse=1</code>
	* To ~~use~~ the joystick, use <code>--LogJoystick=1</code>		* To log the joystick, use <code>--LogJoystick=1</code>
	* To ~~use~~ the 5DT Data Glove Ultra, use <code>--LogDataGlove=1</code> . '''Please be gentle with the data glove'''.		* To log the 5DT Data Glove Ultra, use <code>--LogDataGlove=1</code> . '''Please be gentle with the data glove'''.
	* To ~~use~~ the Nintendo Wiimote (support for which is currently still unofficial but will be released soon):		* To log the Nintendo Wiimote (support for which is currently still unofficial but will be released soon):
	*# Ensure that a Bluetooth dongle is attached.		*# Ensure that a Bluetooth dongle is attached.
	*# Press the (1) and (2) buttons simultaneously on the Wiimote. Lights will flash for several seconds, during which the Wiimote is receptive to pairing.		*# Press the (1) and (2) buttons simultaneously on the Wiimote. Lights will flash for several seconds, during which the Wiimote is receptive to pairing.

Jhill at 23:26, 14 May 2011

2011-05-14T23:26:32Z

← Older revision		Revision as of 23:26, 14 May 2011
Line 12:		Line 12:
	* To use the mouse or trackpad, use <code>--LogMouse=1</code>		* To use the mouse or trackpad, use <code>--LogMouse=1</code>
	* To use the joystick, use <code>--LogJoystick=1</code>		* To use the joystick, use <code>--LogJoystick=1</code>
	* To use the 5DT Data Glove Ultra, use <code>--LogDataGlove=1</code>		* To use the 5DT Data Glove Ultra, use <code>--LogDataGlove=1</code> . '''Please be gentle with the data glove'''.
	* To use the Nintendo Wiimote (support for which is currently still unofficial but will be released soon):		* To use the Nintendo Wiimote (support for which is currently still unofficial but will be released soon):
	*# Ensure that a Bluetooth dongle is attached.		*# Ensure that a Bluetooth dongle is attached.

Jhill at 23:23, 14 May 2011

2011-05-14T23:23:52Z

← Older revision		Revision as of 23:23, 14 May 2011
Line 4:		Line 4:
	# In the Operator, open the ''View'' menu and select ''States''.		# In the Operator, open the ''View'' menu and select ''States''.
	# Note down the names of the state variables, then quit BCI2000 again.		# Note down the names of the state variables, then quit BCI2000 again.
	# Edit your batch file such that the source module (in this case SignalGenerator) is started with the [[~~User_Reference~~:~~Module_Command_Line_Options~~ command-line option]] <code>--LogMouse=1</code>		# Edit your batch file such that the source module (in this case SignalGenerator) is started with the [[User Reference:Module Command Line Options\|command-line option]] <code>--LogMouse=1</code>
	# Relaunch BCI2000 using the updated batch file, and check the States again. Note that there are now additional state variables, in accordance to what the [[User_Reference:Logging_Input documentation on the mouse and joystick loggers]] tells us to expect.		# Relaunch BCI2000 using the updated batch file, and check the States again. Note that there are now additional state variables, in accordance to what the [[User_Reference:Logging_Input\|documentation on the mouse and joystick loggers]] tells us to expect.
	# '''TODO''': Work out a way to visualize one's chosen state (ExpressionFilter + visualizations, Matlab, Python, ...)		# '''TODO''': Work out a way to visualize one's chosen state (ExpressionFilter + visualizations, Matlab, Python, ...)

Jhill at 23:18, 14 May 2011

2011-05-14T23:18:49Z

New page

# Copy one of the existing batch files and use it as a template to write your own batch file.
# In your new batch file, open the Operator, SignalGenerator, DummySignalProcessing and DummyApplication.
# Launch BCI2000 using your new batch file.
# In the Operator, open the ''View'' menu and select ''States''.
# Note down the names of the state variables, then quit BCI2000 again.
# Edit your batch file such that the source module (in this case SignalGenerator) is started with the [[User_Reference:Module_Command_Line_Options command-line option]] <code>--LogMouse=1</code>
# Relaunch BCI2000 using the updated batch file, and check the States again. Note that there are now additional state variables, in accordance to what the [[User_Reference:Logging_Input documentation on the mouse and joystick loggers]] tells us to expect.
# '''TODO''': Work out a way to visualize one's chosen state (ExpressionFilter + visualizations, Matlab, Python, ...)

The following devices are supported on the workshop installations. You can log as many devices simultaneously as the CPU and number of available USB ports will allow (just keep appending the flags). For whichever device(s) you choose, check to see which states are added.

* To use the mouse or trackpad, use <code>--LogMouse=1</code>
* To use the joystick, use <code>--LogJoystick=1</code>
* To use the 5DT Data Glove Ultra, use <code>--LogDataGlove=1</code>
* To use the Nintendo Wiimote (support for which is currently still unofficial but will be released soon):
*# Ensure that a Bluetooth dongle is attached.
*# Press the (1) and (2) buttons simultaneously on the Wiimote. Lights will flash for several seconds, during which the Wiimote is receptive to pairing.
*# Launch <code>ConnectWiimotes.exe</code>
*# Wait for the program to find the Wiimote and pair with it.
*# Since the Windows XP Bluetooth implementation is flaky, verify that the device is connected using the Start menu -> Control Panel -> Bluetooth Devices. You should see an entry for the Wiimote there: if it says "connected" underneath, connection has succeeded. If the word "connected" is absent, it has failed: close the control panel, re-run <code>ConnectWiimote.exe</code>, and re-open the control panel to verify. Repeat until it works.
*# The Wiimote will now stay connected across multiple BCI2000 sessions, but there will be a constant drain on the batteries. Therefore, please disconnect it as soon as you are no longer using it (go to the control panel again, highlight the Wiimote and click "Remove").
*# The flag you need when starting your source module is <code>--LogWiimote=1</code>

Support for the Tobii eyetracker will also be released soon.