MUSE XI engagement

[alexdewar]

MUSE XI engagement

I've created this page as a place to make notes about the plans for the next MUSE engagement (the 11th!). We can edit it during our meeting. Once we've settled on the issues to be tackled for this engagement and the paperwork is complete, we can close it if we want. Anyone can leave comments.

I've created two new milestones for this engagement: v0.2.0 and v0.3.0. These will correspond to new releases of MUSE 2.0 (published on GitHub and crates.io).

We need to come up with a plan for what issues will be tackled for each of the milestones (with priorities) and then we can add due dates to them. I've already populated the milestones with some open issues, some of which we will definitely want to do. Some of the others are just possible tasks for the engagement -- we can remove any that we don't want. There will also likely be other tasks that we come up that we wish to add. Probably most of these extra tasks should go in the v0.3.0 milestone, unless they're a priority, as I'd like to publish a basic version of the code before we build on top of it.

v0.2.0 milestone: Minimum viable product

The objective for this milestone is to produce a minimum viable product that can be released, i.e. which runs a basic version of the model and produces results (#303). For this, we will need to implement agent investment (#304) and fix various small bugs. We should also add CI workflows to publish the code on release (#128, #129).

Some of the issues for this milestone have already been completed by @tsmbland. The remainder can be found here.

v0.3.0 milestone: ...everything else

For this milestone I've added things which are either not essential for the MVP or are possible features from the issue backlog. We will want to whittle this down and probably add some more tasks. The current list of issues for this milestone is available here

I've tagged issues that we may or may not want to do as "questions", because we'll need input from @ahawkes on this.

Extra possible features:

• Save objective value of dispatch optimisation with output data #428
• Add commodity trade parameters #509
• Allow for adding process flow share constraints #123
• Allow for adding process investment constraints #124
• Allow for adding commodity constraints #143
• Add support for flexible assets #360

Input/validation:

• Allow for setting both upper and lower bounds for process availabilities #363
• Warn users about assets which will not be commissioned during the simulation #400
• Prevent users from supplying inf and NaN in CSV files #426
• For every commodity of "SVD" type, there must be at least one asset in the base year that can produce the commodity for every region where the SVD>0 for the base year. #169

Other business

• We should finish up PR documentation changes March 2025 #466 and get it merged.
• How much time is @tsmbland likely to be able to allocate to MUSE 2.0 for this engagement?

[alexdewar]

Notes from meeting

• Forbid commodity loops? Or leave to user?
• Make complex example to test out MVP
• Add regression tests
• How to deal with multiple outputs? If hard, should go in v0.3.0
• Must have: Open issue for COMPETE vs CAPTIVE options for demand (net present value poss better cf lcox for COMPETE)
• Must have: NPV
• Trade: important
• Should have: investment constraints: to do with capacity? optional
• Could have: commodity constraints
• Should have: document output format (define schema?)
• Should have: List of checks for input validation (also: audit code to check what validation is being done)
• Output TOML file: diagnostics (how long for each section of algo), program metadata, objective value (Save objective value of dispatch optimisation with output data #428), what decisions were made and why, information about processes not selected (could be an extra verbose option)
• Must have: Allow for setting both upper and lower bounds for process availabilities #363 (also at different temporal scales)
• Could have: For every commodity of "SVD" type, there must be at least one asset in the base year that can produce the commodity for every region where the SVD>0 for the base year. #169, Warn users about assets which will not be commissioned during the simulation #400
• @tsmbland to give half FTE for engagement
• Schedule meetings every two weeks

[alexdewar]

Agenda for meeting 13/5/2025

• Proposal document. Any questions?
• Progress in last sprint
• Plans for this sprint (NB: @tsmbland is mostly away)
• Questions on documentation changes March 2025 #466

[alexdewar]

This engagement is now finished. Closing.