fix(v1): drop solve-time coord consistency guard rejecting disjoint labels - #989
Merged
Merged
Conversation
Build cost — v1 vs legacyv1 build peak & time relative to legacy, on this commit — not a comparison against master (that is CodSpeed).
Full table (time + peak, mean)📊 Interactive plots + CSV: download the semantics-report-v1-vs-legacy artifact from this run. Report-only · not a gate · refreshed on every push · obsolete once legacy is dropped. |
Merging this PR will not alter performance
Comparing Footnotes
|
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.
Closes #986.
Note
The following content was generated by AI.
Changes proposed in this Pull Request
Under v1 semantics,
Model.solve()ranModel._check_coord_consistency()(added withModel.assign_coordsin #955). It raised whenever two containers share a dimension name but their labels do not nest. PyPSA uses onenamedimension for all components with disjoint labels, so every multi-component PyPSA model failed at solve time.The guard is removed:
join="exact"where containers are actually combined, at arithmetic time.assign_coordsreturns detached copies, and solver matrices pair terms by variable label, not by coordinate value. So only the private_assign_coordscould produce the state the guard targeted.Model.assign_coordsstill validates its own inputs (full-index length, subset mapping, duplicate and ambiguous full-index containers).Also removed: the guard's tests, the
constants.pycomment that pointed to it, and the release-note sentence. Since #955 is unreleased, no bug-fix note is needed. A regression test intest/test_optimization.pysolves a model with disjoint labels on a shared dimension under both semantics. It fails on master under v1.Checklist
AGENTS.md).doc.doc/release_notes.rstof the upcoming release is included. (The unreleased feat(model): Model.assign_coords — reassign coordinates on an existing model #955 note was amended.)