|
Size: 9908
Comment:
|
Size: 12746
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| == Existing delays == The full description of this auditory dataset is available on this page: [[DatasetIntroduction|Introduction dataset]]. |
== Documented delays == Reminder: The full description of this auditory dataset is available on this page: [[DatasetIntroduction|Introduction dataset]]. |
| Line 13: | Line 13: |
| The delays we can expect between the generation of the sim trigger and the delivery in the ears are: | '''Delay #1''': Production of the sound |
| Line 15: | Line 15: |
| * '''Delay #1''': Production of the sound. <<BR>>The software generates the request to play a sound, which goes through the operating system, the sound card drivers and the sound card electronics. The sound card produces an analog sound signal that is sent in the MEG room and copied to * This is mostly due to the software running on the computer (stimulation software, operating system, sound card drivers, sound card electronics). The delay can be measured from the recorded files by comparing the triggers in the two channels: Delay''' between 11.5ms and 12.8ms''' (std = 0.3ms) This delay is '''not constant''', we will need to correct for it. |
* The stimulation software generates the request to play a sound, the corresponding trigger is recorded in the stim channel by the MEG acquisition software. * Then this request goes through different software layers (operating system, sound card drivers) and the sound card electronics. The sound card produces an analog sound signal that is sent at the same time to the subject and to MEG acquisition system. The acquisition software saves a copy of it in an audio channel together with the MEG recordings and the stim channel. * The delay can be measured from the recorded files by comparing the triggers in the stim channel and the actual sound in the audio channel. We measured delays''' between 11.5ms and 12.8ms''' (std = 0.3ms). These delays are '''not constant''', we should correct for them. Jitters in the stimulus triggers cause the different trials to be aligned incorrectly in time, hence "blurred" averaged responses. |
| Line 18: | Line 19: |
| '''Delay #2''': Transmission of the sound | |
| Line 19: | Line 21: |
| * '''Delay #2''': Transmission of the sound. Between when the sound card plays the sound and when the subject receives the sound in the ears. This is the time it takes for the transducer to convert the analog audio signal into a sound, plus the time it takes to the sound to travel through the air tubes from the transducer to the subject's ears. This delay cannot be estimated from the recorded signals: before the acquisition, we placed a sound meter at the extremity of the tubes to record when the sound is delivered. Delay '''between 4.8ms and 5.0ms''' (std = 0.08ms). At a sampling rate of 2400Hz, this delay can be considered '''constant''', we will not compensate for it. |
* The sound card plays the sound, the audio signal is sent with a cable to two transducers located in the MEG room, close to the subject. This causes no observable delay. |
| Line 22: | Line 23: |
| * '''Delay #3''': Recording of the signals. The CTF MEG systems have a constant delay of '''4 samples''' between the MEG/EEG channels and the analog channels (such as the audio signal UADC001), because of an anti-aliasing filtered that is applied to the first and not the second. This translate here to a '''constant delay''' of '''1.7ms'''. |
* The transducers convert the analog audio signal into a sound (air vibration). Then this sound is delivered to the subject's ears through air tubes. Those two operations cause a small delay. |
| Line 25: | Line 25: |
| * '''Delay #4''': Over-compensation of delay #1. When correcting of delay #1, the process we use to detect the beginning of the triggers on the audio signal (UADC001) sets the trigger in the middle of the ramp between silence and the beep. We "over-compensate" the delay #1 by 1.7ms. This can be considered as '''constant delay '''of about '''-1.7ms'''. |
* This delay cannot be estimated from the recorded signals: before the acquisition, we placed a sound meter at the extremity of the tubes to record when the sound is delivered. We measured delays '''between 4.8ms and 5.0ms''' (std = 0.08ms). At a sampling rate of 2400Hz, this delay can be considered '''constant''', we will not compensate for it. |
| Line 28: | Line 27: |
| * '''Uncorrected delays''': We will correct for the delay #1, and keep the other delays (#2, #3 and #4). After we compensate for delay #1 our MEG signals will have a '''constant delay '''of about 4.9 + 1.7 - 1.7 = '''4.9 ms'''. We decide not to compensate for those delays because they do not introduce any jitter in the responses and they are not going to change anything in the interpretation of the data. | '''Delay #3''': Recording of the signals |
| Line 30: | Line 29: |
| * The CTF MEG systems have a constant delay of '''4 samples''' between the MEG/EEG channels and the analog channels (such as the audio signal), because of an anti-aliasing filtered that is applied to the first and not the second. This translate here to a '''constant delay''' of '''1.7ms'''. | |
| Line 31: | Line 31: |
| <<BR>> | |
| Line 32: | Line 33: |
| {{attachment:delays_sketch.gif||height="142",width="712"}} | {{attachment:delays_sketch.gif||height="156",width="708"}} |
| Line 37: | Line 38: |
| * Right-click on Run01/Link to raw file > '''Stim '''> Display time series (stimuls channel, UDIO001) Right-click on Run01/Link to raw file > '''ADC V''' > Display time series (audio signal generated, UADC001) | Let's display simultaneously the stimulus channel and the audio signal. |
| Line 39: | Line 40: |
| * In the Record tab, set the duration of display window to '''0.200s'''. Jump to the third event in the "standard" category. | * Right-click AEF#01 link > '''Stim '''> Display time series: The audio channel is '''UADC001'''. * Right-click AEF#01 link > '''ADC V''' > Display time series: The audio channel is '''UDIO001'''. |
| Line 41: | Line 43: |
| * We can observe that there is a delay of about '''13ms''' between the time where the stimulus trigger is generated by the stimulation computer and the moment where the sound is actually played by the sound card of the stimulation computer ('''delay #1'''). This is matching the documentation of the experiment in the first section of this tutorial. . {{http://neuroimage.usc.edu/brainstorm/Tutorials/Auditory?action=AttachFile&do=get&target=stim1.gif|stim1.gif|height="282",width="590",class="attachment"}} |
* In the Record tab, set the duration of display window to '''0.200s'''. |
| Line 44: | Line 45: |
| == Selecting files to process == First thing to do is to define the files you are going to process. This is done easily by picking files or folders in the database explorer and dropping them in the empty list of the Process1 tab. |
* Jump to the third event in the "standard" category. |
| Line 47: | Line 47: |
| 1. Drag and drop the following nodes in the Process1 list: Right/ERF (recordings), Right (condition), and Subject01 (subject) . {{http://neuroimage.usc.edu/brainstorm/Tutorials/TutProcesses?action=AttachFile&do=get&target=files1.gif|files1.gif|class="attachment"}} * The number in the brackets next to each node represents the number of data files that where found in each of them. The node ERF "contains" only itself (1), Subject01/Right contains ERF and Std files (2), and Subject01 contains 2 conditions x 2 recordings (4). * The total number of files, ie. the sum of all those values, appears in the title of the panel "Files to process [7]". 1. The buttons on the left side allow you to select what type of file you want to process: Recordings, sources, time-frequency, other. Now select the second button "Sources". All the counts are updated and now reflect the number of sources files that are found for each node. . {{http://neuroimage.usc.edu/brainstorm/Tutorials/TutProcesses?action=AttachFile&do=get&target=files2.gif|files2.gif|class="attachment"}} 1. If you select the third button "Time-frequency", you would see "0" everywhere because there are no time-frequency decompositions in the database yet. . {{http://neuroimage.usc.edu/brainstorm/Tutorials/TutProcesses?action=AttachFile&do=get&target=files3.gif|files3.gif|class="attachment"}} 1. Now clear the list from all the files. You may either right-click on the list (popup menu ''Clear list''), or select all the nodes (holding ''Shift ''or ''Crtl ''key) and then press the ''Delete ''key. 1. Select both files Left/ERF and Right/ERF in the tree (holding ''Ctrl ''key), and put the in Process list. We are going to apply some functions on those two files. You cannot distinguish them after they are dropped in the list, because they are both referred as "ERP". If at some point you need to know what is in the list, just leave you mouse over a node for a few seconds, and a tooltip would give you information about it. Just like in the database explorer. . {{http://neuroimage.usc.edu/brainstorm/Tutorials/TutProcesses?action=AttachFile&do=get&target=files4.gif|files4.gif|class="attachment"}} |
* We can observe that there is a delay of about '''13ms''' between the time where the stimulus trigger is generated by the stimulation computer and the moment where the sound is actually played by the sound card of the stimulation computer ('''delay #1'''). <<BR>><<BR>> {{attachment:delays_evaluate.gif||height="241",width="631"}} |
| Line 59: | Line 49: |
| == Correction == * '''Delay #1''': We can detect the triggers from the analog audio signal (ADC V/UADC001) rather than using the events already detected by the CTF software from the stim channel (Stim/UDIO001). * Drag and drop '''Run01 '''and '''Run02 '''to the Process1 box. * Add '''twice''' the process "'''Events > Detect analog triggers'''". Once with event name="standard_fix" and reference event="standard". Once with event name="deviant_fix" and reference event="deviant". Set the other options as illustrated below: . {{http://neuroimage.usc.edu/brainstorm/Tutorials/Auditory?action=AttachFile&do=get&target=stim2.gif|stim2.gif|class="attachment"}} * Open Run01 (channel ADC V) to evaluate the correction that was performed by this process. If you look at the third trigger in the "standard" category, you can measure a 14.6ms delay between the original event "standard" and the new event "standard_fix". . {{http://neuroimage.usc.edu/brainstorm/Tutorials/Auditory?action=AttachFile&do=get&target=stim3.gif|stim3.gif|height="151",width="570",class="attachment"}} * Open '''Run01''' to re-organize the event categories: * '''Delete '''the unused event categories: '''standard''', '''deviant'''. * '''Rename '''standard_fix and deviant_fix to '''standard''' and '''deviant'''. * Open '''Run02''' and do the same cleaning operations: . {{http://neuroimage.usc.edu/brainstorm/Tutorials/Auditory?action=AttachFile&do=get&target=stim5.gif|stim5.gif|height="149",width="502",class="attachment"}} * '''Important note''': We compensated for the jittered delays (delay #1), but not for the other ones (delays #2, #3 and #4). There is still a''' constant 5ms delay''' between the stimulus triggers ("standard" and "deviant") and the time where the sound actually reaches the subject's ears. |
* What we want to do is to discard the existing triggers and replace them with new, more accurate ones created based on the audio signal. We need to detect the beginning of the sound on analog channel UDIO001. |
| Line 73: | Line 51: |
| === Sort analog events into event categories === Typically the analog channel contains events (like a photodiode signal) that do not contain information about which event is occurring. This can be rectified by matching the event marker from the acquisition with the events detected on the analog channel: |
* Note that the representation of the oscillation of the sound tone is really bad represented here. The frequency of this standard tone is 440Hz. This was correctly captured by the original recordings at 2400Hz, but not in the downsampled version we use in the tutorial for taster processing. It should still be good enough for performing the detection of the stimulus. |
| Line 76: | Line 53: |
| Run > Events > Combine stim/response | == Detection of the analog triggers == ==== Detecting the standard triggers ==== Run the detection of the "standard" audio triggers on channel UDIO001 for file AEF#01. |
| Line 78: | Line 57: |
| ignore ; B_AB ; A ; B | * Keep the same windows open as previously. * In the Record tab, select the menu '''File > Detect analog triggers'''. * This opens the Pipeline editor with the process '''Events > Detect analog triggers''' selected. This window will be introduced later, for now we will just use it to configure the process options. Configure it as illustrated below:<<BR>><<BR>> {{attachment:delays_detect.gif||height="497",width="558"}} |
| Line 80: | Line 61: |
| substitute ‘B’ with the photodiode event name | '''Explanation of the options''' (for future reference, you can skip this now): |
| Line 82: | Line 63: |
| substitute ‘A’ with the event name of interest | * '''Event name''': Name of the new event category created to store the detected triggers. <<BR>>We can start with the event "standard", and call the corrected triggers "standard_fix". * '''Channel name''': Channel on which to perform the detection (audio channel UADC001). * '''Time window''': Time segment on which you want to detect analog triggers. <<BR>>Leave the default time window or check the box "All file", it will do the same thing. * '''Amplitude threshold''': A sliding window screens all the file, and a trigger is set whenever the amplitude of the signal increases above X times the standard deviation of the signal over this sliding window. Increase this value if you want the detection to be less sensitive. * '''Min duration between two events''': If the event we want to detect is an oscillation, we don't want to detect a trigger at each cycle of this oscillation. After we detect one, we stop the detection for a short time. Use a value that is always between the duration of the stimulus (here 100ms) and the inter-stimulus interval (here > 700ms). * '''Apply band-pass filter before the detection''': Use this option if the effect you are trying to detect is more visible in a specific frequency band. In our case, the effect is obvious in the broadband signal, we don't need to apply any filter. * '''Reference''': If you have an approximation of the triggers timing, you can specify it here. Here we have the events "standard" and we want to detect a trigger in their neighborhood. <<BR>>If we do not use this option, the process creates only one new group with all the audio signals, without distinction between the deviant and standard tones. * '''Detect falling edge''' (instead of rising edge): Detects the end of the tone instead of the beginning. * '''Remove DC offset''': If the signal on which we perform the detection does not oscillate around zero or has a high continuous component, removing the average of the signal can improve the detection. * '''Enable classification''': Tries to classify automatically the different types of events that are detected based on the morphology of the signal in the neighborhood of the trigger. |
| Line 84: | Line 74: |
| == Button responses == Same thing with button responses: re-detect from Stim/UDIO001 |
==== Results of the detection ==== * Navigate through a few of the new "standard_fix" events to evaluate if the result is correct. You can observe that the corrected triggers are consistently detected after the rising partion of the audio signal, two samples after the last sample where the signal was flat. * This means that we are over-compensating by 3.3ms. But at least this delay is constant and will not affect the analysis. We can count this as a '''constant delay''' of '''-3.3ms'''.<<BR>><<BR>> {{attachment:delays_results.gif||height="237",width="520"}} |
| Line 87: | Line 78: |
| ==== Detecting the deviant triggers ==== * Repeat the same operation for the deviant tones. * In the Record tab, select the menu '''File > Detect analog triggers'''. <<BR>><<BR>> {{attachment:delays_deviant.gif||height="522",width="589"}} ==== Some cleaning ==== * We will only use the corrected triggers, we can delete the original ones for avoiding any confusion. * Delete the event groups "deviant" and "standard" (select them and press the '''Delete '''key). * Rename the group "deviant_fix" into "deviant" (double-click on the group name). * Rename the group "standard_fix" into "standard". * Close all: Answer YES to save the modifications.<<BR>><<BR>> {{attachment:delays_final.gif}} == Repeat on acquisition run #02 == Repeat all the exact same operations on the link to file''' AEF#02''': * Right-click AEF#01 link > '''Stim '''> Display time series: The audio channel is '''UADC001'''. * Right-click AEF#01 link > '''ADC V''' > Display time series: The audio channel is '''UDIO001'''. * In the Record tab, select menu '''File > Detect analog triggers''': '''standard_fix''' * In the Record tab, select menu '''File > Detect analog triggers''': '''deviant_fix''' * Check that the events are correctly detected. * Delete the event groups "deviant" and "standard" (select them and press the '''Delete '''key). * Rename the group "deviant_fix" into "deviant" (double-click on the group name). * Rename the group "standard_fix" into "standard". * Close all: Answer YES to save the modifications. == Delays after this correction == We compensated for the jittered delays (delay #1), but not for the other ones (delays #2, #3). The final delay between the production of "standard_fix" triggers and the moment when the subject gets the stimulus is now: delay #2 + delay #3 + over-compensation. '''Final constant delay''': 4.9 + 1.7 - 3.3 = '''3.3ms''' We decide not to compensate for those delays because they do not introduce any jitter in the responses and they are not going to change anything in the interpretation of the data. == Detection of the button responses == As we described in the previous tutorial, the '''button''' markers are also incorrect. The subject presses a button with the right index finger when a deviant is presented. Because of some issues with the way this CTF system saves the triggers, some are doubled (49 markers for 40 button presses). We don't really need to correct this category of events because we will not use them in the introduction tutorials, this is documented here for future reference. The digital channel Stim/'''UDIO001''' contains the inputs from the response button box (optic device, negligeable delay). Each bit of the value on this channel corresponds to the activation of one button. We can read this channel directy to get accurate timing for the button presses. * Right-click AEF#01 link > '''Stim '''> Display time series: The audio channel is '''UDIO001'''. * In the Record tab: Set the page duration to '''3 seconds'''. * Browse through a few '''button '''events, notice that some of them are doubled. <<BR>>Explanation: The CTF acquisition software may generate a trigger at the beginning of an epoch (remember that this file has been recorded as contiguous epochs of 1 second) when a stim line is in a non-zero state at the first sample of the epoch. When the button is still pressed when a new block of 1s starts, we get an erroneous trigger. <<BR>><<BR>> {{attachment:delays_button.gif||height="193",width="540"}} * Note on the DC removal: You may see the base value of the UDIO001 channel "below" the zero line. This is an effect of the DC correction that is applied on the fly to the recordings. The average over all the loaded page is averaged and subtracted, to center the signal on its reference line. To restore the real value, you can uncheck the [DC] button in the Record tab, or just remember that the reference line for a channel doesn't necessarily means "zero" when the [DC] removal option is on. * In the Record tab, select menu '''File > Read events from channel''': '''UDIO001 / Value''' <<BR>><<BR>> {{attachment:delays_button_detect.gif||height="312",width="583"}} * === Photodiode === |
|
| Line 89: | Line 124: |
| How to <<EmbedContent("http://neuroimage.usc.edu/bst/get_prevnext.php?prev=Tutorials/EventMarkers&next=Tutorials/ArtifactsFilter")>> |
<<EmbedContent("http://neuroimage.usc.edu/bst/get_prevnext.php?prev=Tutorials/EventMarkers&next=Tutorials/PipelineEditor")>> |
Tutorial 8: Stimulation delays
Authors: Francois Tadel, Elizabeth Bock
The event markers that are saved in the file might not accurate. In most cases, the stimulation triggers saved by the acquisition system indicate when the stimulation computer requested a stimulus to be presented. After this request, the equipment used to deliver the stimulus to the subject (projector, screen, sound card, electric or tactile device) always introduce some delays. Therefore, the stimulus triggers are saved before the instant when the subject actually receives the stimulus.
For accurate timing of the brain responses, it is very important to estimate those delays precisly and if possible to account for them in the analysis. This tutorial explains how to correct for the different types of delays in the case of an auditory study, if the output of the soundcard is saved together with the MEG/EEG recordings. A similar approach can be used in visual experiments using a photodiode.
Contents
Documented delays
Reminder: The full description of this auditory dataset is available on this page: Introduction dataset.
Delay #1: Production of the sound
- The stimulation software generates the request to play a sound, the corresponding trigger is recorded in the stim channel by the MEG acquisition software.
- Then this request goes through different software layers (operating system, sound card drivers) and the sound card electronics. The sound card produces an analog sound signal that is sent at the same time to the subject and to MEG acquisition system. The acquisition software saves a copy of it in an audio channel together with the MEG recordings and the stim channel.
The delay can be measured from the recorded files by comparing the triggers in the stim channel and the actual sound in the audio channel. We measured delays between 11.5ms and 12.8ms (std = 0.3ms). These delays are not constant, we should correct for them. Jitters in the stimulus triggers cause the different trials to be aligned incorrectly in time, hence "blurred" averaged responses.
Delay #2: Transmission of the sound
- The sound card plays the sound, the audio signal is sent with a cable to two transducers located in the MEG room, close to the subject. This causes no observable delay.
- The transducers convert the analog audio signal into a sound (air vibration). Then this sound is delivered to the subject's ears through air tubes. Those two operations cause a small delay.
This delay cannot be estimated from the recorded signals: before the acquisition, we placed a sound meter at the extremity of the tubes to record when the sound is delivered. We measured delays between 4.8ms and 5.0ms (std = 0.08ms). At a sampling rate of 2400Hz, this delay can be considered constant, we will not compensate for it.
Delay #3: Recording of the signals
The CTF MEG systems have a constant delay of 4 samples between the MEG/EEG channels and the analog channels (such as the audio signal), because of an anti-aliasing filtered that is applied to the first and not the second. This translate here to a constant delay of 1.7ms.
![[ATTACH]](/brainstorm/Tutorials/StimDelays?action=AttachFile&do=upload_form&ticket=0067242e77.774354d58efe1dedee3a044bd12fadf10669fd11&target=delays_sketch.gif "[ATTACH]"){kind=small}
Evaluation of the delay
Let's display simultaneously the stimulus channel and the audio signal.
Right-click AEF#01 link > Stim > Display time series: The audio channel is UADC001.
Right-click AEF#01 link > ADC V > Display time series: The audio channel is UDIO001.
In the Record tab, set the duration of display window to 0.200s.
- Jump to the third event in the "standard" category.
We can observe that there is a delay of about 13ms between the time where the stimulus trigger is generated by the stimulation computer and the moment where the sound is actually played by the sound card of the stimulation computer (delay #1).
- What we want to do is to discard the existing triggers and replace them with new, more accurate ones created based on the audio signal. We need to detect the beginning of the sound on analog channel UDIO001.
- Note that the representation of the oscillation of the sound tone is really bad represented here. The frequency of this standard tone is 440Hz. This was correctly captured by the original recordings at 2400Hz, but not in the downsampled version we use in the tutorial for taster processing. It should still be good enough for performing the detection of the stimulus.
Detection of the analog triggers
Detecting the standard triggers
Run the detection of the "standard" audio triggers on channel UDIO001 for file AEF#01.
- Keep the same windows open as previously.
In the Record tab, select the menu File > Detect analog triggers.
This opens the Pipeline editor with the process Events > Detect analog triggers selected. This window will be introduced later, for now we will just use it to configure the process options. Configure it as illustrated below:
Explanation of the options (for future reference, you can skip this now):
Event name: Name of the new event category created to store the detected triggers.
We can start with the event "standard", and call the corrected triggers "standard_fix".Channel name: Channel on which to perform the detection (audio channel UADC001).
Time window: Time segment on which you want to detect analog triggers.
Leave the default time window or check the box "All file", it will do the same thing.Amplitude threshold: A sliding window screens all the file, and a trigger is set whenever the amplitude of the signal increases above X times the standard deviation of the signal over this sliding window. Increase this value if you want the detection to be less sensitive.
Min duration between two events: If the event we want to detect is an oscillation, we don't want to detect a trigger at each cycle of this oscillation. After we detect one, we stop the detection for a short time. Use a value that is always between the duration of the stimulus (here 100ms) and the inter-stimulus interval (here > 700ms).
Apply band-pass filter before the detection: Use this option if the effect you are trying to detect is more visible in a specific frequency band. In our case, the effect is obvious in the broadband signal, we don't need to apply any filter.
Reference: If you have an approximation of the triggers timing, you can specify it here. Here we have the events "standard" and we want to detect a trigger in their neighborhood.
If we do not use this option, the process creates only one new group with all the audio signals, without distinction between the deviant and standard tones.Detect falling edge (instead of rising edge): Detects the end of the tone instead of the beginning.
Remove DC offset: If the signal on which we perform the detection does not oscillate around zero or has a high continuous component, removing the average of the signal can improve the detection.
Enable classification: Tries to classify automatically the different types of events that are detected based on the morphology of the signal in the neighborhood of the trigger.
Results of the detection
- Navigate through a few of the new "standard_fix" events to evaluate if the result is correct. You can observe that the corrected triggers are consistently detected after the rising partion of the audio signal, two samples after the last sample where the signal was flat.
This means that we are over-compensating by 3.3ms. But at least this delay is constant and will not affect the analysis. We can count this as a constant delay of -3.3ms.
Detecting the deviant triggers
- Repeat the same operation for the deviant tones.
In the Record tab, select the menu File > Detect analog triggers.
Some cleaning
- We will only use the corrected triggers, we can delete the original ones for avoiding any confusion.
Delete the event groups "deviant" and "standard" (select them and press the Delete key).
- Rename the group "deviant_fix" into "deviant" (double-click on the group name).
- Rename the group "standard_fix" into "standard".
Close all: Answer YES to save the modifications.
Repeat on acquisition run #02
Repeat all the exact same operations on the link to file AEF#02:
Right-click AEF#01 link > Stim > Display time series: The audio channel is UADC001.
Right-click AEF#01 link > ADC V > Display time series: The audio channel is UDIO001.
In the Record tab, select menu File > Detect analog triggers: standard_fix
In the Record tab, select menu File > Detect analog triggers: deviant_fix
- Check that the events are correctly detected.
Delete the event groups "deviant" and "standard" (select them and press the Delete key).
- Rename the group "deviant_fix" into "deviant" (double-click on the group name).
- Rename the group "standard_fix" into "standard".
- Close all: Answer YES to save the modifications.
Delays after this correction
We compensated for the jittered delays (delay #1), but not for the other ones (delays #2, #3). The final delay between the production of "standard_fix" triggers and the moment when the subject gets the stimulus is now: delay #2 + delay #3 + over-compensation.
Final constant delay: 4.9 + 1.7 - 3.3 = 3.3ms
We decide not to compensate for those delays because they do not introduce any jitter in the responses and they are not going to change anything in the interpretation of the data.
Detection of the button responses
As we described in the previous tutorial, the button markers are also incorrect. The subject presses a button with the right index finger when a deviant is presented. Because of some issues with the way this CTF system saves the triggers, some are doubled (49 markers for 40 button presses). We don't really need to correct this category of events because we will not use them in the introduction tutorials, this is documented here for future reference.
The digital channel Stim/UDIO001 contains the inputs from the response button box (optic device, negligeable delay). Each bit of the value on this channel corresponds to the activation of one button. We can read this channel directy to get accurate timing for the button presses.
Right-click AEF#01 link > Stim > Display time series: The audio channel is UDIO001.
In the Record tab: Set the page duration to 3 seconds.
Browse through a few button events, notice that some of them are doubled.
Explanation: The CTF acquisition software may generate a trigger at the beginning of an epoch (remember that this file has been recorded as contiguous epochs of 1 second) when a stim line is in a non-zero state at the first sample of the epoch. When the button is still pressed when a new block of 1s starts, we get an erroneous trigger.
- Note on the DC removal: You may see the base value of the UDIO001 channel "below" the zero line. This is an effect of the DC correction that is applied on the fly to the recordings. The average over all the loaded page is averaged and subtracted, to center the signal on its reference line. To restore the real value, you can uncheck the [DC] button in the Record tab, or just remember that the reference line for a channel doesn't necessarily means "zero" when the [DC] removal option is on.
In the Record tab, select menu File > Read events from channel: UDIO001 / Value
Photodiode
You can do similar things with a photodiode in the case of a visual experiment.