-
Notifications
You must be signed in to change notification settings - Fork 308
[MAINT] Pin tedana version #2117
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
Conversation
…ersion # Conflicts: # setup.cfg
…ersion # Conflicts: # setup.cfg
…ersion # Conflicts: # setup.cfg
…ersion # Conflicts: # setup.cfg
|
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
|
The t2smap_workflow bug is still there, until 0.0.9 is released.
…ersion # Conflicts: # setup.cfg
mgxd
left a comment
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.
👍, just a few comments.
setup.cfg
Outdated
| sdcflows @ git+https://github.com/nipreps/sdcflows.git@master | ||
| smriprep @ git+https://github.com/poldracklab/smriprep.git@master | ||
| tedana >= 0.0.5 | ||
| tedana ~= 0.0.9a1 |
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.
will this pick up 0.0.9? When pinning RCs in the past, we've had to do this manually, i.e.
>= 0.0.9a1, < 0.0.10
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.
It was able to grab 0.0.9a1 in the tests, but I wasn't thinking about 0.0.9. Should I switch to >= 0.0.9a1, < 0.0.10 so it grabs 0.0.9 once it's released, or is it okay to pin to 0.0.9a1?
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 would lean towards allowing grabbing a more stable version, but i'm not familiar with tedana's release cycle so whatever you think would be best
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.
That should be fine. I'm happy to change it.
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 can always increase/drop the maximum version, thanks!
Co-authored-by: Mathias Goncalves <[email protected]>
This PR pins the tedana version to 0.0.9a1, given several breaking changes since 0.0.8.
Changes proposed in this pull request:
Documentation that should be reviewed
init_bold_t2s_wfworkflow__desc__has been changed to reflect the improved T2*/S0 estimation method.T2* Driven CoregistrationtoT2*-driven echo combination. This fixes an oversight on my part from ENH: Remove t2s-coreg #2109.