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
Describe the bug
Downloading ds001705 via aws does not download the latest version of the dataset (v1.0.1) nor does it download the original version of the dataset (v1.0.0). It seems to download a hybrid mix of both versions of the dataset.
Notice how this download via aws includes files such as sub-000101/ses-baseline/pet/sub-000101_ses-baseline_rec-MLEM_pet.json which, according to the website, are included in v1.0.0 and not in v1.0.1, however this is not simply a download of v1.0.0 of the dataset, since files such as sub-000101/ses-baseline/pet/sub-000102_ses-baseline_K1.nii.gz are not included.
Expected behavior aws s3 --no-sign-request sync s3://openneuro.org/ds001705 ./ds001705 should produce a local directory structure that matches the latest version of the dataset
Hi, thanks for the bug report. This looks like it may be an issue with git-annex, so I've reported what I found there and we'll investigate further. In the meantime, you should be able to download a consistent export of 1.0.1 with datalad or git-annex, it is a complete export but delete markers are missing for the non-annexed files.
Describe the bug
Downloading
ds001705
via aws does not download the latest version of the dataset (v1.0.1) nor does it download the original version of the dataset (v1.0.0). It seems to download a hybrid mix of both versions of the dataset.To Reproduce
Steps to reproduce the behavior:
aws s3 --no-sign-request sync s3://openneuro.org/ds001705 ./ds001705
cd ./ds001705
tree
sub-000101/ses-baseline/pet/sub-000101_ses-baseline_rec-MLEM_pet.json
which, according to the website, are included in v1.0.0 and not in v1.0.1, however this is not simply a download of v1.0.0 of the dataset, since files such assub-000101/ses-baseline/pet/sub-000102_ses-baseline_K1.nii.gz
are not included.Expected behavior
aws s3 --no-sign-request sync s3://openneuro.org/ds001705 ./ds001705
should produce a local directory structure that matches the latest version of the datasetAdditional context
Possibly related to #2319
The text was updated successfully, but these errors were encountered: