Contributions:Emotiv - Revision history

Mellinger: /* Functional Description */

2011-05-31T14:20:01Z

Functional Description

← Older revision		Revision as of 14:20, 31 May 2011
Line 20:		Line 20:
	The output from the Emotiv is in muV, however it has quite a large DC Offset of about 4000~4200 units. The remaining DC offset comes from such factors as stored potential in the subject, and offsets added in the library to facilitate plotting. As such, a 0.1 Hz high pass filter is applied in the source module to the output signal. This effectively eliminates extra DC Offset. You will notice a "Settling Time" before the signals all reach an approximate 0 DC Offset. This time is about 10 to 15 seconds. It would be advisable to wait until the signal has settled out before proceeding.		The output from the Emotiv is in muV, however it has quite a large DC Offset of about 4000~4200 units. The remaining DC offset comes from such factors as stored potential in the subject, and offsets added in the library to facilitate plotting. As such, a 0.1 Hz high pass filter is applied in the source module to the output signal. This effectively eliminates extra DC Offset. You will notice a "Settling Time" before the signals all reach an approximate 0 DC Offset. This time is about 10 to 15 seconds. It would be advisable to wait until the signal has settled out before proceeding.

	<!-- Emotiv is contained in the Contrib distribution ==Installation==		<!-- Emotiv is now contained in the Contrib distribution, does not need to be compiled separately
			==Installation==
	Compile the Emotiv module using [[Programming_Reference:Build_System#How_To_Build_Using_CMake\|CMake and your compiler]]. Currently only Visual Studio libraries for the Emotiv API are provided. The resulting Emotiv.exe should be placed in the prog directory automatically.		Compile the Emotiv module using [[Programming_Reference:Build_System#How_To_Build_Using_CMake\|CMake and your compiler]]. Currently only Visual Studio libraries for the Emotiv API are provided. The resulting Emotiv.exe should be placed in the prog directory automatically.
	Copy the '''edk.dll''' and '''edk_utils.dll''' found in http://{{SERVERNAME}}/svn/trunk/src/contrib/SignalSource/Emotiv/dll to the prog directory for the module to work.		Copy the '''edk.dll''' and '''edk_utils.dll''' found in http://{{SERVERNAME}}/svn/trunk/src/contrib/SignalSource/Emotiv/dll to the prog directory for the module to work.

	'''It is advisable to run the "Emotiv Testbench" alongside the BCI2000 module for a realtime visualization of the Emotiv Contact Quality and other important states.'''		'''It is advisable to run the "Emotiv Testbench" alongside the BCI2000 module for a realtime visualization of the Emotiv Contact Quality and other important states.'''-->
	-->

	==Parameters==		==Parameters==

Mellinger: /* Installation */

2011-05-31T14:19:17Z

Installation

← Older revision		Revision as of 14:19, 31 May 2011
Line 20:		Line 20:
	The output from the Emotiv is in muV, however it has quite a large DC Offset of about 4000~4200 units. The remaining DC offset comes from such factors as stored potential in the subject, and offsets added in the library to facilitate plotting. As such, a 0.1 Hz high pass filter is applied in the source module to the output signal. This effectively eliminates extra DC Offset. You will notice a "Settling Time" before the signals all reach an approximate 0 DC Offset. This time is about 10 to 15 seconds. It would be advisable to wait until the signal has settled out before proceeding.		The output from the Emotiv is in muV, however it has quite a large DC Offset of about 4000~4200 units. The remaining DC offset comes from such factors as stored potential in the subject, and offsets added in the library to facilitate plotting. As such, a 0.1 Hz high pass filter is applied in the source module to the output signal. This effectively eliminates extra DC Offset. You will notice a "Settling Time" before the signals all reach an approximate 0 DC Offset. This time is about 10 to 15 seconds. It would be advisable to wait until the signal has settled out before proceeding.

	==Installation==		<!-- Emotiv is contained in the Contrib distribution ==Installation==
	Compile the Emotiv module using [[Programming_Reference:Build_System#How_To_Build_Using_CMake\|CMake and your compiler]]. Currently only Visual Studio libraries for the Emotiv API are provided. The resulting Emotiv.exe should be placed in the prog directory automatically.		Compile the Emotiv module using [[Programming_Reference:Build_System#How_To_Build_Using_CMake\|CMake and your compiler]]. Currently only Visual Studio libraries for the Emotiv API are provided. The resulting Emotiv.exe should be placed in the prog directory automatically.
	Copy the '''edk.dll''' and '''edk_utils.dll''' found in http://{{SERVERNAME}}/svn/trunk/src/contrib/SignalSource/Emotiv/dll to the prog directory for the module to work.		Copy the '''edk.dll''' and '''edk_utils.dll''' found in http://{{SERVERNAME}}/svn/trunk/src/contrib/SignalSource/Emotiv/dll to the prog directory for the module to work.

	'''It is advisable to run the "Emotiv Testbench" alongside the BCI2000 module for a realtime visualization of the Emotiv Contact Quality and other important states.'''		'''It is advisable to run the "Emotiv Testbench" alongside the BCI2000 module for a realtime visualization of the Emotiv Contact Quality and other important states.'''
			-->

	==Parameters==		==Parameters==

Mellinger: /* Installation */

2011-05-31T14:17:39Z

Installation

← Older revision		Revision as of 14:17, 31 May 2011
Line 21:		Line 21:

	==Installation==		==Installation==
	Compile the Emotiv module using CMake and your compiler. Currently only Visual Studio libraries for the Emotiv API are provided. The resulting Emotiv.exe should be placed in the prog directory automatically.		Compile the Emotiv module using [[Programming_Reference:Build_System#How_To_Build_Using_CMake\|CMake and your compiler]]. Currently only Visual Studio libraries for the Emotiv API are provided. The resulting Emotiv.exe should be placed in the prog directory automatically.
	Copy the '''edk.dll''' and '''edk_utils.dll''' found in http://{{SERVERNAME}}/svn/trunk/src/contrib/SignalSource/Emotiv/dll to the prog directory for the module to work.		Copy the '''edk.dll''' and '''edk_utils.dll''' found in http://{{SERVERNAME}}/svn/trunk/src/contrib/SignalSource/Emotiv/dll to the prog directory for the module to work.

Bitrayne: /* Installation */

2011-02-28T16:25:13Z

Installation

← Older revision		Revision as of 16:25, 28 February 2011
Line 22:		Line 22:
	==Installation==		==Installation==
	Compile the Emotiv module using CMake and your compiler. Currently only Visual Studio libraries for the Emotiv API are provided. The resulting Emotiv.exe should be placed in the prog directory automatically.		Compile the Emotiv module using CMake and your compiler. Currently only Visual Studio libraries for the Emotiv API are provided. The resulting Emotiv.exe should be placed in the prog directory automatically.
	Copy the '''edk.dll''' and '''edk_utils.dll''' found in http://{{SERVERNAME}}/svn/~~branches/3.0~~/src/contrib/SignalSource/Emotiv/dll to the prog directory for the module to work.		Copy the '''edk.dll''' and '''edk_utils.dll''' found in http://{{SERVERNAME}}/svn/trunk/src/contrib/SignalSource/Emotiv/dll to the prog directory for the module to work.

	'''It is advisable to run the "Emotiv Testbench" alongside the BCI2000 module for a realtime visualization of the Emotiv Contact Quality and other important states.'''		'''It is advisable to run the "Emotiv Testbench" alongside the BCI2000 module for a realtime visualization of the Emotiv Contact Quality and other important states.'''

Bitrayne: /* Location */

2011-02-28T16:24:56Z

Location

← Older revision		Revision as of 16:24, 28 February 2011
Line 3:		Line 3:

	==Location==		==Location==
	http://{{SERVERNAME}}/svn/~~branches/3.0~~/src/contrib/SignalSource/Emotiv		http://{{SERVERNAME}}/svn/trunk/src/contrib/SignalSource/Emotiv/

	==Versioning==		==Versioning==

Gmilsap: Took out un-needed parameters - emotiv doesn't support acquisition through EmoComposer.

2010-07-08T14:11:44Z

Took out un-needed parameters - emotiv doesn't support acquisition through EmoComposer.

← Older revision		Revision as of 14:11, 8 July 2010
Line 33:		Line 33:
	* '''SourceChOffset''' is a list of DC offsets to be applied to the signal output before the signal leaves the source module. Due to the filtering done by the source module, '''a DC Offset of 0 is required for each channel'''		* '''SourceChOffset''' is a list of DC offsets to be applied to the signal output before the signal leaves the source module. Due to the filtering done by the source module, '''a DC Offset of 0 is required for each channel'''
	* '''SourceChGain''' is a list of signal gains which transform the signal output to muV. The API already provides output in muV. The SourceChGain '''must be set to 1 for each channel'''.		* '''SourceChGain''' is a list of signal gains which transform the signal output to muV. The API already provides output in muV. The SourceChGain '''must be set to 1 for each channel'''.
	* '''ConnectionType''' defines the way you would like to connect to the device. If you're using SDKLite, you'll need to connect to the device through the EmoComposer program. If you choose "EmoComposer" for this parameter, you must also set EmoComposerIP. If you're using a direct connection and you have a research edition of the Emotiv device connected to the same computer, just leave this parameter as "Direct". NOTE: EmoComposer connections are untested in this program, though they should work. It should be noted, however, that connecting to the device through EmoComposer may result in poor system performance due to the nature of a socketed connection to another program which is acquiring the signal.
	* '''EmoComposerIP''' is where you put the IP of the computer running the EmoComposer software. '''This parameter is NOT REQUIRED if you're using a "Direct" connection.''' See '''"ConnectionType"''' for more details.

	==States==		==States==

Gmilsap: /* States */ - Not floating point in next commit.

2010-07-07T15:44:32Z

States: - Not floating point in next commit.

← Older revision		Revision as of 15:44, 7 July 2010
Line 37:		Line 37:

	==States==		==States==
	* '''EmotivGyroX''' is a 32 bit ~~floating point number~~ which represents the x axis of the onboard Emotiv gyro.		* '''EmotivGyroX''' is a 16 bit integer which represents the x axis of the onboard Emotiv gyro.
	* '''EmotivGyroY''' is a 32 bit ~~floating point number~~ which represents the y axis of the onboard Emotiv gyro.		* '''EmotivGyroY''' is a 16 bit integer which represents the y axis of the onboard Emotiv gyro.
	~~These states are helpful for distinguishing~~ head ~~movements~~ and ~~using them to filter artifacts from your signal~~. ~~'''Note: These~~ states ~~are interpreted by~~ the ~~BCI2000 system~~ to ~~be 32 bit integers~~. ~~If you interpret these numbers at~~ the ~~bit level to be IEEE 754 Floating point numbers~~, ~~you get~~ the ~~gyro output~~.		The gyro values will idle around 29000. The actual range that the gyros output is undocumented in the Emotiv API. In practice, the floating point values given from the API appear to range from 0 to 4000 with the most extreme head movement and idle around 1800. The output value is multiplied by 16 then pushed into states. As such, the maximum value translates to about 64000 and the minimum to 0.

			To recalibrate the gyro, simply hold the head still for a few seconds.

	* '''EmotivCQXXX''' is a 4 bit integer which corresponds to the contact quality of a specific electrode on the Emotiv EPOC. The possible values are as follows:		* '''EmotivCQXXX''' is a 4 bit integer which corresponds to the contact quality of a specific electrode on the Emotiv EPOC. The possible values are as follows:

Gmilsap: /* Installation */

2010-07-01T17:19:06Z

Installation

← Older revision		Revision as of 17:19, 1 July 2010
Line 23:		Line 23:
	Compile the Emotiv module using CMake and your compiler. Currently only Visual Studio libraries for the Emotiv API are provided. The resulting Emotiv.exe should be placed in the prog directory automatically.		Compile the Emotiv module using CMake and your compiler. Currently only Visual Studio libraries for the Emotiv API are provided. The resulting Emotiv.exe should be placed in the prog directory automatically.
	Copy the '''edk.dll''' and '''edk_utils.dll''' found in http://{{SERVERNAME}}/svn/branches/3.0/src/contrib/SignalSource/Emotiv/dll to the prog directory for the module to work.		Copy the '''edk.dll''' and '''edk_utils.dll''' found in http://{{SERVERNAME}}/svn/branches/3.0/src/contrib/SignalSource/Emotiv/dll to the prog directory for the module to work.


	'''It is advisable to run the "Emotiv Testbench" alongside the BCI2000 module for a realtime visualization of the Emotiv Contact Quality and other important states.'''		'''It is advisable to run the "Emotiv Testbench" alongside the BCI2000 module for a realtime visualization of the Emotiv Contact Quality and other important states.'''

Gmilsap: Added more Emotiv states

2010-07-01T17:18:46Z

Added more Emotiv states

← Older revision		Revision as of 17:18, 1 July 2010
Line 42:		Line 42:
	These states are helpful for distinguishing head movements and using them to filter artifacts from your signal. '''Note: These states are interpreted by the BCI2000 system to be 32 bit integers. If you interpret these numbers at the bit level to be IEEE 754 Floating point numbers, you get the gyro output.		These states are helpful for distinguishing head movements and using them to filter artifacts from your signal. '''Note: These states are interpreted by the BCI2000 system to be 32 bit integers. If you interpret these numbers at the bit level to be IEEE 754 Floating point numbers, you get the gyro output.

	~~States regarding~~ contact quality~~, and artifact causing physical motions~~ are in ~~the works~~.		* '''EmotivCQXXX''' is a 4 bit integer which corresponds to the contact quality of a specific electrode on the Emotiv EPOC. The possible values are as follows:

			'''0:''' ''No Contact. Appears black in TestBench.''

			'''1:''' ''Very Bad Contact. Appears red in TestBench.''

			'''2:''' ''Poor Contact. Appears orange in TestBench.''

			'''3:''' ''Fair Contact. Appears yellow in TestBench.''

			'''4:''' ''Good Contact. Appears green in TestBench.''

	==Future Work==		==Future Work==

Gmilsap: /* Future Work */

2010-07-01T17:05:52Z

Future Work

← Older revision		Revision as of 17:05, 1 July 2010
Line 45:		Line 45:

	==Future Work==		==Future Work==
	A visualization panel which shows real time contact quality is in the works. This panel will allow the experimenter to see the current quality of the seating of the Emotiv on the subject's head, as well as important figures such as signal quality, head movement, and battery life of the device.

	Due to the nature of the signal processing that the Emotiv Software suite provides, it is possible to record facial movements such as eye blinks and jaw clenching into the states as well. This could allow for detailed filtering of signal artifacts from the output and could greatly enhance the quality of the final recording. These states are in the works.		Due to the nature of the signal processing that the Emotiv Software suite provides, it is possible to record facial movements such as eye blinks and jaw clenching into the states as well. This could allow for detailed filtering of signal artifacts from the output and could greatly enhance the quality of the final recording. These states are in the works.