Operationeller Einsatz von Talsim-NG/en: Unterschied zwischen den Versionen
Ferrao (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „The TaskServer takes over the postprocessing. This step includes the compilation of the most important results, the export of result charts in other formats or…“) |
Ferrao (Diskussion | Beiträge) Keine Bearbeitungszusammenfassung |
||
| (6 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt) | |||
| Zeile 5: | Zeile 5: | ||
== | ==Preprocessing== | ||
TALSIM-NG | TALSIM-NG itself is not designed to retrieve measuring sensors. As a rule, established tools are already available for this purpose. From TALSIM-NG's point of view, the process sequence begins with the interface to a data supplier (control system, control software, etc.). The design of the interface varies from case to case and requires precise coordination. The aim is to provide the required data in a timely manner. It is irrelevant whether the data request is started by TALSIM-NG or whether data is to be accumulated and reacted to by TALSIM-NG in a time-controlled manner. In the end, current measurement data is available in a time-defined or variable rhythm. The interface is part of the preprocessing, which is operated by a separate tool in the TALSIM-NG product family, the TaskServer. | ||
If the current data are read out via interface, they are usually archived in the own time series management. The next step is to check the accumulated data. A check will always be necessary if unchecked raw data are read in. The type and range of checks have to be determined in each individual case and are defined in so-called tasks. The TaskServer reads these tasks and implements them. Behind this, there is a kind of scripting language that describes what exactly has to be implemented. These tasks are saved in files and are configured for the specific case. | If the current data are read out via interface, they are usually archived in the own time series management. The next step is to check the accumulated data. A check will always be necessary if unchecked raw data are read in. The type and range of checks have to be determined in each individual case and are defined in so-called tasks. The TaskServer reads these tasks and implements them. Behind this, there is a kind of scripting language that describes what exactly has to be implemented. These tasks are saved in files and are configured for the specific case. | ||
| Zeile 26: | Zeile 26: | ||
In the case of a 2nd or 3rd order examination, the focus of the work is on providing the examination rules. | In the case of a 2nd or 3rd order examination, the focus of the work is on providing the examination rules. | ||
Like all other process steps, the results of the test can also be stored in report form, e.g. as PDF. | |||
== Forecasts== | == Forecasts== | ||
The type of forecasts depends on the respective application. In case of a pure rainfall-runoff modelling it is obvious to provide expected precipitation. The principle process is comparable to the interface for data transfer. | |||
==Simulation== | ==Simulation== | ||
A preconfigured data set must be available for the simulation. Although changes to the data set are possible at any time via the graphical user interface of TALSIM NG, a distinction is made between the production data set, which is used for sharp operation, and any number of derivatives or variants thereof. | |||
Basically, no user input is required for a simulation. However, it is in principle possible to release certain parameters which have to be set before the simulation starts. These editable parameters are called Hot Spots. In this way, even an extremely complicated system can be reduced to a simple input of a few values without the risk of unwanted effects due to incorrect input. | |||
| Zeile 46: | Zeile 46: | ||
== | == Data transfer back to a control system == | ||
If necessary, data can also be returned to the data supplier from TALSIM NG. | If necessary, data can also be returned to the data supplier from TALSIM NG. | ||
Aktuelle Version vom 23. September 2020, 16:28 Uhr
If TALSIM-NG is to be used in operational mode, some preliminary work is required. This becomes clear in the following process flow:
Picture
Preprocessing
TALSIM-NG itself is not designed to retrieve measuring sensors. As a rule, established tools are already available for this purpose. From TALSIM-NG's point of view, the process sequence begins with the interface to a data supplier (control system, control software, etc.). The design of the interface varies from case to case and requires precise coordination. The aim is to provide the required data in a timely manner. It is irrelevant whether the data request is started by TALSIM-NG or whether data is to be accumulated and reacted to by TALSIM-NG in a time-controlled manner. In the end, current measurement data is available in a time-defined or variable rhythm. The interface is part of the preprocessing, which is operated by a separate tool in the TALSIM-NG product family, the TaskServer.
If the current data are read out via interface, they are usually archived in the own time series management. The next step is to check the accumulated data. A check will always be necessary if unchecked raw data are read in. The type and range of checks have to be determined in each individual case and are defined in so-called tasks. The TaskServer reads these tasks and implements them. Behind this, there is a kind of scripting language that describes what exactly has to be implemented. These tasks are saved in files and are configured for the specific case. Checks can take place at different depths:
- 1st order test: basic test of a time series in itself
- - Min-, Max values
- - Allowed gradients
- 2st order test: extended test with derived values
- - Correlation to other measured values/ confidence intervals
- - hydrological tests
- 3st order test:
- - Rule tree with transfer functions
- - Neural networks to determine substitute values
Picture
In the case of a 2nd or 3rd order examination, the focus of the work is on providing the examination rules.
Like all other process steps, the results of the test can also be stored in report form, e.g. as PDF.
Forecasts
The type of forecasts depends on the respective application. In case of a pure rainfall-runoff modelling it is obvious to provide expected precipitation. The principle process is comparable to the interface for data transfer.
Simulation
A preconfigured data set must be available for the simulation. Although changes to the data set are possible at any time via the graphical user interface of TALSIM NG, a distinction is made between the production data set, which is used for sharp operation, and any number of derivatives or variants thereof.
Basically, no user input is required for a simulation. However, it is in principle possible to release certain parameters which have to be set before the simulation starts. These editable parameters are called Hot Spots. In this way, even an extremely complicated system can be reduced to a simple input of a few values without the risk of unwanted effects due to incorrect input.
Postprocessing
The TaskServer takes over the postprocessing. This step includes the compilation of the most important results, the export of result charts in other formats or a graphical representation of the recommendations for action.
Data transfer back to a control system
If necessary, data can also be returned to the data supplier from TALSIM NG.
Overall control of the sequence
The overall control of the process is handled by the so-called jobService. Together with the time control system talsimCronos can operate both event and time controll. The entire process has a modular structure, i.e. it is defined in detail which sub-processes are required and in which order they should run. Thus, it is also conceivable that only one pre- and postprocessing takes place, or pre- and postprocessing run in a different time cycle than simulations.