Show stadion's numbers instead of describing them - #9
Merged
Conversation
The site said stadion places a score between the classical method and the optimum, and then left the reader to take that on trust. The measurements exist - six tasks, the distance between the two references, each with a bootstrap interval - and they are the most convincing thing the project has. The spread is what the table is for. Inventory leaves 0.4% because the newsvendor formula is already near-optimal; the battery leaves 26.6% because a price threshold cannot decide to arrive at the evening peak with charge in hand. A benchmark whose tasks all leave generous headroom has selected for problems the standard method happens to be bad at, and this one can show that it did not. Figures copied from the repository's own README table rather than recomputed, and the caption carries the conditions so the column can be read without the repository open.
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 site said stadion places a score between the tuned classical method and the computed optimum, and then left the reader to take that on trust. The measurements exist — six tasks, the distance between the two references, each with a bootstrap interval — and they are the most convincing thing the project has.
inventoryjoint-pricingpricingqueueingsupply-chainenergyThe spread is what the table is for. Inventory leaves 0.4% because the newsvendor formula is already near-optimal; the battery leaves 26.6% because a fixed price threshold cannot decide to arrive at the evening peak with charge in hand. A benchmark whose tasks all leave generous headroom has selected for problems the standard method happens to be bad at — and this one can show that it did not.
Figures are copied from stadion's own README table, not recomputed here. The caption carries the measurement conditions, so the column can be read without opening the repository.
Verified
scripts/check_site.pypasses on all four pages, and the cross-language scan finds no unmarked text on either landing page.Rendered locally: the table sits in the wider left column at 569px on desktop and reflows to 335px on mobile without the page scrolling sideways.
overflow-x: autoon the wrapper is there as a floor, not because it is currently needed. Figures render withtabular-nums, so the percent column aligns on the decimal.