Belastungsdefinition/ Modellinput/en: Unterschied zwischen den Versionen

Aus TALSIM Docs
Keine Bearbeitungszusammenfassung
Keine Bearbeitungszusammenfassung
Zeile 10: Zeile 10:
The user interface takes the temperature data only into consideration for the evaporation and the snow calculation and consequently for the water balance. Water temperatures of the system elements are not simulated.
The user interface takes the temperature data only into consideration for the evaporation and the snow calculation and consequently for the water balance. Water temperatures of the system elements are not simulated.


Losses of water, substances or thermal energy can be made via the elements [[Special:MyLanguage/Verbraucher|consumer]]  and [[Special:MyLanguage/Verzweigung|diversion]]. [[Special:MyLanguage/Speicher|Reservoir elements]] can also withdraw water from the system if the evaporation calculation is activated. Via the discharge splitting of the [[Special:MyLanguage/Einzugsgebiet|catchment area elements]] it is possible to discharge individual discharge components from the system in addition to the evaporation term (e.g. urban surface runoff or deep base runoff).
A loss of water, substances or thermal energy can be made via the elements [[Special:MyLanguage/Verbraucher|consumer]]  and [[Special:MyLanguage/Verzweigung|diversion]]. [[Special:MyLanguage/Speicher|Reservoir elements]] can also extract water from the system if the evaporation calculation is activated. Via the runoff distribution of the [[Special:MyLanguage/Einzugsgebiet|catchment area elements]] it is possible to discharge individual discharge components from the system in addition to the evaporation term (e.g. urban surface runoff or deep base runoff).


Depending on the simulation type and system element, there are different possibilities for entering loads:
Depending on the simulation type and system element, there are different possibilities for entering loads:

Version vom 22. Dezember 2020, 15:29 Uhr

Sprachen:

Loads in the form of precipitation, temperature, evaporation, inflow, substances and extractions can affect water management systems.

The system elements point source and catchment area are the ones which particularly contribute water to the system. Consumer und reservoir can also add flow to the system: Consumers via the input of punctual contributions, reservoirs via an accordingly allocated precipitation, which scales with the reservoir's surface. Thus, the latter contribution to the water input is especially relevant for e.g. dams with large water surfaces.

Substance entries into the system can only be made using the point source element.

Currently, it is not possible to enter a specific entry/loss of thermal energy via the user interface. However, it can be already entered on file level using transport reach. A water temperature at the outlet of the transport element can be defined so the heat exchange between the water surface and the air can be calculated. For more details see: Temperature Modelling. The user interface takes the temperature data only into consideration for the evaporation and the snow calculation and consequently for the water balance. Water temperatures of the system elements are not simulated.

A loss of water, substances or thermal energy can be made via the elements consumer and diversion. Reservoir elements can also extract water from the system if the evaporation calculation is activated. Via the runoff distribution of the catchment area elements it is possible to discharge individual discharge components from the system in addition to the evaporation term (e.g. urban surface runoff or deep base runoff).

Depending on the simulation type and system element, there are different possibilities for entering loads:

Simulation type long-term simulation
- Hydrographs
- Time series
Simulation type short-term forecast
- model rain
- flood waves from flood characteristics


Hydrographs: Annual, Weekly, Daily Patterns

If hydrographs are chosen as the input option for a load, a constant value can be scaled with a recurring constant yearly and/or weekly and/or daily pattern. For daily patterns, a value can be defined for each hour of the day, for weekly patterns a constant value for each day of the week and for annual patterns, you can either enter constant monthly values or defined variable time periods between specific dates. In the datasheets of system elements only the assignment of hydrographs is done. The hydrographs are created independently from single system elements in the respective hydrograph window.


Time Series

Interpretation of time series

Time series are time sequences of data, i.e. ascending date and time stamps are assigned to values. Both measurement time series and simulated time series can be used as model input.

It is important that the time series are gap-free over the simulation period. Possible gaps in the time series must be closed before (e.g. by regressions to similar time series or by other assumptions). Ideally, but not necessarily, the time series are equidistant in at least the resolution of the simulation time step. Apart from the date and time series value, the interpretation of the time series is also crucial for the simulation. Furthermore, it is important to ensure that time series are given in the appropriate unit (e.g. m³/s for the discharge or mg/l for the concentration). Some system elements offer the option to scale time series with an additional factor.

In the data sheets of system elements only the time series assignment is done. The time series are created independently from individual system elements and even independently from variants and projects centrally in the time series management and stored on the server, i.e. time series of a client can be used in different projects.


Model rain

Flood waves from flood characteristics