filters/notch

A scenario of the Gyro filters, from tools/trace/scenarios/filters/notch.cpp.

✓ pass

• The clang run (clang 18.1 optimized) matches the committed trace.
• The gcc run (gcc 13.3 optimized) matches the committed trace.

Shown on

These players show the same trace, with panels chosen to explain it:

• What does one notch do to a tone that sweeps through it? (How the Gyro Filters Work)
• Is the notch as wide as its closed form says? (Gyro Filters V&V Plan)

Every channel

filters/notch: every channel 1× real time

tone_hz [Hz] tone_hz

output_spectrum -60 dB0 dB (level, dB re 1)

gain_db [dB] [0] [1]

t = 0.000 s / 4.000 s

Keys (with the player focused): Space play/pause · ← → one sample (Shift: ten) · Home/End · [ ] speed

4 s of the dsp/filters scenario notch.cpp, 161 samples every 0.025 s. The panels plot every channel that changes: tone_hz, output_spectrum, gain_db. 4 events are marked. Pass criteria: BB-V1 width_error_hz <= 3.75 Hz.

1. t = 0.00 s a unit tone at 50 Hz: the notch passes it
2. t = 1.26 s the tone reaches the notch's lower −3 dB edge
3. t = 1.43 s the tone crosses f0 = 264 Hz, where the notch's gain is zero
4. t = 1.61 s past the upper −3 dB edge: unity gain again

• ✓ passBB-V1 width_error_hz = 0.472 Hz (<= 3.75), computed by the scenario harness

Block dsp/filtersScenario tools/trace/scenarios/filters/notch.cppSeed 0dt_sim 0.000125 s · dt_trace 0.025 sgcc 13.3 optimizedGenerated at 2183adcFormat reflex-trace/1, checked by CI against a fresh run

Constant over the run

• spectrum_bin_hz = 31.25 Hz
• notch_hz = 264.2 Hz

All scenarios