mrikasper
commented
1 year ago Dear Darius,
This is a good point, and was on our mind for a while (also for another format, [ISMR]MRD). The issue, as so often, is time and resources, so the more users want this functionality, the more we can gravitate to prioritize its development.
At the moment, we are keen on finishing the BIDS-writer part with @likeajumprope (see here) and incorporating some external and internal improvements for the next release. But after May, we might have some resources.
If you, on the other hand, would like to implement such a functionality, we will support these efforts wholeheartedly and you can join as an external developer (see CONTRIBUTING guide).
Technically, I think retrieving the information to populate the input parameters of PhysIO is straightforward (log_files for the physiological logfiles, sqpar for the sequence timing parameters and synchronization, model for motion and aCompCor input files). I am not sure what the BIDS-appification entails beyond that in terms of API (e.g., does it have to be a compiled version of the code via Neurodesk or is it OK within Matlab). The user would still have to decide what types of model output they want, which is currently done via the Matlab .m files or SPM job files (as in the examples).
Let me know if this helps - I am happy to hear more about your ideas.
All the best, Lars
We were wondering if there are any plans to expand PhysIO with BIDSapps-style read in of data (i.e. inputting a BIDS subject directory and automatically running PhysIO on the contained logfile-fMRI file pairs?)
Best, Darius