-
Notifications
You must be signed in to change notification settings - Fork 0
2026 workplan #2
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
Open
nick-gorman
wants to merge
3
commits into
main
Choose a base branch
from
2026-workplan
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+52
−0
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,52 @@ | ||||||
| # 2026 Work plan summary | ||||||
|
|
||||||
| This document summarises the OpenISP work plan for 2026. The original draft is a synthesis of the early 2026 | ||||||
| planning workshops held in Melbourne. | ||||||
|
|
||||||
| The general approach discussed was to: | ||||||
|
|
||||||
| - Postpone introducing backwards compatibility for old ISP versions and focus on updating to support the 2026. | ||||||
| - Implement data validation processes to support flexible inputs and improve software robustness. | ||||||
| - Then proceed incrementally adding modeling methodology features, based on priority order.* | ||||||
|
|
||||||
| *Note, this is an explicit shift away from the `MVP` framing discussed previously. Rather than trying to strictly | ||||||
| define an MVP to work towards (which is use case dependent), features will be sorted into a rough priority order and | ||||||
| released incrementally as completed. | ||||||
|
|
||||||
| The key tasks and priorities are outlined in a series of tranches, with each tranche indicating a set of tasks with | ||||||
| roughly equal priority which can be implemented (mostly) in parallel. | ||||||
|
|
||||||
| ## Tranche 1 - 2026 ISP update and data validation: | ||||||
|
|
||||||
| - Review translater output (ISPyPSA tables format) | ||||||
| - Update translater to work 2026 ISP IASR and implement changes flowing from review | ||||||
| - Implement data validation for ISPyPSA tables and translator tables | ||||||
| - Update the trace parser to work with 2026 ISP traces | ||||||
| - Update ISPyPSA to support PyPSA 1.0 and lastest Python 3.10-14 | ||||||
|
|
||||||
| ## Tranche 2+ (to be broken up with prioritisation): | ||||||
|
|
||||||
| - Generators | ||||||
| - Hydro | ||||||
| - using inflows and general structure of AEMO methods | ||||||
| - Finalise utility storage | ||||||
| - CER storage | ||||||
| - Outages (deratings for capacity outlook) | ||||||
| - Seasonal ratings | ||||||
| - Renewable energy entrants outside REZs (if minimal work required) | ||||||
| - Reserves | ||||||
| - Hydrogen | ||||||
|
|
||||||
| - Network Network | ||||||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
| - Seasonal ratings | ||||||
| - Network losses | ||||||
|
|
||||||
| - Policy constraints | ||||||
| - Carbon budget | ||||||
| - Renewable energy target | ||||||
| - Storage targets_ | ||||||
|
|
||||||
| - Temporal resolution reduction | ||||||
| - sampled chronology | ||||||
| - (alternative is to do representative year for an investment period??) | ||||||
|
|
||||||
File renamed without changes.
File renamed without changes.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Just checking - is this meant to be
templaterhere rather thantranslater?