ข้ามสารบัญไปยังเนื้อหา
อัปเดต 2026-09-07
Specific solver-failure messages
which node, which constraint
A non-converging solve surfaces the engine's actual failure reason and location in the UI — which node or constraint broke down, and by how much — instead of a generic 'solve failed' that leaves you guessing what in the model to fix.
เมื่อไรจึงใช้
- A solve fails and you need to know WHERE to look in the network, not just that something is wrong.
- You're debugging a new model and want the fastest path from 'it doesn't converge' to 'this junction's demand is infeasible'.
- You're comparing DekEn's failure UX against a black-box tool that just reports 'no solution' with no diagnostic.
คำนวณอย่างไร
The failure message is generated from the actual internal solver state at the point of divergence (residual by node/link, which constraint was violated) rather than a caught-and-generic exception message.
ข้อควรระวัง
noteA specific failure message describes the LAST solver state before it gave up — for a genuinely infeasible model that location is diagnostic; for a model that's merely hard to converge, the same location can be a red herring pointing at wherever the iteration happened to be worst, not the true root cause.
noteThis is a UX/diagnostics feature, not a scope-note detector — it fires on solver FAILURE, whereas the honesty register fires on solver SUCCESS with a caveat; don't conflate the two channels when triaging a bad run.
ที่เกี่ยวข้อง