Operationeller Einsatz von Talsim-NG/en - Versionsgeschichte

Froehlich: Die Seite wurde neu angelegt: „Alternatively, it is possible to use Talsim-NG within an existing operational framework (such as e.g. Delft-FEWS), which takes care of all the pre- and postprocessing tasks.“

2024-05-29T09:54:11Z

Die Seite wurde neu angelegt: „Alternatively, it is possible to use Talsim-NG within an existing operational framework (such as e.g. Delft-FEWS), which takes care of all the pre- and postprocessing tasks.“

← Nächstältere Version		Version vom 29. Mai 2024, 11:54 Uhr
Zeile 2:		Zeile 2:
	If TALSIM-NG is to be used in operational mode, some preliminary work is required, which is described below:		If TALSIM-NG is to be used in operational mode, some preliminary work is required, which is described below:

	~~Eine alternative Möglichkeit ist~~, Talsim-NG ~~innerhalb eines bestehenden operativen Frameworks~~ (~~wie z~~.B. [[Special:MyLanguage/Delft-FEWS\|Delft-FEWS]]), ~~welches die Aufgaben des Pre~~- ~~und Postprocessings übernimmt, einzusetzen~~.		Alternatively, it is possible to use Talsim-NG within an existing operational framework (such as e.g. [[Special:MyLanguage/Delft-FEWS\|Delft-FEWS]]), which takes care of all the pre- and postprocessing tasks.

	==Preprocessing==		==Preprocessing==

Froehlich am 29. Mai 2024 um 09:53 Uhr

2024-05-29T09:53:10Z

← Nächstältere Version		Version vom 29. Mai 2024, 11:53 Uhr
Zeile 1:		Zeile 1:
	<languages/>		<languages/>
	~~<div class="mw-translate-fuzzy">~~		If TALSIM-NG is to be used in operational mode, some preliminary work is required, which is described below:
	If TALSIM-NG is to be used in operational mode, some preliminary work is required~~. This becomes clear in the following process flow~~:
	~~</div>~~

	Eine alternative Möglichkeit ist, Talsim-NG innerhalb eines bestehenden operativen Frameworks (wie z.B. [[Special:MyLanguage/Delft-FEWS\|Delft-FEWS]]), welches die Aufgaben des Pre- und Postprocessings übernimmt, einzusetzen.		Eine alternative Möglichkeit ist, Talsim-NG innerhalb eines bestehenden operativen Frameworks (wie z.B. [[Special:MyLanguage/Delft-FEWS\|Delft-FEWS]]), welches die Aufgaben des Pre- und Postprocessings übernimmt, einzusetzen.

FuzzyBot: Übernehme Bearbeitung einer neuen Version der Quellseite

2024-05-29T09:52:48Z

Übernehme Bearbeitung einer neuen Version der Quellseite

← Nächstältere Version		Version vom 29. Mai 2024, 11:52 Uhr
Zeile 1:		Zeile 1:
	<languages/>		<languages/>
			<div class="mw-translate-fuzzy">
	If TALSIM-NG is to be used in operational mode, some preliminary work is required. This becomes clear in the following process flow:		If TALSIM-NG is to be used in operational mode, some preliminary work is required. This becomes clear in the following process flow:
			</div>

	~~Picture~~		Eine alternative Möglichkeit ist, Talsim-NG innerhalb eines bestehenden operativen Frameworks (wie z.B. [[Special:MyLanguage/Delft-FEWS\|Delft-FEWS]]), welches die Aufgaben des Pre- und Postprocessings übernimmt, einzusetzen.


	==Preprocessing==		==Preprocessing==
Zeile 29:		Zeile 30:


			<span id="Prognosen"></span>
	== Forecasts==		== Forecasts==

Zeile 46:		Zeile 48:


			<span id="Datentransfer_zurück_zu_einem_Leitsystem"></span>
	== Data transfer back to a control system ==		== Data transfer back to a control system ==

Zeile 51:		Zeile 54:


			<span id="Gesamtsteuerung_des_Ablaufs"></span>
	== Overall control of the sequence ==		== 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.		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.

Ferrao am 23. September 2020 um 14:28 Uhr

2020-09-23T14:28:05Z

← Nächstältere Version		Version vom 23. September 2020, 16:28 Uhr
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.

	~~Die Ergebnisse der Prüfung können wie alle sonstigen Prozessschritte auch~~ in ~~Berichtsform z~~.B. ~~als~~ PDF ~~abgelegt werden~~.		Like all other process steps, the results of the test can also be stored in report form, e.g. as PDF.

Ferrao am 23. September 2020 um 14:27 Uhr

2020-09-23T14:27:06Z

← Nächstältere Version		Version vom 23. September 2020, 16:27 Uhr
Zeile 5:		Zeile 5:


	==~~Vorverarbeitung~~==		==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.		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.

Ferrao: Die Seite wurde neu angelegt: „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 TA…“

2020-09-23T14:26:08Z

Die Seite wurde neu angelegt: „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 TA…“

← Nächstältere Version		Version vom 23. September 2020, 16:26 Uhr
Zeile 36:		Zeile 36:
	==Simulation==		==Simulation==

	~~Für die Simulation muss ein vorkonfigurierter Datensatz vorliegen~~. ~~Änderungen am Datensatz sind zwar jederzeit über die graphische Benutzungsoberfläche von~~ TALSIM NG ~~möglich~~, ~~jedoch wird hier unterschieden in Produktionsdatensatz~~, ~~der für den scharfen Betrieb eingesetzt wird und quasi beliebig vielen Ableitungen bzw. Varianten davon~~.		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.		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.

Ferrao: Die Seite wurde neu angelegt: „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 p…“

2020-09-23T14:25:28Z

Die Seite wurde neu angelegt: „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 p…“

← Nächstältere Version		Version vom 23. September 2020, 16:25 Uhr
Zeile 31:		Zeile 31:
	== Forecasts==		== Forecasts==

	~~Die Art der Prognosen hängt vom jeweiligen Einsatzzweck ab~~. ~~Im Falle einer reinen Niederschlag~~-~~Abfluss Modellierung liegt es nahe, erwartete Niederschläge bereitzustellen~~. ~~Der prinzipielle Ablauf ist mit der Schnittstelle zur Datenübernahme vergleichbar~~.		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.

Ferrao: Die Seite wurde neu angelegt: „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 simul…“

2020-09-23T14:14:01Z

Die Seite wurde neu angelegt: „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 simul…“

← Nächstältere Version		Version vom 23. September 2020, 16:14 Uhr
Zeile 38:		Zeile 38:
	Für die Simulation muss ein vorkonfigurierter Datensatz vorliegen. Änderungen am Datensatz sind zwar jederzeit über die graphische Benutzungsoberfläche von TALSIM NG möglich, jedoch wird hier unterschieden in Produktionsdatensatz, der für den scharfen Betrieb eingesetzt wird und quasi beliebig vielen Ableitungen bzw. Varianten davon.		Für die Simulation muss ein vorkonfigurierter Datensatz vorliegen. Änderungen am Datensatz sind zwar jederzeit über die graphische Benutzungsoberfläche von TALSIM NG möglich, jedoch wird hier unterschieden in Produktionsdatensatz, der für den scharfen Betrieb eingesetzt wird und quasi beliebig vielen Ableitungen bzw. Varianten davon.

	~~Grundsätzlich braucht es für eine Simulation keine Eingabe eines Anwenders~~. ~~Es ist aber prinzipiell möglich~~, ~~bestimmte Parameter freizugeben, die vor Simulationsbeginn gesetzt werden müssen~~. ~~Diese editierbaren Parameter werden~~ Hot Spots ~~genannt~~. ~~So lässt sich auch ein extrem kompliziertes System auf eine einfache Eingabe von wenigen Werten reduzieren, ohne Gefahr zu laufen~~, ~~durch Fehleingaben unerwünschte Effekte zu erzielen~~.		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.

Ferrao: Die Seite wurde neu angelegt: „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…“

2020-09-23T14:07:44Z

Die Seite wurde neu angelegt: „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…“

← Nächstältere Version		Version vom 23. September 2020, 16:07 Uhr
Zeile 7:		Zeile 7:
	==Vorverarbeitung==		==Vorverarbeitung==

	TALSIM-NG ~~selbst ist nicht konzipiert~~, ~~Messsensoren abzurufen. In der Regel liegen dafür bereits etablierte Werkzeuge vor~~. ~~Der Prozessablauf aus Sicht von~~ TALSIM-NG ~~beginnt mit der Schnittstelle zu einem Datenlieferanten~~ (~~Leitsystem~~, ~~Steuerungssoftware~~, etc.). ~~Die Ausgestaltung der Schnittstelle ist von Fall zu Fall unterschiedlich und bedarf der genauen Abstimmung~~. ~~Ziel ist es, zeitnah die benötigten Daten bereitzustellen~~. ~~Dabei ist es unerheblich, ob die Datenanfrage von Seiten~~ TALSIM-NG ~~gestartet wird oder ob Daten zeitgesteuert auflaufen und~~ TALSIM-NG ~~reagieren soll~~. ~~Letztendlich stehen aktuelle Messdaten~~ in ~~einem zeitlich definierten oder variablen Rhythmus zur Verfügung~~. ~~Die Schnittstelle ist Teil des Preprocessings~~, ~~welches von einem eigenen Tool~~ in ~~der~~ TALSIM-NG ~~Produktfamilie bedient wird~~, ~~dem~~ TaskServer.		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.

Ferrao: Die Seite wurde neu angelegt: „== Data transfer back to a control system ==“

2020-09-23T14:07:06Z

Die Seite wurde neu angelegt: „== Data transfer back to a control system ==“

← Nächstältere Version		Version vom 23. September 2020, 16:07 Uhr
Zeile 46:		Zeile 46:


	== ~~Datentransfer zurück zu einem Leitsystem~~ ==		== 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.