Skip to content

Build .model.transport on .model.material for CircEUlar #296

Open
@khaeru

Description

@khaeru

@r-aneeque @macflo8 and I discussed on 2025-02-14.

  • For CircEUlar, some scenarios are required for research (exact RQs TBD) focused on the material flows associated with additions to/removals from the stock of (road, passenger) light-duty vehicles.
  • There are multiple ways to implement this:
    1. A "soft-link" such as exists between STURM and MESSAGEix-Materials (hereinafter Mix-M). In this, the STURM model is run separately, and some of its outputs are used by code in .model.material to parametrize a representation in Mix-M.
    2. A "hard-link" in which both MESSAGEix-Transport (Mix-T) and Mix-M detail are added to a base scenario.
  • We decided that (2) seems a better alternative at the moment. The

In order to implement this, some steps:

  1. @khaeru to read and digest the .model.material documentation, with guidance from @macflo8.
  2. @khaeru and @r-aneeque to design a method for adapting data received from collaborators at NTNU (LDVs_mat_comp.xlsx, SharePoint/internal) to the structure required for input parameter(s) for .model.material
  3. @khaeru to adapt existing code in .model.transport to perform (2), if so configured.
  4. @khaeru to construct a workflow that builds Mix-T with these added details/parameter values on top of an existing Mix-M scenario, to be identified by @macflo8.

Work will proceed in 1 or more branches/PRs; this issue is for a central point of reference and to collect information.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhNew features or functionalitymaterialMESSAGEix-Materials variantp:CircEUlarCircEUlar projecttransportMESSAGEix-Transport variant or transport in the base model

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions