This is a collaborative space. In order to contribute, send an email to maximilien.chaumon@icm-institute.org
On any page, type the letter L on your keyboard to add a "Label" to the page, which will make search easier.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

APP UNDER DEVELOPMENT PRIVATE APP ON BL

This app aims at computing the mean transformation matrix across all runs of a MEG session to correct the head position of all runs thanks to this matrix. This mean transformation matrix is stored in an empty .fif file, which then can be passed as a parameter in mne.preprocessing.maxwell_filter (destination parameter).

GitHub repository

https://github.com/AuroreBussalb/app-mean-transformation-matrix

Brainlife datatype used:

Inputs of the App:

Files

Format

Datatype

Description

Optional

MEG signal

.fif

meg/fif

first run

No

MEG signal

.fif

meg/fif

second run

No

…

…

…

…

Yes

MEG signal

.fif

meg/fif

nth run

Yes

At least two runs are required.

Output of the App:

Files

Format

Datatype

Description

Raw file

.fif

meg/fif-override

  • Info and fake data created

  • the mean transformation matrix is contained in raw.info["dev_head_t"]["trans"]

Besides, in the output directory, there are the optional files we will use in a next App. This is mandatory, because the App that will be run after app-mean-transformation-matrix will take as input all the files in app-mean-transformation-matrix’s output directory corresponding to the datatype of the input of the next App (see How to run Apps one after another).

Parameters of the App

The parameters of the App correspond to the parameters passed to the Python functions used in the App. They are listed in the config.json.example when you test your App locally, then when you register you App on Brainlife, you enter them and a config.json is created by Brainlife.

Here, we used the parameters set by default by mne.

Next improvements

  • Rename it into “app-compute-realigment-matrix”?

  • Allow the user to compute a destination.fif that is not the mean of all the runs but a specific run? To do so, it would be best not to save the entire .fif file (i.e. the MEG signal) but to extract the raw.info[“dev_head_t"]["trans"] from this file and put it in an empty fif file, like we do when we compute the mean of the runs (it would save space).

  • No labels