Processing Config Filter

[jennyuxi]

• Added processing.ts for reusable default configuration
• Added conditions which change processing config that is sent to backend depending on selections in frontend in filter-node.tsx
• Added code to use the configurations that are sent to backend in useWebsocket.tsx

[github-actions]

✅ PR approval conditions satisfied (1 lead OR 2 team members approved).
[Last checked: 2026-02-10T21:28:30.772Z]

[HeisSteve]

Looks good on the backend side

[MaddieWright]

Have you run this locally? It looks like there’s an extra slider being rendered below the node, in addition to the sliders inside combo-box.tsx. Instead of adding a new slider in the FilterNode, you should pass the cutoff state from the FilterNode to the ComboBox via props (lowCutoff, highCutoff, setLowCutoff, setHighCutoff) and let the ComboBox handle all sliders.

Also, the current setup does not account for the bandpass filter configuration. So you could also update for that now. Just a refresher that this is what the backend expects:

• Lowpass - l_freq: null, h_freq: highCutoff
• Highpass - l_freq: lowCutoff, h_freq: null
• Bandpass - l_freq: lowCutoff, h_freq: highCutoff

[MaddieWright]

looks good, will ask team to test out when building off of it for new tasks