-
Notifications
You must be signed in to change notification settings - Fork 296
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: Remove t2s-coreg #2109
ENH: Remove t2s-coreg #2109
Conversation
Thank your for raising your pull request. Some of the fMRIPRep maintainers will review your changes as soon as time permits. PR ReviewPlease check off boxes as applicable, and elaborate in comments below. Your review is not limited to these topics, as described in the reviewer guide
Please check what applies in the following aspects of the PR: Code documentation
Documentation site
Tests
Data
Dependencies: smriprep
Dependencies: niworkflows
Dependencies: sdcflows
Dependencies: Nipype
Dependencies: other
Reports generated within CI tests
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haven't checked locally, but this looks pretty awesome. I'll try to review and get this merged tomorrow.
Thanks much for this!
fmriprep/workflows/bold/t2s.py
Outdated
('outputnode.skull_stripped_file', 'bold_ref_brain')]), | ||
(t2smap_node, outputnode, [ | ||
('optimal_comb', 'bold'), | ||
('t2star_map', 'bold_ref_brain')]), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This workflow is now inputnode -> t2smap_node -> outputnode
, so the workflow itself can be replaced in the calling function by t2smap_node
. Unless it's useful to keep this space open to expand the workflow in the future?
Also, bold_ref_brain
does not seem to be being used anywhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if implementing it would require that bold_t2s_wf
remain a workflow, but in #1010 (comment) I'm proposing a way to incorporate tedana's component classification into fMRIPrep. It might be worth it to keep the workflow around until #1010 is resolved at least.
I can remove bold_ref_brain
now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure. Let's keep this change minimal and we can reconsider architecture later. I realized there's also the workflow description that would need to be moved out of this separate module.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should also remove the config option:
https://github.com/poldracklab/fmriprep/blob/3cd56d5eaef6bd59c118116878841dcacfffc43b/fmriprep/config.py#L455-L456
@mgxd thank you for catching that. It should be good now. |
LGTM, thanks! |
LGTM. Merge at will, @oesteban. |
Sorry for the naive question, when would I expect to see this change in a release? |
20.1.0, which is coming Real Soon Now. Seriously, we're trying to wrap up as quickly as possible, but everything's taking longer than we intended. Out of curiosity, is this a feature that you needed? |
If I've followed all of the references right, I think this PR started with an issue I had with masking multi-echo rest sequences: I had forgotten about it and ran fmriprepv20.0.5 without selecting a single echo (which was my work around) and found that a lot of the rest sequences have brain excluded from the brain mask around the base of the brain, which was the original issue:
|
@tsalo, I know I'm lat to the party here, but did you by any chance check to see if the masking here works on this dataset: https://openneuro.org/datasets/ds002156/versions/1.0.0 |
@Shotgunosine I haven't checked the masking at all, sorry. I built this PR off of @emdupre's initial work in #1800, which I believe dealt with the masking more than what I added, which was just removing the t2s_coreg option from the workflow (and thus didn't touch non-t2s-coreg masking). However, there was a glaring masking bug in the t2smap workflow in tedana <= 0.0.8 (see ME-ICA/tedana#544). I think that that bug could be responsible for at least some of the problems, and we should probably check how the masking works once 0.0.9 is released and I've pinned that version in fMRIPrep (see #2117). |
Ok, sounds good. Looking at #1800 it seems like she verified that those changes worked with my data, so I'm optimistic that 20.1 will help when it gets here. |
In 04cf152 I moved all of the Regardless, yes, I ran on yours locally and it looked right @Shotgunosine ! But fMRIPrep has had a lot of updates since then, so I'd be curious to re-run with a patched docker image for the current master. |
To test with
|
Resolves #1786. This builds off of #1800, but removes the T2*-based coregistration option completely, based on the most recent comments in #1786 and discussion with @emdupre.
Changes proposed in this pull request
--t2s-coreg
option from CLIt2s_coreg
-related steps from workflows.--t2s-coreg
option from docs/workflows.rst.Documentation that should be reviewed
docs/workflows.rst
, I remove a sentence about--t2s-coreg
.