Repository navigation
experiments: the chip counters cover the run, and the export is JSON - #41
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.
Follows MeshBench/meshbench#746, which now measures each cell's
chipcounters from the cell's baseline rather than from boot, the same point the delivery totals start from.pages/reference-control.md: theexperiment.exportanswer matches the verb's own description again ("what each node's radio counted over the cell and how it was set at the end"), replacing "at the end of the cell" from reference: irq_suppressed on node stats, and chip counters in the experiment export #40.pages/experiments.md: step 7 said the export writes an HTML report. It writes JSON. The step now says so and says whatchipcarries and over which window.Merge after MeshBench/meshbench#746.