Contributions:ResponseTimeBox - Revision history

Wengelhardt: /* Latency */

2024-09-03T17:57:35Z

Latency

← Older revision		Revision as of 17:57, 3 September 2024
Line 122:		Line 122:
	</gallery>		</gallery>

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

Gladwellra at 21:09, 14 October 2022

2022-10-14T21:09:14Z

← Older revision		Revision as of 21:09, 14 October 2022
Line 114:		Line 114:
	[[File:RTBoxTime.png\| 1500 px\| thumb\| center \| Figure 2. Procedure for interpreting ResponseTime Box Time]]		[[File:RTBoxTime.png\| 1500 px\| thumb\| center \| Figure 2. Procedure for interpreting ResponseTime Box Time]]

	===Latency===		==Latency==
	The device has a fairly low latency, measured at 9.033 ± 6.3430 ms compared to the g.USBamp, a device that is generally accepted to have ~0 ms latency. To determine the device latency, trials were run where photodiodes were connected to both the ResponseTime Box and the g.USBamp. For the trials, the sampling rate was set to 4800 Hz and the block size was 50. The difference in time between the StimulusCode, which determined when the flashes would occur, and the ResponseTime box was determined to evaluate the video latency. The difference in time between the g.USB amp and the ResponseTime box was determined to evaluate the acquisition latency. Histograms showing both latencies are included below.		The device has a fairly low latency, measured at 9.033 ± 6.3430 ms compared to the g.USBamp, a device that is generally accepted to have ~0 ms latency. To determine the device latency, trials were run where photodiodes were connected to both the ResponseTime Box and the g.USBamp. For the trials, the sampling rate was set to 4800 Hz and the block size was 50. The difference in time between the StimulusCode, which determined when the flashes would occur, and the ResponseTime box was determined to evaluate the video latency. The difference in time between the g.USB amp and the ResponseTime box was determined to evaluate the acquisition latency. Histograms showing both latencies are included below.
	<gallery mode="packed" widths=400px heights=400px>		<gallery mode="packed" widths=400px heights=400px>

Gladwellra at 21:09, 14 October 2022

2022-10-14T21:09:01Z

← Older revision		Revision as of 21:09, 14 October 2022
Line 114:		Line 114:
	[[File:RTBoxTime.png\| 1500 px\| thumb\| center \| Figure 2. Procedure for interpreting ResponseTime Box Time]]		[[File:RTBoxTime.png\| 1500 px\| thumb\| center \| Figure 2. Procedure for interpreting ResponseTime Box Time]]

			===Latency===
	The device has a fairly low latency, measured at 9.033 ± 6.3430 ms compared to the g.USBamp, a device that is generally accepted to have ~0 ms latency. To determine the device latency, trials were run where photodiodes were connected to both the ResponseTime Box and the g.USBamp. For the trials, the sampling rate was set to 4800 Hz and the block size was 50. The difference in time between the StimulusCode, which determined when the flashes would occur, and the ResponseTime box was determined to evaluate the video latency. The difference in time between the g.USB amp and the ResponseTime box was determined to evaluate the acquisition latency. Histograms showing both latencies are included below.		The device has a fairly low latency, measured at 9.033 ± 6.3430 ms compared to the g.USBamp, a device that is generally accepted to have ~0 ms latency. To determine the device latency, trials were run where photodiodes were connected to both the ResponseTime Box and the g.USBamp. For the trials, the sampling rate was set to 4800 Hz and the block size was 50. The difference in time between the StimulusCode, which determined when the flashes would occur, and the ResponseTime box was determined to evaluate the video latency. The difference in time between the g.USB amp and the ResponseTime box was determined to evaluate the acquisition latency. Histograms showing both latencies are included below.
	<gallery mode="packed" widths=400px heights=400px>		<gallery mode="packed" widths=400px heights=400px>

Gladwellra at 21:08, 14 October 2022

2022-10-14T21:08:26Z

← Older revision		Revision as of 21:08, 14 October 2022
Line 74:		Line 74:
	===Device Time===		===Device Time===
	The device time is absolute (meaning the value reflects the total time the RTBox has been powered on) and is delivered in 6-bytes continuously or with every event. To find the millisecond value of the device time, it is necessary to compare it to the SourceTime state. Do this by first finding the value of the event time for the event of interest. It is 6-byte, so it occupies 48 bits and is split up into two states, RTEventTime1 and RTEventTime2. Find the value in RTContTime1 and RTContTime2 that most closely matches the event time. Take the index of this value and find the SourceTime at this index. The process is outlined below.		The device time is absolute (meaning the value reflects the total time the RTBox has been powered on) and is delivered in 6-bytes continuously or with every event. To find the millisecond value of the device time, it is necessary to compare it to the SourceTime state. Do this by first finding the value of the event time for the event of interest. It is 6-byte, so it occupies 48 bits and is split up into two states, RTEventTime1 and RTEventTime2. Find the value in RTContTime1 and RTContTime2 that most closely matches the event time. Take the index of this value and find the SourceTime at this index. The process is outlined below.


	===Event Time===		===Event Time===

Gladwellra at 21:07, 14 October 2022

2022-10-14T21:07:52Z

@@ Line 75: / Line 75: @@
 The device time is absolute (meaning the value reflects the total time the RTBox has been powered on) and is delivered in 6-bytes continuously or with every event. To find the millisecond value of the device time, it is necessary to compare it to the SourceTime state. Do this by first finding the value of the event time for the event of interest. It is 6-byte, so it occupies 48 bits and is split up into two states, RTEventTime1 and RTEventTime2. Find the value in RTContTime1 and RTContTime2 that most closely matches the event time. Take the index of this value and find the SourceTime at this index. The process is outlined below.
 ===Event Time===
@@ Line 120: / Line 111: @@
 The figure below shows the parallel port pin out. The ParallelPortFilter extension follows this paradigm, so using it means that only 8 pins are accessible for reading and writing at a time. With this extension, pins D0-D7 can be written to or read from. Settings for these pins will need to be adjusted in the ParallelPort tab in BCI2000.
 [[File:ParallelPort.png | 500 px |thumb|  center | Figure 7. Pin out for the parallel port]]
 [[Category:Contributions]][[Category:Extension]]

Gladwellra at 21:06, 14 October 2022

2022-10-14T21:06:32Z

← Older revision		Revision as of 21:06, 14 October 2022
Line 28:		Line 28:
	<youtube alignment="center" dimensions="700">https://youtu.be/Wy47CgEULII</youtube>		<youtube alignment="center" dimensions="700">https://youtu.be/Wy47CgEULII</youtube>
	<br>		<br>
	Event names have been updated to include "RT" at the front to aid in identification and avoid confusion		Event names have been updated to include "RT" at the front to aid in identification and avoid confusion
	==Integration into BCI2000==		==Integration into BCI2000==
	Compile the extension into your source module by enabling contributed extensions in your CMake configuration. You can do this by going into your root build folder and opening <code>Configure.sh.cmd</code>. In the CMake GUI, enable '''EXTENSIONS_RESPONSETIMEBOX''' and then click generate. Then recompile BCI2000. Once the extension is built into the source module, enable it by appending <code>--LogResponseTimeBox=1</code> along the source module line within the batch file.		Compile the extension into your source module by enabling contributed extensions in your CMake configuration. You can do this by going into your root build folder and opening <code>Configure.sh.cmd</code>. In the CMake GUI, enable '''EXTENSIONS_RESPONSETIMEBOX''' and then click generate. Then recompile BCI2000. Once the extension is built into the source module, enable it by appending <code>--LogResponseTimeBox=1</code> along the source module line within the batch file.

Gladwellra at 21:06, 14 October 2022

2022-10-14T21:06:11Z

← Older revision		Revision as of 21:06, 14 October 2022
Line 28:		Line 28:
	<youtube alignment="center" dimensions="700">https://youtu.be/Wy47CgEULII</youtube>		<youtube alignment="center" dimensions="700">https://youtu.be/Wy47CgEULII</youtube>
	<br>		<br>
			Event names have been updated to include "RT" at the front to aid in identification and avoid confusion
	==Integration into BCI2000==		==Integration into BCI2000==
	Compile the extension into your source module by enabling contributed extensions in your CMake configuration. You can do this by going into your root build folder and opening <code>Configure.sh.cmd</code>. In the CMake GUI, enable '''EXTENSIONS_RESPONSETIMEBOX''' and then click generate. Then recompile BCI2000. Once the extension is built into the source module, enable it by appending <code>--LogResponseTimeBox=1</code> along the source module line within the batch file.		Compile the extension into your source module by enabling contributed extensions in your CMake configuration. You can do this by going into your root build folder and opening <code>Configure.sh.cmd</code>. In the CMake GUI, enable '''EXTENSIONS_RESPONSETIMEBOX''' and then click generate. Then recompile BCI2000. Once the extension is built into the source module, enable it by appending <code>--LogResponseTimeBox=1</code> along the source module line within the batch file.

Gladwellra at 21:04, 14 October 2022

2022-10-14T21:04:35Z

← Older revision		Revision as of 21:04, 14 October 2022
Line 23:		Line 23:
	==Functional Description==		==Functional Description==
	Oftentimes, the reaction time of a subject is measured by calculating the interval between a stimulus and the subject's reaction. However, difficulty can arise when devices with high latency are used to collect the exact time of the subject's reaction, or when the device clock is mismatched with the computer clock. The RTBox is designed to consolidate the entire experiment by directly measuring the stimulus onset (audio or light), the button press(es), and the time interval simultaneously with essentially no latency, thereby circumnavigating the aforementioned difficulties.		Oftentimes, the reaction time of a subject is measured by calculating the interval between a stimulus and the subject's reaction. However, difficulty can arise when devices with high latency are used to collect the exact time of the subject's reaction, or when the device clock is mismatched with the computer clock. The RTBox is designed to consolidate the entire experiment by directly measuring the stimulus onset (audio or light), the button press(es), and the time interval simultaneously with essentially no latency, thereby circumnavigating the aforementioned difficulties.

			==Video Overview==
			<br>
			<youtube alignment="center" dimensions="700">https://youtu.be/Wy47CgEULII</youtube>
			<br>

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

Gladwellra at 16:08, 14 October 2022

2022-10-14T16:08:21Z

← Older revision		Revision as of 16:08, 14 October 2022
Line 82:		Line 82:
	===Event Time===		===Event Time===

	====~~EventTime1~~====		====RTEventTime1====
	This state will spike to the first 3 bytes of the current 6-byte device time whenever an event occurs (buttons, light, sound, or aux).		This state will spike to the first 3 bytes of the current 6-byte device time whenever an event occurs (buttons, light, sound, or aux).

	====~~EventTime2~~====		====RTEventTime2====
	This state will spike to the last 3 bytes of the current 6-byte device time whenever an event occurs (buttons, light, sound, or aux).		This state will spike to the last 3 bytes of the current 6-byte device time whenever an event occurs (buttons, light, sound, or aux).

	===Continuous Time===		===Continuous Time===

	====~~ConTime1~~====		====RTConTime1====
	This state updates continuously along with the first 3 bytes of the 6-byte device time.		This state updates continuously along with the first 3 bytes of the 6-byte device time.

	====~~ConTime2~~====		====RTConTime2====
	This state updates continuously along with the last 3 bytes of the 6-byte device time.		This state updates continuously along with the last 3 bytes of the 6-byte device time.

Gladwellra at 16:07, 14 October 2022

2022-10-14T16:07:51Z

← Older revision		Revision as of 16:07, 14 October 2022
Line 46:		Line 46:
	==State Variables==		==State Variables==

	===~~Button1~~===		===RTButton1===
	This state has a value of 1 when button 1 is pressed, or when TTL pin 1 is stimulated, and 0 when released.		This state has a value of 1 when button 1 is pressed, or when TTL pin 1 is stimulated, and 0 when released.

	===~~Button2~~===		===RTButton2===
	This state has a value of 1 when button 2 is pressed, or when TTL pin 2 is stimulated, and 0 when released.		This state has a value of 1 when button 2 is pressed, or when TTL pin 2 is stimulated, and 0 when released.

	===~~Button3~~===		===RTButton3===
	This state has a value of 1 when button 3 is pressed, or when TTL pin 3 is stimulated, and 0 when released.		This state has a value of 1 when button 3 is pressed, or when TTL pin 3 is stimulated, and 0 when released.

	===~~Button4~~===		===RTButton4===
	This state has a value of 1 when button 4 is pressed, or when TTL pin 4 is stimulated, and 0 when released.		This state has a value of 1 when button 4 is pressed, or when TTL pin 4 is stimulated, and 0 when released.

	===~~Light~~===		===RTLightEvent===
	This state will spike to value 1 when the photodiode detects light, or when TTL pin 6 is stimulated, then return to 0.		This state will spike to value 1 when the photodiode detects light, or when TTL pin 6 is stimulated, then return to 0.

	===~~Sound~~===		===RTSoundEvent===
	This state will spike to value 1 when the sound port detects sound, or when TTL pin 5 (low active) or 9 (high active) are stimulated, then return to 0.		This state will spike to value 1 when the sound port detects sound, or when TTL pin 5 (low active) or 9 (high active) are stimulated, then return to 0.

	===~~Aux~~===		===RTAuxEvent===
	This state will spike to value 1 when TTL pin 8 is stimulated, then return to 0.		This state will spike to value 1 when TTL pin 8 is stimulated, then return to 0.

	===Device Time===		===Device Time===
	The device time is absolute (meaning the value reflects the total time the RTBox has been powered on) and is delivered in 6-bytes continuously or with every event. To find the millisecond value of the device time, it is necessary to compare it to the SourceTime state. Do this by first finding the value of the event time for the event of interest. It is 6-byte, so it occupies 48 bits and is split up into two states, ~~EventTime1~~ and ~~EventTime2~~. Find the value in ~~ContTime1~~ and ~~ContTime2~~ that most closely matches the event time. Take the index of this value and find the SourceTime at this index. The process is outlined below.		The device time is absolute (meaning the value reflects the total time the RTBox has been powered on) and is delivered in 6-bytes continuously or with every event. To find the millisecond value of the device time, it is necessary to compare it to the SourceTime state. Do this by first finding the value of the event time for the event of interest. It is 6-byte, so it occupies 48 bits and is split up into two states, RTEventTime1 and RTEventTime2. Find the value in RTContTime1 and RTContTime2 that most closely matches the event time. Take the index of this value and find the SourceTime at this index. The process is outlined below.

	[[File:RTBoxTime.png\| 1500 px\| thumb\| center \| Figure 2. Procedure for interpreting ResponseTime Box Time]]		[[File:RTBoxTime.png\| 1500 px\| thumb\| center \| Figure 2. Procedure for interpreting ResponseTime Box Time]]