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

✨ Uniform template management #24

Open
gkiar opened this issue May 27, 2022 · 0 comments
Open

✨ Uniform template management #24

gkiar opened this issue May 27, 2022 · 0 comments
Labels

Comments

@gkiar
Copy link
Contributor

gkiar commented May 27, 2022

Related problem

Currently, users can/have to specify templates for each stage of processing. In practice, it is unlikely that anyone would intend to use multiple at various stages of process for the vast majority of experiments — almost certainly not without it being a key avenue of exploration. With the present configuration, there is too much room for error that we are noticing even when building configs internally.

Proposed feature

Global template specification. Something nearly as simple as "MNI2006", e.g., that would internally map that template and its derivatives to the resource pool where appropriate. Individual derivatives (e.g., template tissue maps) could also be overridden manually, taking their place in the prepopulated list. Finally, nodes could still override much in the same way. However, they will all inherit the decision from the data-config specified template, by default.

Acceptance criteria

The above.

Alternatives

No response

Additional context

No response

@gkiar gkiar added user-reported enhancement New feature or request labels May 27, 2022
@shnizzedy shnizzedy added the Epic label Dec 11, 2023
@shnizzedy shnizzedy transferred this issue from FCP-INDI/C-PAC Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

2 participants