Raise error if two-echo data are provided #3569
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
25.2.0 (October 01, 2025) New feature release in the 25.2.x series. This release is an *fMRIPrep Long-Term Support (LTS)* release. The planned support window is 4 years, until October 2029. This release is an incremental improvement over 25.1.x, but includes some fixes and improvements that do not fit within our `bug-fix policy <https://www.nipreps.org/devs/releases/#bug-fix-releases>`__. Importantly, the change in interpolation in 25.1.0 introduced artifacts for some datasets. This release changes the default interpolation mode to ``grid-constant``, which resolves those problems while not reintroducing the issue the previous release sought to fix. This release also (finally) introduces per-session processing. The ``--session-label`` flag selects the sessions to process, and the ``--subject-anatomical-reference`` flag indicates whether and how to combine across sessions. Existing filters passed via ``--bids-filter-file`` may need to be updated or removed in favor of using these flags to achieve the desired behavior. We would like to thank the AMP-SCZ and ENIGMA consortia for testing out and providing feedback on this release. * FIX: Clean up output report language (nipreps#3529) * FIX: Default to grid-constant interpolation mode (nipreps#3516) * FIX: Adapt to transposed ndcoords in nitransforms (nipreps#3517) * FIX: Write out Freesurfer-derived outputs (nipreps#3512) * FIX: Add kwargs to _warnings.py (nipreps#3483) * ENH: Resample BOLD data to any surface template space using the Connectome Workbench (nipreps#3461) * ENH: Add boldref / sbref to source metadata (nipreps#3532) * ENH: Add dedicated session filtering, alternative anatomical template options (nipreps#3495) * ENH: Write out goodvoxels mask (nipreps#3513) * ENH: Add registration metadata to boldref-to-anat transforms (nipreps#3500) * ENH: Write out cortex mask GIFTIs (nipreps#3491) * ENH: Update transforms.py according to new transform chain of nitransforms (nipreps#3494) * RF/DOC: Improve and document command-line parser defaults (nipreps#3487) * DOC: Explain better SDC and B0FieldSource requirement (nipreps#2768) * DOC: Document `freesurfer` parameter in BOLD confound workflow init (nipreps#3504) * DOC: Add myself to contributor list (nipreps#3506) * DOC: Fix non-standard Input/Output docstring section management (nipreps#3505) * MNT: Split Dockerfile into base and pixi layers (nipreps#3521) * MNT: Replace conda with pixi and lock (nipreps#3503) * MNT: Update license metadata using SPDX expression (nipreps#3486) * MNT: no need to re-run `ruff check` after `ruff format` (nipreps#3480) * MNT: Update pre-commit ruff legacy alias (nipreps#3479)
updates: - [github.com/astral-sh/ruff-pre-commit: v0.13.1 → v0.13.2](astral-sh/ruff-pre-commit@v0.13.1...v0.13.2)
<!--pre-commit.ci start--> updates: - [github.com/astral-sh/ruff-pre-commit: v0.13.1 → v0.13.2](astral-sh/ruff-pre-commit@v0.13.1...v0.13.2) <!--pre-commit.ci end-->
25.2.2 (October 06, 2025) Bug-fix release in the 25.2.x series. This fix addresses an issue in the Docker containers. FreeSurfer's ``recon-all`` depends on a full Perl installation being available in the environment. * FIX: Ensure perl is installed in container (nipreps#3547)
updates: - [github.com/astral-sh/ruff-pre-commit: v0.13.2 → v0.13.3](astral-sh/ruff-pre-commit@v0.13.2...v0.13.3)
<!--pre-commit.ci start--> updates: - [github.com/astral-sh/ruff-pre-commit: v0.13.2 → v0.13.3](astral-sh/ruff-pre-commit@v0.13.2...v0.13.3) <!--pre-commit.ci end-->
Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 6 to 7. - [Release notes](https://github.com/astral-sh/setup-uv/releases) - [Commits](astral-sh/setup-uv@v6...v7) --- updated-dependencies: - dependency-name: astral-sh/setup-uv dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 6 to 7. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/setup-uv/releases">astral-sh/setup-uv's releases</a>.</em></p> <blockquote> <h2>v7.0.0 🌈 node24 and a lot of bugfixes</h2> <h2>Changes</h2> <p>This release comes with a load of bug fixes and a speed up. Because of switching from node20 to node24 it is also a breaking change. If you are running on GitHub hosted runners this will just work, if you are using self-hosted runners make sure, that your runners are up to date. If you followed the normal installation instructions your self-hosted runner will keep itself updated.</p> <p>This release also removes the deprecated input <code>server-url</code> which was used to download uv releases from a different server. The <a href="https://github.com/astral-sh/setup-uv?tab=readme-ov-file#manifest-file">manifest-file</a> input supersedes that functionality by adding a flexible way to define available versions and where they should be downloaded from.</p> <h3>Fixes</h3> <ul> <li>The action now respects when the environment variable <code>UV_CACHE_DIR</code> is already set and does not overwrite it. It now also finds <a href="https://docs.astral.sh/uv/reference/settings/#cache-dir">cache-dir</a> settings in config files if you set them.</li> <li>Some users encountered problems that <a href="https://github.com/astral-sh/setup-uv?tab=readme-ov-file#disable-cache-pruning">cache pruning</a> took forever because they had some <code>uv</code> processes running in the background. Starting with uv version <code>0.8.24</code> this action uses <code>uv cache prune --ci --force</code> to ignore the running processes</li> <li>If you just want to install uv but not have it available in path, this action now respects <code>UV_NO_MODIFY_PATH</code></li> <li>Some other actions also set the env var <code>UV_CACHE_DIR</code>. This action can now deal with that but as this could lead to unwanted behavior in some edgecases a warning is now displayed.</li> </ul> <h3>Improvements</h3> <p>If you are using minimum version specifiers for the version of uv to install for example</p> <pre lang="toml"><code>[tool.uv] required-version = ">=0.8.17" </code></pre> <p>This action now detects that and directly uses the latest version. Previously it would download all available releases from the uv repo to determine the highest matching candidate for the version specifier, which took much more time.</p> <p>If you are using other specifiers like <code>0.8.x</code> this action still needs to download all available releases because the specifier defines an upper bound (not 0.9.0 or later) and "latest" would possibly not satisfy that.</p> <h2>🚨 Breaking changes</h2> <ul> <li>Use node24 instead of node20 <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/608">#608</a>)</li> <li>Remove deprecated input server-url <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/607">#607</a>)</li> </ul> <h2>🐛 Bug fixes</h2> <ul> <li>Respect UV_CACHE_DIR and cache-dir <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/612">#612</a>)</li> <li>Use --force when pruning cache <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/611">#611</a>)</li> <li>Respect UV_NO_MODIFY_PATH <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/603">#603</a>)</li> <li>Warn when <code>UV_CACHE_DIR</code> has changed <a href="https://github.com/jamesbraza"><code>@jamesbraza</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/601">#601</a>)</li> </ul> <h2>🚀 Enhancements</h2> <ul> <li>Shortcut to latest version for minimum version specifier <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/598">#598</a>)</li> </ul> <h2>🧰 Maintenance</h2> <ul> <li>Bump dependencies <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/613">#613</a>)</li> <li>Fix test-uv-no-modify-path <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/604">#604</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/astral-sh/setup-uv/commit/3259c6206f993105e3a61b142c2d97bf4b9ef83d"><code>3259c62</code></a> Bump deps (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/633">#633</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/bf8e8ed895b7f686f85839659243f31a7df4a977"><code>bf8e8ed</code></a> Split up documentation (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/632">#632</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/9c6b5e9fb575cac8e82bb437dd7fc25a094bd85d"><code>9c6b5e9</code></a> Add resolution-strategy input to support oldest compatible version selection ...</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/a5129e99f44f5d2ba22cdc54770745bd6f0d9c33"><code>a5129e9</code></a> Add copilot-instructions.md (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/630">#630</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/d18bcc753ac29c1ed721aa4a812a90eb937852d6"><code>d18bcc7</code></a> Add value of UV_PYTHON_INSTALL_DIR to path (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/628">#628</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/bd1f875aba1ebb6d38211b773b094ad1dcca58df"><code>bd1f875</code></a> Set output venv when activate-environment is used (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/627">#627</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/1a91c3851df47749b241e3c5c696350957c93ff0"><code>1a91c38</code></a> chore: update known checksums for 0.9.2 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/626">#626</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/c79f606987cb4a0f3d1a95a3e44bcebfb0a9b303"><code>c79f606</code></a> chore: update known checksums for 0.9.1 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/625">#625</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/e0249f159931b41f44fc8208c9b4cff085288cc9"><code>e0249f1</code></a> Fall back to PR for updating known versions (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/623">#623</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/6d2eb15b4979924f7be71aa06908c6211f80ac88"><code>6d2eb15</code></a> Cache python installs (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/621">#621</a>)</li> <li>Additional commits viewable in <a href="https://github.com/astral-sh/setup-uv/compare/v6...v7">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
25.2.3 (October 17, 2025) Bug-fix release in the 25.2.x series. This fix addresses an incompatibility between the PyBIDS and universal-pathlib dependencies. The only change is reverting universal-pathlib to a compatible version in the lock file, which will also fix the container.
Bumps [prefix-dev/setup-pixi](https://github.com/prefix-dev/setup-pixi) from 0.9.1 to 0.9.2. - [Release notes](https://github.com/prefix-dev/setup-pixi/releases) - [Commits](prefix-dev/setup-pixi@v0.9.1...v0.9.2) --- updated-dependencies: - dependency-name: prefix-dev/setup-pixi dependency-version: 0.9.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
=== Do not change lines below ===
{
"chain": [],
"cmd": "pixi lock",
"exit": 0,
"extra_inputs": [],
"inputs": [
"pyproject.toml",
"pixi.lock"
],
"outputs": [
"pixi.lock"
],
"pwd": "."
}
^^^ Do not change lines above ^^^
…3557) Bumps [prefix-dev/setup-pixi](https://github.com/prefix-dev/setup-pixi) from 0.9.1 to 0.9.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/prefix-dev/setup-pixi/releases">prefix-dev/setup-pixi's releases</a>.</em></p> <blockquote> <h2>v0.9.2</h2> <!-- raw HTML omitted --> <h2>What's Changed</h2> <h3>✨ New features</h3> <ul> <li>feat: Allow caching global environment(s) by <a href="https://github.com/olivier-lacroix"><code>@olivier-lacroix</code></a> in <a href="https://redirect.github.com/prefix-dev/setup-pixi/pull/226">prefix-dev/setup-pixi#226</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/prefix-dev/setup-pixi/compare/v0.9.1...v0.9.2">https://github.com/prefix-dev/setup-pixi/compare/v0.9.1...v0.9.2</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/prefix-dev/setup-pixi/commit/28eb668aafebd9dede9d97c4ba1cd9989a4d0004"><code>28eb668</code></a> feat: Allow caching global environment(s) (<a href="https://redirect.github.com/prefix-dev/setup-pixi/issues/226">#226</a>)</li> <li>See full diff in <a href="https://github.com/prefix-dev/setup-pixi/compare/v0.9.1...v0.9.2">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
Co-authored-by: Chris Markiewicz <[email protected]>
) Closes nipreps#3507. As of 25.1.0, tedana has an `--exclude` parameter in its t2smap CLI, which allows users to ignore certain volumes when estimating T2* and S0. This PR bumps the tedana version and leverages that parameter to ignore dummy scans. If it proves useful, we could also ignore high-motion volumes in the future. ## Changes proposed in this pull request - Increase minimum tedana version from 25.0.0 to 25.1.0. - Use estimated number of dummy scans to set `exclude` parameter in t2smap call, so that those volumes do not contribute to the estimation of T2*, which is in turn used to optimally combine the data across echoes. I doubt the dummy scans actually have much effect on T2* estimation, but it still stands to reason that they are not _helping_. ## Documentation that should be reviewed <!-- Please summarize here the main changes to the documentation that the reviewers should be aware of. --> <!-- Welcome, new contributors! We ask you to read through the Contributing Guide: https://github.com/nipreps/fmriprep/blob/master/CONTRIBUTING.md These are guidelines intended to make communication easier by describing a consistent process, but don't worry if you don't get it everything exactly "right" on the first try. To boil it down, here are some highlights: 1) Consider starting a conversation in the issues list before submitting a pull request. The discussion might save you a lot of time coding. 2) Please use descriptive prefixes in your pull request title, such as "ENH:" for an enhancement or "FIX:" for a bug fix. (See the Contributing guide for the full set.) And consider adding a "WIP" tag for works-in-progress. 3) Any code you submit will be licensed under the same terms (Apache License 2.0) as the rest of fMRIPrep. 4) We invite every contributor to add themselves to the `.zenodo.json` file (https://github.com/nipreps/fmriprep/blob/master/.zenodo.json), which will result in your being listed as an author at the next release. Please add yourself as the next-to-last entry, just above Russ. A pull request is a conversation. We may ask you to make some changes before accepting your PR, and likewise, you should feel free to ask us any questions you have. -->
In nipreps#3556, @tsalo discovered he couldn't (effectively) run `pixi lock` from a mac, which I believe is due to prefix-dev/pixi#3081. This PR runs `pixi lock` on PRs and commits to the incoming branch if they are out-of-date. nipreps#3559 demonstrates (see, e.g., 35151f7).
Bumps [prefix-dev/setup-pixi](https://github.com/prefix-dev/setup-pixi) from 0.9.2 to 0.9.3. - [Release notes](https://github.com/prefix-dev/setup-pixi/releases) - [Commits](prefix-dev/setup-pixi@v0.9.2...v0.9.3) --- updated-dependencies: - dependency-name: prefix-dev/setup-pixi dependency-version: 0.9.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…3564) Bumps [prefix-dev/setup-pixi](https://github.com/prefix-dev/setup-pixi) from 0.9.2 to 0.9.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/prefix-dev/setup-pixi/releases">prefix-dev/setup-pixi's releases</a>.</em></p> <blockquote> <h2>v0.9.3</h2> <!-- raw HTML omitted --> <h2>What's Changed</h2> <h3>✨ New features</h3> <ul> <li>feat: Switch order of pixi info and pixi install by <a href="https://github.com/pavelzw"><code>@pavelzw</code></a> in <a href="https://redirect.github.com/prefix-dev/setup-pixi/pull/234">prefix-dev/setup-pixi#234</a></li> </ul> <h3>📝 Documentation</h3> <ul> <li>Update documentation links to new pixi URLs by <a href="https://github.com/ruben-arts"><code>@ruben-arts</code></a> in <a href="https://redirect.github.com/prefix-dev/setup-pixi/pull/230">prefix-dev/setup-pixi#230</a></li> </ul> <h3>⬆️ Dependency updates</h3> <ul> <li>chore(deps): bump the gh-actions group with 3 updates by <a href="https://github.com/dependabot"><code>@dependabot</code></a>[bot] in <a href="https://redirect.github.com/prefix-dev/setup-pixi/pull/228">prefix-dev/setup-pixi#228</a></li> <li>chore(deps): bump the gh-actions group with 4 updates by <a href="https://github.com/dependabot"><code>@dependabot</code></a>[bot] in <a href="https://redirect.github.com/prefix-dev/setup-pixi/pull/232">prefix-dev/setup-pixi#232</a></li> <li>chore(deps): bump the nodejs group across 1 directory with 9 updates by <a href="https://github.com/dependabot"><code>@dependabot</code></a>[bot] in <a href="https://redirect.github.com/prefix-dev/setup-pixi/pull/233">prefix-dev/setup-pixi#233</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/prefix-dev/setup-pixi/compare/v0.9.2...v0.9.3">https://github.com/prefix-dev/setup-pixi/compare/v0.9.2...v0.9.3</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/prefix-dev/setup-pixi/commit/82d477f15f3a381dbcc8adc1206ce643fe110fb7"><code>82d477f</code></a> feat: Switch order of pixi info and pixi install (<a href="https://redirect.github.com/prefix-dev/setup-pixi/issues/234">#234</a>)</li> <li><a href="https://github.com/prefix-dev/setup-pixi/commit/a97638076335f9354933c7f56606c58b98165b63"><code>a976380</code></a> chore(deps): bump the nodejs group across 1 directory with 9 updates (<a href="https://redirect.github.com/prefix-dev/setup-pixi/issues/233">#233</a>)</li> <li><a href="https://github.com/prefix-dev/setup-pixi/commit/de110d6265c5ff3d76eaf3cfaba9b7e3029130b8"><code>de110d6</code></a> chore(deps): bump the gh-actions group with 4 updates (<a href="https://redirect.github.com/prefix-dev/setup-pixi/issues/232">#232</a>)</li> <li><a href="https://github.com/prefix-dev/setup-pixi/commit/59d669bca01299140a23e5e8a9f713ad36f1f069"><code>59d669b</code></a> Update documentation links to new pixi URLs (<a href="https://redirect.github.com/prefix-dev/setup-pixi/issues/230">#230</a>)</li> <li><a href="https://github.com/prefix-dev/setup-pixi/commit/046c0f75f27d4aa92d448dabd2e0a2f6ba152720"><code>046c0f7</code></a> chore(deps): bump the gh-actions group with 3 updates (<a href="https://redirect.github.com/prefix-dev/setup-pixi/issues/228">#228</a>)</li> <li><a href="https://github.com/prefix-dev/setup-pixi/commit/34ef3cc29847a6ef30b6da1585017362caf9163e"><code>34ef3cc</code></a> docs: Reference latest Pixi version in README (<a href="https://redirect.github.com/prefix-dev/setup-pixi/issues/227">#227</a>)</li> <li>See full diff in <a href="https://github.com/prefix-dev/setup-pixi/compare/v0.9.2...v0.9.3">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
Member
|
Can you rebase this off of |
…riprep into raise-error-on-two-echo
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## maint/25.2.x #3569 +/- ##
================================================
- Coverage 72.92% 72.88% -0.04%
================================================
Files 60 60
Lines 4817 4821 +4
Branches 625 626 +1
================================================
+ Hits 3513 3514 +1
- Misses 1162 1164 +2
- Partials 142 143 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
tsalo
added a commit
to tsalo/fmriprep
that referenced
this pull request
Nov 24, 2025
Collaborator
Author
|
Since I messed up the rebase, I'm closing in favor of #3570. |
effigies
pushed a commit
to tsalo/fmriprep
that referenced
this pull request
Nov 25, 2025
effigies
pushed a commit
to tsalo/fmriprep
that referenced
this pull request
Nov 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relates to #3364. This acts as a short-term patch until we figure out how best to process two-echo fMRI data.
Changes proposed in this pull request
--echo-idxis not, raise a RuntimeError.