You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users have reported memory issues with the nonlinear T2*/S0 fitting setting (e.g., #2935 and #2827), so it might be worthwhile to give them control over the setting. I don't think it merits a command-line parameter, but is it perhaps something that could be controlled via the config file?
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
Alternatively, I could change the fittype from nonlinear to the less memory-intensive, but potentially less accurate, loglin option.
The text was updated successfully, but these errors were encountered:
I think it would be okay to add a parameter. --me-t2s-fit-method or something. I'd rather it be accessible by CLI than make people start caring about config files.
Closes#3029.
## Changes proposed in this pull request
- Add a new command line parameter, `--me-t2s-fit-method`, to control
how T2* and S0 will be estimated with tedana. The default, "curvefit",
is slower and more memory intensive, which has led to out-of-memory
errors for some users. The new option, "loglin", shouldn't result in the
same memory issues, but it also may produce less accurate estimates.
## Documentation that should be reviewed
I added a couple of sentences on the new parameter to the "T2*-driven
echo combination" section of `workflows.rst`.
What would you like to see added in fMRIPrep?
Users have reported memory issues with the nonlinear T2*/S0 fitting setting (e.g., #2935 and #2827), so it might be worthwhile to give them control over the setting. I don't think it merits a command-line parameter, but is it perhaps something that could be controlled via the config file?
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
Alternatively, I could change the fittype from nonlinear to the less memory-intensive, but potentially less accurate,
loglin
option.The text was updated successfully, but these errors were encountered: