Older versions Open Neuro

Hi there,

Just wondered if the old versions of data were still available on Open Neuro and I’m just missing it. They used to be on Open fMRI and my FSL tutorial series on YouTube used an older version of ds00008.

Thanks!
Jeanette

Hi @Jeanette_Mumford

Thank you for your question! When OpenfMRI was merged over to OpenNeuro the most recent version of the dataset was merged over. Legacy datasets are available on OpenfMRI too (with the past sets on OpenfMRI)

Thank you,
Franklin

Hi Franklin!

Thanks. The only thing I don’t understand is how to get to OpenfMRI. As soon as I click on a data set it jumps to openNeuro. I’m trying to access ds0008 that would have been available on Jan 18, 2016. Thanks!

Jeanette

Ahh, I see. To access the legacy OpenfMRI datasets, they can be found by searching on legacy.openfmri.org. So ds00008 would be at - https://legacy.openfmri.org/dataset/ds000008/ . It appears version 1.0.1 would have been available on Jan 18, 2016. The 1.1.0 version was released about a month later.

Thank you,
Franklin

Great, thanks!

Cheers,
Jeanette

here is datalad way:
$> datalad install ///openfmri/ds000008
[INFO ] Cloning http://datasets.datalad.org/openfmri/ds000008 [1 other candidates] into ‘/tmp/ds000008’
[INFO ] access to dataset sibling “datalad” not auto-enabled, enable with:
| datalad siblings -d “/tmp/ds000008” enable -s datalad
install(ok): /tmp/ds000008 (dataset)
1 11117
hopa:/tmp
$> cd ds000008
CHANGES sub-01/ sub-05/ sub-10/ sub-14/
README sub-02/ sub-06/ sub-11/ sub-15/
dataset_description.json sub-03/ sub-07/ sub-12/ task-conditionalstopsignal_bold.json
participants.tsv sub-04/ sub-09/ sub-13/ task-stopsignal_bold.json
1 11118
(git-annex)hopa:/tmp/ds000008[master]
$> git tag
1.0.0
1.1.0
1.1.1
1.1.1+1
2.0.0
2.0.0+1
2.0.0+2
2.0.0+3
2.0.0+4
1 11119
(git-annex)hopa:/tmp/ds000008[master]
$> git co 1.0.0
Note: checking out ‘1.0.0’.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 57078104 Merge branch 'incoming-processed'

(git-annex)hopa:/tmp/ds000008
$> datalad get sub001/anatomy 
get(ok): /tmp/ds000008/sub001/anatomy/highres001_brain_mask.nii.gz (file) [from web...]                         
get(ok): /tmp/ds000008/sub001/anatomy/inplane_brain.nii.gz (file) [from web...]                                 
get(ok): /tmp/ds000008/sub001/anatomy/inplane.nii.gz (file) [from web...]                                       
get(ok): /tmp/ds000008/sub001/anatomy/highres001_brain.nii.gz (file) [from web...]   | 0.00/737k [00:00<?, ?B/s]
get(ok): /tmp/ds000008/sub001/anatomy/highres001.nii.gz (file) [from web...]                                    
get(ok): /tmp/ds000008/sub001/anatomy (directory)
action summary:
  get (ok: 6)