DekEn

อัปเดต 2026-09-07

Transient honesty register (T1–T25)

MOC + gas-transient scope notes

The same refuse/blocking/warn/info discipline extended to the time-domain transient engine (T1–T25) — naming why a multi-scenario run fell back to a legacy solver path, flagging column-separation/cavitation, enforcing a low-Mach envelope on gas transients, and disclosing modelling gaps like the boundary-adjacent unsteady-friction shortfall — closing what had been the biggest systemic honesty gap versus the steady-solve register.

เมื่อไรจึงใช้
  • You're reviewing a water-hammer or gas-transient result and need to know which physics were actually modelled versus assumed.
  • A transient run silently used a different solver path than you expected — the register names the cause instead of leaving you to guess.
  • You're checking whether a gas-line transient is within its validated low-Mach envelope before trusting a blowdown or valve-transient number.
ค่าที่ต้องกรอก
ค่าคำอธิบาย
คำนวณอย่างไร

Shared sync/async detector helpers run on every dispatch route (single-scenario MOC, quick pump-trip/burst, the background worker) so the same honesty check can't fork between the interactive and background paths; the result carries structured notes plus which solver path actually ran, and the frontend feeds the same ScopeBanner used by the steady register.

ข้อควรระวัง
noteBefore this register existed, a quick pump-trip endpoint was silently erroring on every call and a quick-burst endpoint fabricated cavitation events that never happened — both were caught only by writing the honesty detectors, not by the numbers looking wrong.
noteA column-separation flag narrows as more physics gets modelled — a site that's now explicitly modelled stops tripping the generic 'unmodelled cavitation site' note and a more specific one fires instead. Don't assume a T-code's trigger condition is static across versions.
ที่เกี่ยวข้อง