Scheduled service maintenance on November 22


On Friday, November 22, 2024, between 06:00 CET and 18:00 CET, GIN services will undergo planned maintenance. Extended service interruptions should be expected. We will try to keep downtimes to a minimum, but recommend that users avoid critical tasks, large data uploads, or DOI requests during this time.

We apologize for any inconvenience.

aggregate brain region wise timeseries data

Adina Wagner 2ccaa11554 Merge pull request #1 from loj/README 3 years ago
.datalad fb404dd225 [DATALAD] new dataset 7 years ago
atlases 594256ee5e Add Shen et al. (2013) atlas 8 years ago
code 0b98239b10 Move aggregate data into subfolder 7 years ago
src e7ac59ac5d Register input data 8 years ago
sub-01 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-02 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-03 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-04 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-05 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-06 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-09 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-10 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-14 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-15 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-16 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-17 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-18 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-19 0b98239b10 Move aggregate data into subfolder 7 years ago
sub-20 0b98239b10 Move aggregate data into subfolder 7 years ago
.gitattributes a088123366 [DATALAD] Set default backend for all files to be MD5E 7 years ago
.gitignore 17daf58223 Add Shen atlas mean ROI timeseries aggregate as CSV 7 years ago
.gitmodules e7ac59ac5d Register input data 8 years ago
README.md f41be894e1 DOC: add README with DataLad access instructions 3 years ago

README.md

made-with-datalad

DataLad datasets and how to use them

This repository is a DataLad dataset. It provides fine-grained data access down to the level of individual files, and allows for tracking future updates. In order to use this repository for data retrieval, DataLad is required. It is a free and open source command line tool, available for all major operating systems, and builds up on Git and git-annex to allow sharing, synchronizing, and version controlling collections of large files. You can find information on how to install DataLad at handbook.datalad.org/en/latest/intro/installation.html.

Get the dataset

A DataLad dataset can be cloned by running

datalad clone <url>

Once a dataset is cloned, it is a light-weight directory on your local machine. At this point, it contains only small metadata and information on the identity of the files in the dataset, but not actual content of the (sometimes large) data files.

Retrieve dataset content

After cloning a dataset, you can retrieve file contents by running

datalad get <path/to/directory/or/file>`

This command will trigger a download of the files, directories, or subdatasets you have specified.

DataLad datasets can contain other datasets, so called subdatasets. If you clone the top-level dataset, subdatasets do not yet contain metadata and information on the identity of files, but appear to be empty directories. In order to retrieve file availability metadata in subdatasets, run

datalad get -n <path/to/subdataset>

Afterwards, you can browse the retrieved metadata to find out about subdataset contents, and retrieve individual files with datalad get. If you use datalad get <path/to/subdataset>, all contents of the subdataset will be downloaded at once.

Stay up-to-date

DataLad datasets can be updated. The command datalad update will fetch updates and store them on a different branch (by default remotes/origin/master). Running

datalad update --merge

will pull available updates and integrate them in one go.

Find out what has been done

DataLad datasets contain their history in the git log. By running git log (or a tool that displays Git history) in the dataset or on specific files, you can find out what has been done to the dataset or to individual files by whom, and when.

More information

More information on DataLad and how to use it can be found in the DataLad Handbook at handbook.datalad.org. The chapter "DataLad datasets" can help you to familiarize yourself with the concept of a dataset.