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

Convert results dir structure in a bids-ish way! #27

Open
10 of 16 tasks
robbisg opened this issue Mar 21, 2019 · 1 comment
Open
10 of 16 tasks

Convert results dir structure in a bids-ish way! #27

robbisg opened this issue Mar 21, 2019 · 1 comment
Labels
bids BIDS-ish results thread Collections of issues
Milestone

Comments

@robbisg
Copy link
Owner

robbisg commented Mar 21, 2019

Problem

Use BIDS specs to create dirs and so on!

Every analysis must be included in derivatives folder
the structure must be
<ds-root>/derivatives/<pipeline-name>/<subj-dir>

in the subj dir the files must be named as:
<source_keyword>[_keyword-value]_<suffix>.<ext>
in addition a dataset-description.json must be included.

  1. The best solution is that <pipeline-name> is the on provided by AnalysisPipeline or by Analyzer
  2. dataset-description.json must include PipelineDescription.Name
  3. Maybe we can use keyword-value in file to specify different analyses.
    • A possibility is to use <pipeline-name>-<variant>
  4. Each subdir file should be described by a filename.json file with:

TODO

  • Every analysis must have a pipeline name
  • We must check if dataset is composed by a single subject or by several subjects
  • The derivatives/<subdir> must be [pipeline-<pipeline_name>]_analysis-<searchlight | decoding | connectivity>_[<analysis-specific-key>-<value]
  • Analyzer must implement _get_pipeline_info to build dir name
  • For searchlight analyses we must have derivatives/analsysis-searchlight_radius-0.3
  • For decoding analyses we must have derivatives/analysis-roi_decoding_area-brain
  • Obtain <source_keywords>
  • Analyzer must implement _get_fname_info in order to build filename appropriately.
  • Filenames for searchlight analyses must be <source_keywords>_target-<values>_task-<value>_date-<datetime>_num-<number>_<keyf>-<value>_<avg | cv>.nii.gz
  • Filenames for decoding analyses must be <source_keywords>_target-<values>_task-<task>_mask-<mask>_value-<roi_value>_date-<datetime>_num-<num>_<key>-<value>_data.mat
  • Each filename is paired with filename.json which is our configuration file! Remove hard-coded configuration.json from results.bids package #43
  • We can split information about dataset in dataset-description.json at the top of the pipeline dir Remove hard-coded configuration.json from results.bids package #43

Fixes

@robbisg robbisg added the new-feature New feature label Mar 21, 2019
@robbisg robbisg mentioned this issue Mar 22, 2019
15 tasks
@robbisg robbisg added the bids BIDS-ish results label Mar 29, 2019
@robbisg robbisg added this to the 0.0.1 milestone Apr 4, 2019
@robbisg robbisg pinned this issue Apr 10, 2019
@robbisg
Copy link
Owner Author

robbisg commented Apr 10, 2019

Questions

A: If I run the same analysis in two different times?
R: They will share the same dir but the files inside will have different ids
R: Or if you will name the pipeline differently they will have different directory

A: Who is the responsible for creating subject's subdirs??
R: I don't know (but maybe it should be AnalysisPipeline or Analyzer)

robbisg added a commit that referenced this issue Apr 12, 2019
robbisg added a commit that referenced this issue Apr 12, 2019
@robbisg robbisg unpinned this issue Feb 9, 2020
@robbisg robbisg added thread Collections of issues and removed new-feature New feature labels May 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bids BIDS-ish results thread Collections of issues
Projects
None yet
Development

No branches or pull requests

1 participant