|
Size: 4137
Comment:
|
← Revision 112 as of 2022-08-22 14:06:11 ⇥
Size: 0
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Tutorial: Source estimation = This tutorial is still based on Sabine Meunier's somatotopy experiment, called ''TutorialCTF ''in your Brainstorm database. Now you have in you database a forward model matrix that explains how the cortical sources determine the values on the sensors. This is useful for simulations, but what we really need is to build the inverse information: how to estimate the sources when you have the results. Many solutions described in the literature, some of them are implemented in Brainstorm, and only one is presented in this tutorial: the minimum-norm estimation. It is not really the most advanced solution, but it is one of the most robust. For more information about inverse models and minimum-norm estimation, visit the [[Theory]] section. <<TableOfContents(2)>> == Computing sources for a single data file == 1. Right-click on ''Subject01 / StimRightThumb / ERP'' > ''Compute sources''.<<BR>><<BR>> {{attachment:popupComputeSources.gif}} {{attachment:panelComputeSources.gif}} 1. With this first window you can select the method you want to use to estimate the cortical currents, and the sensors you are going to use for this estimation. * Edit the Comment field if you want. * Select "Min. Norm Imaging" * For the sensors, you have no other option than MEG (All), because those recordings were recorded with only one type of MEG sensors (axial gradiometers) and no EEG signal was registrated at the same time. * Run. 1. The next window shows the options for the minimum norm estimation algorithm.<<BR>><<BR>> {{attachment:minNormOptions.gif}} * Leave the ''Tikhonov ''and ''Forward field normalization'' selected. To know more about those options, please consult the the [[Theory]] section. * However, you need to understand well what is the meaning of the last option, ''Output format'', which defines the way the sources estimates are saved. * '''Full results''': Saves in one big matrix the values of all the sources (15000) for all the time samples (375). * The size in memory of such a matrix is about 45Mb for 300ms of recordings. This is still reasonable, so you may use this option in this case. * But if you need to process longer recordings, you may have some "Out of memory" errors in Matlab, or fill your hard drive quicklky. * '''Kernel only''': Saves only the ''Inversion kernel'', a matrix which describes how to compute the sources when you know the values of the sensors. So its size is: number of sources (15000) x number of sensors (151). * To get the sources time series, you just need to multiply this kernel by the MEG recordings. * '''Full results '''=''' Inversion kernel '''*''' Recordings''' * The size of this matrix is about 18Mb. In this case, the difference is not very important because we only process 375 time samples. But this inversion kernel is independent from the recordings length, so you can easily scale its computation to much longer recordings. * This is possible because the Minimum norm estimation is a linear method. * Which option should you choose ? * Probably "''Kernel only''", as it is faster and produces smaller files. * All the following operations in Brainstorm will be exactly the same whatever you select. Each time you will access the sources values, the program will have to do the multiplication Kernel * Recordings, but this is done in a totally transparent way. * The only reason that would make you chose the "''Full results''" options would be any interest in having the full matrix in one file, in case you want to process the sources values by yourself (filtering, statistics, display...). 1. So please "''Kernel only''" for the moment. And click ''Ok''. 1. A new file is available in the database explorer. * It is displayed'' inside ''the recordings file ERP, because it is related to this file only. * You can have a look to what there is in the corresponding matrix file (right-click > File > View .mat file). You would find all the options of forward and inverse modelling, and only one interesting field : '''ImagingKernel'''. |
Differences between revisions 3 and 112 (spanning 109 versions)