From af53a29753fcbbc21da83ae17b38841465de5468 Mon Sep 17 00:00:00 2001 From: nick-gorman Date: Tue, 3 Feb 2026 13:36:43 +1100 Subject: [PATCH 1/5] archive old docs --- architecture.md => archived/architecture.md | 0 work-plan-ispypsa.md => archived/work-plan-ispypsa.md | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename architecture.md => archived/architecture.md (100%) rename work-plan-ispypsa.md => archived/work-plan-ispypsa.md (100%) diff --git a/architecture.md b/archived/architecture.md similarity index 100% rename from architecture.md rename to archived/architecture.md diff --git a/work-plan-ispypsa.md b/archived/work-plan-ispypsa.md similarity index 100% rename from work-plan-ispypsa.md rename to archived/work-plan-ispypsa.md From e7e9447db01c7ab81f748f9f7dfb27f242e95e33 Mon Sep 17 00:00:00 2001 From: nick-gorman Date: Tue, 3 Feb 2026 16:48:36 +1100 Subject: [PATCH 2/5] draft 2026 workplan --- 2026-workplan.md | 48 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 48 insertions(+) create mode 100644 2026-workplan.md diff --git a/2026-workplan.md b/2026-workplan.md new file mode 100644 index 0000000..d851cf5 --- /dev/null +++ b/2026-workplan.md @@ -0,0 +1,48 @@ +# 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. + +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 + - 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??) + From 306f17811f518ebc4aef6123107b93319844c360 Mon Sep 17 00:00:00 2001 From: nick-gorman Date: Tue, 3 Feb 2026 16:58:41 +1100 Subject: [PATCH 3/5] clarify shift from MVP framing --- 2026-workplan.md | 40 ++++++++++++++++++++++------------------ 1 file changed, 22 insertions(+), 18 deletions(-) diff --git a/2026-workplan.md b/2026-workplan.md index d851cf5..190ce6b 100644 --- a/2026-workplan.md +++ b/2026-workplan.md @@ -1,13 +1,17 @@ # 2026 Work plan summary -This document summarises the OpenISP work plan for 2026. The original draft is a synthesis of the early 2026 +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. +- 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. @@ -23,26 +27,26 @@ roughly equal priority which can be implemented (mostly) in parallel. ## 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 + - 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 - - Seasonal ratings - - Network losses + - Seasonal ratings + - Network losses - Policy constraints - - Carbon budget - - Renewable energy target - - Storage targets_ + - Carbon budget + - Renewable energy target + - Storage targets_ - Temporal resolution reduction - - sampled chronology - - (alternative is to do representative year for an investment period??) + - sampled chronology + - (alternative is to do representative year for an investment period??) From 9a0f5c4c78b7691a9b9edff55f30405de4605fc0 Mon Sep 17 00:00:00 2001 From: nick-gorman <40549624+nick-gorman@users.noreply.github.com> Date: Thu, 26 Feb 2026 11:50:52 +1100 Subject: [PATCH 4/5] Update 2026-workplan.md Co-authored-by: EllieKallmier <61219730+EllieKallmier@users.noreply.github.com> --- 2026-workplan.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2026-workplan.md b/2026-workplan.md index 190ce6b..8e28375 100644 --- a/2026-workplan.md +++ b/2026-workplan.md @@ -37,7 +37,7 @@ roughly equal priority which can be implemented (mostly) in parallel. - Reserves - Hydrogen -- Network Network +- Network - Seasonal ratings - Network losses From 01251de3e0d63d0b335fc8d8dc9566d5c8e0b526 Mon Sep 17 00:00:00 2001 From: nick-gorman Date: Thu, 26 Feb 2026 12:04:40 +1100 Subject: [PATCH 5/5] fix typos in 2026 workplan --- 2026-workplan.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/2026-workplan.md b/2026-workplan.md index 190ce6b..6597cc8 100644 --- a/2026-workplan.md +++ b/2026-workplan.md @@ -18,11 +18,11 @@ 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 +- Review templater output (ISPyPSA tables format) +- Update templater to work with 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 +- Update ISPyPSA to support PyPSA 1.0 and latest Python 3.10-14 ## Tranche 2+ (to be broken up with prioritisation): @@ -37,14 +37,14 @@ roughly equal priority which can be implemented (mostly) in parallel. - Reserves - Hydrogen -- Network Network +- Network - Seasonal ratings - Network losses - Policy constraints - Carbon budget - Renewable energy target - - Storage targets_ + - Storage targets - Temporal resolution reduction - sampled chronology