Speicher/en: Unterschied zwischen den Versionen

Aus TALSIM Docs
Keine Bearbeitungszusammenfassung
Keine Bearbeitungszusammenfassung
 
(22 dazwischenliegende Versionen von 3 Benutzern werden nicht angezeigt)
Zeile 5: Zeile 5:
[[Datei:Systemelement006.png|50px|none]]
[[Datei:Systemelement006.png|50px|none]]


Reservoirs are used to store an inflow and, depending on the current storage content and operating rules, to release water for different uses to up to three different system elements. With the possibility to [[Special:MyLanguage/Betriebsregelkonzept|regulate and control]] releases, it is an extremely flexible system element with a variety of options. Originally, the reservoir was developed to represent reservoirs behind dams, but it can also be used to model other reservoirs such as flood control reservoirs or similar.
Storages are used to store an inflow and, depending on the current storage content and operating rules, to release water for different uses to up to three different system elements. With the possibility to [[Special:MyLanguage/Betriebsregelkonzept|regulate and control]] releases, it is an extremely flexible system element with a variety of options. Originally, the storage element was developed to represent reservoirs behind dams, but it can also be used to model other storages such as flood control reservoirs or similar.
Additionally, it is possible to optionally simulate the addition of water to the reservoir by precipitation, as well as losses from the reservoir by evaporation and infiltration.
Additionally, it is possible to optionally simulate the addition of water to the storage by precipitation, as well as losses from the storage by evaporation and infiltration.


The reservoir system element can also be used to simulate [[Special:MyLanguage/Speicher mit Wasserkraftanlagen|hydro power plants]].
The storage system element can also be used to simulate [[Special:MyLanguage/Speicher mit Wasserkraftanlagen|hydro power plants]].




==Rating Curve==
==Rating Curve==


The reservoir rating curve defines the relationship between storage volume, water level and surface area.
The storage rating curve defines the relationship between storage volume, water level and surface area.
It forms the basis for all calculation options that depend on not only the storage volume but also the water level and/or the surface area e.g., precipitation/losses, flow over a weir, pressurized flow through pipes.
It forms the basis for all calculation options that depend on not only the storage volume but also the water level and/or the surface area e.g., precipitation/losses, flow over a weir, pressurized flow through pipes.




==Releases==
==Releases==
The term release is used to describe any discharge of water according to operating rules from the reservoir to the downstream area through regulated or unregulated outlets. This includes controlled releases through operating and bottom outlets as well as releases via a spillway.  
The term release is used to describe any discharge of water according to operating rules from the storage to the downstream area through regulated or unregulated outlets. This includes controlled releases through operating and bottom outlets as well as releases via a spillway.  


Releases are often related to operating rules, therefore, it is possible or sometimes also necessary to define several releases for each outlet.
Releases are often related to operating rules, therefore, it is possible or sometimes also necessary to define several releases for each outlet.
Zeile 24: Zeile 24:
===Calculation Options===
===Calculation Options===


Independent of the selected calculation option, releases can always be scaled with a system state/control cluster, which makes it possible to model complex [[Special:MyLanguage/Betriebsregelkonzept|operating rules]], which are not only dependent on states within the reservoir, but also on other states within the river basin.
Independent of the selected calculation option, releases can always be scaled with a system state/control cluster, which makes it possible to model complex [[Special:MyLanguage/Betriebsregelkonzept|operating rules]], which are not only dependent on states within the storage, but also on other states within the river basin.


====Release per Timestep / Release Sequence====
====Release per Timestep / Release Sequence====
Zeile 40: Zeile 40:
|
|
KNL
KNL
|Kennlinie
|Rating curve
|-
|-
|
|
LAM
LAM
|Lamellenplan
|Pool-based operating plan
|-
|-
|
|
XYZ
XYZ
|Zeitabhängige Funktion
|Time-dependent function
|}
|}


Zeile 59: Zeile 59:
=====Pool-Based Operating Plan=====
=====Pool-Based Operating Plan=====


With the option pool-based operating plan, the reservoir storage is divided into different pools which vary over the year and these pools are each assigned a fixed release amount. A pool-based operating plan is defined by entering a number of releases with ascending amounts and specifying the corresponding storage volume for each release amount at different times of the year.  
With the option pool-based operating plan, the storage is divided into different pools which vary over the year and these pools are each assigned a fixed release amount. A pool-based operating plan is defined by entering a number of releases with ascending amounts and specifying the corresponding storage volume for each release amount at different times of the year.  


The areas between the entered nodes can be interpreted as steps. However, it is also possible to interpolate linearly in time and/or between the release amounts.<br clear="all" />
The areas between the entered nodes can be interpreted as steps. However, it is also possible to interpolate linearly in time and/or between the release amounts.<br clear="all" />
Zeile 93: Zeile 93:
===Limits===
===Limits===


The [[Betriebsregeltypen#Grundsatz:_.C3.9Cberpr.C3.BCfung_physikalischer_Grenzen|physically maximum possible output]] can also be entered for the individual outlet organs of the storage tank as a function of the storage tank content, which additionally limits the desired outputs. A minimum permissible discharge can also be entered here, below which the discharge is set to 0.
The [[Special:MyLanguage/Betriebsregeltypen|maximum physically possible output]] of individual outlets can be entered as functions of storage volume, causing releases to be limited to these values. It is also possible to specify a minimum permissible release value, below which the release will be set to 0.




===Internal dependencies===
===Internal Dependencies===


Internal dependencies are used to define the [[Betriebsregeltypen#Regel_Typ_9:_Priorit.C3.A4ten_bei_mehreren.2C_konkurrierenden_Abgaben_aus_einem_Speicher|priorities in case of several, competing deliveries from one storage]]. One or more charges can be reduced if another charge exceeds a certain amount or if the memory content falls below a certain amount.  
Internal dependencies are used to define the [[Special:MyLanguage/Betriebsregeltypen|priorities in case of multiple competing releases from one storage]]. One or more releases can be reduced if another release exceeds a certain amount or if the storage volume falls below a certain value.  


The respective limits of output and storage volume for internal dependencies are constants, which can still be scaled by constant graphs.
The limits for releases and storage volumes for internal dependencies are entered as constant values, which can however be scaled with daily, weekly and/or annual patterns.


If several charges are reduced, the order in which they are to be reduced must also be specified.
If several releases are to be reduced simultaneously, the order in which they should be reduced must also be specified.


Example:
Example:
''If output B > 0 and the memory content S < X, then reduce output A by the amount of output B, whereby output A may not become less than zero.''
''If release B > 0 and the storage volume S < X, then reduce release A by the amount of release B, but at most to a minimum value of zero.''


This means, that between A and B a linear dependence exists as long as B is equal to the value of A. If B rises further, A remains constant zero.
This means that there is a linear relatioship between A and B until B is equal to the value of A. If the value of B rises any further, A still remains zero.




==Contribution/Loss at the Reservoir ==
==Precipitation/Losses==


A contribution or loss at the reservoir in the form of precipitation, evaporation or infiltration can be considered via two options:
An addition of water caused by precipitation onto the storage's surface or losses caused by evaporation or infiltration can be considered via two options:


* Constant chart (daily, weekly and/or yearly)
* Constant pattern (daily, weekly and/or annual pattern)
* Time series
* Time series


These can be scaled by a factor.
These can be additionally scaled by a factor.
The reservoir loss/contribution is additionally scaled automatically with the current storage surface
Precipitation, evaporation and infiltration values must be provided as a linear unit such as e.g. mm. During the simulation, the provided values are converted to water volumes by multiplying with the current storage surface area.

Aktuelle Version vom 30. August 2021, 11:48 Uhr

Sprachen:
Systemelement006.png

Storages are used to store an inflow and, depending on the current storage content and operating rules, to release water for different uses to up to three different system elements. With the possibility to regulate and control releases, it is an extremely flexible system element with a variety of options. Originally, the storage element was developed to represent reservoirs behind dams, but it can also be used to model other storages such as flood control reservoirs or similar. Additionally, it is possible to optionally simulate the addition of water to the storage by precipitation, as well as losses from the storage by evaporation and infiltration.

The storage system element can also be used to simulate hydro power plants.


Rating Curve

The storage rating curve defines the relationship between storage volume, water level and surface area. It forms the basis for all calculation options that depend on not only the storage volume but also the water level and/or the surface area e.g., precipitation/losses, flow over a weir, pressurized flow through pipes.


Releases

The term release is used to describe any discharge of water according to operating rules from the storage to the downstream area through regulated or unregulated outlets. This includes controlled releases through operating and bottom outlets as well as releases via a spillway.

Releases are often related to operating rules, therefore, it is possible or sometimes also necessary to define several releases for each outlet.

Calculation Options

Independent of the selected calculation option, releases can always be scaled with a system state/control cluster, which makes it possible to model complex operating rules, which are not only dependent on states within the storage, but also on other states within the river basin.

Release per Timestep / Release Sequence

With this option, you define the release values by directly entering (up to 365) values. During the simulation, these values are then used as release values for the individual simulation timesteps in the given order.


Function (+ Hydrograph/Time Series)

With this option, releases are defined as functions of storage volume by entering the nodes of the function. These releases can additionally be scaled with a factor, an annual, weekly and/or daily pattern (and, as with all calculation options, with a system state or a control cluster) or with a factor and a time series.

The following function types are available:

KNL

Rating curve

LAM

Pool-based operating plan

XYZ

Time-dependent function


Rating Curve

The rating curve consists of a time-independent functional relationship between releases and storage volume. You can specify whether the function should be interpolated linearly between the entered nodes or whether the function should be interpreted as a step function.


Pool-Based Operating Plan

With the option pool-based operating plan, the storage is divided into different pools which vary over the year and these pools are each assigned a fixed release amount. A pool-based operating plan is defined by entering a number of releases with ascending amounts and specifying the corresponding storage volume for each release amount at different times of the year.

The areas between the entered nodes can be interpreted as steps. However, it is also possible to interpolate linearly in time and/or between the release amounts.


Time-Dependent Function

A time-dependent function is very similar to a pool-based operating plan, but a bit more flexible: the releases defined at different time periods only have to be of equal number but not in value, and they do not necessarily have to be ascending. This makes it possible to define arbitrary functions with individual nodes for release amounts and storage volumes for different time periods.

By default the functions are interpreted as steps with constant values between the entered nodes. However, it is also possible to interpolate linearly in time and/or between the entered storage-release value pairs.


Weir Overflow

The release is calculated using the weir formula according to Poleni as free / submerged overflow.


Pressure Pipeline

The release is calculated according to the Prandtl-Colebrook and Darcy-Weisbach formulas.


Turbine

Based on the characteristics of the turbine, the flow through the turbine is determined depending on the storage level and the downstream water level, such that the desired power output is maintained as long as the maximum possible flow rate of the outlet is not exceeded. See also the page on hydropower plants.


Limits

The maximum physically possible output of individual outlets can be entered as functions of storage volume, causing releases to be limited to these values. It is also possible to specify a minimum permissible release value, below which the release will be set to 0.


Internal Dependencies

Internal dependencies are used to define the priorities in case of multiple competing releases from one storage. One or more releases can be reduced if another release exceeds a certain amount or if the storage volume falls below a certain value.

The limits for releases and storage volumes for internal dependencies are entered as constant values, which can however be scaled with daily, weekly and/or annual patterns.

If several releases are to be reduced simultaneously, the order in which they should be reduced must also be specified.

Example: If release B > 0 and the storage volume S < X, then reduce release A by the amount of release B, but at most to a minimum value of zero.

This means that there is a linear relatioship between A and B until B is equal to the value of A. If the value of B rises any further, A still remains zero.


Precipitation/Losses

An addition of water caused by precipitation onto the storage's surface or losses caused by evaporation or infiltration can be considered via two options:

  • Constant pattern (daily, weekly and/or annual pattern)
  • Time series

These can be additionally scaled by a factor. Precipitation, evaporation and infiltration values must be provided as a linear unit such as e.g. mm. During the simulation, the provided values are converted to water volumes by multiplying with the current storage surface area.