Calibration/ScenarioComparison/hydrology/en - Revision history

BhawaniRegmi: /* Combination from Scenarios */

2017-02-18T13:27:19Z

Combination from Scenarios

← Older revision		Revision as of 13:27, 18 February 2017
Line 5:		Line 5:
	The new project structure of KalypsoHydrology from version 12 differs significantly from the earlier Kalypso versions. Instead of a ''Basic model'' and ''Calculation variants'', a project now consists of ''Scenarios'' and ''Simulations''. In contrast to the previous ''Calculation variants'', which always contained a separate copy of the model, a simulation now contains only the control parameters required for a simulation and accesses the model data of its scenario.		The new project structure of KalypsoHydrology from version 12 differs significantly from the earlier Kalypso versions. Instead of a ''Basic model'' and ''Calculation variants'', a project now consists of ''Scenarios'' and ''Simulations''. In contrast to the previous ''Calculation variants'', which always contained a separate copy of the model, a simulation now contains only the control parameters required for a simulation and accesses the model data of its scenario.

	Due to this changed project structure, the old project cannot be executed ~~completely~~ automatically.		Due to this changed project structure, the old project cannot be executed automatically.

	The simplest approach would be to import the previous basis model as a ~~basal~~ scenario, and the previous calculation variants as simulations. However, this can lead to data losses in practice, since it is not guaranteed that ~~all rake~~ variants were derived from the unchanged basic model as intended. If changes were made to the ~~rake~~ variants, they would be lost in the old project simulation because the simulations do not contain a copy of the model data as before. The user must ultimately decide which model variant is to be adopted as a new basic scenario. This takes place in several steps, described in the following.		The simplest approach would be to import the previous basis model as a base scenario, and the previous calculation variants as simulations. However, this can lead to data losses in practice, since it is not guaranteed that variants were derived from the unchanged basic model as intended. If changes were made to the variants, they would be lost in the old project simulation because the simulations do not contain a copy of the model data as before. The user must ultimately decide which model variant is to be adopted as a new basic scenario. This takes place in several steps, described in the following.
	[[File:Hydrology_Projectconversion_example.png\|250px\|thumb\|''Example structure after the old project import'']]		[[File:Hydrology_Projectconversion_example.png\|250px\|thumb\|''Example structure after the old project import'']]
	First, in order to avoid data losses, independent scenarios with a simulation calculation (corresponding to the old calculation variant) are generated from the old project variants. These can (and should) be merged again after completion of the old project by the user. The user must decide which model version (~~that is~~, which scenario created automatically from the computational variants) is to be used as the basic scenario.		First, in order to avoid data losses, independent scenarios with a simulation calculation (corresponding to the old calculation variant) are generated from the old project variants. These can (and should) be merged again after completion of the old project by the user. The user must decide which model version (i.e., which scenario created automatically from the computational variants) is to be used as the basic scenario.

	See also (see Figure [[:File:Hydrology_Projectconversion_example.png\|'' Example structure after the old project import'']]). The picture shows an example, which was created from a basic model with two types of variants (called ''Long-term simulation'' and ''Short-term simulation''). These were imported as a base scenario with two sub-scenarios. Each sub-scenario contains a simulation definition of the same name.		See also (see Figure [[:File:Hydrology_Projectconversion_example.png\|'' Example structure after the old project import'']]). The picture shows an example, which was created from a basic model with two types of variants (called ''Long-term simulation'' and ''Short-term simulation''). These were imported as a base scenario with two sub-scenarios. Each sub-scenario contains a simulation definition of the same name.

BhawaniRegmi: /* Compare the scenario data */

2017-02-18T13:23:09Z

Compare the scenario data

← Older revision		Revision as of 13:23, 18 February 2017
Line 28:		Line 28:
	== Compare the scenario data ==		== Compare the scenario data ==

	Before merging, the user should decide which model version (~~that is~~, which scenario created automatically from the computational variants) to use, as this is used for all future simulations. To simplify the decision, an additional tool for comparing scenarios was integrated.		Before merging, the user should decide which model version (i.e, which scenario created automatically from the computational variants) to use, as this is used for all future simulations. To simplify the decision, an additional tool for comparing scenarios was integrated.

	To do this, several scenarios are selected in the ''Scenarios''- view and then the ''Scenarios comparison'' is started with the right mouse button. A new query window opens from which the ''Reference scenario'' is selected. Click ''OK'' to start the comparison scenario. An Excel spreadsheet with several spreadsheets opens automatically. For each sheet, the compared parameters of a group (for example Node, Strand, Inflow area, Land use, etc.) are documented per scenario. Parameters that differ from the reference scenario are marked in red. The Excel table is automatically saved in the Temp directory of the computer when it is opened.		To do this, several scenarios are selected in the ''Scenarios''- view and then the ''Scenarios comparison'' is started with the right mouse button. A new query window opens from which the ''Reference scenario'' is selected. Click ''OK'' to start the comparison scenario. An Excel spreadsheet with several spreadsheets opens automatically. For each sheet, the compared parameters of a group (for example Node, Strand, Inflow area, Land use, etc.) are documented per scenario. Parameters that differ from the reference scenario are marked in red. The Excel table is automatically saved in the Temp directory of the computer when it is opened.

BhawaniRegmi: /* Combine Scenarios */

2017-02-18T13:21:37Z

Combine Scenarios

← Older revision		Revision as of 13:21, 18 February 2017
Line 13:		Line 13:
	See also (see Figure [[:File:Hydrology_Projectconversion_example.png\|'' Example structure after the old project import'']]). The picture shows an example, which was created from a basic model with two types of variants (called ''Long-term simulation'' and ''Short-term simulation''). These were imported as a base scenario with two sub-scenarios. Each sub-scenario contains a simulation definition of the same name.		See also (see Figure [[:File:Hydrology_Projectconversion_example.png\|'' Example structure after the old project import'']]). The picture shows an example, which was created from a basic model with two types of variants (called ''Long-term simulation'' and ''Short-term simulation''). These were imported as a base scenario with two sub-scenarios. Each sub-scenario contains a simulation definition of the same name.

	== ~~Combine~~ Scenarios ==		== Merge Scenarios ==
	[[File:Hydrology_Projectconversion_mergeScenarios_menu.png\|250px\|thumb\|right\|''~~Combine~~ Scenarios'' Tool]]		[[File:Hydrology_Projectconversion_mergeScenarios_menu.png\|250px\|thumb\|right\|''Merge Scenarios'' Tool]]
	When ~~combining~~ scenarios, the simulation definitions of one or more scenarios are transferred to a target scenario. The model data of the target scenario remains unchanged, i.e. The simulation definitions are applied to these model data. The procedure is as follows:		When merging scenarios, the simulation definitions of one or more scenarios are transferred to a target scenario. The model data of the target scenario remains unchanged, i.e. The simulation definitions are applied to these model data. The procedure is as follows:

	Activate the ''Merge Scenarios'' tool from the scenario view context menu (see [[:File:Hydrology_Projectconversion_mergeScenarios_menu.png\| ''Merge tool scenarios'']]).		Activate the ''Merge Scenarios'' tool from the scenario view context menu (see [[:File:Hydrology_Projectconversion_mergeScenarios_menu.png\| ''Merge tool scenarios'']]).

BhawaniRegmi: /* Combine Scenarios */

2017-02-18T13:20:57Z

Combine Scenarios

← Older revision		Revision as of 13:20, 18 February 2017
Line 1:		Line 1:
	== Scenario Comparison ==		== Scenario Comparison ==

	= ~~Combine~~ Scenarios =		= Combination from Scenarios =

	The new project structure of KalypsoHydrology from version 12 differs significantly from the earlier Kalypso versions. Instead of a ''Basic model'' and ''Calculation variants'', a project now consists of ''Scenarios'' and ''Simulations''. In contrast to the previous ''Calculation variants'', which always contained a separate copy of the model, a simulation now contains only the control parameters required for a simulation and accesses the model data of its scenario.		The new project structure of KalypsoHydrology from version 12 differs significantly from the earlier Kalypso versions. Instead of a ''Basic model'' and ''Calculation variants'', a project now consists of ''Scenarios'' and ''Simulations''. In contrast to the previous ''Calculation variants'', which always contained a separate copy of the model, a simulation now contains only the control parameters required for a simulation and accesses the model data of its scenario.

BhawaniRegmi: /* Combine Scenarios */

2017-02-18T13:18:34Z

Combine Scenarios

← Older revision		Revision as of 13:18, 18 February 2017
Line 14:		Line 14:

	== Combine Scenarios ==		== Combine Scenarios ==
	[[File:Hydrology_Projectconversion_mergeScenarios_menu.png\|250px\|thumb\|right\|~~Werkzeug~~ ''Combine Scenarios'']]		[[File:Hydrology_Projectconversion_mergeScenarios_menu.png\|250px\|thumb\|right\|''Combine Scenarios'' Tool]]
	When combining scenarios, the simulation definitions of one or more scenarios are transferred to a target scenario. The model data of the target scenario remains unchanged, i.e. The simulation definitions are applied to these model data. The procedure is as follows:		When combining scenarios, the simulation definitions of one or more scenarios are transferred to a target scenario. The model data of the target scenario remains unchanged, i.e. The simulation definitions are applied to these model data. The procedure is as follows:

BhawaniRegmi: /* Combine Scenarios */

2017-02-18T13:16:47Z

Combine Scenarios

← Older revision		Revision as of 13:16, 18 February 2017
Line 3:		Line 3:
	= Combine Scenarios =		= Combine Scenarios =

	The new project structure of KalypsoHydrology from version 12 differs significantly from the earlier Kalypso versions. Instead of a ''Basic model'' and ''Calculation variants'', a project now consists of ''Scenarios'' and ''Simulations''. In contrast to the previous ''Calculation variants, which always contained a separate copy of the model, a simulation now contains only the control parameters required for a simulation and accesses the model data of its scenario.		The new project structure of KalypsoHydrology from version 12 differs significantly from the earlier Kalypso versions. Instead of a ''Basic model'' and ''Calculation variants'', a project now consists of ''Scenarios'' and ''Simulations''. In contrast to the previous ''Calculation variants'', which always contained a separate copy of the model, a simulation now contains only the control parameters required for a simulation and accesses the model data of its scenario.

	Due to this changed project structure, the old project cannot be executed completely automatically.		Due to this changed project structure, the old project cannot be executed completely automatically.

BhawaniRegmi: /* Combine Scenarios */

2017-02-18T13:16:22Z

Combine Scenarios

← Older revision		Revision as of 13:16, 18 February 2017
Line 8:		Line 8:

	The simplest approach would be to import the previous basis model as a basal scenario, and the previous calculation variants as simulations. However, this can lead to data losses in practice, since it is not guaranteed that all rake variants were derived from the unchanged basic model as intended. If changes were made to the rake variants, they would be lost in the old project simulation because the simulations do not contain a copy of the model data as before. The user must ultimately decide which model variant is to be adopted as a new basic scenario. This takes place in several steps, described in the following.		The simplest approach would be to import the previous basis model as a basal scenario, and the previous calculation variants as simulations. However, this can lead to data losses in practice, since it is not guaranteed that all rake variants were derived from the unchanged basic model as intended. If changes were made to the rake variants, they would be lost in the old project simulation because the simulations do not contain a copy of the model data as before. The user must ultimately decide which model variant is to be adopted as a new basic scenario. This takes place in several steps, described in the following.
	[[File:Hydrology_Projectconversion_example.png\|250px\|thumb\|''Example structure ~~according to~~ the old project import'']]		[[File:Hydrology_Projectconversion_example.png\|250px\|thumb\|''Example structure after the old project import'']]
	First, in order to avoid data losses, independent scenarios with a simulation calculation (corresponding to the old calculation variant) are generated from the old project variants. These can (and should) be merged again after completion of the old project by the user. The user must decide which model version (that is, which scenario created automatically from the computational variants) is to be used as the basic scenario.		First, in order to avoid data losses, independent scenarios with a simulation calculation (corresponding to the old calculation variant) are generated from the old project variants. These can (and should) be merged again after completion of the old project by the user. The user must decide which model version (that is, which scenario created automatically from the computational variants) is to be used as the basic scenario.

BhawaniRegmi: /* Zusammenführen von Szenarien */

2017-02-18T13:15:32Z

Zusammenführen von Szenarien

← Older revision		Revision as of 13:15, 18 February 2017
Line 1:		Line 1:
	== Scenario Comparison ==		== Scenario Comparison ==

	= ~~Zusammenführen von Szenarien~~ =		= Combine Scenarios =

	~~Die Neue Projektstruktur von~~ KalypsoHydrology ~~ab Version~~ 12 ~~unterscheidet sich wesentlich von der früherer~~ Kalypso ~~Versionen~~. ~~Statt~~ ''~~Basismodell~~'' ~~und~~ ''~~Rechenvarianten~~'' ~~besteht ein Projekt jetzt aus~~ ''~~Szenarien~~'' ~~und~~ ''~~Simulationen~~''. ~~Im Gegensatz zu den bisherigen ''Rechenvarianten~~'', ~~welche stets eine eigenständige Kopie des Modells beinhalteten~~, ~~enthält eine ''Simulation'' jetzt lediglich die für eine Simulation benötigten Steuerparameter und greift auf die Modelldaten ihres Szenarios zurück~~.		The new project structure of KalypsoHydrology from version 12 differs significantly from the earlier Kalypso versions. Instead of a ''Basic model'' and ''Calculation variants'', a project now consists of ''Scenarios'' and ''Simulations''. In contrast to the previous ''Calculation variants, which always contained a separate copy of the model, a simulation now contains only the control parameters required for a simulation and accesses the model data of its scenario.

	~~Aufgrund dieser geänderten Projektstruktur kann der Altprojektimport nicht vollständig automatisch ablaufen~~.		Due to this changed project structure, the old project cannot be executed completely automatically.

	~~Der einfachste Ansatz wäre~~, ~~das bisherige Basismodell als Basisszenario~~, ~~und die bisherigen Rechenvarianten als Simulationen zu importieren. Dies kann~~ in ~~der Praxis aber zu Datenverlusten führen, da nicht gewährleistet ist~~, ~~dass alle Rechenvarianten wie vorgesehen vom unveränderten Basismodell abgeleitet wurden~~. ~~Wurden an den Rechenvarianten nachträglich Veränderungen vorgenommen~~, ~~würden diese beim Altprojektimport verloren gehen, da die Simulationen keine Kopie der Modelldaten wie bisher enthalten~~. ~~Der Anwender muss daher letztendlich entscheiden, welche Modellvariante als neues Basisszenario übernommen werden soll~~. ~~Dies findet~~ in ~~mehreren~~, ~~im Folgenden beschriebenen, Schritten statt~~.		The simplest approach would be to import the previous basis model as a basal scenario, and the previous calculation variants as simulations. However, this can lead to data losses in practice, since it is not guaranteed that all rake variants were derived from the unchanged basic model as intended. If changes were made to the rake variants, they would be lost in the old project simulation because the simulations do not contain a copy of the model data as before. The user must ultimately decide which model variant is to be adopted as a new basic scenario. This takes place in several steps, described in the following.
	[[File:Hydrology_Projectconversion_example.png\|250px\|thumb\|''~~Beipielstruktur nach dem Altprojektimport~~'']]		[[File:Hydrology_Projectconversion_example.png\|250px\|thumb\|''Example structure according to the old project import'']]
	~~Zuerst werden~~, ~~um Datenverluste zu vermeiden~~, ~~über das Altprojekt aus allen bisherigen Rechenvarianten eigenständige Szenarien mit jeweils einer Simulationsrechnung~~ (~~entspricht der alten Rechenvariante~~) ~~erstellt~~. ~~Diese können~~ (~~und sollten~~) ~~nach Abschluss des Altprojektimports durch den Anwender wieder zusammengeführt werden~~. ~~Der Anwender muss dabei entscheiden~~, ~~welche Modellversion (also welches automatisch aus den Rechenvarianten angelegte Szenario~~) ~~als Basisszanario zu verwenden ist~~.		First, in order to avoid data losses, independent scenarios with a simulation calculation (corresponding to the old calculation variant) are generated from the old project variants. These can (and should) be merged again after completion of the old project by the user. The user must decide which model version (that is, which scenario created automatically from the computational variants) is to be used as the basic scenario.

	~~Siehe hierzu auch~~ (~~siehe Abbildung~~ [[:File:Hydrology_Projectconversion_example.png\|''~~Beipielstruktur nach dem Altprojektimport~~'']]). ~~Im Bild sieht man ein Beispiel~~, ~~welches aus einem Basismodell mit zwei Rechenvarianten~~ (~~namens~~ ''~~Langzeitsimulation~~'' ~~und~~ ''~~Kurzzeitsimulation~~'') ~~entstanden ist~~. ~~Diese wurden als Basisszenario mit zwei Unterszenarien importiert~~. ~~Jedes der Unterszenarien enthält eine Simulationsdefinition gleichen Namens~~.		See also (see Figure [[:File:Hydrology_Projectconversion_example.png\|'' Example structure after the old project import'']]). The picture shows an example, which was created from a basic model with two types of variants (called ''Long-term simulation'' and ''Short-term simulation''). These were imported as a base scenario with two sub-scenarios. Each sub-scenario contains a simulation definition of the same name.

			== Combine Scenarios ==
			[[File:Hydrology_Projectconversion_mergeScenarios_menu.png\|250px\|thumb\|right\|Werkzeug ''Combine Scenarios'']]
			When combining scenarios, the simulation definitions of one or more scenarios are transferred to a target scenario. The model data of the target scenario remains unchanged, i.e. The simulation definitions are applied to these model data. The procedure is as follows:

			Activate the ''Merge Scenarios'' tool from the scenario view context menu (see [[:File:Hydrology_Projectconversion_mergeScenarios_menu.png\| ''Merge tool scenarios'']]).
	~~== Szenarien Zusammenführen ==~~
	~~[[File:Hydrology_Projectconversion_mergeScenarios_menu.png\|250px\|thumb\|right\|Werkzeug~~ ''~~Szenarien zusammenführen~~'']]
	Beim Zusammenführen von Szenarien werden die Simulationsdefinitionen eines oder mehrerer Szenarien in ein Zielszenario übertragen. Die Modelldaten des Zielszenarios bleiben unverändert, d.h. die Simulationsdefinitionen werden auf diese Modelldaten angewandt. Es wird wie folgt vorgegangen:

	~~Aktivieren Sie das Werkzeug ''Szenarien zusammenführen'' über das Kontextmenü der Szenarioansicht~~ (~~siehe auch~~ [[:File:Hydrology_Projectconversion_mergeScenarios_menu.png\| ~~Werkzeug~~ ''~~Szenarien zusammenführen~~'']])

	{{Clear}}		{{Clear}}
	[[File:Hydrology_Projectconversion_mergeScenarios_dialog.png\|300px\|thumb\|~~Dialog~~ ''~~Szenarien zusammenführen~~'' ~~mit Ergebnis des Szenarienvergleichs~~]]		[[File:Hydrology_Projectconversion_mergeScenarios_dialog.png\|300px\|thumb\|Dialogue ''Combining scenarios '' with the results of the scenario comparison]]

	~~Im folgenden~~ [[:File:Hydrology_Projectconversion_mergeScenarios_dialog.png\|~~Dialog~~]] ~~werden die Szenarien ausgewählt, deren Simulation~~ in ~~das Zielszenario übernommen werden sollen. Das Zielszenario ist~~ ''~~fett~~'' ~~dargestellt und kann nicht ausgewählt werden~~. ~~Beim Abschluss des Dialogs werden alle in den gewählten Szenarien vorliegenden Simulationsdefinitionen~~ in ~~das Zielszenario kopiert und dort gespeichert~~. ~~Werden die ursprünglichen Szenarien nicht mehr benötigt~~, ~~können diese mit der Option~~ ''~~Importierte Szenarien löschen~~'' ~~gleichzeitig gelöscht werden~~.		The following [[:File:Hydrology_Projectconversion_mergeScenarios_dialog.png\|Dialogue]] is used to select the scenarios whose simulation is to be transferred to the target scenario. The target scenario is displayed in ''Bold'' and can not be selected. When the dialogue is completed, all simulation definitions in the selected scenarios are copied to the target scenario and stored there. If the original scenarios are no longer required, they can be deleted at the same time with the option ''Delete imported scenarios''.

	{{Clear}}		{{Clear}}

	== ~~Vergleichen der Szenariendaten~~ ==		== Compare the scenario data ==

	Vor dem Zusammenführen sollte der Anwender entscheiden, welches Modellversion (also welches automatisch aus den Rechenvarianten angelegte Szenario) zu verwenden ist, da diese für alle zukünftigen Simulationen verwendet wird. Um die Entscheidung zu vereinfachen wurde ein zusätzliches Werkzeug zum Vergleichen von Szenarien integriert.

	Hierzu werden zunächst mehrere Szenarien in der ''Szenarien-''Ansicht selektiert und dann mit dem rechten Maustaste das ''Szenarien vergleichen'' gestartet. Hierbei öffnet sich automatisch ein neuer Abfragefenster aus dem der ''Referenzszenario'' ausgewählt wird. Mit ''OK'' wird der Szenario vergleich gestartet. Im Anschluss öffnet sich automatisch eine Excel-Tabelle mit mehreren Tabellenblättern. Pro Blatt werden die verglichenen Parameter einer Gruppe (z.B. Knoten, Strang, Teileinzugsgebiet, Landnutzung, usw.) pro Szenario dokumentiert. Parameter, die von dem Referenzszenario abweichen werden rot markiert. Die Excel-Tabelle wird beim Öffnen automatisch in dem Temp-Verzeichnis des Rechners gespeichert.

	~~Nach dem Zusammenführen der Szenarien empfiehlt sich zum Abschluss des Altprojektimports~~, ~~aus dem gewählten Szenario ein eigenständiges Projekt über das Werkzeug [[Kalibrierung/Übernahme_als_Basisszanrio/hydrology/de\| als Basisszenario übernehmen]] zu erstellen~~.		Before merging, the user should decide which model version (that is, which scenario created automatically from the computational variants) to use, as this is used for all future simulations. To simplify the decision, an additional tool for comparing scenarios was integrated.

			To do this, several scenarios are selected in the ''Scenarios''- view and then the ''Scenarios comparison'' is started with the right mouse button. A new query window opens from which the ''Reference scenario'' is selected. Click ''OK'' to start the comparison scenario. An Excel spreadsheet with several spreadsheets opens automatically. For each sheet, the compared parameters of a group (for example Node, Strand, Inflow area, Land use, etc.) are documented per scenario. Parameters that differ from the reference scenario are marked in red. The Excel table is automatically saved in the Temp directory of the computer when it is opened.
			After combining the scenarios, it is recommended to create an independent project from the selected scenario using the tool as the basic scenario.

	{{Clear}}		{{Clear}}
	[[Category:Hydrology/en]]		[[Category:Hydrology/en]]
	{{Languages\|Kalibrierung/Szenario Vergleich/hydrology}}		{{Languages\|Kalibrierung/Szenario Vergleich/hydrology}}

Sandra at 16:33, 8 February 2017

2017-02-08T16:33:13Z

@@ Line 1: / Line 1: @@
 == Scenario Comparison ==
-siehe [[Zusammenführen_von_Szenarien/Altprojekt/hydrology/de#Vergleichen der Szenariendaten|Szenario Vergleich]]
+= Zusammenführen von Szenarien =
-<br />
 {{Clear}}
 [[Category:Hydrology/en]]
 {{Languages|Kalibrierung/Szenario Vergleich/hydrology}}

BhawaniRegmi: Created page with "== Scenario Comparison == siehe Szenario Vergleich
{{Clear}} [[Category:Hydro..."

2016-10-21T17:37:58Z

Created page with "== Scenario Comparison == siehe Szenario Vergleich <br /> {{Clear}} [[Category:Hydro..."

New page

== Scenario Comparison ==

siehe [[Zusammenführen_von_Szenarien/Altprojekt/hydrology/de#Vergleichen der Szenariendaten|Szenario Vergleich]]
<br />

{{Clear}}
[[Category:Hydrology/en]]
{{Languages|Kalibrierung/Szenario Vergleich/hydrology}}

Calibration/ScenarioComparison/hydrology/en - Revision history

BhawaniRegmi: /* Combination from Scenarios */

BhawaniRegmi: /* Compare the scenario data */

BhawaniRegmi: /* Combine Scenarios */

BhawaniRegmi: /* Combine Scenarios */

BhawaniRegmi: /* Combine Scenarios */

BhawaniRegmi: /* Combine Scenarios */

BhawaniRegmi: /* Combine Scenarios */

BhawaniRegmi: /* Zusammenführen von Szenarien */

Sandra at 16:33, 8 February 2017

BhawaniRegmi: Created page with "== Scenario Comparison == siehe Szenario Vergleich {{Clear}} [[Category:Hydro..."

BhawaniRegmi: Created page with "== Scenario Comparison == siehe Szenario Vergleich
{{Clear}} [[Category:Hydro..."