feat(tagline): "15s vs 3-4 weeks" benchmark + comparison page#51
Merged
Conversation
New `ropeway tagline` command times the optimizer end-to-end on six
representative corridors (Andean urban, alpine 3S, funitel, urban
gondola, tourist tram, pulsed gondola), then frames the wall-clock
against a 3-week / 120-engineer-hour / ~$60k feasibility-study baseline
per corridor and writes a JSON manifest + markdown comparison page.
Headline on the default pack: six corridors, 100% feasible,
~4s total wall-clock, ~626 000x speedup vs the manual baseline.
Outputs land at docs/tagline/tagline.{json,md}; the page is wired into
the mkdocs nav as "15s vs 3-4 weeks". README gets the speedup table.
7 new tests cover row math, summary aggregation, JSON round-trip,
markdown shape, file emission, and an end-to-end optimizer smoke.
Full suite: 435 passing.
# Conflicts: # CHANGELOG.md
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.
Summary
ropeway taglineCLI times the optimizer end-to-end on six representative corridors and frames it against the manual-engineer baseline (3 weeks / 120 h / ~$60k per corridor).docs/tagline/tagline.json+tagline.md; page wired into mkdocs nav as "15s vs 3-4 weeks".Why
Directly proves the project's tagline so any engineer can reproduce the claim with one command.
Test plan
ropeway taglineround-trip: 6 corridors, 100% feasible, ~4 s, ~627 000× speedup