High-contrast homogenization: #
Provider.PolynomialHomogenization.Root.CorrectorComposition.CertificateProjections
Imported from the Apache-2.0 HighContrastHomogenization development at commit
7a13dbcd8d6609264a713373f5c69ceeac870472.
The certificate projections, discharged #
Three certificate-side premises were carried as consumer-supplied corrector-family hypotheses:
- the corrector-and-flux decay clause's
hproject—rootGoodScaleAt … → PrintOrderRateBearingCommonAffineGoodScale …; - the large-scale Lipschitz estimate clause's
hcustody—rootGoodScaleAt … → DecoupledRootGoodScale d g cD κc …; - the ceiling comparisons that let a module read the certificate at its own smallness.
All three are theorems, not assumptions, once the certificate is the ceiling-exporting
smallness interface c-parameterised one. The reason is structural and worth stating:
RootInterface.RootGoodScalehides its smallness behind∃ c ∈ Ioo 0 1, and the root instantiation pins thatcto1/2. The only available transport,PrintOrderRateBearingCommonAffineGoodScale.mono_smallness, moves the smallness upward only. So fromRootGoodScaleone cannot reach the corrector-and-flux decay clause'scanonicalCorrectorSmallness d g hgor the large-scale Lipschitz estimate clause's(2 * Crec)⁻¹, both of which may be far below1/2. That is exactly the gapHCPoly.Provider.PolynomialHomogenization.RootInterface.SmallnessMonotone's own docstring names.CorrectorComposition.rootGoodScaleAtexposes the smallness as a binder, andexists_rootGoodScaleAt_of_quenchedRowproveshhomogenizedat every smallness. So the certificate can be produced atcStar gbelow every module ceiling, andmono_smallnessthen moves it up to each module's own constant. The direction of the monotonicity is now the useful one.
The projections themselves are then one field access plus one application.
The two projections #
The ceiling-exporting smallness interface exposes the printed rate-bearing certificate at
its own smallness. It is literally the good field of the retained-row
structure; nothing is estimated.
The same certificate read at any larger smallness.
The decoupled certificate the large-scale Lipschitz estimate clause consumes. The
private-order half is
recovered from the printed one by
Root.DecoupledRootGoodScale.of_printOrder; nothing stochastic is added.
The two hole-side corrector-family hypothesis premises, discharged #
the large-scale Lipschitz estimate clause's certificate projection, in the exact shape
exists_largeScaleLipschitz_of_goodScaleProjection demands. This is the whole
of the large-scale Lipschitz estimate clause's residue, and it is a theorem.
the large-scale Lipschitz estimate clause, unconditional at the ceiling-exporting smallness #
interface
the large-scale Lipschitz estimate clause at the c-parameterised certificate, with no
hypothesis at
all. The ceiling cMax is the (2 * Crec)⁻¹ the decoupled terminal
itself selects.
the corrector-and-flux decay clause, reduced to the family corrector-family hypothesis #
alone