Skip to content

Reconsider output format in the context of divisible assets #1042

@tsmbland

Description

@tsmbland

Asset division currently produces a potentially large number of assets with small capacities, which are otherwise treated just like fully-fledged assets and reported in full in the output data.

Most likely most users won't care about tracking the capacities and flows of every single unit, so reporting all this in full just makes life harder for users. From a user's perspective, I think the important things are:

  • when investment/decommissioning decisions were made, and how much capacity was added/removed
  • total capacities of each process in each region/year
  • flows over these total capacities

I think we may need to rethink the output file format to make life easy for users without presenting unnecessary data (by all means keeping the existing format as a debug feature), or otherwise give very clear instructions about how to analyse the existing files.

I don't think we should prioritise this, as other work related to divisible assets may lend itself to a solution for this, but something to bear in mind.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    📋 Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions