Julien Cohen-Adad

> > > Do you think the spec is implying or just suggesting that _dwi.nii.gz implies _dwi.bval and _dwi.bvec here? > > > > > > dwi data definitely need...

Thank you for your feedback @sandrinebedard and @kousu. I agree it is unrealistic to have a single derivatives/ folder that will accommodate all related research for the next 50 years...

> Anyway I think we could probably replace spine-generic-processed with just the set of files in this last list. Then the two datasets would collectively be normalized. sorry i'm not...

@valosekj these issues are _only_ about data quality (not about issues with segmentations, which should be dealt with in release-specific issues, like #35), which hamper the relevance/quality of the output...

I would remove (for MTsat and T1): - sub-fslAchieva04_acq-T1w_MTS.nii.gz - sub-beijingPrisma01_acq-T1w_MTS.nii.gz The other scans seem acceptable.

> But, fix of SC segmentations (#35 (comment)) can fix these outlier values. the segmentations did not seem crazy to me, but we'll see. @alexfoias did them, so i'll upload...

wow! great catch @valosekj 👍

fslAchieva-01 and 02 are _also_outliers, with MTsat values around 7. json file for MTon/off: ~~~ "RepetitionTime": 0.057, --> under specs ~~~ Ah! the problem might be related to the signal...

good catch @leandervaneekelen 🎉 here is the culprit: https://github.com/spine-generic/data-multi-subject_DO-NOT-USE/issues/10 we need to fix this inconsistency (rename the seg)

> Just `sudo` it. oopsi 😬 ~~~ [jcohen@gra-login2 ~]$ sudo rm -rf data-multi-subject We trust you have received the usual lecture from the local System Administrator. It usually boils down...