You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for non-DICOM datasets (such as those from LONI IDA, HCP etc), key properties of MR volumes present only in NIfTI headers but NOT in JSON sidecars e.g., number of volumes, voxel size, image dimensions, and image obliquity... Hence, this also should be a format we support by default
The text was updated successfully, but these errors were encountered:
Unless the dataset provides hierarchical information ( e.g. dataset, modality, subject, session) it would be difficult to organize NIfTI-only datasets for protocol compliance. The hierarchical organization is straightforward in BIDS dataset, but it may not be the same for other datasets such as from LONI IDA. For example, ADNI provides an XML file to store hierarchical information.
they are all coming from similar projects, so there is definitely correspondence, its a matter of us writing the datasets parsers and populating methods :). let's discuss that.
for non-DICOM datasets (such as those from LONI IDA, HCP etc), key properties of MR volumes present only in NIfTI headers but NOT in JSON sidecars e.g., number of volumes, voxel size, image dimensions, and image obliquity... Hence, this also should be a format we support by default
The text was updated successfully, but these errors were encountered: