Attendees
Soichi Hayasi
Guiomar Niso
Brent McPherson
The datatype can be anything with Brainlife
the choice of the datatype is up to the developer
a lot of Apps can handle the same datatype
It’s possible to deprecate a datatype
Generic network datatype: combine different datatypes (maybe useful for connectivity using MEG and fMRI)
Best not to create your own datatype, best to use existing datatypes because Apps will communicate through datatypes
Sometimes an App can be used in a way we don’t expect
Datatype is usually linked to a toolbox environment: this shouldn’t be the case in MEG
If in a pipeline we used Apps based on different toolboxes (MNE, Brainstorm, …), converters between Apps may be needed
using converters between each App can become heavy
in the early steps of processing of a pipeline, converters may not be needed but between more sophisticated steps, converters may be needed
No need for an App to read a lot of inputs formats (3 is fine)
Brainlife team works on updating how Brainlife inputs MEG and EEG datasets
for now, there are 23 datasets EEG and 7 datasets MEG
possible to import these datasets in Brainlife
Creation of visualization tools for raw MEG and EEG by the Brainlife team
Brainstorm visualization tools are very strong
but using Brainstorm in Brainlife seems redundant: Guio will start with MNE and she is in contact with the creator of Brainstorm to discuss how Brainstorm Apps can be integrated in Brainlife
0 Comments