Workflow with ESDL

[clizbe]

Discussed in #56

^{Originally posted by datejada August 22, 2023}
I can foresee three data files in the model that need to be considered as inputs and outputs for the model; see Figure below.

1. ESDL files (.esdl): These files will contain the available information that can be stored in this format. Generally speaking, it is capacities, efficiencies, investment costs, operational costs, and commission and decommissions dates.
2. Complementary information files (.csv?): Here we have two categories

• Extra information for assets: Information not available in the ESDL format, e.g., unit-commitment parameters.
• Configuration parameters: setting parameters such as the years to run, type of simulation (only dispatch or with investment), etc.

3. Profiles database (.sqllite?): This file/DB will contain a large amount of input data (e.g., availability profiles) and results (e.g., production profiles for each asset).

Maybe we need more types of files; I'm not sure. In addition, the pre-processing and post-processing can be either in Julia or Python; these steps should be able to link the information in all the data sources with the optimization model.

I hope these comments and general overview help in the discussion for next week's meeting to talk about the design of the model.

[clizbe]

This is now containted within the Epic: ESDL to GML + CSV