README.rst 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115
  1. studyforrest.org Dataset
  2. ************************
  3. |license| |access|
  4. Pre-aligned MRI data
  5. ====================
  6. This repository contains data derived from the raw data releases of the
  7. *studyforrest.org* project. In particular these are:
  8. * BOLD fMRI timeseries aligned to subject-specific template images
  9. and using transformations available from
  10. https://github.com/psychoinformatics-de/studyforrest-data-templatetransforms
  11. For more information about the project visit: http://studyforrest.org
  12. File name conventions
  13. ---------------------
  14. Each directory in the subject directories corresponds to one template image
  15. space. Data in ``sub*`` directories are participant-specific (not aligned
  16. across participants). However, templates with
  17. the same name have corresponding input data.
  18. Each directory contains one or more image files with more-or-less
  19. self-explanatory names, identifying the corresponding participant and scan.
  20. Lastly, the ``code/`` directory contains the source code for computing all
  21. files contained, as well as a number of validation analyses.
  22. How to obtain the dataset
  23. -------------------------
  24. This repository is a `DataLad <https://www.datalad.org/>`__ dataset. It provides
  25. fine-grained data access down to the level of individual files, and allows for
  26. tracking future updates. In order to use this repository for data retrieval,
  27. `DataLad <https://www.datalad.org>`_ is required.
  28. It is a free and open source command line tool, available for all
  29. major operating systems, and builds up on Git and `git-annex
  30. <https://git-annex.branchable.com>`__ to allow sharing, synchronizing, and
  31. version controlling collections of large files. You can find information on
  32. how to install DataLad at `handbook.datalad.org/en/latest/intro/installation.html
  33. <http://handbook.datalad.org/en/latest/intro/installation.html>`_.
  34. Get the dataset
  35. ^^^^^^^^^^^^^^^
  36. A DataLad dataset can be ``cloned`` by running::
  37. datalad clone <url>
  38. Once a dataset is cloned, it is a light-weight directory on your local machine.
  39. At this point, it contains only small metadata and information on the
  40. identity of the files in the dataset, but not actual *content* of the
  41. (sometimes large) data files.
  42. Retrieve dataset content
  43. ^^^^^^^^^^^^^^^^^^^^^^^^
  44. After cloning a dataset, you can retrieve file contents by running::
  45. datalad get <path/to/directory/or/file>
  46. This command will trigger a download of the files, directories, or
  47. subdatasets you have specified.
  48. DataLad datasets can contain other datasets, so called *subdatasets*. If you
  49. clone the top-level dataset, subdatasets do not yet contain metadata and
  50. information on the identity of files, but appear to be empty directories. In
  51. order to retrieve file availability metadata in subdatasets, run::
  52. datalad get -n <path/to/subdataset>
  53. Afterwards, you can browse the retrieved metadata to find out about
  54. subdataset contents, and retrieve individual files with ``datalad get``. If you
  55. use ``datalad get <path/to/subdataset>``, all contents of the subdataset will
  56. be downloaded at once.
  57. Keep data up-to-date
  58. ^^^^^^^^^^^^^^^^^^^^
  59. DataLad datasets can be updated. The command ``datalad update`` will *fetch*
  60. updates and store them on a different branch (by default
  61. ``remotes/origin/master``). Running::
  62. datalad update --merge
  63. will *pull* available updates and integrate them in one go.
  64. Find out what has been done
  65. ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  66. DataLad datasets contain their history in the ``git log``.
  67. By running ``git log`` (or a tool that displays Git history) in the dataset or on
  68. specific files, you can find out what has been done to the dataset or to individual files
  69. by whom, and when.
  70. More information
  71. ^^^^^^^^^^^^^^^^
  72. More information on DataLad and how to use it can be found in the DataLad Handbook at
  73. `handbook.datalad.org <http://handbook.datalad.org/en/latest/index.html>`_. The
  74. chapter "DataLad datasets" can help you to familiarize yourself with the
  75. concept of a dataset.
  76. .. |license|
  77. image:: https://img.shields.io/badge/license-PDDL-blue.svg
  78. :target: http://opendatacommons.org/licenses/pddl/summary
  79. :alt: PDDL-licensed
  80. .. |access|
  81. image:: https://img.shields.io/badge/data_access-unrestricted-green.svg
  82. :alt: No registration or authentication required