Somatosensory data for group analyses in the Frontiers Reseach Topic: From raw MEG/EEG to publication: how to perform MEG/EEG group analysis with free academic software.
- 1. CFIN, Aarhus University
If you use the data or the analysis pipeline, please refer to:
Andersen, L.M., 2018. Group Analysis in MNE-Python of Evoked Responses from a Tactile Stimulation Paradigm: A Pipeline for Reproducibility at Every Step of Processing, Going from Individual Sensor Space Representations to an across-Group Source Space Representation. Front. Neurosci. 12. https://doi.org/10.3389/fnins.2018.00006
Andersen, L.M., 2018. Group Analysis in FieldTrip of Time-Frequency Responses: A Pipeline for Reproducibility at Every Step of Processing, Going From Individual Sensor Space Representations to an Across-Group Source Space Representation. Front. Neurosci. 12. https://doi.org/10.3389/fnins.2018.00261
Version 2 only contains subjects 1, 18, 20 and a new version of the FreeSurfer folder. This is due to a (very) wrong co-registration for subject 1 and due to 18 and 20 having had their anatomy files mixed up. This has now been fixed. For all other subjects, please see version 1. Also, get the updated scripts from github instead at: https://github.com/ualsbombe/omission_frontiers.git
Unzipping the data
Data is compressed into twenty-two different zip-files, one for each of the twenty subjects, one for the FreeSurfer data, one for the scripts files . The easiest way to uncompress and prepare the analysis directories is to create a directory in your home folder called "analyses", which has a sub-directory called "omission_frontiers_BIDS-FieldTrip", which has a sub-directory called "data".
Thus, as an example, in my case, I should have the path: /home/lau/analyses/omission_frontiers_BIDS-FieldTrip/data
on a Linux system the path would be /home/your_name/analyses/omission_frontiers_BIDS-FieldTrip/data
on a macOS system the path would be /Users/your_name/analyses/omission_frontiers_BIDS-FieldTrip/data
on a Windows system the path would be C:\Users\your_name\analyses\omission_frontiers_BIDS-FieldTrip\data
Steps for unzipping:
1. Set up the folder above according to your operating system, following the examples above and substitute "your_name" for your user name.
2. Unzip each of the subject folders into the data folder (sub-01 - sub-20) (/home/your_name/analyses/omission_frontiers_BIDS-FieldTrip/data)
3. Also unzip the FreeSurfer folder into the data folder (/home/your_name/analyses/omission_frontiers_BIDS-FieldTrip/data)
4. Finally, unzip the scripts folder into /home/your_name/analyses/omission_frontiers_BIDS-FieldTrip/
Now you are ready to run the analyses.
The MEG data
Raw fif files are contained in the data folder, ordered by subject (n=20)
There is one recording for each subject, MaxFiltered, called oddball_absence-tsss-mc_meg.fif. These are split into three files with -1 and -2 being the remainder of the recording
Processed MRI data
For the MRI, only the segmented data are provided. This is to sufficient to make the volume conduction model and the source model, while protecting the subjects' identity
For Fieldtrip, there is an mri_segmented.mat for each subject, which is found in the meg (sic!) folder for each subject. This has been co-registered to the MEG data
For MNE-Python, the FreeSurfer directory should also be used, which contains a folder for each subject that contains surfaces (surf) and boundary element methods models (bem) that are used for source reconstruction in MNE-python. There is also a trans-file for each subject (oddball_absence_dense-trans.fif) in the meg folder specifying the co-registration between MEG and MRI coordinate systems for the MNE-Python analysis. Finally, the FreeSurfer folder also contains the labels for the cortical surface. This is not used in any of the analyses, but are supplied for interested users.
Each subject has a number of tsv-files:
*channel.tsv contain information about the channels in that recording
*events.tsv contain information about the events in that recording
removed_trial_indices.tsv contains information about which events were removed manually (NB! this is only used for the FieldTrip analysis)
ica_components.tsv contains information which independent component were removed manually (NB! this is only used for the FieldTrip analysis)
*scans_tsv contain information about the scans conducted
Please see Github for the updated scripts at: https://github.com/ualsbombe/omission_frontiers.git