Demo Iteration Project - Revision history

Frank@tygron.nl: /* Exploring the results */

2026-07-14T11:36:56Z

Exploring the results

← Older revision		Revision as of 11:36, 14 July 2026
Line 94:		Line 94:
	* Iteration Infil Speed: The infiltration speed in meters per day		* Iteration Infil Speed: The infiltration speed in meters per day
	* Iteration Rain: The total amount of rainfall up to that point in the simulation in meters.		* Iteration Rain: The total amount of rainfall up to that point in the simulation in meters.
	* Iteration ~~grondtable~~: The groundwater level in m + datum.		* Iteration ground table: The groundwater level in m + datum.
	When the iteration Infil speed is viewed, it becomes clear that the two different soil types (BOFEK IDs) give a different result in the infiltration speed.		When the iteration Infil speed is viewed, it becomes clear that the two different soil types (BOFEK IDs) give a different result in the infiltration speed.

Frank@tygron.nl: /* Indicator */

2026-07-14T11:36:46Z

Indicator

← Older revision		Revision as of 11:36, 14 July 2026
Line 82:		Line 82:

	==Indicator==		==Indicator==
	The indicator sets the start and end times for the rainfall overlay iteration steps. It uses queries like <code>SELECT_ITERATIONS_WHERE</code> and <code>~~SELECT_ATTRIBUUT_WHERE_NAME_IS_RAIN_M_AND_OVERLAY_IS_10_AND_RELATION_IS_WEATHER_AND_INDEX_IS_2~~</code> to determine the number of steps and total simulation time. The <code>UPDATE_OVERLAY_PARTIAL_START_SEC_WHERE_OVERLAY_IS_3</code> and <code>UPDATE_OVERLAY_PARTIAL_END_SEC_WHERE_OVERLAY_IS_3</code> queries then adjust the timing for the next step, identified via <code>SELECT_ITERATION_WHERE</code>. Fraction Start and End define these as fractions of the total simulation time.		The indicator sets the start and end times for the rainfall overlay iteration steps. It uses queries like <code>SELECT_ITERATIONS_WHERE</code> and <code> SELECT_ATTRIBUTE_WHERE_NAME_IS_RAIN_M_AND_OVERLAY_IS_10_AND_RELATION_IS_WEATHER_AND_INDEX_IS_2</code> to determine the number of steps and total simulation time. The <code>UPDATE_OVERLAY_PARTIAL_START_SEC_WHERE_OVERLAY_IS_3</code> and <code>UPDATE_OVERLAY_PARTIAL_END_SEC_WHERE_OVERLAY_IS_3</code> queries then adjust the timing for the next step, identified via <code>SELECT_ITERATION_WHERE</code>. Fraction Start and End define these as fractions of the total simulation time.

	==Number of Iterations==		==Number of Iterations==

Frank@tygron.nl at 11:36, 14 July 2026

2026-07-14T11:36:02Z

Maxim@tygron.com at 09:32, 9 July 2026

2026-07-09T09:32:59Z

← Older revision		Revision as of 09:32, 9 July 2026
Line 12:		Line 12:
	The demo project simulates a Dutch polder to demonstrate how rainfall infiltration can be modeled using the [[Simulation Core\|iteration]] option.		The demo project simulates a Dutch polder to demonstrate how rainfall infiltration can be modeled using the [[Simulation Core\|iteration]] option.

	We want the speed at which rainwater infiltrates to depend on the degree of saturation of the soil. By dividing the rain event into several iteration steps, we can adjust the infiltration rate for each iteration step based on the degree of saturation of the soil. ~~In this way, infiltration can be calculated in~~ a more ~~realistic way~~.		We want the speed at which rainwater infiltrates to depend on the degree of saturation of the soil. By dividing the rain event into several iteration steps, we can adjust the infiltration rate for each iteration step based on the degree of saturation of the soil. This approach allows for a more accurate calculation of infiltration based on soil saturation levels.

	The purpose of this demo project is to clarify how an iterative calculation can be made. In this case, the infiltration of water during and after a precipitation event was chosen. This demo project can also serve as a basis for performing other iterative calculations.		The purpose of this demo project is to clarify how an iterative calculation can be made. In this case, the infiltration of water during and after a precipitation event was chosen. This demo project can also serve as a basis for performing other iterative calculations.
Line 95:		Line 95:
	* Iteration Rain: The total amount of rainfall up to that point in the simulation in meters.		* Iteration Rain: The total amount of rainfall up to that point in the simulation in meters.
	* Iteration grondtable: The groundwater level in m + datum.		* Iteration grondtable: The groundwater level in m + datum.
	When the iteration ~~ifil~~ speed is viewed, it becomes clear that the two different soil types (BOFEK IDs) give a different result in the infiltration speed.		When the iteration Infil speed is viewed, it becomes clear that the two different soil types (BOFEK IDs) give a different result in the infiltration speed.

	==Notes and Limitations==		==Notes and Limitations==
Line 104:		Line 104:
	In a standard calculation, the precipitation event is executed in a single step. In an iterative calculation, on the other hand, the event is split into multiple time steps, for example 10. After each iteration step, the data is stored and prepared for the next step. Rounding occurs during this process, which can affect the accuracy of the results.<br>		In a standard calculation, the precipitation event is executed in a single step. In an iterative calculation, on the other hand, the event is split into multiple time steps, for example 10. After each iteration step, the data is stored and prepared for the next step. Rounding occurs during this process, which can affect the accuracy of the results.<br>
	The water levels are stored internally in a 64-bit format, which provides high precision with 12 decimal places. However, the results are displayed in a 32-bit format, which has an accuracy of 6 decimal places. In the iterative calculation, the 32-bit result is used. This causes small rounding differences between the results. The more iteration steps there are, the more often this rounding occurs and the larger the deviation can become.<br>		The water levels are stored internally in a 64-bit format, which provides high precision with 12 decimal places. However, the results are displayed in a 32-bit format, which has an accuracy of 6 decimal places. In the iterative calculation, the 32-bit result is used. This causes small rounding differences between the results. The more iteration steps there are, the more often this rounding occurs and the larger the deviation can become.<br>
	~~At this point, these~~ differences are ~~considered negligible~~. If ~~necessary~~, measures can be ~~taken~~ to ~~solve this problem~~.		These rounding differences are minimal. If required, additional measures can be implemented to further increase precision.

	{{article end		{{article end

Frank@tygron.nl at 09:18, 8 July 2026

2026-07-08T09:18:24Z

← Older revision		Revision as of 09:18, 8 July 2026
Line 14:		Line 14:
	We want the speed at which rainwater infiltrates to depend on the degree of saturation of the soil. By dividing the rain event into several iteration steps, we can adjust the infiltration rate for each iteration step based on the degree of saturation of the soil. In this way, infiltration can be calculated in a more realistic way.		We want the speed at which rainwater infiltrates to depend on the degree of saturation of the soil. By dividing the rain event into several iteration steps, we can adjust the infiltration rate for each iteration step based on the degree of saturation of the soil. In this way, infiltration can be calculated in a more realistic way.

	The purpose of this demo project is to clarify how an iterative calculation can be made. In this case, the infiltration of water during and after a precipitation event was chosen. ~~However, on the basis of this~~ demo project~~, it should~~ also ~~be possible to calculate~~ other calculations ~~iteratively~~.		The purpose of this demo project is to clarify how an iterative calculation can be made. In this case, the infiltration of water during and after a precipitation event was chosen. This demo project can also serve as a basis for performing other iterative calculations.

	==Setup of the Demo Project==		==Setup of the Demo Project==
Line 28:		Line 28:

	===Combo Surface U and Combo Surface V===		===Combo Surface U and Combo Surface V===
	These overlays ~~say something about~~ the initial ~~velocity of the~~ surface water in x and y directions. ~~When~~ water ~~flows~~ down a slope, ~~we want to use~~ the ~~speed at which the water flows at the end~~ of an iteration step as the initial ~~speed at~~ the next ~~iteration step~~. The input grid is the result of the last calculation. ~~In the~~ formula ~~of this combo overlay, you can see that the formula is aimed at making sure that it computes with the~~ data from the previous time step, ~~unless the previous iteration step was~~ step 0~~. In that case~~, 0 is used.		These overlays define the initial surface water velocity in the X and Y directions. For water flowing down a slope, the final velocity of one iteration step becomes the initial velocity for the next. The input grid is the result of the last calculation. The formula ensures calculations use data from the previous time step, except for step 0, where a value of 0 is used.

	Make sure to check the box "previous" to make sure the [[Combo Overlay]] uses the U and V of the previous itertationstep.<br>		Make sure to check the box "previous" to make sure the [[Combo Overlay]] uses the U and V of the previous itertationstep.<br>
Line 34:		Line 34:

	===Combo Fraction and Combo Groundwater Depth===		===Combo Fraction and Combo Groundwater Depth===
	~~The purpose of the combo overlay~~ Combo Fraction and ~~the combo~~ Groundwater Depth ~~is to set the~~ input from the previous iteration step ~~to be used~~, unless ~~the previous iteration step was~~ step 0. In that case, a [[Global]] value is used. The [[Global]] DEFAULT_FRACTION is used for the saturation percentage, and the global DEFAULT_TABLE is used for the groundwater level.		Combo Fraction and Combo Groundwater Depth use input from the previous iteration step, unless it is step 0. In that case, a [[Global]] value is used. The [[Global]] DEFAULT_FRACTION is used for the saturation percentage, and the global DEFAULT_TABLE is used for the groundwater level.

	<br> The formula in the combo overlay Combo Fraction should in this case read:		<br> The formula in the combo overlay Combo Fraction should in this case read:
Line 58:		Line 58:
	When setting the rainfall overlay, the default settings can be used. The exceptions are described below.		When setting the rainfall overlay, the default settings can be used. The exceptions are described below.

	Rain Event Duration: ~~Here the~~ the total duration ~~of the calculation is specified. Later this~~ is divided into ~~different iterationsteps~~.		Rain Event Duration: Specifies the total calculation duration, which is subsequently divided into iteration steps.
	<br>Water System – Water Level: Here the initial water level and the U and V flow are set. Use the option "Advanced: Select Grid Overaly to set initial water level and also flow UV".		<br>Water System – Water Level: Here the initial water level and the U and V flow are set. Use the option "Advanced: Select Grid Overaly to set initial water level and also flow UV".
	The water level is set based on a specific overlay, which is the combo overaly Surface. Similarly, the y and x speed from the combo overlay is used as initial input.		The water level is set based on a specific overlay, which is the combo overaly Surface. Similarly, the y and x speed from the combo overlay is used as initial input.
Line 77:		Line 77:

	==Iteration Collector==		==Iteration Collector==
	The [[Iteration Overlay\|Iteration Collector]] is a type of overlay. It shows the results of each iteration step. An iteration collector needs an input overlay, in this case it is the Rainfall overlay. Of each iteration step ~~one timeframes wil be saved~~.		The [[Iteration Overlay\|Iteration Collector]] is a type of overlay. It shows the results of each iteration step. An iteration collector needs an input overlay, in this case it is the Rainfall overlay. One timeframe is saved for each iteration step.

	~~An attribute of the [[Iteration Overlay\|Iteration Collector]] is the~~ [[Iteration Overlay#Modules\|Modulus]]~~. The [[~~Iteration ~~Overlay#Modules\|Modulus]]~~ determines how many iterations ~~you store~~. By default, this is set to 1. This means that only one (the last) result of each iteration step is saved and used as a timeframe in the iteration collector. When the modulus is set to 1, every iteration is stored. When you set the modulus to 2, half of the iteration values are stored.		The [[Iteration Overlay#Modules\|Modulus]] attribute of the Iteration Collector determines how many iterations are stored. By default, this is set to 1. This means that only one (the last) result of each iteration step is saved and used as a timeframe in the iteration collector. When the modulus is set to 1, every iteration is stored. When you set the modulus to 2, half of the iteration values are stored.

	==Indicator==		==Indicator==
	~~Het doel van de~~ indicator ~~is het instellen van de~~ start ~~en eind tijd van de iteratiestap van de regenwateroverlay~~. ~~Om dit te bewerkstelligen worden een aantal~~ queries ~~uitgevoerd . Allereerst wordt bepaald hoeveel iteratiestappen zijn gekozen en hoe lang de totale simulatietijd is ingesteld. Dit gebeurd met de query~~ <code>SELECT_ITERATIONS_WHERE</code> en <code>SELECT_ATTRIBUUT_WHERE_NAME_IS_RAIN_M_AND_OVERLAY_IS_10_AND_RELATION_IS_WEATHER_AND_INDEX_IS_2</code>.~~<br><br>~~		The indicator sets the start and end times for the rainfall overlay iteration steps. It uses queries like <code>SELECT_ITERATIONS_WHERE</code> and <code>SELECT_ATTRIBUUT_WHERE_NAME_IS_RAIN_M_AND_OVERLAY_IS_10_AND_RELATION_IS_WEATHER_AND_INDEX_IS_2</code> to determine the number of steps and total simulation time. The <code>UPDATE_OVERLAY_PARTIAL_START_SEC_WHERE_OVERLAY_IS_3</code> and <code>UPDATE_OVERLAY_PARTIAL_END_SEC_WHERE_OVERLAY_IS_3</code> queries then adjust the timing for the next step, identified via <code>SELECT_ITERATION_WHERE</code>. Fraction Start and End define these as fractions of the total simulation time.
	~~Met de querys~~ <code>UPDATE_OVERLAY_PARTIAL_START_SEC_WHERE_OVERLAY_IS_3</code> en <code>UPDATE_OVERLAY_PARTIAL_END_SEC_WHERE_OVERLAY_IS_3</code> ~~worden respectievelijk de begin en eindtijd van de volgende iteratiestap bijgesteld. Om te weten wat de volgende iteratiestap is wordt de query~~ <code>SELECT_ITERATION_WHERE ~~uitgevoerd~~</code>.~~<br><br>~~
	Fraction Start ~~en Fraction End geven de start en end als fractie. Bij Start en~~ End ~~wordt dit uitgedrukt in seconden door deze fractie te vermenigvuldigen met de totale simulatietijd~~.

	==Number of Iterations==		==Number of Iterations==
	~~The~~ number of iterations ~~can be set via~~ the [[calculation panel]]~~. Here you find~~ the option ~~iteration where you can set the number of iterations~~. This is set to 1 by default.		Set the number of iterations in the [[calculation panel]] under the 'iteration' option. This is set to 1 by default.

	==Exploring the results==		==Exploring the results==
	To view the results ~~of the calculation~~, the ~~Iteration can be played everywhere~~. The following results can be seen here:		To view the results, play back the iteration sequence. The following results can be seen here:
	* Water on ground level in meters		* Water on ground level in meters
	* Iteration Fraction: The fraction of the total water storage capacity of the unsaturated zone that is filled with water in meters		* Iteration Fraction: The fraction of the total water storage capacity of the unsaturated zone that is filled with water in meters

Maxim@tygron.com at 13:04, 26 January 2026

2026-01-26T13:04:40Z

← Older revision		Revision as of 13:04, 26 January 2026
Line 1:		Line 1:
	{{~~stub~~\|~~todo~~=		{{technical\|type=section}}
	* Demo Project must be in English
	* Article must be in English, but now has a dutch paragraph
	** Dutch section ~~also includes erroneously translates TQL statements ("select attribuut")~~
	}}

	{{demo project summary		{{demo project summary

Rudolf@tygron.nl at 06:25, 13 February 2025

2025-02-13T06:25:06Z

← Older revision		Revision as of 06:25, 13 February 2025
Line 2:		Line 2:
	* Demo Project must be in English		* Demo Project must be in English
	* Article must be in English, but now has a dutch paragraph		* Article must be in English, but now has a dutch paragraph
			** Dutch section also includes erroneously translates TQL statements ("select attribuut")
	}}		}}

Rudolf@tygron.nl at 06:23, 13 February 2025

2025-02-13T06:23:58Z

← Older revision		Revision as of 06:23, 13 February 2025
Line 1:		Line 1:
	{{stub\|todo=		{{stub\|todo=
	* Demo Project must be in English		* Demo Project must be in English
			* Article must be in English, but now has a dutch paragraph
	}}		}}

Rudolf@tygron.nl at 06:18, 13 February 2025

2025-02-13T06:18:56Z

← Older revision		Revision as of 06:18, 13 February 2025
Line 1:		Line 1:
			{{stub\|todo=
			* Demo Project must be in English
			}}

	{{demo project summary		{{demo project summary
	\| title=Demo Iteration		\| title=Demo Iteration

Maxim@tygron.com at 15:53, 3 February 2025

2025-02-03T15:53:44Z

← Older revision		Revision as of 15:53, 3 February 2025
Line 1:		Line 1:
	~~{{stub\|todo=~~
	* Demo Project must be in English
	}}

	{{demo project summary		{{demo project summary
	\| title=Demo Iteration		\| title=Demo Iteration

← Older revision		Revision as of 11:36, 14 July 2026
Line 6:		Line 6:
	\| showcases=the rainfall overlay in a iteration mode		\| showcases=the rainfall overlay in a iteration mode
	\| image=Demo_iteration.jpg		\| image=Demo_iteration.jpg
	\| description=The demo ~~show~~ the [[Simulation Core\|iteration]] functionality ~~that can be used to adjust the~~ ground infiltration speed ~~using~~ a combo formula.		\| description=The demo showcases the [[Simulation Core\|iteration]] functionality for adjusting ground infiltration speed via a combo formula.
	}}		}}

Line 12:		Line 12:
	The demo project simulates a Dutch polder to demonstrate how rainfall infiltration can be modeled using the [[Simulation Core\|iteration]] option.		The demo project simulates a Dutch polder to demonstrate how rainfall infiltration can be modeled using the [[Simulation Core\|iteration]] option.

	We want the speed at which rainwater infiltrates to depend on the degree of saturation of the soil. ~~By dividing~~ the rain event into ~~several~~ iteration steps~~, we can adjust~~ the infiltration rate ~~for each iteration step~~ based on ~~the degree of~~ saturation ~~of the soil. This approach allows for a more accurate~~ calculation ~~of infiltration based on soil saturation levels~~.		We want the speed at which rainwater infiltrates to depend on the degree of saturation of the soil. Dividing the rain event into multiple iteration steps allows the infiltration rate to be adjusted based on soil saturation, increasing calculation accuracy.

	The purpose of this demo project is to clarify how an iterative calculation can be made. In this case, the infiltration of water during and after a precipitation event was chosen. This demo project can also serve as a basis for performing other iterative calculations.		The purpose of this demo project is to clarify how an iterative calculation can be made. In this case, the infiltration of water during and after a precipitation event was chosen. This demo project can also serve as a basis for performing other iterative calculations.
Line 30:		Line 30:
	These overlays define the initial surface water velocity in the X and Y directions. For water flowing down a slope, the final velocity of one iteration step becomes the initial velocity for the next. The input grid is the result of the last calculation. The formula ensures calculations use data from the previous time step, except for step 0, where a value of 0 is used.		These overlays define the initial surface water velocity in the X and Y directions. For water flowing down a slope, the final velocity of one iteration step becomes the initial velocity for the next. The input grid is the result of the last calculation. The formula ensures calculations use data from the previous time step, except for step 0, where a value of 0 is used.

	Make sure to check the box "previous" to make sure the [[Combo Overlay]] uses the U and V of the previous ~~itertationstep~~.<br>		Make sure to check the box "previous" to make sure the [[Combo Overlay]] uses the U and V of the previous iteration step.<br>
	The formula in the combo overlay should in this case read: <code>IF(EQ(ITERATION, 0), 0, A)</code>		The formula in the combo overlay should in this case read: <code>IF(EQ(ITERATION, 0), 0, A)</code>

Line 59:		Line 59:

	Rain Event Duration: Specifies the total calculation duration, which is subsequently divided into iteration steps.		Rain Event Duration: Specifies the total calculation duration, which is subsequently divided into iteration steps.
	<br>Water System – Water Level: Here the initial water level and the U and V flow are set. Use the option "Advanced: Select Grid ~~Overaly~~ to set initial water level and also flow UV".		<br>Water System – Water Level: Here the initial water level and the U and V flow are set. Use the option "Advanced: Select Grid overlay to set initial water level and also flow UV".
	The water level is set based on a specific overlay, which is the combo ~~overaly~~ Surface. Similarly, the y and x speed from the combo overlay is used as initial input.		The water level is set based on a specific overlay, which is the combo overlay Surface. Similarly, the y and x speed from the combo overlay is used as initial input.
	<br>Groundwater: Initialize the groundwater level using the Groundwater Depth combo overlay.		<br>Groundwater: Initialize the groundwater level using the Groundwater Depth combo overlay.