Repository navigation
Conversation
`relations:` is `sets:`. A set named in the `dims:` of a parameter, a variable or a constraint, or in `over=`, stands for its dimensions at the combinations it lists: the entry has coordinates only there, and a tool refuses a data row of a parameter anywhere else. There is no `in:` key. A set's bare name in the `where:` of such an entry is refused, with the set in `dims:` as the rewrite. In math a sum or an index ranges over a set, so the construct that `dims:` and `over=` take is named a set. Co-Authored-By: Fabian Hofmann <fab.hof@gmx.de> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018B3nA1xxh6NMJN6mrYY34Q
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018B3nA1xxh6NMJN6mrYY34Q
Documentation build overview
49 files changed ·
|
This was referenced Nov 16, 2026
An entry over a dimension twice, as TIMES' IRE_FLO: the alias's docs example names the set in dims:, a test states IRE_FLO in this spelling, and a set with two columns over one dimension is refused with an alias as the rewrite. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018B3nA1xxh6NMJN6mrYY34Q
This was referenced Nov 16, 2026
`in:` was answered "Did you mean 'in_'?", the field the load fills from `dims:` and a file may not write. The suggestion now leaves it out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018B3nA1xxh6NMJN6mrYY34Q
The TIMES examples in this PR's spelling: sets: in place of relations:, act over [prc_ts, rtp_vintyr], and ire_flo, trade_cost and export over the set top_ire. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018B3nA1xxh6NMJN6mrYY34Q
sparse.yaml in this PR's spelling: sets:, and every entry over a set names it in dims:. Restating balance found that over= a set beside by= was refused; a set in over= now stands for its dimensions there too, with the failing test first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018B3nA1xxh6NMJN6mrYY34Q
Contributor
Author
|
Note The following content was generated by AI.
Generated by Claude Code |
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
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.
Note
The following content was generated by AI.
Why it is a rename: a sum runs over a set, not a relation
dims: [connection, …],sum(x, over=connection)where:relations:filter, entries listin:sets:set C within U cross P; param f{C}; sum{(u,p) in C}What this changes
Option B of three for a sparse set. A set in
dims:orover=stands for its dimensions at the combinations it lists. Noin:key; entries stay flat, so operators and alignment by name are unchanged. Stacked on #1020 (alias), which states a dimension named twice.The TIMES examples (
examples/times/)Method, gate output, what is not done
in:machinery: a set indims:is turned into dimensions plusin_before validation (Spec._sets_in_dims), and folded back on write (_sets_written_back).inis no YAML key;in_written by hand is refused, and a mistyped key is not told of it (b221638)dims:too; a named expression does not, it derives its rows from its operandsover=a set expands to its dimensions (_members_of_sets)SetSpec,Spec.sets, every error message, the reference pages (relations.mdkeeps its file name, retitled "Sets and maps"), glossary, how-tos, tutorials, the TIMES pages. Not renamed: the program API (Program.relations,Relation,RelationDefined), internal names,docs/about/relations-as-linear-maps.md,docs/development/limits.md(this PR admits it)fa45382,12315cf): the alias docs example names the set indims:;tests/test_alias.pyandexamples/times/stateIRE_FLOin this spelling12315cf: ruff, ruff format, pyrefly (0 errors), pytest (4270 passed, 1 skipped), typos,zensical build --strict, prettier on changed files; schema, goldens, generated pages regenerated. Not run:compile-tex; no pixi, uv venv🤖 Generated with Claude Code
https://claude.ai/code/session_018B3nA1xxh6NMJN6mrYY34Q