Document the expansion path, and the portfolio's gaps - #21
Open
thomaschristopherking wants to merge 1 commit into
Open
Document the expansion path, and the portfolio's gaps#21thomaschristopherking wants to merge 1 commit into
thomaschristopherking wants to merge 1 commit into
Conversation
The four parts below this one added a capacity-expansion destination, and no document told a user how to run it or what it leaves behind. The AEMO case study had a dispatch path and a Sienna path, and the gap analysis covered dispatch fidelity alone. The case study gains the expansion path beside the other two, and the gap analysis gains seven entries for what the portfolio leaves out. Documentation only. No code changes. Signed-off-by: Thomas C. King <thomas.k@transitionzero.org>
|
Warning Review limit reachedNext included review available in 59 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (6)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
thomaschristopherking
added this pull request to stack #23
September 11, 2026 09:56
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.
TL;DR
The four parts below this one added a capacity-expansion destination, and no document told a
user how to run it or what it leaves behind: the AEMO case study had a dispatch path and a
Sienna path, and the gap analysis covered dispatch fidelity alone. This adds the expansion path
to the case study and seven portfolio entries to the gap analysis.
Fifth and last of five for transition-zero/tz-infra-interop#116,
stacked on #20. Documentation only, no code changes.
Files to review (6, +245 / -34):
docs/case_studies/aemo-isp-2024.md(start here)### The expansion path, beside the dispatch and Sienna paths.docs/translation_mappings/plexos-to-sienna-gap-analysis.mddocs/translation_mappings/translation-from-plexos-to-sienna.mdWhy
A user running the AEMO ISP through the new pipeline has no way to know the command, what it
writes, or which parts of their plan do not survive. The gap analysis is where they look for the
second question, and it described only the dispatch translation.
Reviewer notes
durations, per the repository rule about unreproducible measurements.
Tests
No code changes. 638 scenarios still pass, and all 17 pre-commit hooks.
Open workspace in Conductor