Tutorial Module10 Archive - Revision history

Anne.Kolega: /* Introduction */ e.g.

2026-04-01T22:18:40Z

Introduction: e.g.

← Older revision		Revision as of 08:18, 2 April 2026
Line 4:		Line 4:
	This tutorial focuses on demonstrating various Scenario and Event management options. In TUFLOW terminology:		This tutorial focuses on demonstrating various Scenario and Event management options. In TUFLOW terminology:
	* Scenario = A topographic or model configuration feature. <br>		* Scenario = A topographic or model configuration feature. <br>
	:(eg. existing catchment topography, development scenario topography, cell size etc.)<br>		:(e.g. existing catchment topography, development scenario topography, cell size etc.)<br>
	* Event = An input associated with a forcing boundary condition. Examples include: <br>		* Event = An input associated with a forcing boundary condition. Examples include: <br>
	:* Event magnitude: (eg. 10, 20, 50, 100 year ARI etc.) <br>		:* Event magnitude: (e.g. 10, 20, 50, 100 year ARI etc.) <br>
	:* Storm duration (eg. 1,2,3,6,12, 24, 36 hours etc.) <br>		:* Storm duration (e.g. 1,2,3,6,12, 24, 36 hours etc.) <br>
	:* Design storm temporal pattern (eg. Australian Rainfall and Runoff 1 to 10)<br>		:* Design storm temporal pattern (e.g. Australian Rainfall and Runoff 1 to 10)<br>
	:* Tail water condition (eg. high tide, low tide, storm tide, climate change etc.) <br>		:* Tail water condition (e.g. high tide, low tide, storm tide, climate change etc.) <br>
	In previous tutorials, new TUFLOW Control File (TCF), TUFLOW Geometry Control (TGC) file and ESTRY Control Files (ECF) were required each time a different model scenario or event was modelled. During complex modelling projects this has the potential to result in a large number of input files. This can become a project management challenge. TUFLOW incorporates scenario and event control logic to overcome these challenges, significantly reducing the number of simulation files required during a complex project. The figure below shows a project requiring over 30 simulations consolidated into a single TCF file.<br>		In previous tutorials, new TUFLOW Control File (TCF), TUFLOW Geometry Control (TGC) file and ESTRY Control Files (ECF) were required each time a different model scenario or event was modelled. During complex modelling projects this has the potential to result in a large number of input files. This can become a project management challenge. TUFLOW incorporates scenario and event control logic to overcome these challenges, significantly reducing the number of simulation files required during a complex project. The figure below shows a project requiring over 30 simulations consolidated into a single TCF file.<br>

Pavlina Monhartova: /* Results */

2025-04-18T05:39:31Z

Results

← Older revision		Revision as of 15:39, 18 April 2025
Line 593:		Line 593:
	==Results==		==Results==
	Using the methods described above in the <u>[[Tutorial_Module01_Archive#Viewing_Results \| Viewing Results]]</u> section of Module 1.		Using the methods described above in the <u>[[Tutorial_Module01_Archive#Viewing_Results \| Viewing Results]]</u> section of Module 1.
	* Check the simulation logs in the ~~DOS~~ window, .tlf and .hpc.tlf log files.		* Check the simulation logs in the console window, .tlf and .hpc.tlf log files.
	* View the results in your preferred package.		* View the results in your preferred package.
	Do the logs and results appear different to the TUFLOW Classic simulation?		Do the logs and results appear different to the TUFLOW Classic simulation?

Emilie Nielsen: /* Troubleshooting for GPU Simulations */

2025-02-20T06:32:37Z

Troubleshooting for GPU Simulations

← Older revision		Revision as of 16:32, 20 February 2025
Line 612:		Line 612:
	</ol>		</ol>
	<br>		<br>
	If you experience an issue that is not detailed above please send an email to support@tuflow.com<br>		If you experience an issue that is not detailed above please send an email to [mailto:support@tuflow.com support@tuflow.com]<br>

Abigail.lillo: /* Advanced - HPC Solver (Optional) */

2024-10-10T01:57:08Z

Advanced - HPC Solver (Optional)

← Older revision		Revision as of 11:57, 10 October 2024
Line 532:		Line 532:
	= Advanced - HPC Solver (Optional) =		= Advanced - HPC Solver (Optional) =
	This section introduces how to run the model using TUFLOW’s HPC (Heavily Parallelised Compute) solver with scenario control. It is much more convenient to select the model solver using scenario control than how it was done in other tutorials, because you only need to create one .tcf file for both the HPC and/or Classic simulations.		This section introduces how to run the model using TUFLOW’s HPC (Heavily Parallelised Compute) solver with scenario control. It is much more convenient to select the model solver using scenario control than how it was done in other tutorials, because you only need to create one .tcf file for both the HPC and/or Classic simulations.

			Please see [[HPC_Features_Archive \| HPC Features Archive]] for more information on TUFLOW HPC features supported in the 2017 release.

	==Model Setup==		==Model Setup==

Emilie Nielsen at 00:34, 23 September 2024

2024-09-23T00:34:09Z

← Older revision		Revision as of 10:34, 23 September 2024
Line 376:		Line 376:
	<font color="blue"><tt>Set Variable <name> </tt></font> <font color="red"><tt>==</tt></font> <tt><value></tt><br>		<font color="blue"><tt>Set Variable <name> </tt></font> <font color="red"><tt>==</tt></font> <tt><value></tt><br>
	The Variable can be used in any TUFLOW control file. The variable is called by bounding the variable name within "<<" and ">>" characters. <br>		The Variable can be used in any TUFLOW control file. The variable is called by bounding the variable name within "<<" and ">>" characters. <br>
	''Tip: if you find that your Set Variables are becoming a large part of your TUFLOW control files, it can be beneficial to collate the variables within a TUFLOW <font color="blue"><tt>Read File</tt></font>. Refer to the TUFLOW ~~manual~~ for more details.''		''Tip: if you find that your Set Variables are becoming a large part of your TUFLOW control files, it can be beneficial to collate the variables within a TUFLOW <font color="blue"><tt>Read File</tt></font>. Refer to the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u> for more details.''
	<br>		<br>

Emilie Nielsen at 03:20, 5 April 2024

2024-04-05T03:20:00Z

← Older revision		Revision as of 13:20, 5 April 2024
Line 104:		Line 104:

	==Run The Model and Review Results==		==Run The Model and Review Results==
	Run '''M10_5m_~s1~_001.tcf''' using your preferred method, as described <u>[[Tutorial_Module01_Archive#~~Running_TUFLOW~~\|~~here~~]]</u>.<br>		Run '''M10_5m_~s1~_001.tcf''' using your preferred method, as described in <u>[[Tutorial_Module01_Archive#Run_Simulation \| Module 1]]</u>.<br>

	The default scenario we have specified in the TCF using the <font color="blue"><tt> Model Scenarios </tt></font> command will be selected if you run the model from a text editor. Running the model from a batch file is more common for models using scenario logic. The scenario specified within the batch file will take precedence over the scenario specified with the TCF.		The default scenario we have specified in the TCF using the <font color="blue"><tt> Model Scenarios </tt></font> command will be selected if you run the model from a text editor. Running the model from a batch file is more common for models using scenario logic. The scenario specified within the batch file will take precedence over the scenario specified with the TCF.

ElizaCollison at 23:50, 8 January 2023

2023-01-08T23:50:20Z

Pavlina Monhartova: Created page with "
=Introduction= This module further develops the model created during Module 01. Please complete Module 01 before attempting this tutorial, it..."

2022-06-02T04:10:25Z

Created page with "<ol> =Introduction= This module further develops the model created during <u>Module 01</u>. Please complete Module 01 before attempting this tutorial, it..."

Show changes

← Older revision		Revision as of 09:50, 9 January 2023
Line 1:		Line 1:
	<ol>		<ol>
	=Introduction=		=Introduction=
	This module further develops the model created during <u>[[~~Tutorial_Module01~~\|Module 01]]</u>. Please complete Module 01 before attempting this tutorial, it is the starting point for the model updates documented below.<br>		This module further develops the model created during <u>[[Tutorial_Module01_Archive\|Module 01]]</u>. Please complete Module 01 before attempting this tutorial, it is the starting point for the model updates documented below.<br>
	This tutorial focuses on demonstrating various Scenario and Event management options. In TUFLOW terminology:		This tutorial focuses on demonstrating various Scenario and Event management options. In TUFLOW terminology:
	* Scenario = A topographic or model configuration feature. <br>		* Scenario = A topographic or model configuration feature. <br>
Line 104:		Line 104:

	==Run The Model and Review Results==		==Run The Model and Review Results==
	Run '''M10_5m_~s1~_001.tcf''' using your preferred method, as described <u>[[~~Tutorial_Module01~~#Running_TUFLOW\|here]]</u>.<br>		Run '''M10_5m_~s1~_001.tcf''' using your preferred method, as described <u>[[Tutorial_Module01_Archive#Running_TUFLOW\|here]]</u>.<br>

	The default scenario we have specified in the TCF using the <font color="blue"><tt> Model Scenarios </tt></font> command will be selected if you run the model from a text editor. Running the model from a batch file is more common for models using scenario logic. The scenario specified within the batch file will take precedence over the scenario specified with the TCF.		The default scenario we have specified in the TCF using the <font color="blue"><tt> Model Scenarios </tt></font> command will be selected if you run the model from a text editor. Running the model from a batch file is more common for models using scenario logic. The scenario specified within the batch file will take precedence over the scenario specified with the TCF.
Line 123:		Line 123:
	<li> Double click the batch file in Windows Explorer to run TUFLOW. Two simulations will be executed in series. The EXG scenario will run first, followed by the DEV scenario.		<li> Double click the batch file in Windows Explorer to run TUFLOW. Two simulations will be executed in series. The EXG scenario will run first, followed by the DEV scenario.
	<li>Review the model results in your preferred result viewing program (i.e. SMS, WaterRIDE, QGIS, Blue Kenue).<br>		<li>Review the model results in your preferred result viewing program (i.e. SMS, WaterRIDE, QGIS, Blue Kenue).<br>
	''Note: For useful tips how to compare simulation results, refer to the Compare Results section of <u>[[~~Tutorial_Module05~~#Compare_results \|Module 05]]</u>.''		''Note: For useful tips how to compare simulation results, refer to the Compare Results section of <u>[[Tutorial_Module05_Archive#Compare_results \|Module 05]]</u>.''
	</ol>		</ol>

Line 590:		Line 590:

	==Results==		==Results==
	Using the methods described above in the <u>[[~~Tutorial_Module01~~#Viewing_Results \| Viewing Results]]</u> section of Module 1.		Using the methods described above in the <u>[[Tutorial_Module01_Archive#Viewing_Results \| Viewing Results]]</u> section of Module 1.
	* Check the simulation logs in the DOS window, .tlf and .hpc.tlf log files.		* Check the simulation logs in the DOS window, .tlf and .hpc.tlf log files.
	* View the results in your preferred package.		* View the results in your preferred package.