You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
[0.27.0] - 2026-10-06
Added
Receiver output power and IIP3 requirements — add optional output-power limits at a selected reference tone and two-tone IIP3 tests with configurable tone spacing and input-level sweeps. The Receiver Requirements panel evaluates and reports both alongside gain and noise-figure limits, with configuration persisted in project files.
Fixed
Network Analyzer and Receiver Requirements through switched filter banks — a 1:2 switch feeding parallel branches that rejoin at a 2:1 switch is now measured instead of reporting no data (#169). Analyzer gain follows the selected switch throws (or, where the selected filter passes no tone, any leakage from the other branch), and its noise figure includes the unselected branch's noise leaking through isolation; receiver output power and IIP3 measure the same circuit. Combiners, merges fed by a source outside the measured path, and a Point A component that feeds the bank through more than one output port still report no data.
Testing
Cover receiver output-power and IIP3 measurement/evaluation, partial IIP3 sweeps, project persistence, and panel integration.
Add switched-filter-bank coverage: analyzer gain and noise figure against the live engines (matched, flipped, and mismatched throws; low-isolation noise), an IdealFilter bank whose gain reads the other branch's leakage in the selected filter's stopband, the shared path discovery and runner (both branches wired in topological order, rejected topologies, malformed paths), receiver output power and IIP3 through a bank, and the production app clone adapter.
Make the Receiver Requirements pause/resume UI test deterministic in optimized builds: it caps the receiver engine's chain runs per frame, because a Release build otherwise finished the whole sweep before the test hid the view. Unit coverage pins the per-update cap.