Repository navigation
v0.6.30: Add Measurement Repeatability - #44
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Builds on runtime-confirmed v0.6.29. Adds persistent per-output Measurement Repeatability without replacing the existing primary REW response. Each Measurement session/output can store up to 4 additional repeat REW responses (primary + 4 repeats total). A new isolated repeatability_api.py provides get/add/delete WebSocket commands and stores data additively inside the existing measurement session, so Store version and model.py remain unchanged. Frontend v0.6.30 adds a Measurement Repeatability panel with measurement count, mean shape spread, percentage within ±1.5 dB, agreement grade, per-EQ-candidate repeat match chips, repeat import/remove controls, and persistent reload across navigation/restart. Confidence remains advisory but now also weighs whether each EQ feature repeats across stored measurements; Crossover Guard and Null/Boost Guard remain the only automatic blocks. Primary response generation, EQ suggestions, Prediction, Apply Preview, Apply/Restore, snapshots, channel EQ and Goldhorn isolation are unchanged.