-
-
Notifications
You must be signed in to change notification settings - Fork 41
Open
Description
Related problem
The "selected functional volume" sbref generation nodeblock has a confusing flow for picking the input BOLD data.
- Its first choice for input BOLD is
desc-brain_bold, which may not exist in the resource pool, leading to missing resource errors. There is also the possibility thatdesc-preproc_boldis already skull-stripped. - There is conditional logic for the
reg_with_skulloption for coregistration, which chooses betweendesc-brain_boldfor skull-stripped and eitherdesc-motion_boldorboldfor whole-head. However, there is no guarantee these two may be whole-head.
Proposed feature
Ideally, in the final engine iteration, SkullStripped status will be handled in the meta-data within the resource pool.
In the meantime, the easiest solution would probably be:
- Change the input to
desc-preproc_boldand leave it to the user to enable BOLD masking if they want a skull-strippedsbref - Change the whole-head input to something like
desc-head_bold(which doesn't exist yet) similar to how we have for the T1w - Create
desc-head_boldas a bookmark resource - can also use justbold(raw BOLD ingressed) but this would exclude any other preprocessing done to it - Possibly: add the ability to mask the
sbrefas an option within the nodeblock, or as its own nodeblock
Acceptance criteria
- Users can include the
Selected Functional Volumeoption to create ansbrefwithout needingdesc-brain_boldin the resource pool. - Flexible options for either brain or whole-head
sbrefvia this nodeblock (and ideally allsbrefnodeblocks) that are easy and clear to use
Alternatives
No response
Additional context
No response
birajstha
Metadata
Metadata
Assignees
Type
Projects
Status
No status