Skip to content

Set compat='no_conflicts' explicitly#1802

Merged
JoerivanEngelen merged 1 commit intomasterfrom
issue_#1796_quell_future_warnings
Apr 9, 2026
Merged

Set compat='no_conflicts' explicitly#1802
JoerivanEngelen merged 1 commit intomasterfrom
issue_#1796_quell_future_warnings

Conversation

@JoerivanEngelen
Copy link
Copy Markdown
Contributor

@JoerivanEngelen JoerivanEngelen commented Apr 8, 2026

Fixes #1796

Description

Explicitly set compat='no_conflicts' to quell a noisy warning thrown repeatedly, as we call xr.merge a lot. This is the current default of xarray.

We can later reconsider if this should be "override" in some cases. This would increase performance, at the risk of providing unexpected results when incorrect data is provided. We'd have to profile this on a heavy case (e.g. our user acceptance test) to see if it increases performance.

Checklist

  • Links to correct issue
  • Update changelog, if changes affect users
  • PR title starts with Issue #nr, e.g. Issue #737
  • Unit tests were added
  • If feature added: Added/extended example
  • If feature added: Added feature to API documentation
  • If pixi.lock was changed: Ran pixi run generate-sbom and committed changes

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 8, 2026

@JoerivanEngelen
Copy link
Copy Markdown
Contributor Author

Tests pretty much succeeded, but they timed out because the modelsplitter unittests took most of the time. We really have to speed those up, but that is something for a separate PR.

@JoerivanEngelen JoerivanEngelen merged commit e40db42 into master Apr 9, 2026
7 of 8 checks passed
@JoerivanEngelen JoerivanEngelen deleted the issue_#1796_quell_future_warnings branch April 9, 2026 07:07
Manangka pushed a commit that referenced this pull request Apr 9, 2026
Fixes #1796

# Description
Explicitly set compat='no_conflicts' to quell a noisy warning thrown
repeatedly, as we call xr.merge a lot. This is the current default of
xarray.

We can later reconsider if this should be "override" in some cases. This
would increase performance, at the risk of providing unexpected results
when incorrect data is provided. We'd have to profile this on a heavy
case (e.g. our user acceptance test) to see if it increases performance.

# Checklist
<!---
Before requesting review, please go through this checklist:
-->

- [x] Links to correct issue
- [ ] Update changelog, if changes affect users
- [x] PR title starts with ``Issue #nr``, e.g. ``Issue #737``
- [ ] Unit tests were added
- [ ] **If feature added**: Added/extended example
- [ ] **If feature added**: Added feature to API documentation
- [ ] **If pixi.lock was changed**: Ran `pixi run generate-sbom` and
committed changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix xarray FutureWarning about changing compat defaults

1 participant