Lock the DASH7 leakage SNR-curve experiment before it runs - #14
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
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.
What changed
Adds
docs/leakage-real-snr.md: the locked command, seeds, wait conditions, artifact names, and hour estimate for repeating the synthetic SNR curve on DASH7. The curve has not been measured.Why
ROADMAP Now item 1 is still the n=15 SNR sweep on a real capture (
artifacts/leakage_real_runs.jsondoes not exist). The stride half is already published. Starting that grid without locking n, without waiting forIQFORGE_DASH7and an idle parity gate, or by using the script default SNR list, would either contend with the gate or reproduce the ceiling table the pilot already ruled out.How it was verified
No training run. No download. Turkish docs left untracked.
Conventions it touches
--sourceonly