We provide a number of derived data products based on this dataset. The technical documentation below describes how they are produced; the same material is also available as a single PDF.
As of 2024-02-22, we recommend using the derived data in the *_sync tables —
eeg_sync, fnirs_sync,
ekg_sync, and gsr_sync —
rather than the CSVs in the older derived-data releases listed at the bottom of this page.
The 2024-02-22 release fixes a number of issues with the 2023-08-28 version of the derived
data (see the 2024-02-22 update for details).
Derived Data Description
The synchronized EEG, fNIRS, EKG and GSR signals generated by the steps described in the previous section are located in the following tables:
eeg_sync
fnirs_sync
ekg_sync
gsr_sync
The column frequency indicates the frequency of the shared clock which is 200Hz by default. If we include other frequencies in the feature, the value in this column can be used to select the desired one.
Not all experiments may have data present in the tables due to a couple of primary reasons. Firstly, time constraints can result in certain tasks remaining incomplete in some experiments. Secondly, the recorded signals are compromised during certain tasks can also lead to the absence of signals in the tables.
In cases where only two participants participated in the sections, signals for the third participant are spurious but they were synchronized and saved to the sync tables for a computational choice. However, they can be filtered out by joining with the data_validity table.
the table below, the table below and the table below detail the mapping between the montage in the montage figure and the naming convention used in the EEG and fNIRS sync tables.
| EEG signal columns | Description (topological location of the subject’s brain) |
|---|---|
<subject>_eeg_AFF1h |
Left anterior frontal region |
<subject>_eeg_F7 |
Left frontal region |
<subject>_eeg_FC5 |
Left fronto-central region |
<subject>_eeg_C3 |
Left central region |
<subject>_eeg_T7 |
Left temporal region |
<subject>_eeg_TP9 |
Left temporal-parietal region |
<subject>_eeg_Pz |
Central parietal region |
<subject>_eeg_P3 |
Left parietal region |
<subject>_eeg_P7 |
Left parietal region |
<subject>_eeg_O1 |
Left occipital region |
<subject>_eeg_O2 |
Right occipital region |
<subject>_eeg_P8 |
Right parietal region |
<subject>_eeg_P4 |
Right parietal region |
<subject>_eeg_TP10 |
Right temporal-parietal region |
<subject>_eeg_Cz |
central region |
<subject>_eeg_C4 |
Right central region |
<subject>_eeg_T8 |
Right temporal region |
<subject>_eeg_FC6 |
Right fronto-central region |
<subject>_eeg_FCz |
Central fronto-central region |
<subject>_eeg_F8 |
Right frontal region |
<subject>_eeg_AFF2h |
Right anterior frontal region |
| fNIRS raw signal columns | Description (topological location of the subject’s brain) |
|---|---|
<subject>_fnirs_S1-D1_760 |
’F3-F5’: left frontal region |
<subject>_fnirs_S1-D2_760 |
’F3-F1’: left frontal region |
<subject>_fnirs_S2-D1_760 |
’Af7-F5’: left anterior frontal region |
<subject>_fnirs_S2-D3_760 |
’Af7-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D1_760 |
’Af3-F5’: left anterior frontal region |
<subject>_fnirs_S3-D3_760 |
’Af3-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D4_760 |
’Af3-Afz’: left anterior frontal region |
<subject>_fnirs_S4-D2_760 |
’Fz-F1’: left frontal region |
<subject>_fnirs_S4-D4_760 |
’Fz-Afz’: central frontal region |
<subject>_fnirs_S4-D5_760 |
’Fz-F2’: right frontal region |
<subject>_fnirs_S5-D3_760 |
’Fpz-Fp1’: left frontal polar region |
<subject>_fnirs_S5-D4_760 |
’Fpz-Afz’: central frontal polar region |
<subject>_fnirs_S5-D6_760 |
’Fpz-Fp2’: right frontal polar region |
<subject>_fnirs_S6-D4_760 |
’Af4-Afz’: right anterior frontal region |
<subject>_fnirs_S6-D6_760 |
’Af4-Fp2’: right anterior frontal region |
<subject>_fnirs_S6-D7_760 |
’Af4-F6’: right anterior frontal region |
<subject>_fnirs_S7-D5_760 |
’F4-F2’: right frontal region |
<subject>_fnirs_S7-D7_760 |
’F4-F6’: right frontal region |
<subject>_fnirs_S8-D6_760 |
’Af8-Fp2’: right anterior frontal region |
<subject>_fnirs_S8-D7_760 |
’Af8-F6’: right anterior frontal region |
<subject>_fnirs_S1-D1_850 |
’F3-F5’: left frontal region |
<subject>_fnirs_S1-D2_850 |
’F3-F1’: left frontal region |
<subject>_fnirs_S2-D1_850 |
’Af7-F5’: left anterior frontal region |
<subject>_fnirs_S2-D3_850 |
’Af7-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D1_850 |
’Af3-F5’: left anterior frontal region |
<subject>_fnirs_S3-D3_850 |
’Af3-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D4_850 |
’Af3-Afz’: left anterior frontal region |
<subject>_fnirs_S4-D2_850 |
’Fz-F1’: left frontal region |
<subject>_fnirs_S4-D4_850 |
’Fz-Afz’: central frontal region |
<subject>_fnirs_S4-D5_850 |
’Fz-F2’: right frontal region |
<subject>_fnirs_S5-D3_850 |
’Fpz-Fp1’: left frontal polar region |
<subject>_fnirs_S5-D4_850 |
’Fpz-Afz’: central frontal polar region |
<subject>_fnirs_S5-D6_850 |
’Fpz-Fp2’: right frontal polar region |
<subject>_fnirs_S6-D4_850 |
’Af4-Afz’: right anterior frontal region |
<subject>_fnirs_S6-D6_850 |
’Af4-Fp2’: right anterior frontal region |
<subject>_fnirs_S6-D7_850 |
’Af4-F6’: right anterior frontal region |
<subject>_fnirs_S7-D5_850 |
’F4-F2’: right frontal region |
<subject>_fnirs_S7-D7_850 |
’F4-F6’: right frontal region |
<subject>_fnirs_S8-D6_850 |
’Af8-Fp2’: right anterior frontal region |
<subject>_fnirs_S8-D7_850 |
’Af8-F6’: right anterior frontal region |
| fNIRS raw signal columns | Description (topological location of the subject’s brain) |
|---|---|
<subject>_fnirs_S1-D1_HbO |
’F3-F5’: left frontal region |
<subject>_fnirs_S1-D2_HbO |
’F3-F1’: left frontal region |
<subject>_fnirs_S2-D1_HbO |
’Af7-F5’: left anterior frontal region |
<subject>_fnirs_S2-D3_HbO |
’Af7-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D1_HbO |
’Af3-F5’: left anterior frontal region |
<subject>_fnirs_S3-D3_HbO |
’Af3-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D4_HbO |
’Af3-Afz’: left anterior frontal region |
<subject>_fnirs_S4-D2_HbO |
’Fz-F1’: left frontal region |
<subject>_fnirs_S4-D4_HbO |
’Fz-Afz’: central frontal region |
<subject>_fnirs_S4-D5_HbO |
’Fz-F2’: right frontal region |
<subject>_fnirs_S5-D3_HbO |
’Fpz-Fp1’: left frontal polar region |
<subject>_fnirs_S5-D4_HbO |
’Fpz-Afz’: central frontal polar region |
<subject>_fnirs_S5-D6_HbO |
’Fpz-Fp2’: right frontal polar region |
<subject>_fnirs_S6-D4_HbO |
’Af4-Afz’: right anterior frontal region |
<subject>_fnirs_S6-D6_HbO |
’Af4-Fp2’: right anterior frontal region |
<subject>_fnirs_S6-D7_HbO |
’Af4-F6’: right anterior frontal region |
<subject>_fnirs_S7-D5_HbO |
’F4-F2’: right frontal region |
<subject>_fnirs_S7-D7_HbO |
’F4-F6’: right frontal region |
<subject>_fnirs_S8-D6_HbO |
’Af8-Fp2’: right anterior frontal region |
<subject>_fnirs_S8-D7_HbO |
’Af8-F6’: right anterior frontal region |
<subject>_fnirs_S1-D1_HbR |
’F3-F5’: left frontal region |
<subject>_fnirs_S1-D2_HbR |
’F3-F1’: left frontal region |
<subject>_fnirs_S2-D1_HbR |
’Af7-F5’: left anterior frontal region |
<subject>_fnirs_S2-D3_HbR |
’Af7-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D1_HbR |
’Af3-F5’: left anterior frontal region |
<subject>_fnirs_S3-D3_HbR |
’Af3-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D4_HbR |
’Af3-Afz’: left anterior frontal region |
<subject>_fnirs_S4-D2_HbR |
’Fz-F1’: left frontal region |
<subject>_fnirs_S4-D4_HbR |
’Fz-Afz’: central frontal region |
<subject>_fnirs_S4-D5_HbR |
’Fz-F2’: right frontal region |
<subject>_fnirs_S5-D3_HbR |
’Fpz-Fp1’: left frontal polar region |
<subject>_fnirs_S5-D4_HbR |
’Fpz-Afz’: central frontal polar region |
<subject>_fnirs_S5-D6_HbR |
’Fpz-Fp2’: right frontal polar region |
<subject>_fnirs_S6-D4_HbR |
’Af4-Afz’: right anterior frontal region |
<subject>_fnirs_S6-D6_HbR |
’Af4-Fp2’: right anterior frontal region |
<subject>_fnirs_S6-D7_HbR |
’Af4-F6’: right anterior frontal region |
<subject>_fnirs_S7-D5_HbR |
’F4-F2’: right frontal region |
<subject>_fnirs_S7-D7_HbR |
’F4-F6’: right frontal region |
<subject>_fnirs_S8-D6_HbR |
’Af8-Fp2’: right anterior frontal region |
<subject>_fnirs_S8-D7_HbR |
’Af8-F6’: right anterior frontal region |
Derived data
Synchronization of EEG, EKG, GSR, and fNIRS Signals
In multimodal neuroimaging studies, synchronizing signals from multiple modalities is a crucial step to conducting comprehensive studies on all these modalities together. The discrepancy between EEG and fNIRS signals’ time series is an issue that researchers encounter frequently due to the limitations of recording hardware or the necessity to remove invalid signals. Additionally, these two modalities have distinct recording rates, further complicating their alignment. To facilitate comprehensive evaluation of EEG and fNIRS signals, it is essential to synchronize these two signals.
We plotted histograms of the EEG and fNIRS signals to check they were sampled at the expected hardware frequency (10Hz for fNIRS and 500Hz for EEG). This is important because the filtering step assumes samples are equally spaced. Having confirmed that, the synchronization process is a two-step approach involving the noise artifacts removal from the signals, followed by resampling and synchronization of the interpolated signals at the desired sampling rate.
Removing Noise in EEG Signals with Notch Filter
EEG signals often exhibit susceptibility to artifacts, an interference that can be attributed to several sources. For instance, physiological factors such as eye movements or blinks can induce such artifacts , as can environmental elements like fluorescent lighting or grounding complications .
Upon thorough examination and visualization of the raw EEG data, we identified a consistent 60 Hz electrical disturbance within the signal, along with corresponding harmonics. An anomalous peak was also noted around the 5 Hz mark, potentially attributable to a grounding irregularity or an other environmental factors.
With the aid of MNE-Python , we efficiently mitigated these intrusive noises by deploying a notch filter. The filter was configured with a frequency of 60 Hz, a transition bandwidth of 9 Hz, and notch widths of 2 Hz.
Mitigating Artifacts in fNIRS Signals Utilizing Bandpass Filter
fNIRS signals are often susceptible to motion artifacts (MA) stemming from physiological activities, including cardiac and respiratory disturbances. These artifacts become particularly noticeable in the measurement of oxyhemoglobin (HbO) and deoxyhemoglobin (HbR) concentrations within the signal channels.
To address these challenges, we employed a bandpass filter as an effective noise reduction strategy. The filter was calibrated in line with the recommendations provided by . With a low cutoff bandwidth of 0.01 Hz and a high cutoff bandwidth of 0.2 Hz for the 4th order Butterworth method, the filter was tailored to selectively allow signal components within this frequency range while attenuating components outside the range.
Pre-processing EKG and GSR Signals
To remove noise and improve peak-detection accuracy for EKG signals, we employed a finite impulse response (FIR) filter with 0.67 Hz low cutoff frequency, 45 Hz high cutoff frequency, and order of 1.5x the sampling rate (where sampling rate is 500 Hz) implemented by NeuroKit2 .
We removed noise and smoothed the GSR signals using a low-pass filter with a 3 Hz cutoff frequency and a 4th order Butterworth filter, both implemented by Neurokit2.
Synchronization of EEG, EKG, GSR, and fNIRS Signals
After the EEG, EKG, GSR, and fNIRS signals are pre-processed to remove noise, the signals are upsampled to 2000Hz using the FFT-based resampling method mne.filter.resample available in the Python MNE library .
For each experiment, we define a common clock with initial time starting 2 minutes before the beginning of the first task (rest state) and end time set to 2 minutes after the final task (typically Minecraft). We create equally spaced ticks in this clock at the frequency of 200Hz. Then, the signals are downsampled to this clock’s scale via linear interpolation.
Mapping to the Task Data
Mapping between signals and data will depend on the task being performed. For instance, one can choose to map a signal to the closest data observation or a collection of them. Therefore, we opted for providing the timestamp as a column in the synchronized signals tables so that they can be used for alignment with the task observations.
Description of deprecated derived data products (generated 2023-08-28)
The filtering and synchronization process of raw signals was updated to make it easier to use and reduce unnecessary complexities. For reference, below is a description of the derived data products prior to 2024-02-22, and how they were created.
Derived Data Description
The signals generated by this step correspond to the data in the following tables in the new SQLite3 database that was released 2024-02-22:
eeg_sync
fnirs_sync
ekg_sync
gsr_sync
The column frequency indicates the frequency of the shared clock which is 200Hz by default. If we include other frequencies in the feature, the value in this column can be used to select the desired one.
Derived Data Files
The following folders contain several versions of derived data at various synchronization frequencies:
fnirs_10hzcontains synchronized fNIRS signals and task data at 10 Hz sampling rate.fnirs_500hzcontains synchronized fNIRS signals and task data at 500 Hz sampling rate.eeg_500hzcontains synchronized EEG signals and task data at 500 Hz sampling rate.ekg_500hzcontains synchronized EKG signals and task data at 500 Hz sampling rate.gsr_500hzcontains synchronized GSR signals and task data at 500 Hz sampling rate.fnirs_eeg_ekg_gsr_120hzcontains synchronized fNIRS, EEG, EKG, and GSR signals and task data at 120 Hz sampling rate.fnirs_eeg_ekg_gsr_1200hzcontains synchronized fNIRS, EEG, EKG, and GSR signals and task data at 1200 Hz sampling rate.
Each derived data folder contains synchronized fNIRS, EEG, EKG, and/or GSR signals for each task and for the entire experiment for each experiment:
exp_*/
all.csv
rest_state.csv
finger_tapping.csv
affective_individual_lion.csv
affective_individual_tiger.csv
affective_individual_leopard.csv
affective_team.csv
ping_pong_competitive_lion_tiger.csv
ping_pong_competitive_leopard_cheetah.csv
ping_pong_cooperative.csv
minecraft_saturn_a.csv
minecraft_saturn_b.csv
Each experiment contains the following CSV files, with columns described in the section below:
all.csvcontains the synchronized signal of all participants for the entire recording sessions, including signals and data in all tasks.rest_state.csvcontains the synchronized signal and rest state task data.finger_tapping.csvcontains the synchronized signal and finger tapping task data.affective_individual_lion.csvcontains the synchronized signal and individual affective task data for participant using the Lion computer in the lab.affective_individual_tiger.csvcontains the synchronized signal and individual affective task data for participant using the Leopard computer in the lab.affective_individual_leopard.csvcontains the synchronized signal and individual affective task data for participant using the Leopard computer in the lab.affective_team.csvcontains the synchronized signal and team affective task data.ping_pong_competitive_lion_tiger.csvcontains the synchronized signal and ping pong competitive task data between participants sitting on Lion and Tiger stations.ping_pong_competitive_leopard_cheetah.csvcontains the synchronized signal and ping pong competitive task data between a participant sitting on Leopard station and an experimenter sitting on the Cheetah station.ping_pong_cooperative.csvcontains the synchronized signal and ping pong cooperative task data between three participants against an artificial intelligent agent.minecraft_hands_on_training.csvcontains the synchronized signal and Minecraft search-and-rescue hands-on training mission data.minecraft_saturn_a.csvcontains the synchronized signal and Minecraft search-and-rescue Saturn A mission data.minecraft_saturn_b.csvcontains the synchronized signal and Minecraft search-and-rescue Saturn B mission data.
Not all experiments may include the aforementioned CSV files, due to a couple of primary reasons. Firstly, time constraints can result in certain tasks remaining incomplete in some experiments. Secondly, instances where the experiment involves only two participants or the recorded signals are compromised during certain tasks can also lead to the absence of these CSV files.
Derived Data Columns Descriptions
The columns in each aforementioned CSV file (e.g., rest_state.csv, ping_pong_cooperative.csv) are detailed in the table below, the table below, the table below, the table below, the table below, the table below, the table below, the table below, the table below, the table below, and the table below.
| Channel | Description |
|---|---|
event_type |
Event labels for the rest state task. Event types include start_task signifying the start of the task, and end_task signifying the end of rest state task. |
| Channel | Description |
|---|---|
event_type |
Event labels for the finger tapping task. Event types include start_fingertapping_task signifying the start of the task and the practice period, individual for the period during which the participants must tap in rhythm by themselves, and team for the period during which the participants must tap in synchronized rhythm with other participants. |
countdown_timer |
This is the timer displayed to the participants on the monitor signifying the remaining duration of the task’s phase. |
lion_spacebar_pressed |
0 for when the participant on the Lion computer is not pressing and holding down on the spacebar, and 1 for when the participant is pressing and holding down the space bar. |
tiger_spacebar_pressed |
0 for when the participant on the Tiger computer is not pressing and holding down on the spacebar, and 1 for when the participant is pressing and holding down the space bar. |
leopard_spacebar_pressed |
0 for when the participant on the Leopard computer is not pressing and holding down on the spacebar, and 1 for when the participant is pressing and holding down the space bar. |
| Channel | Description |
|---|---|
event_type |
Event labels for the individual affective task. Event types include start_affective_task signifying the start of the task, intermediate_selection signifying when a participant selects an arousal rating or a valence rating after observing an image, and final_submission signifying when a participant submits the arousal and valence score for an image. For experiments recorded in April, 2023 onward, there are additional events, including show_blank_screen for when a participant’s monitor began rendering the blank, black screen, show_cross_screen for when the monitor began rendering the black background with a plus symbol in the middle of the screen to center the participant’s attention, show_image for when the monitor began rendering an image at the center of the screen in front of a black background, and show_rating_screen for when the monitor began rendering the arousal and valence rating screen at the center of the screen. |
image_path |
The image file that was rendered on the participants’ monitors. |
arousal_score |
The arousal score selected by the participant during the intermediate_selection and final_submission events. |
valence_score |
The valence score selected by the participant during the intermediate_selection and final_submission events. |
| Channel | Description |
|---|---|
lion_event_type |
Similar event types to Table the table below, but also include event show_observe_message signifying when the monitor displayed the message instructing the participants to quietly observe the image, show_discuss_message for when the monitor displayed the message instructing the participants to share and discuss their emotional experience with each other, and show_rater_selected_message for when the monitor displayed the message notifying the participant who has been selected to input the shared arousal and valence rating. The events come from the participant sitting on the Lion computer in the lab. |
tiger_event_type |
Similar to the event types of the participant sitting on the Lion computer, but the events come from the participant sitting on the Tiger computer. |
leopard_event_type |
Similar to the event types of the participant sitting on the Lion computer, but the events come from the participant sitting on the Leopard computer. |
image_path |
The image file that was rendered on the participants’ monitors. |
arousal_score |
The arousal score selected by the participant during the intermediate_selection and final_submission events. |
valence_score |
The valence score selected by the participant during the intermediate_selection and final_submission events. |
| Channel | Description |
|---|---|
player_&_station |
Player &’s station (Lion, Tiger, Leopard, or Cheetah). |
task_started |
Value 0 for when the task is in practice mode: the ball stayed fixed at the center of the screen, while the players were allowed to move the paddles along the vertical axis. Value 1 for when the task is not in practice mode: the ball moved and the players could score points against the other side. |
seconds |
The countdown match timer (seconds) displayed on the screen of each player. |
ball_position_x |
The x-axis coordinate of the ball’s top left pixel, with the lower number located on the left side of the screen, and the higher number on the right side. |
ball_position_y |
The y-axis coordinate of the ball’s top left pixel, with the lower number located toward the top of the screen, and the higher number toward the bottom. |
player_&_paddle_position_x |
The x-axis coordinate of player &’s paddle’s top left pixel, with the lower number located on the left side of the screen, and the higher number on the right side. The x-axis coordinate is fixed, and the lower number indicates that player &’s paddle was on the left side and the higher number indicates that player &’s paddle was on the right side. |
player_&_paddle_position_y |
The y-axis coordinate of player &’s paddle’s top left pixel, with the lower number located toward the top of the screen, and the higher number toward the bottom. |
player_&_score |
The current score for the player &. |
| Channel | Description |
|---|---|
player_&_station |
Player &’s station (Lion, Tiger, or Leopard). |
task_started |
Value 0 for when the task is in practice mode: the ball stayed fixed at the center of the screen, while the players were allowed to move the paddles along the vertical axis. Value 1 for when the task is not in practice mode: the ball moved and the players could score points against the other side. |
seconds |
The countdown match timer (seconds) displayed on the screen of each player. |
ball_position_x |
The x-axis coordinate of the ball’s top left pixel, with the lower number located on the left side of the screen, and the higher number on the right side. |
ball_position_y |
The y-axis coordinate of the ball’s top left pixel, with the lower number located toward the top of the screen, and the higher number toward the bottom. |
player_&_paddle_position_x |
The x-axis coordinate of player &’s paddle’s top left pixel, with the lower number located on the left side of the screen, and the higher number on the right side. The x-axis coordinate is fixed, and the lower number indicates that player &’s paddle was on the left side and the higher number indicates that player &’s paddle was on the right side. |
player_&_paddle_position_y |
The y-axis coordinate of player &’s paddle’s top left pixel, with the lower number located toward the top of the screen, and the higher number toward the bottom. |
ai_paddle_position_x |
The x-axis coordinate of the artificial intelligent agent’s paddle’s top left pixel, with the lower number located on the left side of the screen, and the higher number on the right side. The x-axis coordinate is fixed, and the artificial intelligent agent was on the right side. |
ai_paddle_position_y |
the y-axis coordinate of the artificial intelligent agent’s paddle’s top left pixel, with the lower number located toward the top of the screen, and the higher number toward the bottom. |
team_score |
The current score of the team of participants. |
ai_score |
The current score of the artificial intelligence agent. |
| Channel | Description |
|---|---|
points |
The current score of the team. The team scored points for rescuing victims in a search-and-rescue mission in Minecraft. |
| EEG signal columns | Description (topological location of the subject’s brain) |
|---|---|
<subject>_eeg_AFF1h |
Left anterior frontal region |
<subject>_eeg_F7 |
Left frontal region |
<subject>_eeg_FC5 |
Left fronto-central region |
<subject>_eeg_C3 |
Left central region |
<subject>_eeg_T7 |
Left temporal region |
<subject>_eeg_TP9 |
Left temporal-parietal region |
<subject>_eeg_Pz |
Central parietal region |
<subject>_eeg_P3 |
Left parietal region |
<subject>_eeg_P7 |
Left parietal region |
<subject>_eeg_O1 |
Left occipital region |
<subject>_eeg_O2 |
Right occipital region |
<subject>_eeg_P8 |
Right parietal region |
<subject>_eeg_P4 |
Right parietal region |
<subject>_eeg_TP10 |
Right temporal-parietal region |
<subject>_eeg_Cz |
central region |
<subject>_eeg_C4 |
Right central region |
<subject>_eeg_T8 |
Right temporal region |
<subject>_eeg_FC6 |
Right fronto-central region |
<subject>_eeg_FCz |
Central fronto-central region |
<subject>_eeg_F8 |
Right frontal region |
<subject>_eeg_AFF2h |
Right anterior frontal region |
<subject>_eeg_GSR |
Right hand |
<subject>_eeg_EKG |
4th Intercostal space |
| fNIRS raw signal columns | Description (topological location of the subject’s brain) |
|---|---|
<subject>_fnirs_S1-D1_760 |
’F3-F5’: left frontal region |
<subject>_fnirs_S1-D2_760 |
’F3-F1’: left frontal region |
<subject>_fnirs_S2-D1_760 |
’Af7-F5’: left anterior frontal region |
<subject>_fnirs_S2-D3_760 |
’Af7-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D1_760 |
’Af3-F5’: left anterior frontal region |
<subject>_fnirs_S3-D3_760 |
’Af3-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D4_760 |
’Af3-Afz’: left anterior frontal region |
<subject>_fnirs_S4-D2_760 |
’Fz-F1’: left frontal region |
<subject>_fnirs_S4-D4_760 |
’Fz-Afz’: central frontal region |
<subject>_fnirs_S4-D5_760 |
’Fz-F2’: right frontal region |
<subject>_fnirs_S5-D3_760 |
’Fpz-Fp1’: left frontal polar region |
<subject>_fnirs_S5-D4_760 |
’Fpz-Afz’: central frontal polar region |
<subject>_fnirs_S5-D6_760 |
’Fpz-Fp2’: right frontal polar region |
<subject>_fnirs_S6-D4_760 |
’Af4-Afz’: right anterior frontal region |
<subject>_fnirs_S6-D6_760 |
’Af4-Fp2’: right anterior frontal region |
<subject>_fnirs_S6-D7_760 |
’Af4-F6’: right anterior frontal region |
<subject>_fnirs_S7-D5_760 |
’F4-F2’: right frontal region |
<subject>_fnirs_S7-D7_760 |
’F4-F6’: right frontal region |
<subject>_fnirs_S8-D6_760 |
’Af8-Fp2’: right anterior frontal region |
<subject>_fnirs_S8-D7_760 |
’Af8-F6’: right anterior frontal region |
<subject>_fnirs_S1-D1_850 |
’F3-F5’: left frontal region |
<subject>_fnirs_S1-D2_850 |
’F3-F1’: left frontal region |
<subject>_fnirs_S2-D1_850 |
’Af7-F5’: left anterior frontal region |
<subject>_fnirs_S2-D3_850 |
’Af7-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D1_850 |
’Af3-F5’: left anterior frontal region |
<subject>_fnirs_S3-D3_850 |
’Af3-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D4_850 |
’Af3-Afz’: left anterior frontal region |
<subject>_fnirs_S4-D2_850 |
’Fz-F1’: left frontal region |
<subject>_fnirs_S4-D4_850 |
’Fz-Afz’: central frontal region |
<subject>_fnirs_S4-D5_850 |
’Fz-F2’: right frontal region |
<subject>_fnirs_S5-D3_850 |
’Fpz-Fp1’: left frontal polar region |
<subject>_fnirs_S5-D4_850 |
’Fpz-Afz’: central frontal polar region |
<subject>_fnirs_S5-D6_850 |
’Fpz-Fp2’: right frontal polar region |
<subject>_fnirs_S6-D4_850 |
’Af4-Afz’: right anterior frontal region |
<subject>_fnirs_S6-D6_850 |
’Af4-Fp2’: right anterior frontal region |
<subject>_fnirs_S6-D7_850 |
’Af4-F6’: right anterior frontal region |
<subject>_fnirs_S7-D5_850 |
’F4-F2’: right frontal region |
<subject>_fnirs_S7-D7_850 |
’F4-F6’: right frontal region |
<subject>_fnirs_S8-D6_850 |
’Af8-Fp2’: right anterior frontal region |
<subject>_fnirs_S8-D7_850 |
’Af8-F6’: right anterior frontal region |
| fNIRS raw signal columns | Description (topological location of the subject’s brain) |
|---|---|
<subject>_fnirs_S1-D1_HbO |
’F3-F5’: left frontal region |
<subject>_fnirs_S1-D2_HbO |
’F3-F1’: left frontal region |
<subject>_fnirs_S2-D1_HbO |
’Af7-F5’: left anterior frontal region |
<subject>_fnirs_S2-D3_HbO |
’Af7-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D1_HbO |
’Af3-F5’: left anterior frontal region |
<subject>_fnirs_S3-D3_HbO |
’Af3-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D4_HbO |
’Af3-Afz’: left anterior frontal region |
<subject>_fnirs_S4-D2_HbO |
’Fz-F1’: left frontal region |
<subject>_fnirs_S4-D4_HbO |
’Fz-Afz’: central frontal region |
<subject>_fnirs_S4-D5_HbO |
’Fz-F2’: right frontal region |
<subject>_fnirs_S5-D3_HbO |
’Fpz-Fp1’: left frontal polar region |
<subject>_fnirs_S5-D4_HbO |
’Fpz-Afz’: central frontal polar region |
<subject>_fnirs_S5-D6_HbO |
’Fpz-Fp2’: right frontal polar region |
<subject>_fnirs_S6-D4_HbO |
’Af4-Afz’: right anterior frontal region |
<subject>_fnirs_S6-D6_HbO |
’Af4-Fp2’: right anterior frontal region |
<subject>_fnirs_S6-D7_HbO |
’Af4-F6’: right anterior frontal region |
<subject>_fnirs_S7-D5_HbO |
’F4-F2’: right frontal region |
<subject>_fnirs_S7-D7_HbO |
’F4-F6’: right frontal region |
<subject>_fnirs_S8-D6_HbO |
’Af8-Fp2’: right anterior frontal region |
<subject>_fnirs_S8-D7_HbO |
’Af8-F6’: right anterior frontal region |
<subject>_fnirs_S1-D1_HbR |
’F3-F5’: left frontal region |
<subject>_fnirs_S1-D2_HbR |
’F3-F1’: left frontal region |
<subject>_fnirs_S2-D1_HbR |
’Af7-F5’: left anterior frontal region |
<subject>_fnirs_S2-D3_HbR |
’Af7-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D1_HbR |
’Af3-F5’: left anterior frontal region |
<subject>_fnirs_S3-D3_HbR |
’Af3-Fp1’: left anterior frontal region |
<subject>_fnirs_S3-D4_HbR |
’Af3-Afz’: left anterior frontal region |
<subject>_fnirs_S4-D2_HbR |
’Fz-F1’: left frontal region |
<subject>_fnirs_S4-D4_HbR |
’Fz-Afz’: central frontal region |
<subject>_fnirs_S4-D5_HbR |
’Fz-F2’: right frontal region |
<subject>_fnirs_S5-D3_HbR |
’Fpz-Fp1’: left frontal polar region |
<subject>_fnirs_S5-D4_HbR |
’Fpz-Afz’: central frontal polar region |
<subject>_fnirs_S5-D6_HbR |
’Fpz-Fp2’: right frontal polar region |
<subject>_fnirs_S6-D4_HbR |
’Af4-Afz’: right anterior frontal region |
<subject>_fnirs_S6-D6_HbR |
’Af4-Fp2’: right anterior frontal region |
<subject>_fnirs_S6-D7_HbR |
’Af4-F6’: right anterior frontal region |
<subject>_fnirs_S7-D5_HbR |
’F4-F2’: right frontal region |
<subject>_fnirs_S7-D7_HbR |
’F4-F6’: right frontal region |
<subject>_fnirs_S8-D6_HbR |
’Af8-Fp2’: right anterior frontal region |
<subject>_fnirs_S8-D7_HbR |
’Af8-F6’: right anterior frontal region |
Derived data
Synchronization of EEG, EKG, GSR, and fNIRS Signals
In multimodal neuroimaging studies, synchronizing signals from multiple modalities is a crucial step to conducting comprehensive studies on all these modalities together. The discrepancy between EEG and fNIRS signals’ time series is an issue that researchers encounter frequently due to the limitations of recording hardware or the necessity to remove invalid signals. Additionally, these two modalities have distinct recording rates, further complicating their alignment. To facilitate comprehensive evaluation of EEG and fNIRS signals, it is essential to synchronize these two signals.
The synchronization process is a two-step approach involving the noise artifacts removal from the signals, followed by resampling and synchronization of the interpolated signals at the desired sampling rate.
Removing Noise in EEG Signals with Notch Filter
EEG signals often exhibit susceptibility to artifacts, an interference that can be attributed to several sources. For instance, physiological factors such as eye movements or blinks can induce such artifacts , as can environmental elements like fluorescent lighting or grounding complications .
Upon thorough examination and visualization of the raw EEG data, we identified a consistent 60 Hz electrical disturbance within the signal, along with corresponding harmonics. An anomalous peak was also noted around the 5 Hz mark, potentially attributable to a grounding irregularity or an other environmental factors.
With the aid of MNE-Python , we efficiently mitigated these intrusive noises by deploying a notch filter. The filter was configured with a frequency of 60 Hz, a transition bandwidth of 9 Hz, and notch widths of 2 Hz.
Mitigating Artifacts in fNIRS Signals Utilizing Bandpass Filter
fNIRS signals are often susceptible to motion artifacts (MA) stemming from physiological activities, including cardiac and respiratory disturbances. These artifacts become particularly noticeable in the measurement of oxyhemoglobin (HbO) and deoxyhemoglobin (HbR) concentrations within the signal channels.
To address these challenges, we employed a bandpass filter as an effective noise reduction strategy. The filter was calibrated in line with the recommendations provided by . With a low cutoff bandwidth of 0.01 Hz and a high cutoff bandwidth of 0.2 Hz for the 4th order Butterworth method, the filter was tailored to selectively allow signal components within this frequency range while attenuating components outside the range.
Pre-processing EKG and GSR Signals
To remove noise and improve peak-detection accuracy for EKG signals, we employed a finite impulse response (FIR) filter with 0.67 Hz low cutoff frequency, 45 Hz high cutoff frequency, and order of 1.5x the sampling rate (where sampling rate is 500 Hz) implemented by NeuroKit2 .
We removed noise and smoothed the GSR signals using a low-pass filter with a 3 Hz cutoff frequency and a 4th order Butterworth filter, both implemented by Neurokit2.
Synchronization of EEG, EKG, GSR, and fNIRS Signals
After the EEG, EKG, GSR, and fNIRS signals are pre-processed to remove noise, the signals are resampled to a common sampling rate using the FFT-based resampling method mne.filter.resample available in the Python MNE library . To synchronize the signals, we generate a time series matching the common sampling rate of the resampled signals, with the first timestamp rounded to the nearest second. Then, the signals are interpolated to this generated time series via linear interpolation.
Synchronizing Task Data with EEG and fNIRS Resampled Signals
Understanding the relationship between participants’ behaviors, environmental stimuli, and neuroimaging data requires a precise synchronization of task data with the corresponding EEG and fNIRS signals. By aligning these data streams, we can examine the influence of environmental stimuli on the participants’ neuroimaging signals, which in turn, impact their behavior and task performance.
The process of integrating EEG and fNIRS signals with task data starts with grouping of signals by the tasks during which they were recorded, followed by the synchronization of the task data to the corresponding EEG and fNIRS signals.
Grouping EEG, EKG, GSR, and fNIRS Signals by Task
The preliminary step in our approach to synchronizing EEG, EKG, GSR, and fNIRS signals with the task data involves the grouping of the signals by the tasks during which the signals were recorded. The task data can be categorized into two distinct types: status-based and event-based data.
Status-based task data
This type of task data represent the current state of the task, such as task score. For each task, the grouping process of these data begins by including the signals recorded immediately before the task initiation and immediately following task completion. This ensures no data is overlooked at the boundaries of the task. Subsequently, all signals recorded between these two points are included, forming a complete set of signals associated with the task.
Event-based task data
This type of task data, on the other hand, correspond to specific events that occur during the task, such as affective task arousal or the submission of a valence score. For each task, we determine the EEG, EKG, GSR, and fNIRS entry associated with the first event and the last event. These signal entries, as well as all entries recorded between these points, are included into the data set related to the task.
Synchronizing Task Data with EEG, EKG, GSR, and fNIRS Signals
Having grouped the EEG, EKG, GSR, and fNIRS signals according to task type, we then proceed to synchronize these signal entries with their respective task data.
Status-based task data
The synchronization is accomplished by assigning the status data recorded closest in time to each EEG, EKG, GSR, and fNIRS signal entry. This method ensures that each EEG, EKG, GSR, and fNIRS entry is paired with the most representative status data.
Event-based task data
We assign each event data to the EEG, EKG, GSR, and fNIRS signal entry recorded at the time closest to the occurrence of the event. Those EEG, EKG, GSR, and fNIRS signal entries without a corresponding event data are left unassigned, signifying that no specific event occurred during these recordings.
Older derived data releases
We always recommend using the latest version of the derived data products, as older versions may have issues that are fixed in newer versions, and the documentation is only accurate for the newest version. However, we will continue to provide the older versions for as long as we feasibly can.
- Filtered synchronized data (generated 2023-08-28) (836 GB)
- Filtered synchronized data (1.1 TB). Uploaded 2023-07-19. See the 2023-07-19 update for details.
- Filtered synchronized data (168 GB). Uploaded 2023-06-14.