Open shnizzedy opened 2 years ago
Additional comments / updates not slated for 1.8.5:
h5
or nii.gz
for output transformstsv
or 1D
for output timeseriescorrelations
β conmat
& nodenames
per BEP017
Correlations aren't in the spec yet, but there's a BEP with some good conventions: https://docs.google.com/document/d/1ugBdUF6dhElXdj3u9vw0iWjE6f_Bibsro3ah7sRV0GA/edit. Basically, use the conmat suffix, there's a measure entity for the connectivity measure to keep it separate from "desc", and you need a "nodenames" sidecar file to indicate the atlas node names, because the TSV won't have a header or index.
_motion
outputs fully in compliance with BEP012 via #1576 / #1624
desc-preproc-1
,desc-preproc-2
becomesdesc-preprocReg36Parameter
,desc-preprocRegACompCor
)_motion
outputs closer to compliance with BEP012 via #1832desc-binarizedSmZstd_degreeCentrality.nii.gz
could usedesc-smZstd_dcb
if you want, based on thedcb
suffix in BEP012. BEP012 also has alfcdb
for binarized local functional connectivity density andlfcdw
for the weighted version (in #1849)res-derivative
to give the actual resolution (in #1849)timeseries
andcorrelations
should be post-regression (in #1849)desc-preproc_T1w.nii.gz
is different from otherT1w
s if includedrbc-options
rbc-options
outputs (#1820)desc-preproc_T1w.nii.gz
(in #1820)space-{template}_desc-preproc_T1w.nii.gz
(in #1820)space-{template}_desc-brain_mask.nii.gz
(in #1820)