Pith. sign in
theorem

sample_uncompressed_gt_compressed

proved
show as:
module
IndisputableMonolith.Verification.GWTC3RingdownHDF5SampleSchema
domain
Verification
line
71 · github
papers citing
none yet

plain-language theorem explainer

The recorded compressed byte length of the smallest GWTC-3 ringdown HDF5 member is strictly smaller than its uncompressed length (679110 < 931208). Verification and reproducibility authors cite this as a basic integrity check on the range-read sample. The proof unfolds the two Nat constants and closes by decidable comparison.

Claim. The sample compressed size $679110$ is strictly less than the sample uncompressed size $931208$.

background

This module freezes a one-member schema inspection of the GWTC-3 ringdown ZIP without pulling the full 1.44 GB archive. A companion script range-reads the ZIP central directory, picks the smallest .h5 member (rin/rin_S190727h_pyring_DS_1mode_10M.h5), fetches only its local header and compressed payload, inflates locally, and inspects the HDF5 layout with h5py.

Two Nat constants record the live sizes: compressed size $679110$ bytes and uncompressed size $931208$ bytes. Related frozen fields include local-header and data offsets, object/group/dataset counts, and the path and dimensions of /EXP6/posterior_samples. The module is structural verification only: schema facts, not posterior likelihood or RS dynamics.

proof idea

One-line tactic proof. Unfold the two definitions sampleCompressedSize and sampleUncompressedSize to the concrete naturals $679110$ and $931208$, then decide discharges the strict inequality on Nat.

why it matters

Feeds the certificate bundle gwtc3RingdownHDF5SampleSchemaCert as the field uncompressed_gt_compressed. That cert aggregates named schema facts (member name, positive sizes, object-count split, and this inequality) so downstream verification can treat the sample layout as a single closed record.

In the Recognition verification layer this is infrastructure, not a forcing-chain step: it locks an external LIGO/Virgo ringdown posterior member into Lean so later claims about data provenance cannot silently drift. It does not touch T0–T8, RCL, or the mass ladder; it only certifies that the inspected archive member behaves like a genuine compressed HDF5 payload.

Switch to Lean above to see the machine-checked source, dependencies, and usage graph.