Skip to content

Prepare release 2025.3.0#2237

Merged
visr merged 2 commits intomainfrom
release-2025.3.0
Apr 15, 2025
Merged

Prepare release 2025.3.0#2237
visr merged 2 commits intomainfrom
release-2025.3.0

Conversation

@visr
Copy link
Member

@visr visr commented Apr 14, 2025

[v2025.3.0] - 2025-04-14

The only breaking change in this release is to disallow connecting a single FlowBoundary to multiple Basins.
There are large improvements in the ability to visualize results on the map in QGIS.
We also welcome the Junction node to the family, which will help laying out networks in a recognizable manner.

Added

  • Add spatio-temporal results layers to QGIS. #2208
  • Add topological (straight line) link view toggle to QGIS. #2208
  • Added Junction node type. #2175
  • Write results and log bottlenecks also on an interrupt or crash. #2191 #2200
  • Log computation time and save it to solver_stats.arrow. #2209
  • Experimental support for writing the model network and results into files used by Delft-FEWS, model.to_fews. #2161
  • Document results/concentration.arrow. #2165

Changed

  • Allow max 1 outflow neighbour for FlowBoundary. #2192
  • Automatic differentiation is enabled by default again, autodiff = true, leading to better performance. #2137 #2183

@visr visr requested a review from evetion April 14, 2025 14:24
@visr
Copy link
Member Author

visr commented Apr 14, 2025

Perhaps we should still include #2238 if that indeed makes the results more robust for longer simulations.

@visr visr marked this pull request as draft April 14, 2025 14:59
@evetion
Copy link
Member

evetion commented Apr 14, 2025

We wanted a release because of the functionality currently in main. We can always make another release once we are happy with resetting the cumulative, we don't need to wait on it, nor should we rush it.

@visr
Copy link
Member Author

visr commented Apr 14, 2025

We can check tomorrow if it fixes known issues with models. It is a pretty important issue to resolve, so even if this fix is not optimal, we do need something soon. It is unlikely to be wrong, it just trades performance for accuracy on demand.

@visr visr force-pushed the release-2025.3.0 branch from da55647 to b5fba1f Compare April 15, 2025 12:07
@visr visr marked this pull request as ready for review April 15, 2025 12:07
@visr visr merged commit 1c29bc9 into main Apr 15, 2025
27 of 28 checks passed
@visr visr deleted the release-2025.3.0 branch April 15, 2025 14:41
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.

2 participants