Closed fraimondo closed 3 months ago
Issue can be solved either at the marker collection level, by "merging" the new and old t_data
in line 140 here:
OR, at the PipelineStepMixin level, which I don't really recomend as it is not something of the step, but the application of subsequent steps.
Something like this works:
# Validate preprocessor
old_t_data = t_data.copy()
logger.info(f"Preprocess input type: {t_data}")
new_t_data = preprocessor.validate(old_t_data)
t_data = list(set(old_t_data) | set(new_t_data))
logger.info(f"Preprocess output type: {t_data}")
Something like this works:
# Validate preprocessor old_t_data = t_data.copy() logger.info(f"Preprocess input type: {t_data}") new_t_data = preprocessor.validate(old_t_data) t_data = list(set(old_t_data) | set(new_t_data)) logger.info(f"Preprocess output type: {t_data}")
Can you check if the validation passes?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 100.00%. Comparing base (
208cfdc
) to head (902bdc1
). Report is 1 commits behind head on main.
PR Preview Action v1.4.7 :---: Preview removed because the pull request was closed. 2024-05-14 11:21 UTC
Is there an existing issue for this?
Current Behavior
I'm running a YAML with two pre-processing steps: confound remover + Space Warper.
The process fails because the Space Warper requires the T1w + Warp which is not outputed by the fMRIPrepConfoundRemover.
The bug is basically that: it's not accounting that the data object has the T1w and Warp objects. It just gets the output of the fMRIPrepConfoundRemover.
Expected Behavior
I would expect that the two steps can be used.
Steps To Reproduce
junifer run --element sub-0001 NAME_OF_YAML
Environment
Relevant log output
Anything else?
No response