README.rst 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137
  1. studyforrest.org Dataset
  2. ************************
  3. |license| |access| |doi|
  4. Retinotopic Mapping
  5. ===================
  6. All participants in the phase2 extension of the studyforrest dataset underwent
  7. retinotopic mapping with standard flickering checkerboard stimulus (ring and
  8. wedges). More information on the procedure and the results can be found in:
  9. Ayan Sengupta, Falko R. Kaule, J. Swaroop Guntupalli, Michael B. Hoffmann,
  10. Christian Häusler, Jörg Stadler, Michael Hanke. `An extension of the
  11. studyforrest dataset for vision research
  12. <http://biorxiv.org/content/early/2016/03/31/046573>`_. (submitted for
  13. publication)
  14. For further information about the project visit: http://studyforrest.org
  15. Content
  16. -------
  17. ``code/``:
  18. source code for retinotopic mapping analysis.
  19. - The main script is *process_retmap* and a Python based GUI *easyret_gui* to
  20. call it from an easy to use front end. The *process_retmap* script calls the
  21. Python scripts *RetMap_phaseshift* for post processing phase shift (if
  22. required) and *combine_volumes* for combining the clw/ccw maps and ecc/con
  23. maps together.
  24. ``src/``:
  25. links to repositories containing all inputs for the analysis
  26. ``sub-??/``:
  27. analysis results per participant
  28. ``surface_maps/``:
  29. contains eccentricity and polar angle maps of left and right hemispheres
  30. of a particular participant's cortical surface in *MGH* format
  31. ``post_processing/``:
  32. contains the post-processed/combined compressed *NIfTI* files in a
  33. participant's bold3Tp2 image template space
  34. (see ``src/templatetransforms``), before it is aligned to the
  35. *T1 structural* and represented on cortical surfaces.
  36. ``qa/``:
  37. contains the *pyretmap_subjQuali.ods* file which details the quality of the
  38. participant-wise retinotopic maps produced by the *processing pipeline*.
  39. How to obtain the data files
  40. ----------------------------
  41. This repository is a `DataLad <https://www.datalad.org/>`__ dataset. It provides
  42. fine-grained data access down to the level of individual files, and allows for
  43. tracking future updates up to the level of single files. In order to use
  44. this repository for data retrieval, `DataLad <https://www.datalad.org>`_ is
  45. required. It is a free and open source command line tool, available for all
  46. major operating systems, and builds up on Git and `git-annex
  47. <https://git-annex.branchable.com>`__ to allow sharing, synchronizing, and
  48. version controlling collections of large files. You can find information on
  49. how to install DataLad at `handbook.datalad.org/en/latest/intro/installation.html
  50. <http://handbook.datalad.org/en/latest/intro/installation.html>`_.
  51. Get the dataset
  52. ^^^^^^^^^^^^^^^
  53. A DataLad dataset can be ``cloned`` by running::
  54. datalad clone <url>
  55. Once a dataset is cloned, it is a light-weight directory on your local machine.
  56. At this point, it contains only small metadata and information on the
  57. identity of the files in the dataset, but not actual *content* of the
  58. (sometimes large) data files.
  59. Retrieve dataset content
  60. ^^^^^^^^^^^^^^^^^^^^^^^^
  61. After cloning a dataset, you can retrieve file contents by running::
  62. datalad get <path/to/directory/or/file>
  63. This command will trigger a download of the files, directories, or
  64. subdatasets you have specified.
  65. DataLad datasets can contain other datasets, so called *subdatasets*. If you
  66. clone the top-level dataset, subdatasets do not yet contain metadata and
  67. information on the identity of files, but appear to be empty directories. In
  68. order to retrieve file availability metadata in subdatasets, run::
  69. datalad get -n <path/to/subdataset>
  70. Afterwards, you can browse the retrieved metadata to find out about
  71. subdataset contents, and retrieve individual files with ``datalad get``. If you
  72. use ``datalad get <path/to/subdataset>``, all contents of the subdataset will
  73. be downloaded at once.
  74. Stay up-to-date
  75. ^^^^^^^^^^^^^^^
  76. DataLad datasets can be updated. The command ``datalad update`` will *fetch*
  77. updates and store them on a different branch (by default
  78. ``remotes/origin/master``). Running::
  79. datalad update --merge
  80. will *pull* available updates and integrate them in one go.
  81. More information
  82. ^^^^^^^^^^^^^^^^
  83. More information on DataLad and how to use it can be found in the DataLad Handbook at
  84. `handbook.datalad.org <http://handbook.datalad.org/en/latest/index.html>`_. The
  85. chapter "DataLad datasets" can help you to familiarize yourself with the
  86. concept of a dataset.
  87. .. _Git: http://www.git-scm.com
  88. .. _git-annex: http://git-annex.branchable.com/
  89. .. |license|
  90. image:: https://img.shields.io/badge/license-PDDL-blue.svg
  91. :target: http://opendatacommons.org/licenses/pddl/summary
  92. :alt: PDDL-licensed
  93. .. |access|
  94. image:: https://img.shields.io/badge/data_access-unrestricted-green.svg
  95. :alt: No registration or authentication required
  96. .. |doi|
  97. image:: https://img.shields.io/badge/doi-missing-lightgrey.svg
  98. :target: http://dx.doi.org/
  99. :alt: DOI