Demo Breach Iterate Project - Revision history

Frank@tygron.nl at 14:59, 14 July 2026

2026-07-14T14:59:54Z

Maxim@tygron.com at 12:51, 8 July 2026

2026-07-08T12:51:40Z

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.

← Older revision		Revision as of 14:59, 14 July 2026
Line 6:		Line 6:
	\| showcases=the [[Flooding Overlay]] in an 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 shows 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.
	}}		}}

Line 77:		Line 77:
	These overlays define the initial surface water velocity in the X and Y directions. For water flowing down a slope, the velocity at the end of one iteration serves as 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, unless it is 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 velocity at the end of one iteration serves as 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, unless it is step 0. In that case, 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 itertation 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 87:		Line 87:

	==Flooding Overlay==		==Flooding Overlay==
	When ~~configurating~~ the flooding overlay, the default settings can be used. The exceptions are described below.		When configuring the flooding 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 iteration steps.		Rain Event Duration: Here the total duration of the calculation is specified. Later this is divided into different 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 Overlay 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 overlay 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.
Line 124:		Line 124:
	The project contains several template panels, three of which are excel panels and one is a text panel. These template panels are all performed on breach areas, of which only one is present in this project.		The project contains several template panels, three of which are excel panels and one is a text panel. These template panels are all performed on breach areas, of which only one is present in this project.

	The 'Update Attribute Breach Width (Before)' panel runs at the start of each iteration (indicated by the BEFORE setting). This Template Excel obtains the current iteration using <code>SELECT_ITERATION_WHERE_</code>, and updates the BREACH_WIDTH area to <code>3 + iteration</code> using ~~UPDATE_AREA_BREACH_WIDTH_WHERE_NAME_IS_BREACH_WIDTH_AND_AREA_IS_ID~~</code>		The 'Update Attribute Breach Width (Before)' panel runs at the start of each iteration (indicated by the BEFORE setting). This Template Excel obtains the current iteration using <code>SELECT_ITERATION_WHERE_</code>, and updates the BREACH_WIDTH area to <code>3 + iteration</code> using UPDATE_AREA_BREACH_WIDTH_WHERE_AREA_IS_ID</code>

	The template excel panel named ''Store Breach Width in Width At (After)'' is performed at the end of each iteration, indicated by the AFTER timing setting. This template excel obtains the OBJECT_WIDTH_OUTPUT attribute from the Breach Area at each iteration, using the query <code>SELECT_ATTRIBUTE_WHERE_AREA_IS_ID_AND_NAME_IS_OBJECT_WIDTH_OUTPUT_AND_ITERATION_IS_X</code>. Queries with iterations clauses are cached and only executed when a particular iteration is active. The resulting values can then be concatenated into an array and stored under the attribute '''BREACH_WIDTH_AT''' using <code>UPDATE_AREA_BREACH_WIDTH_AT_WHERE_AREA_IS_ID</code>		The template excel panel named ''Store Breach Width in Width At (After)'' is performed at the end of each iteration, indicated by the AFTER timing setting. This template excel obtains the OBJECT_WIDTH_OUTPUT attribute from the Breach Area at each iteration, using the query <code>SELECT_ATTRIBUTE_WHERE_AREA_IS_ID_AND_NAME_IS_OBJECT_WIDTH_OUTPUT_AND_ITERATION_IS_X</code>. Queries with iterations clauses are cached and only executed when a particular iteration is active. The resulting values can then be concatenated into an array and stored under the attribute '''BREACH_WIDTH_AT''' using <code>UPDATE_AREA_BREACH_WIDTH_AT_WHERE_AREA_IS_ID</code>

← Older revision		Revision as of 12:51, 8 July 2026
Line 32:		Line 32:
	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.		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.		Note 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 wizard, set 'Combo Surface' as the input for the initial water level to use the combo overlay.

	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.
Line 52:		Line 52:

	===Visualization of the simulation===		===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, regarding simulation visualization: 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.

	==Calculations using the Iteration option==		==Calculations using the Iteration option==
	The demo project simulates a Dutch polder to demonstrate how a breach can be adjusted while using the [[Simulation Core\|iteration]] option.		The demo project simulates a Dutch polder to demonstrate how a breach can be adjusted while using the [[Simulation Core\|iteration]] option.

	~~There are situations in which we want more~~ control over ~~what~~ width ~~of a breach~~ each iteration ~~according to some condition~~. By dividing the flooding event into several iteration steps, we can adjust the breach width 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.		Some scenarios require precise control over the breach width for each iteration based on specific conditions. By dividing the flooding event into several iteration steps, we can adjust the breach width 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 approach can be adapted for other iterative calculations.

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

	==Combo Overlays==		==Combo Overlays==
	Before we create the Flooding event, a number of overlays are created that serve as input for the various iteration steps. At the end of each iteration the combo overlay is updated an serves as the input for the next iteration step~~. We'll go through the different combo overlays~~.		Before we create the Flooding event, a number of overlays are created that serve as input for the various iteration steps. At the end of each iteration the combo overlay is updated an serves as the input for the next iteration step.

	===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 velocity at the end of one iteration serves as 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, unless it is step 0. In that case, 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 101:		Line 101:

	==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 will 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.		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.

	==Indicator==		==Indicator==
	The purpose of the indicator is to set the start and end time of each iteration step of the flooding overlay. To accomplish this, a set of queries is performed. First ~~and foremost~~, the ~~amount~~ of iteration steps and the total duration ~~of the simulation obtained~~. This is obtained by using the query <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>.		The purpose of the indicator is to set the start and end time of each iteration step of the flooding overlay. To accomplish this, a set of queries is performed. First, the number of iteration steps and the total simulation duration are retrieved. This is obtained by using the query <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>.

	In this simple situation, the total simulation time will be subdivided into n equal steps, where n is the amount of iterations. The current iteration can be obtained using the query <code>SELECT_ITERATION_WHERE_</code>		In this simple situation, the total simulation time will be subdivided into n equal steps, where n is the amount of iterations. The current iteration can be obtained using the query <code>SELECT_ITERATION_WHERE_</code>
Line 116:		Line 116:

	==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:		Calculation results can be viewed by playing back the iterations. The following results can be seen here:
	* Water on surface level in meters		* Water on surface level in meters
	* Iteration U and V: The speed of the surface water in either the x or y direction.		* Iteration U and V: The speed of the surface water in either the x or y direction.
Line 124:		Line 124:
	The project contains several template panels, three of which are excel panels and one is a text panel. These template panels are all performed on breach areas, of which only one is present in this project.		The project contains several template panels, three of which are excel panels and one is a text panel. These template panels are all performed on breach areas, of which only one is present in this project.

	The ~~template excel panel named '~~'Update Attribute Breach Width (Before)'~~' is performed~~ at the start of each iteration, indicated by the BEFORE setting~~, which can be seen in its Template Excel Detail Panel~~. This Template Excel obtains the current iteration using <code>SELECT_ITERATION_WHERE_</code>, and updates the BREACH_WIDTH area to <code>3 + iteration</code> using UPDATE_AREA_BREACH_WIDTH_WHERE_NAME_IS_BREACH_WIDTH_AND_AREA_IS_ID</code>		The 'Update Attribute Breach Width (Before)' panel runs at the start of each iteration (indicated by the BEFORE setting). This Template Excel obtains the current iteration using <code>SELECT_ITERATION_WHERE_</code>, and updates the BREACH_WIDTH area to <code>3 + iteration</code> using UPDATE_AREA_BREACH_WIDTH_WHERE_NAME_IS_BREACH_WIDTH_AND_AREA_IS_ID</code>

	The template excel panel named ''Store Breach Width in Width At (After)'' is performed at the end of each iteration, indicated by the AFTER timing setting. This template excel obtains the OBJECT_WIDTH_OUTPUT attribute from the Breach Area at each iteration, using the query <code>SELECT_ATTRIBUTE_WHERE_AREA_IS_ID_AND_NAME_IS_OBJECT_WIDTH_OUTPUT_AND_ITERATION_IS_X</code>. Queries with iterations clauses are cached and only executed when a particular iteration is active. The resulting values can then be concatenated into an array and stored under the attribute '''BREACH_WIDTH_AT''' using <code>UPDATE_AREA_BREACH_WIDTH_AT_WHERE_AREA_IS_ID</code>		The template excel panel named ''Store Breach Width in Width At (After)'' is performed at the end of each iteration, indicated by the AFTER timing setting. This template excel obtains the OBJECT_WIDTH_OUTPUT attribute from the Breach Area at each iteration, using the query <code>SELECT_ATTRIBUTE_WHERE_AREA_IS_ID_AND_NAME_IS_OBJECT_WIDTH_OUTPUT_AND_ITERATION_IS_X</code>. Queries with iterations clauses are cached and only executed when a particular iteration is active. The resulting values can then be concatenated into an array and stored under the attribute '''BREACH_WIDTH_AT''' using <code>UPDATE_AREA_BREACH_WIDTH_AT_WHERE_AREA_IS_ID</code>