Julien Cohen-Adad

thanks @alexfoias . Additional info: the image has anisotropic resolution (1x1x5mm), hence the "squashing" appearance, which should be accounted with the pixel size / affine matrix. Here is how it...

thanks for the quick response @pbellec 🙏 > the easiest fix is to add an isotropic background, nilearn/nilearn#2546 of similar FOV, with opacity=1 this seems the best option indeed, as...

@pbellec while you're here: another _really_ cool feature would be to be able to zoom on the image. Do you know if that's possible, and if not, if other technologies/implementations...

can you give us more context? also, this project is no more maintained. Please see the new active project ivadomed

> Do these variations come from varying [versions of the protocol](https://github.com/spine-generic/protocols/blob/main/CHANGES.md)? Good question. It is possible and could easily be verified (someone needs to invest 15min to look at previous...

> Regarding the variations in ReceiveCoilActiveElements for the same ReceiveCoil, is it possible that the scanner automatically (de-)activates coil-elements based on pre-scan measurements? yes, the scanner automatically selects coils, not...

This is a valid concern. However, merging these participants would break the [analysis code](https://github.com/spine-generic/spine-generic), so there is a pros/cons here.

thank you @kousu, this seems like a very reasonable plan. In terms of index vs. scanner name in the filename, i do have a slight preference for encoding in the...

Reviving this thread, given a recent comment https://github.com/spine-generic/data-multi-subject/issues/166 and the demographic-based project from @renelabounek. We should find a reasonable strategy to deal with the same subjects being scanned at multiple...

it would be good if @NathanMolinier can vet this (sorry Nathan, you are now our internal BIDS consultant 😅)