You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #3252, we started creating DatasetLinks for derivative datasets passed through the --derivatives parameter. However, because there's no easy way to infer what each derivative dataset actually is, we're labeling them as deriv-<index> in the DatasetLinks. I think the DatasetLinks and BIDS URIs throughout the derivatives would be more interpretable if users could label their input derivative datsets.
Do you have any interest in helping implement the feature?
Closes#3260.
## Changes proposed in this pull request
- Copy over `ToDict` action from fmriprep-docker over to the main CLI
parser.
- Modify the Config to handle named derivative paths.
- E.g., `--derivatives anat=/path/to/smriprep` --> `DatasetLinks =
{'anat': '/path/to/smriprep'}`
- Infer derivative name from the folder name of the derivative path if
it isn't labeled.
- E.g., `--derivatives /path/to/smriprep` --> `DatasetLinks =
{'smriprep': '/path/to/smriprep'}`
---------
Co-authored-by: Chris Markiewicz <effigies@gmail.com>
What would you like to see added in fMRIPrep?
In #3252, we started creating DatasetLinks for derivative datasets passed through the
--derivatives
parameter. However, because there's no easy way to infer what each derivative dataset actually is, we're labeling them asderiv-<index>
in the DatasetLinks. I think the DatasetLinks and BIDS URIs throughout the derivatives would be more interpretable if users could label their input derivative datsets.Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
I was thinking something like:
The text was updated successfully, but these errors were encountered: