Add Physio object generation from BIDS structures

[maestroque]

The end goal for this issue, would be to have a function that will generate a list of Physio objects, given a BIDS structure, along with an MRI data object. These could be encompassed in a multimodal Physio object in the future

[maestroque]

@m-miedema @me-pic I have a question regarding the commonly used BIDS layouts.

In the v1.9.0 BIDS spec, only the following column labels are specified. And they are not standardized, just recommended:

In your experience, are those conventions followed? Specifically regarding the trigger. Because I would like to detect column names in order to create the appropriate object (either Physio or the MRI trigger data object). Also for example in some datasets (example), it's not followed and the triggers are provided as tr. Other than those two what could other commonly used labels be, in order to be taken into account? For starters, I will just stick to the BIDS spec recommendations

[me-pic]

What about using something like what is implemented in phys2bids where there is an automatic search for the trigger channel based on the naming convention, but users could also have the possibility to specify the index of the trigger channel (see chtrig in phys2bids) ?

[maestroque]

This would aim to be used after phys2bids though, as BIDS output structures would be made into Physio objects to feed into peakdet or phys2denoise.
Would it seem like a good idea, to follow only the phys2bids naming convention for intra-physiopy package compatibility for starters?
@me-pic

[m-miedema]

In the v1.9.0 BIDS spec, only the following column labels are specified. And they are not standardized, just recommended:

These are indeed fairly uncommonly used, to my knowledge. We often use the column labels corresponding to our data acquisition device conventions. Our BIDS Extension Proposal(s) are aimed at reducing some of this ambiguity, but between backwards compatibility and optional depth of labelling, some will always remain.