max-mapper / max-mapper/messages

Discussion about neuroimaging data packages

Open
#45 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
29
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Here are some notes from our discussion just now.

The proposal for making it possible to discover data package installations is https://github.com/nipy/nibabel/wiki/data_packages

I put up an issue for that to https://github.com/tryggvib/datapackage . This is the Python interface for using OKFN datapackage.json data packages. Issue : https://github.com/tryggvib/datapackage/issues/26

There are several implementations of 'get data for examples' that I know of:

and various others at less advanced stage of development.

I think you've already come across http://www.datalad.org/ - a neuroimaging data package tool in development, using git annex - @yarikoptic @hanke - Yarik, Michael - this to put you in touch with Max Ogden and the dat team to see if y'all have insights you can share.

I also mentioned the INCF : http://www.incf.org/ - here I'll ping @jbpoline @chrisfilo about this - JB, Chris - these are notes from a discussion with the dat team about data packages in neuroimaging - I mentioned the INCF and data sharing initiatives.

Also pinging @stefanv

I mentioned the Human Connectome Project : http://www.humanconnectomeproject.org - and the NIfTI data format : http://nifti.nimh.nih.gov/nifti-1

Thanks for the discussion and all the hard thinking y'all are doing.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the data_packages wiki proposal and the referenced datapackage issue 26 first. Then compare dipy/data/fetcher.py, nilearn/datasets.py, and nibabel/data.py; the issue does not define a concrete implementation target or acceptance criteria, so what counts as done remains unresolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, json, python
Domain
data-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.