Skip to content

docs: a tutorial solves one model once per scenario and then window by window - #1746

Merged
FBumann merged 1 commit into
claude/docs-readme-homepagefrom
claude/docs-sweep-tutorial
Sep 25, 2026
Merged

FBumann merged 1 commit into
claude/docs-readme-homepagefrom
claude/docs-sweep-tutorial

Conversation

@FBumann

@FBumann FBumann commented Sep 25, 2026

Copy link
Copy Markdown
Collaborator

Prompt: About the links used: Are there better targets for each box? Or is sth missing from the docs? Like a decomposition tutorial? And tables in/out? What should it show? Data contract? Preparing data? The archiving?

Note

The following content was generated by AI.

The user's follow-up was "Yes. Stacked PR for 2". This PR is stacked on #1743.

What this changes

A new tutorial, "Sweep a model" (docs/sweep.md), runs solve_over twice. First it solves once per scenario. Then it solves window by window, carrying storage state between windows. The home page card "Sweeps and rolling horizons built in" now links it, instead of the 3,000-word reference.

Method, gate output, alternatives
  • docs/sweep.md, 458 words of prose. Every block runs at build time (markdown-exec), so each output is what the code printed.
    1. One solve per scenario: EachCoordinate('scenario') on examples/dispatch.yaml, with a low and a high load. Objectives 7500.0 and 16200.0, and the p schedule per scenario.
    2. Window by window:
      • EachWindow('hour', steps=3, lookahead=3, into='snapshot') on the cyclic examples/storage.yaml is refused before any window is solved. The page quotes the message whole.
      • examples/rolling/horizon.yaml with carry={'soc_initial': 'soc'} then solves 3 windows, and reads back one 8-hour schedule with original_index=True.
    3. Myopic pathways: one sentence, and a link to examples/myopic/run.py. That example needs about ten tables, too many to run on this page.
  • mkdocs.yml: a nav entry under Tutorials.
  • docs/lifecycle.md: "Fix, relax, remove" gets a "Where next" that chains to the next tutorial.
  • README.md and docs/stylesheets/extra.css: the card links …/sweep/ and keeps its icon.
  • Step 2 uses two models. No example model shows both the refusal and the windowed solve, and patching a spec on the page would add steps.
  • Gates (pixi is not installable in this session; a Python 3.12 venv with the docs group's pins stood in):
    • python -m zensical build --strict: "No issues found". The build runs every block.
    • pytest tests/test_doc_examples.py tests/test_docs_site.py tests/test_models_gallery.py: 486 passed, 3 skipped.
    • ruff check ., ruff format --check . (0.16.1): clean.
    • Sentences: n 27, median 14, none over 25.
    • Not run: the full suite, pixi run check.

🤖 Generated with Claude Code

https://claude.ai/code/session_01A89tReSh8rTBG9ocy7688y


Generated by Claude Code

…y window

"Sweep a model" runs solve_over over load scenarios on the dispatch model,
shows a cyclic store refused by the coupling check, and solves the rolling
horizon model with its state of charge carried between windows. The README
card on sweeps and rolling horizons links to it, and "Fix, relax, remove"
ends by pointing at it.

Sentences in docs/sweep.md: n 27, avg 14.2, median 14, over 25: 0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A89tReSh8rTBG9ocy7688y
@codspeed

codspeed Bot commented Sep 25, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

✅ 24 untouched benchmarks
⏩ 82 skipped benchmarks1


Comparing claude/docs-sweep-tutorial (fe4a896) with claude/docs-readme-homepage (5303eeb)

Open in CodSpeed

Footnotes

  1. 82 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

@read-the-docs-community

Copy link
Copy Markdown

@FBumann
FBumann added this pull request to stack #1749 September 25, 2026 09:35
@FBumann
FBumann merged commit 7c15f18 into main Sep 25, 2026
12 checks passed
@FBumann
FBumann deleted the claude/docs-sweep-tutorial branch September 25, 2026 10:27
FBumann added a commit that referenced this pull request Sep 25, 2026
…tem modellers, in cards with icons, and the readme is under half its length (#1743)

> **Prompt:** Look at mathspecs readme and docs homepage. specsolve
should follow its example. Be leaner, show the selling points, use icons
etc. Check the prompts used in the docs prs on mathspec

> [!NOTE]
> The following content was generated by AI.

Later prompts set the four benefits:
- "I think the big selling points are: tables in, tables out… model
topology (sparsity) does not affect performance, built in decomposition
(rolling horizon, scenario sweeps, myopic?), validated against pypsa in
terms of numbers AND capabilities, takes the burden of making the model
building performant off of the user. Minimalistic api… Archivable"
- "The minimal api fits 2… the solver keep feature in rolling etc should
be in 2… 2 and 3 should maybe be swapped"

Later prompts also set the tagline ("Keep the native solver connected
for warmstarts, quick updates… Stay brief!") and the link targets ("Are
there better targets for each box?", then "Yes. Stacked PR for 2"). The
user chose the icons from rendered option sheets.

The README and home page now follow math-spec's
(energy-models/mathspec#698, energy-models/mathspec#699). They show
badges, a tagline, a short intro, and four benefits. On the home page
each benefit is a card with an icon, and the whole card is the link.
README: 1,321 → about 540 words. Home page: 1,034 → 663.

Stacked on this: #1746 (sweep tutorial) → #1747 (tables tutorial) →
#1748 (annotated solve block). The two tutorials repoint cards 1 and 2
to themselves.

<details><summary>Method, gate output, alternatives</summary>

**Tagline**, in the README and the home page hero: "Solve an
optimisation model written in YAML. Attach your data as tables, and keep
the solver loaded for quick updates and warm starts." `update()` keeps
the solver with the model on it, and `keep='progress'` carries on from
the last solve.

**The four benefits** (README `benefits` snippet, which the home page
includes)
1. **Tables in, tables out.** Any Arrow table (polars, pandas, DuckDB)
or a parquet path goes in. Tables come out, and an archive keeps the
model, its data and its results as parquet. → `howto/archiving/` (#1747
repoints it to the tables tutorial)
2. **Sweeps and rolling horizons built in.** Scenario sweeps, rolling
horizons and myopic pathways run in one call, and each window is checked
against how the model couples. → `reference/sweeps/` (#1746 repoints it
to the sweep tutorial). The docs use "decomposition" for Benders, which
`about/decomposition.md` says specsolve ships no driver for, so the card
takes its reference page's name.
3. **Fast, and hard to get wrong.** A model's topology does not change
its cost. The solver stays loaded: `update()` puts new numbers on it,
and `keep='progress'` warm-starts from the last run. The API is a
handful of verbs. → `about/benchmarks-scaling.html`, the results rather
than the method page.
4. **Validated against PyPSA.** All 16 rungs match PyPSA's objective,
and 12 match its duals row for row: two rungs are integer models with no
duals, and rungs 12 and 14 differ on some dual rows, as their ladder
pages show. → `examples/pypsa_ladder/`

**What math-spec's PRs asked for, and what this takes from them**
- #698 asked for the key selling points, core user benefits, clickable
professional boxes, icons, and CSS. Taken here as: the benefits are a
README snippet, which the home page includes inside `grid cards`; the
icons come from CSS, chosen by each card's link; the whole card is the
link.
- #699 asked what could be cut, for the inline comments to go, and for
links instead of prose. Taken here as: no internals diagram, no inline
comments except the objective comment the README test reads, and links
instead of repeated prose.

**README**
- Badges in math-spec's flat style (CI, PyPI, Python, Docs, License), as
a snippet the home page includes.
- The tagline, and an `intro` snippet that names math-spec as the
language, names the solvers, and says the same file can build a
`linopy.Model`.
- The four benefits, with absolute links, because the home page includes
the snippet from inside `docs/`.
- The example; documentation; installation (one command, plus one
sentence on the extras); prior art; status; licence.
- **Removed:**
  - the benchmark paragraphs; the benchmarks page holds them;
  - the mermaid internals diagram;
  - the "Why" list;
  - the linopy code block;
  - the walkthrough paragraph;
  - the install block with inline comments.

**Home page**: the six hand-written cards are gone. Their benchmark
claim ("2–4x faster than linopy") had drifted from the README's "1.01x
to 1.29x". The page includes the README's `badges`, `intro` and
`benefits`, so the text lives once. "Where to next" is a list.

**Cards** (`docs/stylesheets/extra.css`)
- math-spec's card rules. `li:has(> a[href$="…"])` picks each card's
icon by where its link points.
- Icons in `docs/stylesheets/icons/`:
- `table-arrow-right`, `speedometer` and `transmission-tower` are
Material Design Icons, Apache-2.0, Pictogrammers.
  - `split.svg` is drawn for the sweeps card, MIT.

**Also:** `docs/guide.md` linked
`index.md#the-whole-thing-in-one-model`. It now links
`#a-model-is-one-file`.

**Gates** (pixi is not installable in this session; a Python 3.12 venv
with the docs group's pins stood in):
- `python -m zensical build --strict`: "No issues found".
- Headless Chromium: each card's icon resolves. 25 of 25 sample points
on every card resolve to its link, in light and dark.
- `pytest tests/test_doc_examples.py tests/test_docs_site.py
tests/test_models_gallery.py`: passed. The README example solves to
1920.0.
- `ruff check .`, `ruff format --check .` (0.16.1): clean.
- Not run: the full suite, `pixi run check`.

**Not done:** `docs/README.md`, the docs folder index, is unchanged.

</details>

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01A89tReSh8rTBG9ocy7688y

---------

Co-authored-by: Claude <noreply@anthropic.com>
fluxopt-release-bot Bot added a commit that referenced this pull request Sep 25, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.0.1-alpha.358](v0.0.1-alpha.357...v0.0.1-alpha.358)
(2026-09-25)


### Documentation

* a tutorial feeds the dispatch model from parquet, reads the answer as
tables and queries its archive
([#1747](#1747))
([5ecc2ec](5ecc2ec))
* a tutorial solves one model once per scenario and then window by
window ([#1746](#1746))
([7c15f18](7c15f18))
* the readme and home page lead with four benefits for energy system
modellers, in cards with icons, and the readme is under half its length
([#1743](#1743))
([e14f3b8](e14f3b8))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: fluxopt-release-bot[bot] <307443024+fluxopt-release-bot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants