TARE

clock_comparison · evaluate · results_only

tare evaluate --holdout --no_method_disclosure

Request evaluation

fit on train · test on holdout · ship outputs, not recipes · train ∩ test = ∅

RMS_before · typical

low 30s

ns · window-dependent

RMS_after · holdout

17–22

ns · not remainder = 0

Δ_RMS · typical

~45%

not a guarantee on your data

Holdout-validated timing evaluation.

Post-processing for long-baseline GNSS clock comparison. You get corrected outputs and RMS-class summary statistics—the correction recipe stays internal.

For people who already know what “30 s final CLK” means: we publish the evaluation protocol and typical holdout numbers. We do not publish the fit.

Typical performance · held-out

HOME_SPEC_v0 · train ∩ test = ∅
Primary metricRMS on agreed comparison/residual seriesSame definition before and after
Uncorrected (typical)low 30s nsWindow- and baseline-dependent
Corrected (typical holdout)17–22 nsTested configurations; not remainder = 0
Improvement (typical)~45% RMS reductionNot a guarantee on your panel until you run the pilot
Next stepEvidence room → — pinned runs, null tests, strict-window example

// entering evidence mode

Proof layout for people who read footnotes.

Same claims as above—more DOY, more holdout, more show your work.

Open evidence