Implementation of CHP in scenario manager

[TUM-Doepfert]

Is your implementation related to a bug report or feature request? Please describe or link here.
A clear and concise description of what the problem was.

Describe the designed solution
Implement a chp plant in the scenario manager.

Describe alternatives you've considered
Not including it was ruled out

Implementation details
See necessary changes in config file below

################################ combined heat and power settings ####################################
################################ coming soon

"chp_fraction": 0 # fraction of prosumers with heat pumps

"chp_sizing_power": 1 # thermal power 1 = peak heating demand

"chp_heat_elec_ratio": 2 # P_th/P_el

"chp_efficiency": 0.9

"chp_fuel_cost": 0.08 €/kWh_th

"chp_capacity": [2, 3] # integrated thermal storage capacity in hours of
# maximum power, which is the ceiled maximum heat demand from file

"chp_soc_init": 0.1 # initial soc of the storage (0-1)

"chp_controller": "heat_led" # chp control strategy
# "heat_led" - chp's focus is to cover the heat demand
# "elec_led" - chp's focus is to generate power when profitable

"chp_fcast": "nn" # heating demand forecasting technique
# "perfect" - perfect
# "nn" - neural network based on the included weather data
# "mr" - multiple regression based on the included weather data

"chp_fcast_retraining_period": 86400 # models should be periodically retrained based on new data
# how many seconds between retraining periods?

"chp_fcast_update_period": 3600 # forecasts are periodically updated and saved to file where the
# most current forecast can be retrieved by model predictive controllers
# and market agents. How many seconds between updates?

Also:

• "perfect" for hp forecast