Skip to content

Add a data structure able to hold all input/output data #65

@danielolsen

Description

@danielolsen

🚀

  • Is your feature request essential for your project?

Not essential to launch and extract, and preliminary analyses can use the features which are created to address #47 (i.e. #49, #50, #51), but eventually we will a single user interface, like the Scenario object of PowerSimData.

Describe the workflow you want to enable

I wish there was an object from which I could obtain all input and output data related to a Switch optimization. This includes:

  • Grid data
    • the existing Grid
    • allowable expansion candidates. These are currently implemented as nearly-identical to the plant and branch tables in the existing Grid, but this will soon change.
    • the final Grid (initial + expansion)
    • any intermediate Grids (for optimization with multiple investment periods)
  • Profile data
    • input profiles (corresponding to the existing Grid)
    • final profiles (after expansion)
    • any intermediate profiles (for optimization with multiple investment periods)
  • other Switch inputs

Describe your proposed implementation

Initially, we can instantiate an instance of this object from a folder containing all relative files, to aid in getting something stood up quickly. Eventually, we may want to move to an alternate approach, similar to the Scenario framework, where we reduce duplication of identical information (e.g. normalized profiles) by having this information in a common location.

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions