Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HCP multi-pipeline to BIDS #444

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

elodiegermani
Copy link

With @cmaumet, we would like to organize a dataset into BIDS but we need more information due to the particular properties of the dataset.
It is a multi-pipeline dataset with statistic and contrast maps at the subject and group-level for 24 different pipelines. These pipelines are named with the following convention: software-FWHM-number of motion regressors-presence of hrf derivatives.

Here, we propose a first attempt to organize these data as closely as possible to BIDS specifications. The goal is to make it suitable for hosting in the platform public-nEUro.

More information on the dataset are available in the data paper preprint: https://inserm.hal.science/inserm-04356768.

Thanks for your help!

@Remi-Gau Remi-Gau marked this pull request as draft June 6, 2024 10:52
@Remi-Gau
Copy link
Contributor

Remi-Gau commented Jun 6, 2024

Making some comments for general guidance and trying to alignb with WIP BEP 41

https://docs.google.com/document/d/1KHzp-yk8KXvkUIhtN71WU0m4P4kKT9C1yvI-i9_kNeY/edit

  • mention the space in which the images are
  • mention the name of the contrast
  • use the stat map suffix and use the stat entity to distinguish between t-maps and con-maps

con maps

sub-100206_task-righthand_desc-con.nii.gz

becomes

sub-100206_task-righthand[_space-<label>]_contrast-<label>_stat-effect_statmap.nii.gz

t maps

sub-100206_task-righthand_desc-tstat.nii.gz

becomes

sub-100206_task-righthand[_space-<label>]_contrast-<label>_stat-t_statmap.nii.gz

group level as derivatives ?

Not sure but it having a group level as derivative nested within the dataset containing the first level may help make privenance a bit clearer (Note this is not part of the BEP)

hcp_multi_pipeline
├── derivatives
│   ├── fsl-5-0-0
│   └── spm-5-0-0
│       ├── dataset_description.json
│       ├── first-level-analysis
│       │   ├── sub-100206
│       │   │   ├── sub-100206_task-righthand_desc-con.nii.gz
│       │   │   └── sub-100206_task-righthand_desc-tstat.nii.gz
│       │   └── sub-100307
│       │       ├── sub-100307_task-righthand_desc-con.nii.gz
│       │       └── sub-100307_task-righthand_desc-tstat.nii.gz
│       └── derivatives
│           ├── dataset_description.json
│           └── group
│               ├── task-righthand_desc-con.nii.gz
│               └── task-righthand_desc-tstat.nii.gz
└── README.md

@effigies
Copy link
Contributor

effigies commented Jun 6, 2024

The way I organize things with fitlins is as a collection of sibling derivatives:

node-L1/
  dataset_description.json
  sub-01/
    ...
node-L2/
  dataset_description.json
  <no subjects>

node- is nothing official, it's just a naming convention that matches the stats models spec.

@Remi-Gau
Copy link
Contributor

Remi-Gau commented Jun 6, 2024

The way I organize things with fitlins is as a collection of sibling derivatives:

node-L1/
  dataset_description.json
  sub-01/
    ...
node-L2/
  dataset_description.json
  <no subjects>

node- is nothing official, it's just a naming convention that matches the stats models spec.

yeah that makes sense as well: I don't think things need to be nested but having separate BIDS datasets makes sense

@elodiegermani
Copy link
Author

Hi @Remi-Gau and @effigies !
Thanks a lot for your help.
I made a new commit with modifications according to your comments.

I am just not sure about the dataset_description.json included in the different nodes. Is there anything to specify in these files to add the information about the level of the statistics?
And I am also not sure about what is the "XYZ-specific metadata" mentioned in the BEP41 sent by @Remi-Gau ?

@effigies
Copy link
Contributor

"XYZ-specific metadata" is probably boilerplate from the BEP template that didn't get updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants