# Inverse source parameter estimates from EEG/MEG data

FieldTrip has a consistent set of low-level functions for source reconstruction, i.e. estimating the location, strength and other parameters of the sources in the brain that underly the observed EEG and MEG data. The usual mathematical description of the sources is the equivalent current dipole, which is why in the subsequent documentation you will often see *source* and *dipole* used exchangeably.

The objective of supplying these low-level functions as a seperate module/toolbox are to

- facilitate the reuse of these functions in other open-source projects (e.g. EEGLAB, SPM)
- facilitate the implementation and support for new inverse methods, esp. for external users/contributors
- facilitate the implementation of advanced features

The low-level functions are combined in the forward and the inverse toolboxes, which are released together with FieldTrip but can also be downloaded here as separate toolboxes. In the past these functions were combined in one toolbox.

Please note that if you are an end-user interested in analyzing experimental EEG/MEG data, you will probably will want to use the high-level FieldTrip functions. The functions such as **ft_preprocessing**, **ft_timelockanalysis** and **ft_sourceanalysis** provide a user-friendly interface that take care of all relevant analysis steps and the data bookkeeping.

## Module layout

The forward module contains the methods to compute the solution to the volume conduction problem, i.e. “What is the potential or field distribution given a known source?”.

The inverse module contains the methods to estimate the source parameters, i.e. to answer the question “What are the unknown source parameters, given the observed EEG or MEG field distribution?”.

It contains high-level functions that are publicly available for experienced end-user. The functionality of these functions within these modules depend on low-level functions which are not available to the end-user and combined in a private directory.

## Supported methods for inverse estimation of the source parameters

The inverse methods for computing a source reconstruction can be divided into three categories: **dipole fitting** (using an overdetermined model with a few sources), **dipole scaning** (using a metric that can be computed independently on each point of a grid) and **distributed source modelling** (using an underdetermined distributed source model). The following source reconstruction methods are implemented

- dipole fitting
- simultaneous optimisation of position, orientation and strength
- symmetry constrains and/or fixed position, with free orientation and strength

- dipole scanning
- dynamic imaging of coherent sources (DICS)
- linear constrained minimum variance (LCMV)
- partial canonical coherence (PCC)
- multiple signal classification (MUSIC)
- scanning for residual variance

- distributed source modeling
- minimum norm estimation with and without noise regularisation (MNE)

## Definition of the function-calls (API)

The functions for the inverse computation of the source activity, i.e. for computing the source reconstruction are

[dipout] = dipole_fit(dip, sens, vol, dat, ...) [dipout] = beamformer_dics(dip, sens, vol, dat, cov, ...) [dipout] = beamformer_lcmv(dip, sens, vol, dat, cov, ...) [dipout] = beamformer_pcc(dip, sens, vol, dat, cov, ...) [dipout] = music(dip, sens, vol, dat, ...) [dipout] = minimumnormestimate(dip, sens, vol, dat, ...) [dipout] = residualvariance(dip, sens, vol, dat, ...)

The input array “pos” contains the dipole position (1×3 or Nx3).

The input structure “dip” contains the initial dipole model or dipole grid that is used for source reconstruction.

The input structure “sens” contains the electrode positions or the gradiometer positions and orientations.

The input structure “vol” contains the geometry and conductivity of the volume conductor model.

Most functions have additional optional input arguments that are specified as key-value pairs.

We are currently redesigning the interface to these functions, therefore the documentation is a bit sparse at the moment.

# Related documentation

The literature references to the implemented methods are given here.

Frequently asked questions about forward and inverse modeling:

2009/11/09 15:25 | ||

2009/02/17 15:18 | Robert Oostenveld | |

2009/02/17 15:16 | Robert Oostenveld | |

2012/08/17 10:23 | Robert Oostenveld | |

2012/03/02 15:55 | ||

2010/04/25 07:50 | Robert Oostenveld | |

2013/12/05 11:01 | Robert Oostenveld | |

2011/09/07 09:57 | ||

2011/11/10 11:01 | Jan-Mathijs Schoffelen | |

2010/10/06 16:30 | Robert Oostenveld | |

2009/02/17 15:18 | Robert Oostenveld | |

2010/01/12 10:44 | ||

2009/02/17 15:15 | Robert Oostenveld | |

2009/02/26 22:06 | ||

2016/07/13 10:51 | Robert Oostenveld | |

2009/02/17 15:16 | Robert Oostenveld | |

2016/11/30 10:54 | Robert Oostenveld |

Example material for forward and inverse modelingde:

2009/03/03 21:52 | ||

2016/11/09 12:04 | Robert Oostenveld | |

2012/08/09 20:01 | Lilla Magyari | |

2014/09/25 19:55 | ||

2009/03/03 21:52 | ||

2009/03/03 21:52 | ||

2009/07/31 11:49 | ||

2009/07/09 20:11 | ||

2010/07/21 11:04 | Robert Oostenveld | |

2009/05/20 14:57 | ||

2018/05/30 15:57 | Robert Oostenveld | |

2015/11/29 10:55 | Robert Oostenveld | |

2009/05/20 14:57 | ||

2010/04/22 09:01 | ||

2009/03/05 16:56 | Saskia Haegens | |

2009/10/29 16:22 | ||

2009/03/03 21:58 |

Ttutorial material for forward and inverse modeling:

2010/01/13 15:59 | ||

2016/01/04 15:54 | ||

2016/01/04 15:50 | ||

2015/11/23 14:44 | ||

2014/11/12 15:03 | ||

2009/11/03 14:35 | ||

2017/08/18 12:38 | Simon Homölle | |

2017/10/20 09:31 | Robert Oostenveld | |

2009/05/20 14:57 | ||

2013/02/21 14:59 | Jörn M. Horschig | |

2015/07/15 15:33 | NLam | |

2011/07/06 11:47 | Lilla Magyari |