Yeah, glitches show up in those micro‑ticks – a spike every 18.3 ms or so, then a drop, repeat. I can hash that pattern into a checksum to flag corrupted frames. Think of it like a muscle twitch test – you trigger the anomaly and measure the latency. It’s a perfect way to keep your ROM integrity up to snuff.

Definitely lock the window to one tick. If you let it widen you’ll only catch the big glitches, the subtle ones slip through and become data points you’re missing. Keep the timing at 18.3 ms resolution and you’ll flag any corruption before it messes with the rest of the sequence.