Back to What's New

May 9, 20262 min read

Weekly Update May 9, 2026

This week WatDis hardens QA for impossible geometry and leaves a much more reproducible benchmark trail to prioritize real solver work without overstating shipped gains.

EN
qadiagnosticsbenchmarkingsolverwatdis
Ver en español
Weekly Update May 9, 2026

Highlights

  • WatDis now flags physically impossible sub-5 mm pipes and warns on suspicious tiny-pipe geometry before a run starts.

  • The benchmark program became much more reproducible with a committed 233-network external sweep and a deterministic 471-case queue.

  • The story this week is stronger guardrails and better evidence, not a confirmed solver runtime breakthrough.

What's New (By Category)

UI/UX

  • New localized English and Spanish diagnostics messaging landed for the impossible-diameter and extreme length-to-diameter QA findings.
  • In practice, that gives teams clearer feedback before they trust a run built on questionable imported geometry.

QA and Diagnostics

  • QA now raises a critical finding when a pipe is below 5 mm in diameter.
  • It also warns on tiny pipes with extreme length-to-diameter ratios, a useful signal when a model deserves review before anyone trusts the hydraulic output.
  • These checks landed with focused tests and QA changelog updates.

Benchmarking and Evidence

  • A committed external sweep now covers 233 networks with aggregate EPANET and WatDis convergence results.
  • The benchmark campaign now uses a deterministic 471-row queue, clean-reference EPANET gating, and versioned source snapshots so artifacts can be regenerated from a clean checkout.
  • That does not yet prove a numerical solver improvement, but it does make solver triage much more concrete and reproducible.

Solver and Engine

  • No direct solver algorithm or runtime behavior change was confirmed on main this week.
  • The shipped progress was in guardrails, case classification, and experimental discipline so future solver improvements can rest on stronger evidence.

Coming Next

  • Add head/flow parity metrics to the campaign so hard cases can be prioritized with better signal.
  • Turn several already-documented report and regression-pack rules into runtime enforcement.
  • Keep separating invalid inputs from real numerical issues to reduce wasted debugging cycles.