-
Notifications
You must be signed in to change notification settings - Fork 13
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
[BUG]: Validation failure of multiple pre-processing steps with different input data types requirement #339
Conversation
Issue can be solved either at the marker collection level, by "merging" the new and old junifer/junifer/markers/collection.py Lines 133 to 142 in e0cb0f2
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:
|
Can you check if the validation passes? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #339 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 1 1
=========================================
Hits 1 1
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
48592bf
to
eb68ce9
Compare
4d92cf0
to
902bdc1
Compare
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