Skip to content

Handle non-chronological results #4

@GordStephen

Description

@GordStephen

Results that report non-chronological time periods (most notably MT blocks) currently break the solution processor. First noted by @craigl33.

  • Immediate workaround is to not save out MT/PASA properties from PLEXOS
  • Short term fix would be for the package to just ignore those timescales (instead of crashing)
  • Long term fix would be for the package to store them properly (how important is this in practice?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions