Status | ||||
---|---|---|---|---|
|
|
Status | ||||
---|---|---|---|---|
|
This App epochs the data thanks to mne.Epochs.
GitHub repository
https://github.com/AuroreBussalb/app-make-epochs
Brainlife datatype used:
For input: neuro/meg/fif and neuro/meg/fif-override
For outputs: neuro/meg/fif
Inputs of the App
Files | Format | Datatype | Description | Optional |
---|---|---|---|---|
MEG signals | .fif | meg/fif | The data we want to epoch | No |
events | .tsv | meg/fif or meg/fif-override | BIDS compliant events.tsv | no |
This events file can be obtained thanks to the app-get-events
(if so, the file will be linked to the meg/fif-override
datatype) or can be directly available with the meg.fif in the meg/fif
datatype. If there are two events.tsv (one from meg/fif
datatype and the other from meg/fif-override
datatype, only the file from the meg/fif-override
will be used (see How to use the meg/fif-override datatype).
Outputs of the App:
Files | Format | Datatype | Description |
---|---|---|---|
MEG signals | .fif | meg/fif | Epoch data |
Besides, in the output directory, there are the optional files that can be used in a 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. Their default values proposed in Brainlife or in config.json.example
correspond to the default values of MNE Python 0.23.
Note |
---|
With the MNE function used to create epoch, it is possible to directly removed epoch based on their amplitude with the parameters |
Next improvements
Be able to use the
flat
andreject
parameters: register this parameter as aSTRING
in BL and convert it into a Python dict inmake_epochs.py
Make sure that epochs are correctly created with an
events.tsv
frommeg/fif
datatype and fromevents.tsv
extracted from the fif file withapp-get-events