We offer several data loaders (amiris, oeds, pypsa, maybe in the future entsoe #813) next to the csv loader. When loading the data, we often need to assume defaults for values that do not exist in the source data and create configs dynamically. As this is only done in the code during run time, it is often not very transparent what values were actually selected and used in the simulation, as @reinecfi pointed out here for the potential new entsoe loader.
It would be great to have a full export of the scenario setup, in addition to the existing outputs of the simulation results.
This could be for example in our common csv-loader format, so that
- Configuration files (e.g. units or grid data) can be reviewed and adjusted
- Time series input data (e.g. forecasts, fuel cost assumptions, unit availability, ...) can be reviewed and adjusted
- Simulation can be re-run with the csv-loader
We offer several data loaders (amiris, oeds, pypsa, maybe in the future entsoe #813) next to the csv loader. When loading the data, we often need to assume defaults for values that do not exist in the source data and create configs dynamically. As this is only done in the code during run time, it is often not very transparent what values were actually selected and used in the simulation, as @reinecfi pointed out here for the potential new entsoe loader.
It would be great to have a full export of the scenario setup, in addition to the existing outputs of the simulation results.
This could be for example in our common csv-loader format, so that