|
Size: 18810
Comment:
|
Size: 25778
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from TutMindNeuromag = Import and process Neuromag raw recordings = This tutorial describes how to process raw Neuromag recordings. It is based on median nerve stimulation acquired at MGH in 2005 with a Neuromag Vectorview 306 system. The sample dataset contains the results for one subject for both arms. This document shows what to do step by step, but does not really explain what is happening, the meaning of the different options or processes, the issues or bugs you can encounter, and does not provide an exhaustive description of the software features. Those topics are introduced in the basic tutorials based on CTF recordings; so make sure that you followed all those initial tutorials before going through this one. The script file '''tutorial_mind_neuromag.m''' in the brainstorm3/toolbox/script folder performs exactly the same tasks automatically, without any user interaction. Please have a look at this file if you plan to write scripts to process recordings in .fif format. <<TableOfContents(2)>> |
= Elekta-Neuromag tutorial: Median nerve stimulation = This tutorial describes how to process continuous Elekta-Neuromag MEG recordings. It is based on median nerve stimulation acquired at the Massachusetts General Hospital in 2005 with a Neuromag Vectorview 306 system. The sample dataset contains the results for one subject for both arms: 18 minutes, 300 stimulations per arm. Note that the operations used here are not detailed, the goal of this tutorial is not to introduce Brainstorm to new users. For in-depth explanations of the interface and theoretical foundations, please refer to the [[http://neuroimage.usc.edu/brainstorm/Tutorials#Get_started|introduction tutorials]]. <<TableOfContents(3,2)>> <<Include(DatasetMedianNerveNeuromag, , from="\<\<HTML\(\<!-- START-PAGE --\>\)\>\>", to="\<\<HTML\(\<!-- STOP-SHORT --\>\)\>\>")>> |
| Line 12: | Line 11: |
| * It is considered that you followed all the basic tutorials and that you already have a fully working copy of Brainstorm installed on your computer. * Go to the [[http://neuroimage.usc.edu/brainstorm3_register/download.php|Download]] page of this website, and dowload the file "bst_sample_mind_neuromag.zip". * Unzip it in a folder that is not in any of the Brainstorm folders (program folder or database folder). This is really important that you always keep your original data files in a separate folder: the program folder can be deleted when updating the software, and the contents of the database folder is supposed to be manipulated only by the program itself. |
* '''Requirements''': You have already followed all the basic tutorials and you have a working copy of Brainstorm installed on your computer. * Go to the [[http://neuroimage.usc.edu/bst/download.php|Download]] page of this website and download the file '''sample_neuromag.zip''' * Unzip it in a folder that is not in any of the Brainstorm folders (program folder or database folder) |
| Line 16: | Line 15: |
| * Select the menu File > Create new protocol. * Name it "!TutorialNeuromag", and select all the options as illustrated: No default anatomy, Use individual anatomy, Use one channel file per subject (we have only one run, it's possible to share the channels positions and head models between diffrerent conditions).<<BR>><<BR>> {{attachment:createProtocol.gif}} == Importing anatomy == === Create the subject === * Select the "Anatomy" exploration mode (first button in the toolbar above the database explorer). * Right-click on the protocol node and select "New subject".<<BR>><<BR>> {{attachment:createSubjectMenu.gif}} * You can leave the default name "Subject01" and the default options. Then click on Save.<<BR>><<BR>> {{attachment:createSubject.gif}} === Import the MRI === * Right-click on the subject node, and select "Import MRI". Select the file: sample_mind_neuromag/anatomy/T1.mri<<BR>><<BR>> {{attachment:mriImportMenu.gif}} {{attachment:mriFile.gif}} * The orientation of the MRI is already ok, you just have to mark all the six fiducial points, as explained in the following wiki page: [[CoordinateSystems|Coordinate systems]]. Click on save button when you're done.<<BR>><<BR>> {{attachment:fiducials.gif}} * If at some point you do not see the files you've just imported in the database explorer, you just need to refresh the display: by pressing F5, or using the menu File > Refresh tree display. === Import the surfaces === * Right-click again on the subject node, and select "Import surfaces". Select the "!FreeSurfer surfaces" file type, and select all the surface files at once, holding the SHIFT or CTRL buttons. Click on Open.<<BR>><<BR>> {{attachment:surfaceFiles.gif}} * Answer "Yes" to the question "Align surfaces with MRI now?". You should see the following nodes in the database.<<BR>><<BR>> {{attachment:surfListInit.gif}} * "outer skin" = Head, used for surfaces/MRI registration * "inner skull" = Internal surface of the skull, used for the computation of the "overlapping spheres" forward model * "lh" = Left hemisphere * "rh" = Right hemisphere * "pial" = External cortical surface = grey matter/CSF interface (used for source estimation) * "white" = External white matter surface = interface between the grey and the white matter (not used in this tutorial) * Downsample the two pial and the two white surfaces to 7,500 vertices each (right-click > Less vertices) * Merge the two downsampled hemispheres of the pial surface (select both lh.pial_7500 and rh.pial_7500 files, right-click > Merge surfaces). Rename the new surface in "cortex". * Do the same with the white matter. Call the result "white". * Delete all the intermediate lh and rh surfaces. Rename the head and the inner skull with shorter names. Display all the surfaces and play with the colors and transparency to check that everything what imported correctly. You should obtain something like this:<<BR>><<BR>> {{attachment:surfListFinal.gif}} {{attachment:surfTest.gif}} == Importing MEG recordings == * Select the "Functional data / sorted by subject" exploration mode (second button in the toolbar above the database explorer). * Right click on the subject, select Import MEG/EEG. Select the "Neuromag FIFF" file type, and open the only .fif file in the folder sample_mind_neuromag/data.<<BR>><<BR>> {{attachment:megImportMenu.gif}} * Select "Event channel" when asked about the events.<<BR>><<BR>> {{attachment:eventsImport.gif}} * You have then to select from which technical track you want to read the events. <<BR>><<BR>> {{attachment:eventsChannels.gif}} |
* Menu File > Create new protocol > '''TutorialNeuromag''', with the following options: * '''No, use individual anatomy''', * '''No, use one channel file per run'''.<<BR>><<BR>> {{attachment:createProtocol.gif||width="347",height="372"}} == Import the anatomy == * Right-click on the TutorialNeuromag folder > New subject > Subject01 (leave all the defaults).<<BR>><<BR>> {{attachment:createSubjectMenu.gif||width="343",height="165"}} {{attachment:createSubject.gif||width="296",height="309"}} * Right-click on the subject node > Import anatomy folder: * Set the file format: "FreeSurfer folder" * Select the folder: '''sample_neuromag/anatomy''' * Number of vertices of the cortex surface: 15000 (default value) <<BR>><<BR>> {{attachment:mriImportMenu.gif||width="180",height="224"}} {{attachment:mriFile.gif||width="362",height="167"}} * Click on the link "'''Click here to compute MNI transformation'''". * Set the 3 required fiducial points (indicated in MRI coordinates): * NAS: x=131, y=232, z=123 * LPA: x=48, y=136, z=74 * RPA: x=204, y=131, z=67 * At the end of the process, make sure that the file "cortex_15000V" is selected (downsampled pial surface, that will be used for the source estimation). If it is not, double-click on it to select it as the default cortex surface.<<BR>><<BR>> {{attachment:anatomy.gif||width="400",height="248"}} == Access the recordings == === Link the recordings === * Switch to the "functional data" view, the middle button in the toolbar above the database explorer. * Right click on the Subject01 > '''Review raw file''': <<BR>><<BR>> {{attachment:reviewMenu.gif||width="210",height="159"}} {{attachment:reviewFile.gif||width="427",height="160"}} * Select the file format: '''MEG/EEG: Elekta-Neuromag (*.fif)''' * Pick the file: '''sample_neuromag/data/mind004_050924_median01_raw.fif''' * Select "Event channel" when asked about the events.<<BR>><<BR>> {{attachment:eventsImport.gif||width="280",height="157"}} * Then you have to select from which technical tracks you want to read the events. <<BR>><<BR>> {{attachment:eventsChannels.gif||width="375",height="165"}} |
| Line 51: | Line 41: |
| * STI 001: Contains the onsets of the electric stimulation of the '''right '''arm. * STI 002: Contains the onsets of the electric stimulation of the '''left '''arm. * Those are not standard settings, they depend on your acquisition setup. In most cases, you would rather import "events" defined with the Neuromag acquisition software, which are saved in tracks STI 014, STI 101, STI 201... * Select "STI 001" and "STI 002". The full track is read, all the changes of values are detected from those two tracks and a list of events is created. * The following figure appears, that asks how to import those recordings in the Brainstorm database.<<BR>><<BR>> {{attachment:importOptions.gif}} * __Time window__: Time range of interest. Now we want to keep the whole time definition, we are interested by all the stimulations. * __Split__: Useful to import continuous recordings without events. We do not need this here. * __Events selection__: Check the "Use events" option, and select both STI001 and STI002. The value between parenthesis represents the number of occurrences of this event. * __Epoch time__: Time instants that will be extracted before an after each event, to create the epochs that will be saved in the database. Set it to [-100, +300] ms * __Use Signal Space Projections__: Save and use the SSP vectors created by !MaxFilter or during other pre-processing steps. Keep this option selected. * __Remove DC Offset__: Check this option, and select: Time range: [-100, 0] ms. <<BR>>For each epoch, this will: compute the average of each channel over the baseline (pre-stimulus interval: -100ms to 0ms), and subtract it from the channel at all the times in [-100,+300]ms. * __Resample recordings__: Keep this unchecked * __Create new conditions for epochs__: If selected, a new condition is created for each event type (here, it will create a condition "Event_5"). If not selected, all the epochs from all the selected events are saved in the same condition, the one that was selected in the database explorer (if no condition selected, create a condition called "New condition"). * Click on Import and wait. * At the end, you get something like this:<<BR>><<BR>> {{attachment:treeAfterImport1.gif}} * The files that appear in the folder "''(Common files)''" will be shared for all the conditions of Subject01. This mechanism allows to compute the forward and inverse models only once for all the conditions when there is only one run (= one channel file = one position of sensors recorded). * Rename the condition "Event_5" into "Right" (Right-click > Rename, or press F2, or click twice waiting a while before the two clicks). * Repeat all those steps to import the events from track "STI 002". Rename "Event_5" into "Left". Your database should look like this:<<BR>><<BR>> {{attachment:treeAfterImport2.gif}} * __Note__: if you do not rename the condition "Event_5" in "Right" between the two imports, you would have at the end all the epochs in the same Event_5 condition. In this case, another way (and maybe safer) way to proceed is to: * Create two conditions Left and Right before starting to import the recordings. * Import the "STI 001" events in condition Right, and the "STI 002" in Left (do not forget to uncheck the option "Create new conditions for epochs", if not the condition selection would be overridden) |
* '''STI 001''': Contains the onsets of the electric stimulation of the '''right '''arm. * '''STI 002''': Contains the onsets of the electric stimulation of the '''left '''arm. * These are not standard settings, they depend on your acquisition setup. In most cases, you would rather import "events" defined with the Neuromag acquisition software, which are saved in tracks STI 014, STI 101, STI 201... * Select '''STI 001''' and '''STI 002'''. The full tracks are read, all the changes of values are detected from these two tracks and a list of events is created. * At the end, you're asked if you want to "Refine the registration with the head points". This operation improves the initial MRI/MEG registration by fitting the head points digitized at the MEG acquisition and the scalp surface. Answer '''YES'''.<<BR>><<BR>> {{attachment:refine.gif||width="324",height="170"}} <<BR>> * Always make sure that the final registration looks good. The yellow surface represents the inner surface of the MEG helmet and the green dots represent the head points that were saved with the MEG recordings. In this case the registration looks acceptable. If you consider it is not the case, you can fix it manually: right-click on the channel file > MRI registration > Edit. <<BR>><<BR>> {{attachment:checkRegistrationFig.gif||width="218",height="199"}} * A message will finally indicate that some default SSP projectors are available in the file. This is documented in an [[http://neuroimage.usc.edu/brainstorm/Tutorials/TutMindNeuromag#Existing_SSP_projectors|advanced section]] at the end of this page. We will not use them here, simply close the window "Select active projectors". <<BR>><<BR>> {{attachment:sspImport.gif||width="565",height="136"}} === Review the recordings === * Right-click on the "Link to raw file" to see what types of channels are available:<<BR>><<BR>> {{attachment:listTypes.gif||width="332",height="341"}} * '''MEG (all)''': Represents all the MEG sensors in the file (magnetometers and gradiometers) * '''MEG (magnetometers)''': 101 magnetometers (sensor names ending with a "1") * '''MEG (gradiometers)''': 202 planar gradiometers (sensor names ending with "2" or "3") * '''ECG''': Electro-cardiogram * '''EOG''': Electro-oculogram * '''Stim''': All the stimulation lines * Double-click on the file to display all the MEG sensors. * In the Record tab, look at the list of the available default display configurations for the Elekta-Neuromag Vectorview MEG systems. If you would like to use different combinations of sensors, you can create your own combinations with the entry [[Tutorials/MontageEditor|Edit montage]].<<BR>><<BR>> {{attachment:montages.gif||width="457",height="333"}} |
| Line 74: | Line 61: |
| === Stimulation artifact removal === The electric stimulation of the median nerve induces a strong artefact right after 0ms. We are going to use a simple trick to remove this artifact: re-interpolate the values between 0ms and 4ms (linear interpolation). It doesn't affect much the data but will make all the displays much better. * Drag'n'drop the "Subject01" node from the database explorer to the "Processes" tab. Click on the "Recordings" button, and then click on "run process".<<BR>><<BR>> {{attachment:cutStimList.gif}} * Select "Process > Cut stimulation artifact". The baseline time windows represents here the time instants for which the values are going to be re-interpolated. Set it to [0, 3.9]ms. <<BR>><<BR>> {{attachment:cutStimOptions.gif}} * Click on Run. All the files are going to be replaced with the processed ones. === Band-pass filtering === * Drag'n'drop again the "Subject01" node in the list of files to be processed. Select "Process > Band-pass filtering". Select the option "Overwrite intial files". Click on Run. * Set the frequency range to [0, 90] Hz.<<BR>><<BR>> {{attachment:bandpassSelection.gif}} * With all those process tags added, the comments of the files are getting a little too long. Rename them respectively Right and Left, by renaming directly the list (the node that contains all the epochs in each condition). It takes a while but will improve a lot the readability later.<<BR>><<BR>> {{attachment:treeAfterPreprocess.gif}} === Review the epochs === It is always very important to keep an eye on the quality of the data at the different steps of the analysis. There is always a few epochs that are too artifacted or noisy to be used, or one bad sensor. Unfortunately, there are no tools yet in Brainstorm for autoamtic artifact detection and rejection. But here is a procedure for reviewing your epochs manually. * Double-click on the Right epochs list to expand the list of files contained in it. Then display the time series for the first Right epoch by double-clicking on it.<<BR>><<BR>> {{attachment:reviewEpochs.gif}} * Then press F3 to go to the next epoch (or menu "Navigator > Next data file" in the main Brainstorm window). Do that until you reach the last epoch. For each epoch: * Check that the amplitude range in consistant with the previous epochs (in this study: between 1000fT and 2500fT). * You can tag some channels as bad: select a sensor by clicking on it and press the Delete key (or right-click > Channel > Mark selected as bad) * You can completely delete an epoch if you consider it as unusable (delete the files from the tree). * Time series can be also displayed in columns (select the "Display mode" toggle button in the toolbar of the main Brainstorm window). To select create your own selection of sensors, or use a pre-defined set: Right-click on the time-series figure > Display setup > ... Example: Right-temporal sensors only.<<BR>><<BR>> {{attachment:selectionsRT.gif}} * In the case of this study, there are so many trials for each condition and the recorded signal is so strong that you do not really need to spend too much time on the selection of the bad channels and bad epochs. If you just keep everything as it is, it is just fine. * Do the same for the Left condition. |
=== Evaluate the recordings === * Drag and drop the "Link to raw file" into the Process1 list. * Select the process "'''Frequency > Power spectrum density'''", configure it as follows:<<BR>><<BR>> {{attachment:processPsd.gif||width="487",height="358"}} * In all the processes, the types of sensors can be specified using the following convention: * '''MEG''': All the MEG sensors * '''MEG MAG''': All the magnetometers * '''MEG GRAD''': All the gradiometers * '''MEG GRAD2''': Only the first axial gradiometer on each chip (name ends with a "2") * '''MEG GRAD3''': Only the second axial gradiometer on each chip (name ends with a "3") * Double-click on the PSD file to display it.<<BR>><<BR>> {{attachment:processPsdView.gif||width="383",height="179"}} * The sensors are split in '''two groups''' because the two types of MEG sensors record different ranges of values: the gradiometer values are always higher than the magnetometers. * This power spectrum shows that there is no MEG sensor that is clearly bad, but some sensors show a strong contamination from the power lines (60Hz and harmonics). * Note that if you use the continuous head tracking capabilities of your Elekta system, you would see a lot more noise due to this HPI coil activity in the PSD. This is illustrated in [[http://neuroimage.usc.edu/brainstorm/Tutorials/VisualSingle#Spectral_evaluation|this other tutorial]]. === Remove: 60Hz and harmonics === * __Warning__: This process is very time and resource consuming. If you are not planning on analyzing anything specifically around 60Hz, you may want to skip this section and the long computation time associated with it. It is described here as a reference for users who would need it. * Select the process "'''Pre-process > Notch filter'''", configure it as follows: <<BR>><<BR>> {{attachment:processSin.gif}} * To evaluate the results of this process, select the new file ('''"Raw | notch"''') and run again the process "'''Frequency > Power spectrum density'''". * You should observe a significant decrease of the contributions of the removed frequencies (60Hz, 120Hz, 180Hz) compared with the original spectrum. <<BR>><<BR>> {{attachment:processPsdView2.gif||width="425",height="202"}} === Heartbeats and blinks === Signal Space Projection (SSP) is a method for projecting the recordings away from stereotyped artifacts, such as eye blinks and heartbeats. * Double-click on the filtered continuous file to display all the '''MEG '''recordings. * Right-click on the link > '''ECG '''> Display time series, to look at the heartbeats. * Right-click on the link > '''EOG '''> Display time series, to look at the eye movements. * From the Artifacts menu in the Record tab, run the detection processes: * '''Artifacts >''' '''Detect heartbeats:''' Select channel '''ECG 063''', event name "cardiac".<<BR>><<BR>> {{attachment:processDetectEcg.gif||width="310",height="214"}} * '''Artifacts >''' '''Detect eye blinks:''' Select channel '''EOG 062''', event name "blink".<<BR>><<BR>> {{attachment:processDetectEog.gif||width="309",height="213"}} * '''Artifacts >''' '''Remove simultaneous:''' To avoid capturing ocular artifacts in the cardiac SSP.<<BR>>Remove events named: "'''cardiac'''"<<BR>>When too close from events: "'''blink'''"<<BR>>Minimum delay between events: '''250ms'''.<<BR>><<BR>> {{attachment:processRemoveSimult.gif||width="309",height="234"}} * Review the traces of ECG/EOG channels and make sure the events detected make sense.<<BR>><<BR>> {{attachment:processDetectAfter.gif||width="229",height="240"}} * '''Artifacts >''' '''SSP: Heartbeats''': Event "cardiac", sensors="'''MEG MAG'''", use existing SSP. <<BR>>(select component #1) <<BR>><<BR>> {{attachment:sspEcgMag.gif||width="499",height="208"}} * '''Artifacts >''' '''SSP: Heartbeats''': Event "cardiac", sensors="'''MEG GRAD'''", use existing SSP. <<BR>>(select component #1) <<BR>><<BR>> {{attachment:sspEcgGrad.gif||width="500",height="209"}} * '''Artifacts >''' '''SSP: Eyeblinks''': Event "blink", sensors="'''MEG MAG'''", use existing SSP.<<BR>>(select component #1) <<BR>><<BR>> {{attachment:sspEogMag.gif||width="500",height="209"}} * '''Artifacts >''' '''SSP: Eyeblinks''': Event "blink", sensors="'''MEG GRAD'''", use existing SSP.<<BR>>(select component #1)<<BR>><<BR>> {{attachment:sspEogGrad.gif||width="500",height="209"}} * For more information regarding this method, refer to the tutorial: [[http://neuroimage.usc.edu/brainstorm/Tutorials/ArtifactsSsp|Artifact cleaning with SSP]]. * At this stage, you should also review the entire file (pressing repeatedly F3) to detect any obvious bad segment in the recordings. If you detect any, select the time window to mark as bad, right click on the figure > Reject time segment. * You could also use the automatic detection for other artifacts: [[http://neuroimage.usc.edu/brainstorm/Tutorials/BadSegments|Additional bad segments]]. == Epoching and averaging == === Import the recordings === * Right-click on the raw link > Import in database. <<BR>>The following figure appears, that asks how to import these recordings in the Brainstorm database.<<BR>><<BR>> {{attachment:importPopup.gif||width="182",height="209"}} {{attachment:importOptions.gif||width="483",height="273"}} * '''Time window''': Time range of interest, keep all the time definition. * '''Split''': Useful to import continuous recordings without events. We do not need this here. * '''Events selection''': Check the "Use events" option, and select both '''STI 001 '''and '''STI 002'''. The values in the parenthesis represent the number of occurrences of each event. * '''Epoch time''': Time instants that will be extracted before an after each event, to create the epochs that will be saved in the database. Set it to [-100, +300] ms * '''Use Signal Space Projections''': Save and use the SSP vectors created by MaxFilter, MNE and Brainstorm. Keep this option selected. * '''Remove DC Offset''': Check this option, and select: Time range: [-100, 0] ms. <<BR>>For each epoch, this will: compute the average of each channel over the baseline (pre-stimulus interval: -100ms to 0ms), then subtract it from the channel at all the times in [-100,+300]ms. * '''Resample recordings''': Keep this unchecked * '''Create a separate folder for each epoch type''': If selected, a new folder is created for each event type (here, it would create two folders "STI 001" and "STI 002"). This option is mostly for EEG studies with channel files shared across runs. In a MEG study, we usually recommend to use one channel file per run, and to import all the epochs from one run in the same folder. * Click on [Import] and wait. * Rename the two groups of trials "'''STI_001_5'''" and "'''STI_002''''''_5'''" into respectively "'''Right'''" and "'''Left'''" (Right-click > Rename, or press F2, or click twice waiting a while before the two clicks).<<BR>><<BR>> {{attachment:rename.gif||width="268",height="75"}} * At this stage, you should review all the trials (press F3 to jump to the next file), separately for the magnetometers and the gradiometers, to make sure that you don't have any bad trial that have been imported. If you find a bad trial: right-click on the file or on the figure > Reject trial. |
| Line 100: | Line 116: |
| You can use Brainstorm to work on individual trials or on average recordings. But even if you plan to work on single trials, start your exploration of the recordings by computing an average per condition. It would give you a good idea of the quality of your recordings and pre-processing operations. If you do not see anything looking like the effect you are supposed to observe on the average, it is a complete waste of time to go on with source or time-frequency analysis. * Drag'n'drop again the node "Subject01" in the Processes tab, and click on Run process. * Select "Average > Average by condition (Grand average). Click on Run. * Two new files called "GAVE: ...." appeared in the database. They are the averaged response for each condition, locked on the stimulus.<<BR>><<BR>> {{attachment:treeAfterAverage.gif}} * Display the time series for each average: Right-click on the file > MEG (All) > Display time series. * Display the 2D topographies for each average: Right-click on the file > MEG (All) > 2D Sensor cap (or press CTRL+T from the time series figures)<<BR>><<BR>> {{attachment:reviewAverages.gif}} |
* Drag and drop all the left and right trials to the Process1 tab. * Run the process '''Average > Average files > By trial group (folder average)''': <<BR>><<BR>> {{attachment:processAverage.gif||width="484",height="496"}} * Double-click on the Left and Right averages to display all the MEG sensors:<<BR>><<BR>> {{attachment:averageArtifact.gif}} === Stimulation artifact === * We see clearly our evoked responses in these figures, but the stimulation artifact between 0ms and 5ms causes the automatic scaling of the figures to be too high, especially for the right stimulation. This effect would get a lot worse when displaying the sources for these files. To get a better display of these averages, we can cut these peaks at 0ms by replacing the values with linear interpolations. * Select the averages for the Left and Right condition in the Process1 tab. * Run the process '''Artifacts > Cut stimulation artifact''': 0-5ms, overwrite<<BR>><<BR>> {{attachment:processCut.gif}} * Now you can display the averages correctly: Right-click > MEG (All) > Display time series. * Display the 2D topographies for each average: Right-click on the file > MEG (All) > 2D Sensor cap (or press CTRL+T from the time series figures). * You can also add a low-pass filter at 100Hz for the visualization.<<BR>><<BR>> {{attachment:reviewAverages.gif||width="659",height="259"}} |
| Line 108: | Line 128: |
| * Other available displays: 3D Sensor cap, 2D Disc, 2D Layout. Note the shared selection of sensors.<<BR>><<BR>> == Forward model == First step of the source estimation process: establishing a model that describes the way the brain electric activities influence the magnetic fields that are recorded by the MEG sensors. This model can be designated in the documentation by the following terms: head model, forward model, lead field matrix. === MEG / MRI registration === An accurate forward model requires first of all an accurate registration of the anatomy files (MRI+surfaces) and functional recordings (position of the MEG sensors and EEG electrodes). A basic registration is provided by the alignment of the fiducials (Nasion, LPA, RPA), that were both located before the acquisition of the recordings and marked on the MRI in Brainstorm. This registration based on three points only can be very inaccurate, because it is sometimes hard to identify clearly those points, and not everybody identify them the same way. Two methods described in the [[Tutorials/TutImportRecordings|introduction tutorial #3]] may help you to improve this registration. * Right-click on the channel file > MRI Registration > Check MEG-MRI registration<<BR>><<BR>> {{attachment:checkRegistration.gif}} {{attachment:checkRegistrationFig.gif}} * The yellow squares represent the Neuromag MEG sensors, and the green dots represent the head points that where saved with the MEG recordings. * In this case the registration looks acceptable. If you consider it is not your case, you can try the two menus: * Auto-registration: This operation will try to find a better registration of the head points (green dots), on the head surface (grey surface) * Manual resgistration: You rotate/translate the sensor array manually respect to the head surface. === Compute head model === * Right-click on any node that contains the channel file (including the channel file itself), and select: "Compute head model".<<BR>><<BR>> {{attachment:headmodelStart.gif}} * Select "overlapping spheres" and click on Run. Select "Inner skull" when asked what surface to use to estimate the spheres. For more information, read the tutorial "[[Tutorials/TutHeadModel|Computing a head model]]".<<BR>><<BR>> {{attachment:headmodelSurface.gif}} * When the computation is done, close the "Check spheres" figure. The lead field matrix is saved in file "Overlapping spheres" in "Common files", in a the "Gain" field. == Noise covariance matrix == To estimate the sources properly, we need an estimation of the noise level for each sensor. A good way to do this is to compute the covariance matrix of the concatenation of the baselines from all the trials in both conditions. * Select at the same time the two groups of trials (Right and Left). To do this: hold the Control key and click successively on the Right and the Left trial lists. * Right-click on one of them and select: Noise covariance > Compute from recordings. Leave all the options unchanged, and click on Ok.<<BR>><<BR>> {{attachment:noisecovMenu.gif}} {{attachment:noisecovOptions.gif}} * This operation computes the noise covariance matrix based on the baseline, [-100, 0]ms, of all the trials (624 files), and keep only the diagonal values (more stable). The result is stored in a new file in the "Common files" folder. |
== Gradiometers & magnetometers == ==== Scaling factor ==== Magnetometers record values in Tesla (T), while gradiometers record values in Tesla per meter (T/m). The range of values obtained is not the same, therefore it is difficult to represent the two types of signals in the same figures. We can convert the gradiometers values from T/m to T by multiplying them with the distance between the two gradiometer coils (0.0168 meters on the VectorView MEG system). But this still produces values that are too small to be represented with the same scale as the magnetometers. A more practical multiplication factor of '''0.04''' was proposed by Matti Hamalainen. In the time series figure and for Elekta-Neuromag systems (all versions), the gradiometer values are always multiplied by 0.04. This is an empirical scaling factor that is used for visualization only, it is never saved in the recordings and is not used for any other purpose. ==== Magnetic interpolation ==== * You can also display the MEG MAG (top) and MEG GRAD (bottom) sensors separately: <<BR>><<BR>> {{attachment:averageMagGrad.gif||width="379",height="259"}} * The topographies look very similar, because all the values are re-interpolated on a surface of virtual magnetometers. To display the real values for the different types of sensors, without this magnetic interpolation, use the menus "No magnetic interpolation". * Right-click on Left > MEG (mag) > No magnetic interpolation > 2D Sensor cap. <<BR>><<BR>> {{attachment:averageMagNointerp.gif||width="198",height="165"}} * Repeat the same operation for "MEG (gradiometers)". You now have three options, because it is not possible to display at the same time the values for the two planar gradiometers: * '''Grad 2''': First gradiometer, sensor names ending with "2" * '''Grad 3''': Second gradiometer, sensor names ending with "3" * '''Grad norm''': Norm of the two gradiometers => sqrt(grad2^2^ + grad3^2^) * The three options side-by-side at 22ms (grad 2, grad3, norm): <<BR>><<BR>> {{attachment:averageGradNointerp2.gif||width="542",height="165"}} |
| Line 135: | Line 148: |
| Reconstruction of the cortical sources with a weighted minimum norm estimator (wMNE). * Right-click on "Common files", (or on the head model, or on the subject node, this is all equivalent), and select "Compute sources". <<BR>><<BR>> {{attachment:inverseMenu.gif}} * Select "Yes" to ignore the warning about noise covariance used at the same time for averages and single trials (if you do not see such a warning, that's fine too). In this case, this warning does not really apply, the results are the same if we compute separately the minimum norm estimator for the single trials and the averages. * Select "Normal mode" (not "Expert mode"), wMNE, and both gradiometers and magnetometers, as in the figure below. Click on Run.<<BR>><<BR>> {{attachment:inverseOptions.gif}} {{attachment:treeAfterInverse.gif}} * A shared inversion kernel was created in the ''(Common files)'' folder, and a link node is now visible for each recording file, single trials and averages. For more information about what those links mean and the operations performed to display them, please refer to the [[Tutorials/TutSourceEstimation|tutorial #4 "Source estimation"]]. * For the average of condition Right: display the time series, the 2D sensor topography, the sources on the cortex, the sources on 3D orthogonal slices, and the sources in the MRI Viewer.<<BR>><<BR>> {{attachment:inverseAllDisplay.gif}} * Create a scout called LeftSS that covers the most active region of the cortex at 33ms for condition Right. Display its time series for conditions Left and Right at the same time (select both Left and Right source files, right click > Cortical activations > Scouts time series (check "Overlay: conditions").<<BR>><<BR>> {{attachment:inverseScoutLeft.gif}} == Time-frequency == |
We need now to calculate a source model for these recordings, using a noise covariance matrix calculated from the pre-stimulation baselines. This process is not detailed a lot here because it is very similar to what is shown in the introduction tutorials. === Head model === * Right-click on the channel file > '''Compute head model'''. Keep the default options.<<BR>><<BR>> {{attachment:headmodelMenu.gif||width="391",height="250"}} * For more information: [[Tutorials/HeadModel|Head model tutorial]]. === Noise covariance === * Select all the Left and Right trials, right-click > Noise covariance > '''Compute from recordings'''.<<BR>><<BR>> {{attachment:noisecovPopup.gif||width="637",height="253"}} * Leave all the default options and click [OK]. * For more information: [[Tutorials/NoiseCovariance|Noise covariance tutorial]]. === Inverse model === * Right-click on the headmodel > '''Compute sources'''. Select '''dSPM '''and all the default options. This will run a source reconstruction grouping the information from the magnetometers and the gradiometers into the same model. This is the recommended procedure, but you can also estimate sources for the two types of sensors separately if needed.<<BR>><<BR>> {{attachment:inversePopup.gif||width="426",height="242"}} {{attachment:inverseFiles.gif||width="210",height="131"}} * A shared inversion kernel is created in the same folder, and a link node is now visible for each recording file, single trials and averages. * For more information: [[Tutorials/SourceEstimation|Source estimation tutorial]]. === Scouts === Place scouts to capture the activity in the primary and secondary somatosensory areas to track the processing of the electric stimulations in time, at the surface surface of the brain. {{attachment:final.gif||width="624",height="317"}} <<TAG(Advanced)>> == Existing SSP projectors == In the Record tab, select menu "Artifacts > Select active projectors". You will see the file contains three SSP projectors that are not applied by default. In general, every Neuromag Vectorview (306 channel) system has at least two default SSP files, one for the supine position and one for upright. The newer Triux machines may contain a third SSP set. The default bases for the Vectorview are rank 5 for planar gradiometers, and rank 8 for magnetometers, for 13 bases total, but applied separately to the two types of sensors. Some sites may have different rank default bases, such as the massive three-layer magnetically shielded rooms, which may use even smaller rank bases sets. During acquisition, the real-time display projects the data away from these SSP vectors, '''for display purposes only.''' If U is the SSP orthonormal basis, then the data are displayed as (d - U U^T d). The original data "d" are stored without the SSP applied, along with all of the default SSP vectors, U. The default SSP bases are calculated from an empty room recording, often as part of the initial installation of the site, and they rarely need changing, since they are essentially formed by the shape of the room in its environment, and by the position of the instrument within this room, hence the need for different bases dependent on the position of the helmet. If a subject has a very noisy low frequency baseline disturbance, such as due to metal artifacts on the patient, it is beneficial to recalculate SSP bases from a short period of their data (e.g. 2 minutes). Matti Hamalainen's MNE program can regenerate valid SSP data files compatible with the Vectorview, and these can be used in place of the default SSP bases, after restarting the acquisition program. These custom SSP bases are effective for allowing the technician acquiring the data to confirm that all channels continue to acquire usuable data. The machine can then be reset to the defaults. All of these actions can be effected through relatively simple scripts that regenerate the SSP bases, using MNE, in near real-time. After the data are acquired, the original SSP bases are often ignored in subsequent processing. They can be useful for initial viewing of the data. For research analyses, rather than use the default SSP bases, it is preferential to recalculate the noise covariance from appropriate baselines, to include brain noise if possible, and use that as the full noise covariance. SSP is essentially an inverted noise covariance with the eigenvalues set to either 0 (reject) or 1 (pass), which is a generally inadequate description of the noise. At many sites, the MaxFilter "TSSS" program is typically run, which is an implicit LCMV beamformer (programmed as a Generalized Sidelobe Canceller), which has the benefit that it implicitly whitens a lot of the background noise as part of its processing. Therefore, MaxFilter also does not use the original SSP bases, and as part of its default operation, MaxFilter always deletes the original SSP vectors and does not include them in the output FIF file. (As an aside, if motion compensation is on, then MaxFilter adds nine synthetic channels to the data to track head motion, written out using quaternions). Thus when you load data processed by MaxFilter, you will not find any of the original SSP projectors. For additional information about SSP, read the tutorial: [[Tutorials/ArtifactsSsp|Artifact cleaning with SSP]]. <<TAG(Advanced)>> == Existing SSP and pre-processing == * If you select the default SSP projectors and try to run the process "Notch filter" without selecting the option "Process the entire file at once", you would get the following error. Using these projectors requires all the sensors, and filtering requires all the time samples at once. As a consequence, the entire file '''must be read in one block''' in order to apply frequency filters on it. <<BR>><<BR>> {{attachment:sinError.gif||width="658",height="234"}} * Alternatively, if you try with the option "'''Process the entire file at once'''", you would probably crash Matlab or freeze your computer because of a lack of memory. The file is already large and this process requires to create a lot of matrices of the same size in memory. Do not try this unless you have at least 24Gb of memory available on your computer. * The solution is to re-write an '''intermediate file''' with the SSP projectors applied, that you will be able to process easily after. In Process1, keep the "Link to raw file" selected. * Run process "'''Artifacts > Apply SSP and CTF compensation'''". This creates a new continuous file which contains the same data as the original .fif file, but with the SSP projectors applied to the recordings values (instead of being just saved as linear operators on the side).<<BR>><<BR>> {{attachment:processApplySsp.gif||width="270",height="145"}} * Clear the Process1 list and select the new continuous file "'''Raw | clean'''" * Run the process "'''Pre-process > Notch filter'''", configured as follows:<<BR>><<BR>> {{attachment:processSin.gif||width="336",height="274"}} * To evaluate the results of this process, select the last file generated ('''"Raw | clean | notch"''') and run again the process "'''Frequency > Power spectrum density'''".<<BR>><<BR>> {{attachment:processPsd2.gif||width="525",height="296"}} == Scripting == The following script from the Brainstorm distribution reproduces the analysis presented in this tutorial page: [[https://github.com/brainstorm-tools/brainstorm3/blob/master/toolbox/script/tutorial_neuromag.m|brainstorm3/toolbox/script/tutorial_neuromag.m]]''' ''' <<HTML(<div style="border:1px solid black; background-color:#EEEEFF; width:720px; height:500px; overflow:scroll; padding:10px; font-family: Consolas,Menlo,Monaco,Lucida Console,Liberation Mono,DejaVu Sans Mono,Bitstream Vera Sans Mono,Courier New,monospace,sans-serif; font-size: 13px; white-space: pre;">)>><<EmbedContent("http://neuroimage.usc.edu/bst/viewcode.php?f=tutorial_neuromag.m")>><<HTML(</div >)>> == Discussion == * Combining magneto+gradiometers: http://neuroimage.usc.edu/forums/showthread.php?1900 <<EmbedContent(http://neuroimage.usc.edu/bst/get_feedback.php?Tutorials/TutMindNeuromag)>> |
Elekta-Neuromag tutorial: Median nerve stimulation
This tutorial describes how to process continuous Elekta-Neuromag MEG recordings. It is based on median nerve stimulation acquired at the Massachusetts General Hospital in 2005 with a Neuromag Vectorview 306 system. The sample dataset contains the results for one subject for both arms: 18 minutes, 300 stimulations per arm.
Note that the operations used here are not detailed, the goal of this tutorial is not to introduce Brainstorm to new users. For in-depth explanations of the interface and theoretical foundations, please refer to the introduction tutorials.
Contents
License
This data was collected in a multi-site MEG study administered by the MIND institute.
Presentation of the experiment
Experiment
- One subject, one acquisition run of 18 minutes
- The run contains 624 electric stimulations randomly distributed between left and right:
- 301 stimulations of the left hand
- 323 stimulations of the right hand
MEG acquisition
Acquisition at 1793Hz, with a Neuromag Vectorview 306 system
- Recorded at the Massachusetts General Hospital in 2005
- Recorded channels (318):
- 102 MEG magnetometer
- 204 MEG planar gradiometers
- 9 stimulation channels (#307-315)
- 2 EOG bipolar (#316-317)
- 1 ECG bipolar (#318)
1 dataset: mind004_050924_median01_raw.fif
Head shape
- 130 additional head points
Subject anatomy
- Subject with 1.5T MRI
Processed with FreeSurfer 5.2
Download and installation
Requirements: You have already followed all the basic tutorials and you have a working copy of Brainstorm installed on your computer.
Go to the Download page of this website and download the file sample_neuromag.zip
- Unzip it in a folder that is not in any of the Brainstorm folders (program folder or database folder)
- Start Brainstorm (Matlab scripts or stand-alone version)
Menu File > Create new protocol > TutorialNeuromag, with the following options:
No, use individual anatomy,
No, use one channel file per run.
Import the anatomy
Right-click on the TutorialNeuromag folder > New subject > Subject01 (leave all the defaults).
Right-click on the subject node > Import anatomy folder:
Set the file format: "FreeSurfer folder"
Select the folder: sample_neuromag/anatomy
Number of vertices of the cortex surface: 15000 (default value)
Click on the link "Click here to compute MNI transformation".
- Set the 3 required fiducial points (indicated in MRI coordinates):
- NAS: x=131, y=232, z=123
- LPA: x=48, y=136, z=74
- RPA: x=204, y=131, z=67
At the end of the process, make sure that the file "cortex_15000V" is selected (downsampled pial surface, that will be used for the source estimation). If it is not, double-click on it to select it as the default cortex surface.
Access the recordings
Link the recordings
- Switch to the "functional data" view, the middle button in the toolbar above the database explorer.
Right click on the Subject01 > Review raw file:
Select the file format: MEG/EEG: Elekta-Neuromag (*.fif)
Pick the file: sample_neuromag/data/mind004_050924_median01_raw.fif
Select "Event channel" when asked about the events.
Then you have to select from which technical tracks you want to read the events.
- In this dataset, the tracks of interest are:
STI 001: Contains the onsets of the electric stimulation of the right arm.
STI 002: Contains the onsets of the electric stimulation of the left arm.
- These are not standard settings, they depend on your acquisition setup. In most cases, you would rather import "events" defined with the Neuromag acquisition software, which are saved in tracks STI 014, STI 101, STI 201...
Select STI 001 and STI 002. The full tracks are read, all the changes of values are detected from these two tracks and a list of events is created.
At the end, you're asked if you want to "Refine the registration with the head points". This operation improves the initial MRI/MEG registration by fitting the head points digitized at the MEG acquisition and the scalp surface. Answer YES.
Always make sure that the final registration looks good. The yellow surface represents the inner surface of the MEG helmet and the green dots represent the head points that were saved with the MEG recordings. In this case the registration looks acceptable. If you consider it is not the case, you can fix it manually: right-click on the channel file > MRI registration > Edit.
A message will finally indicate that some default SSP projectors are available in the file. This is documented in an advanced section at the end of this page. We will not use them here, simply close the window "Select active projectors".
Review the recordings
Right-click on the "Link to raw file" to see what types of channels are available:
MEG (all): Represents all the MEG sensors in the file (magnetometers and gradiometers)
MEG (magnetometers): 101 magnetometers (sensor names ending with a "1")
MEG (gradiometers): 202 planar gradiometers (sensor names ending with "2" or "3")
ECG: Electro-cardiogram
EOG: Electro-oculogram
Stim: All the stimulation lines
- Double-click on the file to display all the MEG sensors.
In the Record tab, look at the list of the available default display configurations for the Elekta-Neuromag Vectorview MEG systems. If you would like to use different combinations of sensors, you can create your own combinations with the entry Edit montage.
Pre-processing
Evaluate the recordings
- Drag and drop the "Link to raw file" into the Process1 list.
Select the process "Frequency > Power spectrum density", configure it as follows:
- In all the processes, the types of sensors can be specified using the following convention:
MEG: All the MEG sensors
MEG MAG: All the magnetometers
MEG GRAD: All the gradiometers
MEG GRAD2: Only the first axial gradiometer on each chip (name ends with a "2")
MEG GRAD3: Only the second axial gradiometer on each chip (name ends with a "3")
Double-click on the PSD file to display it.
The sensors are split in two groups because the two types of MEG sensors record different ranges of values: the gradiometer values are always higher than the magnetometers.
- This power spectrum shows that there is no MEG sensor that is clearly bad, but some sensors show a strong contamination from the power lines (60Hz and harmonics).
Note that if you use the continuous head tracking capabilities of your Elekta system, you would see a lot more noise due to this HPI coil activity in the PSD. This is illustrated in this other tutorial.
Remove: 60Hz and harmonics
Warning: This process is very time and resource consuming. If you are not planning on analyzing anything specifically around 60Hz, you may want to skip this section and the long computation time associated with it. It is described here as a reference for users who would need it.
Select the process "Pre-process > Notch filter", configure it as follows:
To evaluate the results of this process, select the new file ("Raw | notch") and run again the process "Frequency > Power spectrum density".
You should observe a significant decrease of the contributions of the removed frequencies (60Hz, 120Hz, 180Hz) compared with the original spectrum.
Heartbeats and blinks
Signal Space Projection (SSP) is a method for projecting the recordings away from stereotyped artifacts, such as eye blinks and heartbeats.
Double-click on the filtered continuous file to display all the MEG recordings.
Right-click on the link > ECG > Display time series, to look at the heartbeats.
Right-click on the link > EOG > Display time series, to look at the eye movements.
- From the Artifacts menu in the Record tab, run the detection processes:
Artifacts > Detect heartbeats: Select channel ECG 063, event name "cardiac".
Artifacts > Detect eye blinks: Select channel EOG 062, event name "blink".
Artifacts > Remove simultaneous: To avoid capturing ocular artifacts in the cardiac SSP.
Remove events named: "cardiac"
When too close from events: "blink"
Minimum delay between events: 250ms.
Review the traces of ECG/EOG channels and make sure the events detected make sense.
Artifacts > SSP: Heartbeats: Event "cardiac", sensors="MEG MAG", use existing SSP.
(select component #1)
Artifacts > SSP: Heartbeats: Event "cardiac", sensors="MEG GRAD", use existing SSP.
(select component #1)
Artifacts > SSP: Eyeblinks: Event "blink", sensors="MEG MAG", use existing SSP.
(select component #1)
Artifacts > SSP: Eyeblinks: Event "blink", sensors="MEG GRAD", use existing SSP.
(select component #1)
For more information regarding this method, refer to the tutorial: Artifact cleaning with SSP.
At this stage, you should also review the entire file (pressing repeatedly F3) to detect any obvious bad segment in the recordings. If you detect any, select the time window to mark as bad, right click on the figure > Reject time segment.
You could also use the automatic detection for other artifacts: Additional bad segments.
Epoching and averaging
Import the recordings
Right-click on the raw link > Import in database.
The following figure appears, that asks how to import these recordings in the Brainstorm database.
Time window: Time range of interest, keep all the time definition.
Split: Useful to import continuous recordings without events. We do not need this here.
Events selection: Check the "Use events" option, and select both STI 001 and STI 002. The values in the parenthesis represent the number of occurrences of each event.
Epoch time: Time instants that will be extracted before an after each event, to create the epochs that will be saved in the database. Set it to [-100, +300] ms
Use Signal Space Projections: Save and use the SSP vectors created by MaxFilter, MNE and Brainstorm. Keep this option selected.
Remove DC Offset: Check this option, and select: Time range: [-100, 0] ms.
For each epoch, this will: compute the average of each channel over the baseline (pre-stimulus interval: -100ms to 0ms), then subtract it from the channel at all the times in [-100,+300]ms.Resample recordings: Keep this unchecked
Create a separate folder for each epoch type: If selected, a new folder is created for each event type (here, it would create two folders "STI 001" and "STI 002"). This option is mostly for EEG studies with channel files shared across runs. In a MEG study, we usually recommend to use one channel file per run, and to import all the epochs from one run in the same folder.
- Click on [Import] and wait.
Rename the two groups of trials "STI_001_5" and "STI_002_5" into respectively "Right" and "Left" (Right-click > Rename, or press F2, or click twice waiting a while before the two clicks).
At this stage, you should review all the trials (press F3 to jump to the next file), separately for the magnetometers and the gradiometers, to make sure that you don't have any bad trial that have been imported. If you find a bad trial: right-click on the file or on the figure > Reject trial.
Averaging
- Drag and drop all the left and right trials to the Process1 tab.
Run the process Average > Average files > By trial group (folder average):
Double-click on the Left and Right averages to display all the MEG sensors:
Stimulation artifact
- We see clearly our evoked responses in these figures, but the stimulation artifact between 0ms and 5ms causes the automatic scaling of the figures to be too high, especially for the right stimulation. This effect would get a lot worse when displaying the sources for these files. To get a better display of these averages, we can cut these peaks at 0ms by replacing the values with linear interpolations.
- Select the averages for the Left and Right condition in the Process1 tab.
Run the process Artifacts > Cut stimulation artifact: 0-5ms, overwrite
Now you can display the averages correctly: Right-click > MEG (All) > Display time series.
Display the 2D topographies for each average: Right-click on the file > MEG (All) > 2D Sensor cap (or press CTRL+T from the time series figures).
You can also add a low-pass filter at 100Hz for the visualization.
- Everything looks ok, the time series figures show a clean signal with a very high SNR, and the topographies at the first response peak (about 22ms) show an activity on the left side for the Right condition, and on the right side for the Left condition.
Gradiometers & magnetometers
Scaling factor
Magnetometers record values in Tesla (T), while gradiometers record values in Tesla per meter (T/m). The range of values obtained is not the same, therefore it is difficult to represent the two types of signals in the same figures.
We can convert the gradiometers values from T/m to T by multiplying them with the distance between the two gradiometer coils (0.0168 meters on the VectorView MEG system). But this still produces values that are too small to be represented with the same scale as the magnetometers. A more practical multiplication factor of 0.04 was proposed by Matti Hamalainen.
In the time series figure and for Elekta-Neuromag systems (all versions), the gradiometer values are always multiplied by 0.04. This is an empirical scaling factor that is used for visualization only, it is never saved in the recordings and is not used for any other purpose.
Magnetic interpolation
You can also display the MEG MAG (top) and MEG GRAD (bottom) sensors separately:
- The topographies look very similar, because all the values are re-interpolated on a surface of virtual magnetometers. To display the real values for the different types of sensors, without this magnetic interpolation, use the menus "No magnetic interpolation".
Right-click on Left > MEG (mag) > No magnetic interpolation > 2D Sensor cap.
- Repeat the same operation for "MEG (gradiometers)". You now have three options, because it is not possible to display at the same time the values for the two planar gradiometers:
Grad 2: First gradiometer, sensor names ending with "2"
Grad 3: Second gradiometer, sensor names ending with "3"
Grad norm: Norm of the two gradiometers => sqrt(grad22 + grad32)
The three options side-by-side at 22ms (grad 2, grad3, norm):
Source estimation
We need now to calculate a source model for these recordings, using a noise covariance matrix calculated from the pre-stimulation baselines. This process is not detailed a lot here because it is very similar to what is shown in the introduction tutorials.
Head model
Right-click on the channel file > Compute head model. Keep the default options.
For more information: Head model tutorial.
Noise covariance
Select all the Left and Right trials, right-click > Noise covariance > Compute from recordings.
- Leave all the default options and click [OK].
For more information: Noise covariance tutorial.
Inverse model
Right-click on the headmodel > Compute sources. Select dSPM and all the default options. This will run a source reconstruction grouping the information from the magnetometers and the gradiometers into the same model. This is the recommended procedure, but you can also estimate sources for the two types of sensors separately if needed.
- A shared inversion kernel is created in the same folder, and a link node is now visible for each recording file, single trials and averages.
For more information: Source estimation tutorial.
Scouts
Place scouts to capture the activity in the primary and secondary somatosensory areas to track the processing of the electric stimulations in time, at the surface surface of the brain.
Existing SSP projectors
In the Record tab, select menu "Artifacts > Select active projectors". You will see the file contains three SSP projectors that are not applied by default.
In general, every Neuromag Vectorview (306 channel) system has at least two default SSP files, one for the supine position and one for upright. The newer Triux machines may contain a third SSP set. The default bases for the Vectorview are rank 5 for planar gradiometers, and rank 8 for magnetometers, for 13 bases total, but applied separately to the two types of sensors. Some sites may have different rank default bases, such as the massive three-layer magnetically shielded rooms, which may use even smaller rank bases sets.
During acquisition, the real-time display projects the data away from these SSP vectors, for display purposes only. If U is the SSP orthonormal basis, then the data are displayed as (d - U U^T d). The original data "d" are stored without the SSP applied, along with all of the default SSP vectors, U.
The default SSP bases are calculated from an empty room recording, often as part of the initial installation of the site, and they rarely need changing, since they are essentially formed by the shape of the room in its environment, and by the position of the instrument within this room, hence the need for different bases dependent on the position of the helmet.
If a subject has a very noisy low frequency baseline disturbance, such as due to metal artifacts on the patient, it is beneficial to recalculate SSP bases from a short period of their data (e.g. 2 minutes). Matti Hamalainen's MNE program can regenerate valid SSP data files compatible with the Vectorview, and these can be used in place of the default SSP bases, after restarting the acquisition program. These custom SSP bases are effective for allowing the technician acquiring the data to confirm that all channels continue to acquire usuable data. The machine can then be reset to the defaults. All of these actions can be effected through relatively simple scripts that regenerate the SSP bases, using MNE, in near real-time.
After the data are acquired, the original SSP bases are often ignored in subsequent processing. They can be useful for initial viewing of the data. For research analyses, rather than use the default SSP bases, it is preferential to recalculate the noise covariance from appropriate baselines, to include brain noise if possible, and use that as the full noise covariance. SSP is essentially an inverted noise covariance with the eigenvalues set to either 0 (reject) or 1 (pass), which is a generally inadequate description of the noise.
At many sites, the MaxFilter "TSSS" program is typically run, which is an implicit LCMV beamformer (programmed as a Generalized Sidelobe Canceller), which has the benefit that it implicitly whitens a lot of the background noise as part of its processing. Therefore, MaxFilter also does not use the original SSP bases, and as part of its default operation, MaxFilter always deletes the original SSP vectors and does not include them in the output FIF file. (As an aside, if motion compensation is on, then MaxFilter adds nine synthetic channels to the data to track head motion, written out using quaternions). Thus when you load data processed by MaxFilter, you will not find any of the original SSP projectors.
For additional information about SSP, read the tutorial: Artifact cleaning with SSP.
Existing SSP and pre-processing
If you select the default SSP projectors and try to run the process "Notch filter" without selecting the option "Process the entire file at once", you would get the following error. Using these projectors requires all the sensors, and filtering requires all the time samples at once. As a consequence, the entire file must be read in one block in order to apply frequency filters on it.
Alternatively, if you try with the option "Process the entire file at once", you would probably crash Matlab or freeze your computer because of a lack of memory. The file is already large and this process requires to create a lot of matrices of the same size in memory. Do not try this unless you have at least 24Gb of memory available on your computer.
The solution is to re-write an intermediate file with the SSP projectors applied, that you will be able to process easily after. In Process1, keep the "Link to raw file" selected.
Run process "Artifacts > Apply SSP and CTF compensation". This creates a new continuous file which contains the same data as the original .fif file, but with the SSP projectors applied to the recordings values (instead of being just saved as linear operators on the side).
Clear the Process1 list and select the new continuous file "Raw | clean"
Run the process "Pre-process > Notch filter", configured as follows:
To evaluate the results of this process, select the last file generated ("Raw | clean | notch") and run again the process "Frequency > Power spectrum density".
Scripting
The following script from the Brainstorm distribution reproduces the analysis presented in this tutorial page: brainstorm3/toolbox/script/tutorial_neuromag.m
Discussion
Combining magneto+gradiometers: http://neuroimage.usc.edu/forums/showthread.php?1900