Collect pieces for SSP 2024/ScenarioMIP workflows

[khaeru]

As discussed at today's MESSAGE team meeting.

We want to, at some point, bring together all the improvements and new code used in the SSP/ScenarioMIP workflows. This issue is to:

1. Identify what and where those pieces are, how they are used (in what order), etc.
2. Decide where they should eventually ‘land’ within message-ix-models or other repos.
3. Track as they are associated with PRs, either:
   • If atomic and separable, directly into main, or
   • If they need extensive clean-up that is not yet scheduled, into a ssp-dev branch: #235.

Pieces

General/other

• 233 by @OFR-IIASA (@macflo8 made a similar change)

• Lots of code in iiasa/message_single_country@SSP_Dev_2023
  • TODO List or outline what is included.
  • @OFR-IIASA has reworked some of this code to use message_ix_models.Context objects for settings handling, which should ease future integration with message-ix-models.
• Lots of code in iiasa/message_data@ssp_dev
  • TODO List or outline what is included.
• iiasa/message_ix@ssp_dev
  • Includes (is based on) iiasa/message_ix#726
  • Certain CPLEX settings
  • Work from @GamzeUnlu95 on MESSAGE-MACRO iteration.
  • TODO Confirm: is this iiasa/message_ix#430, or something else?

Direct air capture (DAC)

• Code in @ywpratama branch https://github.com/ywpratama/message_ix/tree/add_dac_disposal_split (this should eventually land in message-ix-models, rather than message_ix)

Materials

• Code on @macflo8's branch https://github.com/macflo8/message-ix-models/tree/ssp_dev-W35

Techno-economic parameters (@measrainsey)

• 206

• 221

• 227

• 222

Water/nexus

• 223

• 236

Things to do

• Leave a comment below or edit the description to add further details.
  • Please try not to add so much that the overall list is not readable; rather add full description at the respective issue/PR, and put a ~1-sentence summary.
  • These can include future plans/intentions for next steps.
• Open a draft PR for any branch with associated code.
  • This PR may not ever be merged, but makes it much easier to understand and communicate about the changes on a branch.
• or, Add to #235.
• Ask @glatterf42 @khaeru if unsure about what to do.

[adrivinca]

Thanks for this, I started a branch wat_SSP_upd1 that takes a bit from the older water_SSP_update (soon obsolete) but that is meant to be for few incremental fixes, including tests when possible

[khaeru]

@adrivinca I updated the description to replace “Another small change by @adrivinca that will be included in a small PR” with #236 —assuming that's the thing you referred to on Thursday. Please correct if I'm wrong there.

[measrainsey]

Hi! Thank you for documenting this process.

I have a question: I have a few scripts (that are currently on a personal repo) that have my workflow of the modifications I made to certain scenarios for the ScenarioMIP submission. Nothing complicated, just small changes to diffusion constraints and share constraints in the transport, residential + commercial, and industry sectors. I imagine it would be best to migrate these scripts to a team-accessible location.

Where would be the best place to move my scripts over? Should they be housed here on message-ix-models (for example, in message_ix_models.project.ssp)?

[khaeru]

@measrainsey yes, that would be wonderful, thank you!

I would suggest:

1. Create a branch like ssp-dev/mm or similar.
2. Create a directory like message_ix_models/project/ssp/script/.
3. Commit files (warts and all, no clean-up needed) into that directory.
4. Open a draft PR into the branch ssp-dev associated with #235.

Once others to do the same, we can check for discrepancies, and figure out an appropriate way to bring the pieces together.