Demo Breach Iterate Project - Revision history

Frank@tygron.nl at 09:38, 10 March 2026

2026-03-10T09:38:16Z

← Older revision		Revision as of 09:38, 10 March 2026
Line 145:		Line 145:
	*[[Iteration Overlay]]		*[[Iteration Overlay]]
	*[[Indicator]]		*[[Indicator]]
	*[[Number of Simulation Iterations]]		*[[Simulation Core\|Number of Simulation Iterations]]
	}}		}}

Frank@tygron.nl: /* Template Excel Panels */

2026-03-10T09:37:59Z

Template Excel Panels

← Older revision		Revision as of 09:37, 10 March 2026
Line 143:		Line 143:
	*[[Combo Overlay]]		*[[Combo Overlay]]
	*[[Rainfall Overlay]]		*[[Rainfall Overlay]]
	*[[Iteration ~~Collector~~]]		*[[Iteration Overlay]]
	*[[Indicator]]		*[[Indicator]]
	*[[Number of Simulation Iterations]]		*[[Number of Simulation Iterations]]
	}}		}}

Frank@tygron.nl: /* Template Excel Panels */

2026-03-10T09:37:34Z

Template Excel Panels

← Older revision		Revision as of 09:37, 10 March 2026
Line 141:		Line 141:
	\|seealso=		\|seealso=
	* [[List of Demo Projects]]		* [[List of Demo Projects]]
			*[[Combo Overlay]]
			*[[Rainfall Overlay]]
			*[[Iteration Collector]]
			*[[Indicator]]
			*[[Number of Simulation Iterations]]
	}}		}}

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

2026-01-26T13:04:56Z

← Older revision		Revision as of 13:04, 26 January 2026
Line 1:		Line 1:
			{{technical\|type=section}}

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

Rudolf@tygron.nl at 12:50, 24 December 2025

2025-12-24T12:50:27Z

← Older revision		Revision as of 12:50, 24 December 2025
Line 8:		Line 8:

	==What does it do==		==What does it do==
	Running a water overlay calculation in ~~Tygron~~ is done by setting the parameters at the start of your simulation. However, by using the iterative option, you can allow parameters to change during the simulation based on a formula. For example, the breach can grow according to a defined formula. In this demo, the formula is that the breach grows by 2 meters per iteration step, with an initial breach width of 3 meters. This formula is chosen to demonstrate how the method works, not to model a realistic breach growth.		Running a water overlay calculation in the {{software}} is done by setting the parameters at the start of your simulation. However, by using the iterative option, you can allow parameters to change during the simulation based on a formula. For example, the breach can grow according to a defined formula. In this demo, the formula is that the breach grows by 2 meters per iteration step, with an initial breach width of 3 meters. This formula is chosen to demonstrate how the method works, not to model a realistic breach growth.

	===Setting the breach width for each iteration step===		===Setting the breach width for each iteration step===
Line 15:		Line 15:
	[[File:Steps.png\|thumb]]		[[File:Steps.png\|thumb]]

	A breach is modeled as an ~~area~~ in ~~Tygron~~. This area has an attribute called BREACH_WIDTH. The value of this attribute needs to be updated after each iteration step. This can be done using an Excel panel. In the demo, this panel is called ''Update Attribute Breach Width (Before): Breach.''		A breach is modeled as an [[Area]] in the {{software}}. This area has an attribute called BREACH_WIDTH. The value of this attribute needs to be updated after each iteration step. This can be done using an Excel panel. In the demo, this panel is called ''Update Attribute Breach Width (Before): Breach.''

	When you download this panel via the Debug Excel sheet, you can see how this is implemented. In the Excel file, cell B5 contains the formula:		When you download this panel via the Debug Excel sheet, you can see how this is implemented. In the Excel file, cell B5 contains the formula:
Line 21:		Line 21:
	This formula states that the breach starts with a width of 3 meters and grows by 2 meters with each iteration step. As mentioned, this is not a realistic formula, but it demonstrates the mechanism. You can replace it with your own formula if needed.		This formula states that the breach starts with a width of 3 meters and grows by 2 meters with each iteration step. As mentioned, this is not a realistic formula, but it demonstrates the mechanism. You can replace it with your own formula if needed.

	To do this, it is important to understand that the value in cell B3 is retrieved using a Query. This query provides the value used in the calculation. In this case, the SELECT_ITERATION query retrieves the current iteration step. The formula in B5 multiplies this value by two and adds 3 meters. The resulting value is then written to the BREACH_WIDTH attribute. This happens because the cell has the name UPDATE_AREA_BREACH_WIDTH_WHERE_AREA_IS_ID, which is a ~~Tygron~~ query that updates the ~~attribute~~. In the next iteration step, the updated BREACH_WIDTH is used.		To do this, it is important to understand that the value in cell B3 is retrieved using a Query. This query provides the value used in the calculation. In this case, the SELECT_ITERATION query retrieves the current iteration step. The formula in B5 multiplies this value by two and adds 3 meters. The resulting value is then written to the BREACH_WIDTH attribute. This happens because the cell has the name UPDATE_AREA_BREACH_WIDTH_WHERE_AREA_IS_ID, which is a [[TQL]] query that updates the [[Attribute]]. In the next iteration step, the updated BREACH_WIDTH is used.

	===Store results for the iteration steps in combo overlays===		===Store results for the iteration steps in combo overlays===
Line 37:		Line 37:

	===Setting the time for your simulation===		===Setting the time for your simulation===
	The simulation time settings also require some explanation. The total duration of the simulation is set in the wizard. ~~Tygron then divides this~~ total time over the specified number of iteration steps.		The simulation time settings also require some explanation. The total duration of the simulation is set in the wizard. This total time is divided over the specified number of iteration steps.

	This is done using two attributes of the Flooding Overlay: PARTIAL_START and PARTIAL_END. These attributes define which part of the total simulation time is executed. During the simulation, these attributes are updated using another Excel sheet, called the iterator.		This is done using two attributes of the Flooding Overlay: PARTIAL_START and PARTIAL_END. These attributes define which part of the total simulation time is executed. During the simulation, these attributes are updated using another Excel sheet, called the iterator.

Rudolf@tygron.nl at 12:48, 24 December 2025

2025-12-24T12:48:59Z

← Older revision		Revision as of 12:48, 24 December 2025
Line 2:		Line 2:
	\| title=Demo Iteration Flood		\| title=Demo Iteration Flood
	\| demographic=hydrologists and other water experts		\| demographic=hydrologists and other water experts
	\| showcases=the [[Flooding Overlay]] in a iteration mode		\| showcases=the [[Flooding Overlay]] in an iteration mode
	\| image=Demo_breach_iterate-iteration_base_typology.gif		\| image=Demo_breach_iterate-iteration_base_typology.gif
	\| description=The demo show the [[Simulation Core\|iteration]] functionality in combination with template excels that can change the width of a breach. It also records the object width and flow output between iterations using additional Template Excel panels, as well as a Text Template panel that plots these values in a chart.		\| description=The demo show the [[Simulation Core\|iteration]] functionality in combination with template excels that can change the width of a breach. It also records the object width and flow output between iterations using additional Template Excel panels, as well as a Text Template panel that plots these values in a chart.

Ward@tygron.nl at 10:09, 18 December 2025

2025-12-18T10:09:00Z

@@ Line 6: / Line 6: @@
 | description=The demo show the [[Simulation Core|iteration]] functionality in combination with template excels that can change the width of a breach. It also records the object width and flow output between iterations using additional Template Excel panels, as well as a Text Template panel that plots these values in a chart.
 }}
 ==What does it do==
@@ Line 58: / Line 51: @@
 ===Visualization of the simulation===
 Finally, the visualization of the simulation. When you inspect the Flooding Overlay, you will see that only the results of the last simulation step are visible. To ensure that the results of all iteration steps can still be viewed, another overlay is needed: the Iteration Collector. This overlay stores the results after each iteration step.
 ==Setup of the Demo Project==

Ward@tygron.nl at 10:08, 18 December 2025

2025-12-18T10:08:15Z

← Older revision		Revision as of 10:08, 18 December 2025
Line 30:		Line 30:
	To do this, it is important to understand that the value in cell B3 is retrieved using a Query. This query provides the value used in the calculation. In this case, the SELECT_ITERATION query retrieves the current iteration step. The formula in B5 multiplies this value by two and adds 3 meters. The resulting value is then written to the BREACH_WIDTH attribute. This happens because the cell has the name UPDATE_AREA_BREACH_WIDTH_WHERE_AREA_IS_ID, which is a Tygron query that updates the attribute. In the next iteration step, the updated BREACH_WIDTH is used.		To do this, it is important to understand that the value in cell B3 is retrieved using a Query. This query provides the value used in the calculation. In this case, the SELECT_ITERATION query retrieves the current iteration step. The formula in B5 multiplies this value by two and adds 3 meters. The resulting value is then written to the BREACH_WIDTH attribute. This happens because the cell has the name UPDATE_AREA_BREACH_WIDTH_WHERE_AREA_IS_ID, which is a Tygron query that updates the attribute. In the next iteration step, the updated BREACH_WIDTH is used.

			===Store results for the iteration steps in combo overlays===
	A requirement for splitting a simulation into steps is that, at the end of each step, the results must be stored so they can be used as input for the next step. In this simulation, the water level is crucial, as well as the flow velocity.		A requirement for splitting a simulation into steps is that, at the end of each step, the results must be stored so they can be used as input for the next step. In this simulation, the water level is crucial, as well as the flow velocity.

Line 42:		Line 43:
	In the same way, two additional combo overlays are created: one for flow velocity in the x-direction and one for the y-direction. These are also used as initial values for the simulation.		In the same way, two additional combo overlays are created: one for flow velocity in the x-direction and one for the y-direction. These are also used as initial values for the simulation.

			===Setting the time for your simulation===
	The simulation time settings also require some explanation. The total duration of the simulation is set in the wizard. Tygron then divides this total time over the specified number of iteration steps.		The simulation time settings also require some explanation. The total duration of the simulation is set in the wizard. Tygron then divides this total time over the specified number of iteration steps.

Line 54:		Line 56:
	for cell G9: UPDATE_GRID_PARTIAL_END_SEC_WHERE_GRIDTYPE_IS_FLOODING		for cell G9: UPDATE_GRID_PARTIAL_END_SEC_WHERE_GRIDTYPE_IS_FLOODING

			===Visualization of the simulation===
	Finally, the visualization of the simulation. When you inspect the Flooding Overlay, you will see that only the results of the last simulation step are visible. To ensure that the results of all iteration steps can still be viewed, another overlay is needed: the Iteration Collector. This overlay stores the results after each iteration step.		Finally, the visualization of the simulation. When you inspect the Flooding Overlay, you will see that only the results of the last simulation step are visible. To ensure that the results of all iteration steps can still be viewed, another overlay is needed: the Iteration Collector. This overlay stores the results after each iteration step.

Ward@tygron.nl: /* Steps */

2025-12-18T10:05:55Z

Steps

← Older revision		Revision as of 10:05, 18 December 2025
Line 17:		Line 17:
	Running a water overlay calculation in Tygron is done by setting the parameters at the start of your simulation. However, by using the iterative option, you can allow parameters to change during the simulation based on a formula. For example, the breach can grow according to a defined formula. In this demo, the formula is that the breach grows by 2 meters per iteration step, with an initial breach width of 3 meters. This formula is chosen to demonstrate how the method works, not to model a realistic breach growth.		Running a water overlay calculation in Tygron is done by setting the parameters at the start of your simulation. However, by using the iterative option, you can allow parameters to change during the simulation based on a formula. For example, the breach can grow according to a defined formula. In this demo, the formula is that the breach grows by 2 meters per iteration step, with an initial breach width of 3 meters. This formula is chosen to demonstrate how the method works, not to model a realistic breach growth.

	===~~Steps~~===		===Setting the breach width for each iteration step===
	With iterative calculation, you essentially split your simulation into a number of steps. In our example, the breach should grow after each step. To model this, we first need to identify where the breach width is defined.		With iterative calculation, you essentially split your simulation into a number of steps. In our example, the breach should grow after each step. To model this, we first need to identify where the breach width is defined.

Line 55:		Line 55:

	Finally, the visualization of the simulation. When you inspect the Flooding Overlay, you will see that only the results of the last simulation step are visible. To ensure that the results of all iteration steps can still be viewed, another overlay is needed: the Iteration Collector. This overlay stores the results after each iteration step.		Finally, the visualization of the simulation. When you inspect the Flooding Overlay, you will see that only the results of the last simulation step are visible. To ensure that the results of all iteration steps can still be viewed, another overlay is needed: the Iteration Collector. This overlay stores the results after each iteration step.


	==Setup of the Demo Project==		==Setup of the Demo Project==

Ward@tygron.nl at 10:04, 18 December 2025

2025-12-18T10:04:34Z

← Older revision		Revision as of 10:04, 18 December 2025
Line 13:		Line 13:

	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. However, on the basis of this demo project, it should also be possible to calculate other calculations iteratively.

			==What does it do==
			Running a water overlay calculation in Tygron is done by setting the parameters at the start of your simulation. However, by using the iterative option, you can allow parameters to change during the simulation based on a formula. For example, the breach can grow according to a defined formula. In this demo, the formula is that the breach grows by 2 meters per iteration step, with an initial breach width of 3 meters. This formula is chosen to demonstrate how the method works, not to model a realistic breach growth.

			===Steps===
			With iterative calculation, you essentially split your simulation into a number of steps. In our example, the breach should grow after each step. To model this, we first need to identify where the breach width is defined.

			[[File:Steps.png\|thumb]]

			A breach is modeled as an area in Tygron. This area has an attribute called BREACH_WIDTH. The value of this attribute needs to be updated after each iteration step. This can be done using an Excel panel. In the demo, this panel is called ''Update Attribute Breach Width (Before): Breach.''

			When you download this panel via the Debug Excel sheet, you can see how this is implemented. In the Excel file, cell B5 contains the formula:
			3 + B3 * 2.
			This formula states that the breach starts with a width of 3 meters and grows by 2 meters with each iteration step. As mentioned, this is not a realistic formula, but it demonstrates the mechanism. You can replace it with your own formula if needed.

			To do this, it is important to understand that the value in cell B3 is retrieved using a Query. This query provides the value used in the calculation. In this case, the SELECT_ITERATION query retrieves the current iteration step. The formula in B5 multiplies this value by two and adds 3 meters. The resulting value is then written to the BREACH_WIDTH attribute. This happens because the cell has the name UPDATE_AREA_BREACH_WIDTH_WHERE_AREA_IS_ID, which is a Tygron query that updates the attribute. In the next iteration step, the updated BREACH_WIDTH is used.

			A requirement for splitting a simulation into steps is that, at the end of each step, the results must be stored so they can be used as input for the next step. In this simulation, the water level is crucial, as well as the flow velocity.

			This is achieved using Combo Overlays. The results at the end of a step are stored in a Combo Overlay and then read at the start of the next step.

			To effectively copy the water level at the end of a step, the combo overlay contains a formula that takes the result from iteration step x of the flooding overlay, except for the first step.

			This is a good moment to mention that numbering starts at 0. So if you have 4 iteration steps, they are numbered from 0 to 3.

			To ensure that the combo overlay is used in your simulation, you specify in the wizard that the combo overlay Combo Surface is used as the input value for the initial water level when running the simulation.

			In the same way, two additional combo overlays are created: one for flow velocity in the x-direction and one for the y-direction. These are also used as initial values for the simulation.

			The simulation time settings also require some explanation. The total duration of the simulation is set in the wizard. Tygron then divides this total time over the specified number of iteration steps.

			This is done using two attributes of the Flooding Overlay: PARTIAL_START and PARTIAL_END. These attributes define which part of the total simulation time is executed. During the simulation, these attributes are updated using another Excel sheet, called the iterator.

			In the iterator, the total number of iterations is retrieved, in this case 20. The previous step is also retrieved, here step 19. From this, the progress of the simulation is calculated as a percentage, which is 95 percent in this case. In the wizard, the total simulation time was set to 4 hours, or 14,400 seconds.

			This means that the start of this iteration step is at second 13,680, which is 95 percent of 14,400 seconds, and it ends at second 14,400.

			These values are written back to the PARTIAL_START and PARTIAL_END attributes of the Flooding overlay:
			for cell F9: UPDATE_GRID_PARTIAL_START_SEC_WHERE_GRIDTYPE_IS_FLOODING
			for cell G9: UPDATE_GRID_PARTIAL_END_SEC_WHERE_GRIDTYPE_IS_FLOODING

			Finally, the visualization of the simulation. When you inspect the Flooding Overlay, you will see that only the results of the last simulation step are visible. To ensure that the results of all iteration steps can still be viewed, another overlay is needed: the Iteration Collector. This overlay stores the results after each iteration step.


	==Setup of the Demo Project==		==Setup of the Demo Project==