-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a git-annex repo for data from basel/6900_nifti_20
#20
Comments
In this case, the data is stored in As for the segmentation, the segmentations also don't have the a json sidecar. They were done for both thoratic and cervical chunks but only for sag pd images. The segmentations are also stored as nii.gz files. @jcohenadad Should I consider that the contacts for this data is the same as the one for @mguaypaq Could you create the git-annex repo |
yes and yes. Please also refer to this discussion in the README. |
The script
The Ready to be pushed when repo is created. |
Code was updated to use The code was run using: python ms-basel-2020/code/bidsification.py --i 6900_nifti_20/ --o ms-basel-2020/ --s 6900_20_lesions-PD/ Ready to be pushed when repo is ready. |
The repo is created, and @plbenveniste has write access: |
PR was opened and it is ready for review ! |
The naming conventions were reviewed (by me) and everything looked fine ! |
The data is stored in
duke/mri/basel/6900_nifti_20
and the segmentations induke/mri/basel/6900_20_lesions-PD
The steps are the following:
@jcohenadad What name should be used for the git-annex repo ?
ms-basel-pd-6900
?Another strategy could be to merge this data with the other dataset under construction from basel (issue #19)
The text was updated successfully, but these errors were encountered: