Public-s3: the name we select for our special remote, so that git-annex and DataLad can identify it The options used in this example include: $ git annex initremote public-s3 type =S3 encryption =none \ bucket = $BUCKET public =yes datacenter =EU autoenable = true Before, the only “sibling” is the actual DataLad dataset: This can be verifiedīy running datalad siblings before and after initializing the special Is that a sibling is added to the DataLad dataset. The steps below have been adapted from instructions provided on git-annex documentation.īy initializing the special remote, what actually happens in the background Scanning for unlocked files (this may take some time )Ĭreate (ok ): /Users/jsheunis/Documents/neuro-data-s3 (dataset )Īdd (ok ): dataset_description.json (file )Īdd (ok ): sub-01/anat/sub-01_T1w.nii (file )Īdd (ok ): sub-01/func/sub-01_task-auditory_bold.nii (file )Īdd (ok ): sub-01/func/sub-01_task-auditory_events.tsv (file )Īdd (ok ): task-auditory_bold.json (file ) $ datalad create -force -description "neuro data to host on s3" Creating a new annex repo at /Users/jsheunis/Documents/neuro-data-s3 Now we can view the directory tree to see the dataset content: Inflating: neuro-data-s3/MoAEpilot/sub-01/anat/sub-01_T1w.nii Inflating: neuro-data-s3/MoAEpilot/sub-01/func/sub-01_task-auditory_bold.niiĬreating: neuro-data-s3/MoAEpilot/sub-01/anat/ Inflating: neuro-data-s3/MoAEpilot/sub-01/func/sub-01_task-auditory_events.tsv Inflating: neuro-data-s3/MoAEpilot/CHANGESĬreating: neuro-data-s3/MoAEpilot/sub-01/Ĭreating: neuro-data-s3/MoAEpilot/sub-01/func/ Inflating: neuro-data-s3/MoAEpilot/dataset_description.json Inflating: neuro-data-s3/MoAEpilot/README Inflating: neuro-data-s3/MoAEpilot/task-auditory_bold.json Unzip neuro-data-s3.zip -d neuro-data-s3
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |