Input data#

User guide: Home

Contents#

Introduction
Data
Electric system only modelling
Multi-energy system modelling

Introduction#

The Oogeso input is an EnergySytemData object, that may be constructed programmatically, or specified in a YAML. This object or yaml file specifies all elements (nodes, edges, devices), how they are connected (network topology) and parameters for each element.

The input data can be specified in a YAML file with the following structure:

parameters:
    <param>: <value>
profiles:
    - id: timeseries1
      data: <list of values>
      data_nowcast: <list of values>
    ...
carriers:
    - id: el
      <param>: <value>
    - id: heat
      <param>: <value>
    ...
devices:
    - id: device1
      <param>: <value>
    ...
nodes:
    - id: node1
      <param>: <value>    
    - id: node2
    ...
edges:
    - id: edge1
      <param>: <value>
    - id: edge2
    ...

The notation <param>: <value> above indicates a set of parameter-value pairs. The relevant parameters are described in the following:

Data#

General parameters (`parameters`)#

parameter	type	description
time_delta_minutes	int	minutes per timestep
planning_horizon	int	number of timesteps in each rolling optimisation
optimisation_timesteps	int	number of timesteps between each optimisation
forecast_timesteps	int	number of timesteps beyond which forecast (instead of nowcast) profile is used
emission_intensity_max	float	maximum allowed emission intensity (kgCO2/Sm3oe), -1=no limit
emission_rate_max	float	maximum allowed emission rate (kgCO2/hour), -1=no limit
objective	string	name of objective function to use (penalty, exportRevenue, costs)
piecewise_repn	string	method for impelementation of peicewise linear constraints in pyomo
optimisaion_return_data	list	(optional) list of variables to return from simulation

Time-series profiles (`profiles`)#

Multiple time-series profiles can be specified. For each profile there are two separate time-series: One representing forecasted values for planning ahead, and one representing the “nowcast” or an updated forecast relevant for the near-real-time decisions.

Note that the actual real-time values (e.g. of power demand or of available wind power) is not used in the simulation, as it only concerns up to near real-time operational planning. To address real-time deviations and balancing, reserve power and backup capacity is required.

Profiles may be specified in the YAML file as indicated above, or they may be read from separate files.

Note regarding the use of profiles

The max/min flow (\(Q\)) constraint (e.g. electric power output from a wind turbine, or power demand by a load) is generally written on the form \(Q_{min}\cdot \text{profile}(t) \le Q(t) \le Q_{max}\cdot \text{profile}(t)\), where \(Q(t)\) is the flow being constrained. That means you can choose where to put the units:

flow_max gives the absolute value (e.g. MW) and the profile is given in relative units (typically in the range 0-1)
flow_max = 1 and the profile is given in absolute units (e.g. MW)

All examples use the first alternative.

Energy carriers (`carriers`)#

parameter	type	description
id	string	carrier type (el, heat, hydrogen, gas, oil, water, wellstream)

Other data differs for the different carrier types.

Network nodes (`nodes`)#

parameter	type	description
id	string	unique node identifier

(No additional data needed)

Network edges (`edges`)#

This consists a set of edges with a set of parameters for each edge that depends on the edge type. These are as follows.

Common parameters for all edges:

parameter	type	description
id	string	unique edge identifier
carrier	string	edge carrier type (el, heat, gas, oil, wellstream, water, hydrogen)
node_from	string	identifier of “from” node
node_to	string	identifier of “from” node
include	int	wheter to include edge or not (1=yes, 0=no)
length_km	float	distance (km)
flow_max	float	(optional) maximum power flow allowed (MW or Sm3/s)

Devices (`devices`)#

This consists a set of devices with a set of parameters for each device that depends on the device type.

Common parameters for all device types:

parameter	type	default	description
id	string		unique device identifier
node_id	string		identifier of node where it is connected
name	string	“”	display name
model	string		name of device model type (see below)
include	bool	True	wether to include the node
profile	string	None	name of time series profile to use for scaling (flow_max)
flow_max	float	None	maximum flow allowed (MW or Sm3/s)
flow_min	float	None	minimum flow allowed (MW or Sm3/s)
max_ramp_up	float	None	maximum ramping (% of flow_max per min)
max_ramp_down	float	None	maximum ramping (% of flow_max per min)
start_stop	StartStopData	None	see below
reserve_factor	float	None	how much of electric power counts towards the reserve (1=all, 0=none)
op_cost	float	None	Operating cost
penalty_function	tuple	None	flow vs penalty function (piecewise linear). A tuple containing a list of x values and a list of y values `([x1,x2,..],[y1,y2,...])`

In addition to these parameters there are parameters that depend on the device model. These are specified further down.

Start and stop data (`StartStopData`)#

Start-stop data may be provided if the device is modelled with start/stop constraints and or penalties.

parameter	type	default	description
is_on_init	bool	False	device is initially on (True) or off (False)
penalty_start	float	0	startup penalty (cost)
penalty_stop	float	0	shutdown penalty (cost)
delay_start_minutes	int	0	minutes delay from activation to being online
minimum_time_on_minutes	int	0	time device must be on once started (min)
minimum_time_off_minutes	int	0	time device must be off once stopped (min)

Electric system only modelling#

A common use case is to use Oogeso to model only the electricity network. Additional input data needed in this case is shown below.

Carriers (electricity)#

`id: el`#

parameter	type	description
powerflow_method	str	“transport” or “dc_pf”
reference_node	str	id of node used as reference for voltage angles (with dc_pf method)
el_reserve_margin	float	required globally spinning reserve (MW).
el_backup_margin	float	(optional) required backup margin in case of genertor failure (MW)
reserve_storage_minutes	int	how long (minutes) stored energy must be sustained to count as reserve

Edges (electric)#

The table below shows the electricity line parameters, used in addition to the generic edge parameters.

`carrier: el`#

parameter	type	description
reactance	float	reactance (ohm/km) (used only with method “dc_pf”)
resistance	float	resistance (ohm/km) (used only with method “dc_pf”)
voltage	float	voltage (kV) of line (single value) or transformer (tuple) (used only with method “dc_pf”)
power_loss_function	tuple	(optional) piecewise linear function/table of power transfer (MW) vs loss (MW). A tuple containing a list of x values and a list of y values `([x1,x2,..],[y1,y2,...])`

Note that for the (default) “transport” electricity power flow method, only the optional power_loss_function is relevant.

Devices (electric only)#

The table below shows device models used with electric only modelling, and their additional parameters. These are specified in addition to the generic device parameters.

`powersource`#

No extra data

`powersink`#

No extra data

`storage_el`#

parameter	type	description
E_max	float	Energy capacity (MWh)
E_min	float	Energy capacity (MWh)
E_init	float	Storage level initially (MWh)
E_end	float	(optional) Required storage level at end of each optimisation (MWh)
E_cost	float	Cost for deviation from target storage
eta	float	Round-trip charge/discharge efficiency
target_profile	string	(optional) name of profile used for desired storage filling level

Multi-energy system modelling#

Additional edge data and device data used with multi-energy modelling is provided here:

Input data

Contents

Input data#

Contents#

Introduction#

Data#

General parameters (parameters)#

Time-series profiles (profiles)#

Energy carriers (carriers)#

Network nodes (nodes)#

Network edges (edges)#

Devices (devices)#

Start and stop data (StartStopData)#