Robert Smith

Posting to register personal investment in this functionality, and to hopefully draw an update on what would be required to contribute given any changes to transformation handling that have happened...

Note that not all transformations necessary to generate the output data will be pre-calculated and available in the existing BIDS Derivatives fmriprep directory. Eg. slice timing correction will need to...

After an initial attempt at this, I decided that implementing and maintaining a stand-alone command for performing this reconstruction would be cumbersome. I am instead focusing on having a command-line...

This will require two small applications for inclusion in the workflow: 1. Generation of a single file of some format that includes the affine transformation (likely in the 1x12 ITK...

Relates to #2207.

Presumably the interface for this would be as a standard space *modifier*. As described [here](https://fmriprep.org/en/21.0.2/spaces.html#standard-spaces) for resolution and sub-cohort selection, a modifier would specify the complexity of the transformation. Primarily...

Already [have the tool](https://mrtrix.readthedocs.io/en/latest/reference/commands/transformcalc.html#transformcalc) to get the rigid component of an affine. In retrospect, given it's a rigid-body and can therefore be applied to the pre-processed BOLD data in T1w...

> I would note that BIDS is itself strict about the order of entities I hadn't actually realised that, I'd always assumed that everything between subject/session and suffix was permutable....

Can confirm that BIDS validator `1.8.5` does *not* issue any message relating to the fact that the order of entities is inconsistent with the specification.

Occurred to me that another potentially useful exemplar to show for inheritance would be two images split across "`_part-mag`" and "`_part-phase`" with a single JSON file being applicable to both...