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

Integrate SynthStrip? #299

Open
oesteban opened this issue Aug 26, 2022 · 8 comments
Open

Integrate SynthStrip? #299

oesteban opened this issue Aug 26, 2022 · 8 comments
Labels
enhancement New feature or request

Comments

@oesteban
Copy link
Member

Considering the incredible success with MRIQC (@ahoopes SynthStrip is amazing), I think we could consider the integration of SynthStrip here.

@oesteban oesteban added the enhancement New feature or request label Aug 26, 2022
@mgxd mgxd added this to Development Aug 29, 2022
@WilliamFCB
Copy link

Hi
Out of curiosity.... has synthstrip already been implemented? Skimming the release notes, this seems not to be the case.
Are there any plans to do this in the near future?
Cheers
William

@oesteban
Copy link
Member Author

oesteban commented Oct 5, 2023

We haven't yet - we are piloting it with MRIQC and on the one hand it is super reliable. But on the other, it is making really hard for people to run MRIQC and not fall into memory errors.

@WilliamFCB
Copy link

I understand. Would it be feasible to add it as an extra option so that people can choose? I have been successfully using synthstrip in different pipelines to optimize masks, for example in fixel-based analyses.

@oesteban
Copy link
Member Author

oesteban commented Oct 5, 2023 via email

@WilliamFCB
Copy link

Why only for mp2rage? I assume implementation wise at least the -b flag will be made parsable?

@margokersey
Copy link

Hi there, I was curious if there are any updates on incorporating SynthStrip as an option in smriprep? I couldn't find information in the documentation. Thank you!

@oesteban
Copy link
Member Author

Why only for mp2rage?

That would be the "official" use-case. When enabled, a warning stating that using SynthStrip on standard MPRAGE/SPGR images can be done at your own risk because it deviates from the 'official' smriprep workflow.

Eventually, I can see how SynthStrip will totally replace the atlas-based extraction in the long term.

@oesteban
Copy link
Member Author

Hi there, I was curious if there are any updates on incorporating SynthStrip as an option in smriprep? I couldn't find information in the documentation. Thank you!

No progress for the moment, unfortunately. We'd be glad to receive the contribution from someone new ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

3 participants