Goal
The main scope of the MRIConfig class is to contain all the relevant information about the MRI scan, that are useful in the following steps of the data processing workflow. These are currently stemming from phys2denoise functions, namely slice_timings, n_scans and tr and are used in metrics computations. Integrating a structure containing those into the Physio object would greatly facilitate the relevant workflow.
Implementation
The acquisition of those parameters could be:
- Manually given by the user
- Automatically detected from the trigger channel of a physio recording.
Especially in case this is done through the load_from_bids function, the trigger channel would be automatically used as a source of acquisition, unless specified against.
Then, the load_from_bids function should output an object containing the array of Physio objects, and an MRIConfig class. This could be the aforementioned multimodal Physio class.
Goal
The main scope of the
MRIConfigclass is to contain all the relevant information about the MRI scan, that are useful in the following steps of the data processing workflow. These are currently stemming fromphys2denoisefunctions, namelyslice_timings,n_scansandtrand are used in metrics computations. Integrating a structure containing those into the Physio object would greatly facilitate the relevant workflow.Implementation
The acquisition of those parameters could be:
Especially in case this is done through the
load_from_bidsfunction, the trigger channel would be automatically used as a source of acquisition, unless specified against.Then, the
load_from_bidsfunction should output an object containing the array of Physio objects, and an MRIConfig class. This could be the aforementioned multimodal Physio class.