Repository navigation
The chip's counters on the Radio tab and in the Results table - #42
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.
The manual for MeshBench/meshbench#749.
pages/debugging.md: a Read the node's radio section for the node window's Radio tab, covering IRQ suppressed (including what not counted means) and spurious detections, with a picture and thenodes.statsfield beside it.pages/experiments.md:irq_suppressedandbusy_msin the metrics table, what the IRQ suppressed and busy time columns of Results show, beside delivered, and when they are a dash, a picture of the table, and the per-cellchiprecord in the export.pages/reference-control.md: resynced withtools/sync-verbs.pyfrom the #749 branch, for theexperiment.resultsdescription.The two pictures are the workbench's own render tests at real scale (
radioshot_test.goand thechip-counterscase ofsweepshot_test.go), not window captures; they carry no node names or network identities. The numbers are from a scotland-strict run of MeshCore 1.16.0, 1.17.0 and 1.17.1.Merge after MeshBench/meshbench#749, since the reference text is synced from that branch.