Repository navigation
Template missing rez ids #151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
c4c1d23
add non-rez geographies N0 and V0 explicitly to renewable_energy_zone…
EllieKallmier 15afff9
exclude N0/V0 non-rez geos from missing initial transmission limits l…
EllieKallmier 8bca1ce
add iasr table replacement: Q8a/b/c -> Q8 in ECAA summary table 'REZ …
EllieKallmier 429295c
move _NON_REZ_GEOGRAPHIES to mappings, add logging
EllieKallmier 2cfdab7
remove stale comments
EllieKallmier File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably a silly question, but is the reason that this works because the resource traces for the assocaited units are all mapped via their IASR ID, and while the a, b, and c areas are resource quality areas, they don't actuall get used for mapping to resource traces?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not at all, and yep - it's IASR ID based mapping for the resource traces (pretty much - I think there are some typos/slightly differently-named traces but the new config setup in the trace-parser also has an 'iasr_aliases' field to cover those cases too).
It is pretty similar for the new entrants too - not exactly the same ordering of name/id components but the traces are named like 'REZ_Q8a_Darling_Downs_SAT...', for the corresponding templated new entrant
'name'='Q8a_SAT_Darling Downs'. I thought about alternatives, but they'd have flow-on effects that I didn't feel made them worth it (yet, at least). Still leaving the related issue open to come back to cause I don't think it's 100% perfectly resolved, but this works for now I think...