Adding a timeseries for a parameter¶
Sometimes you may want to define a parameter not as a scalar value but as a time series. This can for example happen for efficiencies (heat pump COP during the seasons), energy prices (currently only hourly resolution), or the state of charge (for example if you want to achieve a certain stage of charge of an FCEV at a certain point of time).
You can define a scalar as a time series in the csv input files (not applicable for energyConsumption.csv
),
by replacing the scalar value with following dictionary:
{‘file_name’: ‘your_file_name.csv’, ‘header’: ‘your_header’, ‘unit’: ‘your_unit’}
The feature was tested for following parameters:
energy_price
feedin_tariff
dispatch_price
efficiency
You can see an implemented example here, where the heat pump has a time-dependent efficiency:
unit |
heat_pump |
|
---|---|---|
age_installed |
year |
0 |
development_costs |
currency |
0 |
specific_costs |
currency/kW |
7000 |
efficiency |
factor |
{‘file_name’: ‘cops_eers_test.csv’, ‘header’: ‘no_unit’, ‘unit’: ‘NA’} |
inflow_direction |
str |
Electricity |
installedCap |
kW |
0 |
label |
str |
Heat pump |
lifetime |
year |
20 |
specific_costs_om |
currency/kW/year |
0 |
dispatch_price |
currency/kWh |
0 |
optimizeCap |
bool |
True |
outflow_direction |
str |
Heat |
energyVector |
str |
Electricity |
type_oemof |
str |
transformer |
unit |
str |
kW |
The feature is tested with benchmark test test_benchmark_feature_parameters_as_timeseries()
.
Example input files, where at least one parameter is defined as a time series, can be found here:
First example: Defines the
energy_price
(file) of an energy provider as a time seriesSecond example: Defines the
energy_price
(file) of an energy provider and the efficiency of a diesel generator (file) as a time series.