Skip to content

F5 evidence path: scale-relative D8/D10/D11b/D13 and mechanism-valid calibration #101

Description

@marcohost33-maker

Context

Follow-up to issue #97 item 2. The known absolute henrici_eta > 1.0 threshold is not the only rate-unit dependence in the A10/F5 path. Re-audit of main@b1a5681 found that the numerical D10/D11b/D13 estimators also contain absolute rate scales.

claim_status: pending; no classifier change in this issue until calibration and independent physics review.

Verified findings

D8

henrici_eta is rate-dimensioned and transforms as eta(cL)=c eta(L) for c>0.

D10

kreiss_constant() uses fixed grid constants:

  • sigma_lo = 1e-3
  • sigma_hi >= 1
  • omega_max >= 1

The exact continuous-time Kreiss constant is invariant under positive time/rate rescaling, but this dimensional grid is not. A direct reproduction of the current algorithm on A=[[-1,20],[0,-2]] gave materially different estimates under A -> cA (approximately 1.00 at c=1e-10, 9.79 at c=1, 6.77 at c=1e10). This is grid error, not changed physics.

D11b/D12

resolvent_peak_curve() defaults to absolute sigma=1e-3 and omega_max >= 1; the peak and FWHM therefore compare different dimensionless offsets after a unit change.

D13

pseudospectral_radius() uses absolute eps=1e-3 plus absolute 1e-3 span floors. For positive c,

Sigma_eps(cL) = c Sigma_{eps/c}(L).

Thus a fixed absolute epsilon changes the perturbation family under L -> cL. In the same reproduction, the current pseudospectral_radius(cA)/(c*gap) changed from about 7.1e6 at c=1e-10 to 2 at c=1/1e10.

Mechanism mismatch

F5 currently consumes the maximum modulus of the epsilon-pseudospectrum. For slow/phantom relaxation this is not necessarily the relevant extremum: it can be dominated by fast modes far from the origin. The literature ties transient/phantom behaviour more directly to pseudospectral abscissa/intrusion, resolvent growth, localized or ill-conditioned modes, and direct propagator amplification. Henrici alone is generic non-normality evidence, not a proof of F5.

Correct staged solution

Slice A — shared scale and additive diagnostics; no verdict change

  1. Define one positive operator rate scale with explicit zero-operator semantics, preferably a documented norm-based scale.
  2. Add relative Henrici dep_F(L)/||L||_F while preserving legacy D8.
  3. Reparameterise D10/D11b grids in dimensionless coordinates and convert back only for rate-valued outputs.
  4. Define D13 using eps_abs = eps_rel * scale(L); record both values and grid/refinement metadata.
  5. Add a pseudospectral abscissa or gap-directed intrusion diagnostic; do not silently redefine the existing D13 field.
  6. Label coarse-grid results as estimates/lower bounds and provide convergence/refinement metadata.

Slice B — conformance suite

For c in {1e-10,1e-5,1,1e5,1e10}:

  • dimensionless diagnostics invariant within declared tolerance;
  • rate-valued diagnostics scale by c;
  • D14 agrees after t -> t/c;
  • zero, normal, gapless-normal and ordinary non-normal negatives remain non-F5;
  • dense/sparse and basis-change metamorphic tests.

Slice C — preregistered classifier study

  • calibration and holdout sets separated;
  • known phantom/Jordan/skin positives;
  • normal, detailed-balance, gapless-normal and non-phantom non-normal negatives;
  • system-size families to expose Frobenius/dimension bias;
  • FPR/TPR/invariance criteria declared before fitting;
  • no tuning merely to preserve existing anchors;
  • classifier switch only after independent physics review.

Release/claim gate

Until all dimensioned thresholds and absolute grids are removed from the F5 decision path, LiouScope must not claim that A10/F5 is invariant under a change of rate units. The honest interim status is research/candidate evidence with the limitation documented.

Refs #97 item 2.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions