ezmsg.nwb.clockmodel.GAP_ENVELOPE_MULT

GAP_ENVELOPE_MULT = 50.0

sample timestamping jitter is heavy-tailed (on real hardware the worst interval can be tens of times the 99.9th percentile), and a small persistent clock-sync step is not a data gap – it should be smoothed, not preserved. Only a jump well beyond that tail is treated as genuine data loss. Tune via real_gap_threshold when you know a file’s real gap sizes.

Type:

Auto threshold = period + this * envelope. Deliberately large