Engineering Calculation Script Audit

What It Addresses

Engineering calculation scripts often fail not because of syntax, but because formulas are copied incorrectly, applicability limits are missed, numerical solvers are unstable, or invalid inputs cause crashes. This skill targets hydraulic, civil, and water-engineering calculation scripts that need formula review, standards compliance checks, abnormal result debugging, and numerical code inspection, especially against SL, GB, or DL references.

How It Works

The audit follows a staged engineering-review approach:
- Formula compliance validation: extracts core formulas, records code locations, variable meanings, and formula sources. User-provided standard text or retrieved clause text takes priority; internal notes such as formula_reference.md or draft calculation sheets are treated only as low-confidence clues. Findings are rated PASS, WARN, or FAIL with explicit confidence.
- Applicability checks: verifies parameters such as δ/H, P1/H, H0/Hd, and Fr stay within valid physical ranges, checks whether lookup tables are being extrapolated unsafely, and confirms classification logic near boundary values.
- Numerical robustness review: examines iterative solvers, prefers bisection for global localization before Newton polishing, and checks initial guesses, convergence criteria, iteration limits, division by zero, negative square roots, and logarithmic singularities.
- Defensive guards and result validation: requires high-risk operations to return clear, physics-aware errors instead of raw Python stack traces, then validates units, conservation, monotonic behavior, and degenerate cases.

Boundaries

This skill is best used to audit, verify, and debug existing engineering calculation scripts, not to replace a complete design report. When original standard text is unavailable, some findings may remain provisional and should not be treated as final defects.