-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
enhancementNew feature or requestNew feature or request
Description
Is there an existing issue for this?
- I have searched the existing issues
New feature
Currently anything that matches the form of the below template will all be handled with the same identity.
sub-{participant}[_ses-{session}]_task-{task}[_acq-{acq}][_ce-{ce}][_dir-{dir}][_rec-{rec}][_run-{run_index}][_echo-{echo}]_bold.nii.gz (task_image)
If there was an option to use a special character to mark a specific placeholder to store unique configurations that could be very useful. ie.
sub-{participant}[_ses-{session}]_task-{*task}[_acq-{acq}][_ce-{ce}][_dir-{dir}][_rec-{rec}][_run-{run_index}][_echo-{echo}]_bold.nii.gz (task_image)
The '*' marked at task would then allow the program to know that different tasks should be considered as a different item.
Currently a user would have to manually write out different templates in the tree file. i.e.
sub-{participant}[_ses-{session}]_task-{task}[_acq-{acq}][_ce-{ce}][_dir-{dir}][_rec-{rec}][_run-{run_index}][_echo-{echo}]_space-MNI[_desc-{desc}]_bold.nii.gz (task_image_MNI)
sub-{participant}[_ses-{session}]_task-{task}[_acq-{acq}][_ce-{ce}][_dir-{dir}][_rec-{rec}][_run-{run_index}][_echo-{echo}]_space-T1w[_desc-{desc}]_bold.nii.gz (task_image_T1w)
to distinct between MNI and T1w files.
This may not be super important at this time because its pretty easy to just copy and paste to make these unique configurations. Where this fails is if there are many different variations for one type of value.
Unclear documentation
No response
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request