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

[ENH] Option to mark specific parts of a template to distinct unique configurations #60

Open
1 task done
JRandy77 opened this issue Jul 6, 2023 · 1 comment
Open
1 task done
Labels
enhancement New feature or request

Comments

@JRandy77
Copy link
Collaborator

JRandy77 commented Jul 6, 2023

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

@JRandy77 JRandy77 added the enhancement New feature or request label Jul 6, 2023
@JRandy77
Copy link
Collaborator Author

JRandy77 commented Jul 6, 2023

Another weird thing is if you leave the more general template in the file_tree its possible for the thing you are trying to be specific toward to be misclassified. If you order the more general one to be beneath the specific version it seems to work fine, but thats definitely not user friendly. This is an issue that I think is resolvable anyway.

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

No branches or pull requests

1 participant