Skip to content

20260930 - Stop offering the notch filters as settings - #106

Merged
Purple10101 merged 1 commit into
mainfrom
20260930-remove-notch-fields
Sep 30, 2026
Merged

Purple10101 merged 1 commit into
mainfrom
20260930-remove-notch-fields

Conversation

@Purple10101

Copy link
Copy Markdown
Collaborator

What

The "DAB Notch Filter" and "RF Notch Filter" checkboxes are removed from the Configuration page.

Why

offworldlabs/retina-node#46 makes config-merger derive capture.device.dabNotch and rfNotch from the final capture.fc (a notch is on unless the capture band overlaps its stopband: RF 77-115 MHz, DAB 155-235 MHz), and it overwrites whatever user.yml holds. A value saved from the form would be silently ignored.

Fix

  • CaptureFormConfig loses device_dabNotch and device_rfNotch.
  • The capture flatten/unflatten mapping and the unchecked-checkbox defaulting in parse_flat_form_data drop them, so saving the form never writes the notch keys.
  • A user.yml that still holds them is left alone: the merger overwrites them and the next Save drops them.
  • vulture_whitelist.py loses the two entries.

Testing

  • Full suite: 1019 passed. ruff check . and the dead-code gate pass.
  • New test_save_does_not_write_notch_filters: with notch keys already in user.yml and stale notch fields posted, neither key is written.
  • On a test node: the change was deployed to /opt/retina-gui. /config rendered with no notch fields and the other capture fields intact, and Apply ran through to done. The node was restored afterwards.
  • Not verified in a browser: the rendered HTML was checked with curl.

Docs

  • docs/features/config-editor.md: new "Notch filters" section (derived from fc, not user settings, old keys harmless, and a warning that a node tuned inside a stopband may overload until recalibrated). The Capture row and the form-parsing paragraph are updated.
  • docs/features/auto-calibrate.md: new "Notch filters are not retuned" subsection. A live retune changes fc but not the notches.

After this

Merge together with offworldlabs/retina-node#46. On its own this only removes two checkboxes whose values the current merger still honours.

🤖 Generated with Claude Code

The DAB and RF notch checkboxes on the Configuration page no longer did
anything. retina-node's config-merger now derives capture.device.dabNotch
and rfNotch from the final capture.fc (a notch is on unless the capture
band overlaps its stopband, RF 77-115 MHz and DAB 155-235 MHz) and
overwrites whatever user.yml holds, so a value saved from the form was
silently ignored.

The fields are removed from CaptureFormConfig, from the capture
flatten/unflatten mapping, and from the unchecked-checkbox defaulting in
parse_flat_form_data, so saving the form never writes the notch keys. A
user.yml that still holds them is left alone: the merger overwrites them
and the next Save drops them.

docs/features/config-editor.md gains a Notch filters section, including a
warning that a node tuned inside a stopband gets a stronger signal once its
notch turns off, so gain set with the notch on may overload until it is
recalibrated. docs/features/auto-calibrate.md notes that a live retune
changes fc but not the notches, so a candidate in a different notch band
is probed with the wrong notches until /calibrate/apply restarts blah2.

A new test in test_app.py checks that saving the form, with notch keys
already in user.yml and stale notch fields posted, writes neither key.
The full suite passes, as do ruff and the dead-code gate.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@Purple10101
Purple10101 merged commit b58ae53 into main Sep 30, 2026
3 checks passed
@Purple10101
Purple10101 deleted the 20260930-remove-notch-fields branch September 30, 2026 14:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant