Call graphs from eesyplan methods

[paulapreuss]

Goal

• Save copy of datapackage to database to create enerysystem without having to build datapackage from scratch
• Call graphs directly from eesyplan methods instead of openplan code

Notes:

• Added datapackage field to Scenario instead of Simulation to not have to worry about if a simulation object already exists
• Added argument store_database_record to to_jsonified_datapackage method instead of calling again with n_timestamps=0 to only build the datapackage once and strip the timeseries instead of building twice (once for simulation and once for db)
• EnergySystem can be rebuilt from db datapackage after repopulating with Timeseries values
• WIP state: Sankey diagram now works like this (renders) but does not display the correct values yet (probably something is different in the logic of rebuilding the flows?)

[Bachibouzouk]

Thanks for tackling this @paulapreuss - I think it looks nice. However I would wait that the PR oemof/oemof-datapackage#4 is merged (or check that with this version of oemof-datapackage it still works as expected)

[Bachibouzouk]

I am wondering whether we should add this as a method of the Scenario model. However this might add confusion if there are too many methods to get a datapackage or a jsonified datapackage from the Scenario. Because then one has to be sure where the datapackages comes from, from the DB or generated on the fly. And what if the user changed some components without resimulating and would like to export this as a datapackage.

If we decide to go for the method I would

rebuilt_dp = scenario.rebuilt_datapackage() and this method should return an error message if the datapackage attribute wasn't present (or it could generate it on the fly)

[paulapreuss]

You're right, I think it makes a lot of sense to add this as a Scenario method instead.

[Bachibouzouk]

In the future we should then get all this from the results datapackage I guess

[Bachibouzouk]

I updated the EZP simulation server with pip install "oemof-datapackage @ git+https://github.com/oemof/oemof-datapackage.git@fix/multilevel-columns-resources"

[paulapreuss]

Not sure about why, but now with these changes I get an CastError, seemingly about the order of the timeseries names

Traceback (most recent call last):
  File "C:\Users\paula.preuss\AppData\Local\miniforge3\envs\open-plan-5.2\Lib\site-packages\oemof\datapackage\datapackage\reading.py", line 185, in deserialize_energy_system       
    r.read()
  File "C:\Users\paula.preuss\AppData\Local\miniforge3\envs\open-plan-5.2\Lib\site-packages\datapackage\resource.py", line 383, in read
    return self.__get_table().read(
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\paula.preuss\AppData\Local\miniforge3\envs\open-plan-5.2\Lib\site-packages\tableschema\table.py", line 353, in read
    for count, row in enumerate(rows, start=1):
                      ^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\paula.preuss\AppData\Local\miniforge3\envs\open-plan-5.2\Lib\site-packages\tableschema\table.py", line 231, in iter
    exc_handler(
  File "C:\Users\paula.preuss\AppData\Local\miniforge3\envs\open-plan-5.2\Lib\site-packages\tableschema\helpers.py", line 90, in default_exc_handler
    raise exc
datapackage.exceptions.CastError: Table headers (['timeindex', 'PV - Halle 18_migration', 'Wind - Karholz_migration', 'Wind - Winnberg 03_migration', 'Wind - Winnberg 04_migration'
, 'Industriestandort_migration', 'PV - Erweiterung (Wasser)_migration']) don't match schema field names (['timeindex', 'Industriestandort_migration', 'PV - Halle 18_migration', 'PV - Erweiterung (Wasser)_migration', 'Wind - Karholz_migration', 'Wind - Winnberg 04_migration', 'Wind - Winnberg 03_migration']) in row 2

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\paula.preuss\AppData\Local\miniforge3\envs\open-plan-5.2\Lib\site-packages\django\core\handlers\exception.py", line 55, in inner
    response = get_response(request)
               ^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\paula.preuss\AppData\Local\miniforge3\envs\open-plan-5.2\Lib\site-packages\django\core\handlers\base.py", line 197, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\paula.preuss\AppData\Local\miniforge3\envs\open-plan-5.2\Lib\site-packages\django\contrib\auth\decorators.py", line 59, in _view_wrapper
    return view_func(request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\paula.preuss\AppData\Local\miniforge3\envs\open-plan-5.2\Lib\site-packages\django\views\decorators\http.py", line 64, in inner
    return func(request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\paula.preuss\PycharmProjects\gui\app\projects\views.py", line 1211, in scenario_review
    parse_ezp_results(simulation, simulation.results)
  File "C:\Users\paula.preuss\PycharmProjects\gui\app\projects\requests.py", line 170, in parse_ezp_results
    es = create_energy_system_from_dp(dp_path)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\paula.preuss\AppData\Local\miniforge3\envs\open-plan-5.2\Lib\site-packages\oemof\eesyplan\datapackage\energy_system.py", line 16, in create_energy_system_from_dp  
    return EnergySystem.from_datapackage(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\paula.preuss\AppData\Local\miniforge3\envs\open-plan-5.2\Lib\site-packages\oemof\datapackage\datapackage\reading.py", line 187, in deserialize_energy_system       
    raise dp.exceptions.CastError(
datapackage.exceptions.CastError:
Metadata structure of resource `profiles` does not match data structure. Check the column names, types and their order.