Features/integrate esys

[MaGering]

Resolves #3

With this PR it is possible to build, optimize and postprocess an energy system with oemof-B3 based scripts and tools in digipipe.
optimizing and postprocessing serves as a test for the correct set up of the energy system and can be either removed or used as tests in digiplan.

Before merging into dev-branch, please make sure that

• if data flow was adjusted: data pipeline run finishes successfully.
• new and adjusted code is formated using black and isort. -> After Features/add pre commit  #64 is merged
• the CHANGELOG.rst was updated.
• the docs were updated. -> ESYS.md file

[nesnoj]

Log

• raw data stored in /store/datasets/esys_raw/ (dummy data as input for now)
  • data sources are defined and name mapping takes place in config, e.g. in /store/appdata/esys/config.yml, e.g.

datasets:
  wind_feedin:
    file: "timeseries.csv"
    column: "xxx"
    name_esys: "abw-wind-"

• preprocessed in /store/appdata/esys/ with some subdir such as .TEMPLATE with esys template files (which is committed)

[MaGering]

Please rename raw/esys_costs_efficiencies to raw/dea_costs_efficiencies as the dir name in raw should start with the source. If there're multiple sources, we might just name it raw/costs_efficiencies. Cheers

Thanks for the hint. Done with commit 91b3c03.

And I tend to rename the dir snakemake_rules to just rules

For now, I would keep the name because it is named the same as the directory in oemof-B3. If for another repo should be built on the same structure, the mapping of what comes from what would be easier.

[MaGering]

Further notes/tasks for the future:

* Refactor structure for neat integration (best fit into pipeline's structure **VS** reusability in future projects)

* Merge/check for redundant functions from pipeline and esys; functions from esys which could be useful in the entire pipeline (e.g. timing)

True. I created an issue for this: #69

[nesnoj]

Hey @MaGering!
snakemake -j1 make_esys_appdata works out perfectly.
I adjusted some small things, e.g. integrated the esys docs into the mail docs, see commits above.
Merge if you dare! :)