BIDS Execution spec / BIDS Apps 2.0

[effigies]

BIDS Execution spec / BIDS Apps 2.0

Project Description

I have the start of a draft here: https://docs.google.com/document/d/104HLZedFtx0TaXEUwd7eyWvJUlc0CcSUtCzwjNgmGxE/edit#heading=h.4k1noo90gelw

It's based on some notes here: https://docs.google.com/document/d/1NQe5qP0VdfqPI5nl2cIQKzii70ndpPJEzemzK4qn6uY/edit#heading=h.usmuhelpi8fq

Skills required to participate

Reading and writing.

[effigies]

Discussed current spec with @adelavega, @PeerHerholz, @Shotgunosine, with some useful interjections from @tyarkoni. The main results of this discussion:

• We need to have a more defined semantics for the --<entity>-label filters.
• We should output the original command line, and this would probably best happen in dataset_description.json:PipelineDescription.

[PeerHerholz]

There was also a comment from @emdupre on how output folders should be named. The proposal was to include the name of the BIDS-App and its version: <bidsapp>-<version>, e.g., fmriprep-0.1.

[emdupre]

Thanks for noting this, @PeerHerholz ! To reference specific lines, the idea was that here instead of requiring that the folder name contains PipelineDescription.Name as a substring, the string should match exactly.

For example, here, fmripreprocess-v1/ would become fmriprep-v1/.