sampleDataOffset
plain-language theorem explainer
Records the ZIP data-start byte offset of the smallest GWTC-3 ringdown HDF5 member as the natural number 66237294. Verification authors cite it when fixing the HTTP range window used to inflate that member without fetching the full 1.44 GB archive. The body is a bare numeric definition, not a derived proof.
Claim. The data-start byte offset of the inspected GWTC-3 ringdown HDF5 sample member inside the archive is the natural number $66237294$.
background
The module freezes a one-member schema inspection of the GWTC-3 ringdown ZIP. Method: read the ZIP central directory by HTTP range request, pick the smallest .h5 member (rin/rin_S190727h_pyring_DS_1mode_10M.h5), range-read only its local header and compressed payload, inflate locally, and inspect with h5py.
Live metadata from that pass include compressed size 679110, uncompressed size 931208, local-header offset 66237197, and data offset 66237294. Sibling constants pin the remaining counts (HDF5 objects, groups, datasets, posterior path and field counts). This is structural schema capture only, not a posterior likelihood claim. Zero sorry and no new RS-specific axioms.
proof idea
Definitional constant: the right-hand side is the literal natural number 66237294. No lemmas, tactics, or proof obligations.
why it matters
Pins the exact byte window at which compressed member bytes begin after the local header, so downstream verification can reproduce the range-read and inflate step without the full archive. Together with the sibling offset and size constants it closes the structural half of the GWTC-3 ringdown sample schema (module status: structural theorem, closure 2026-05-22). It does not touch RS forcing landmarks (T5–T8, RCL, phi-ladder); it is empirical data hygiene for the verification layer that later compares ringdown posteriors to RS mass or timing predictions.
Switch to Lean above to see the machine-checked source, dependencies, and usage graph.