Revision as of 15:39, 18 April 2025 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,395 edits →Results ← Older edit		Latest revision as of 08:18, 2 April 2026 view source Anne.Kolega (talk \| contribs) Bureaucrats, Administrators 184 edits m →Introduction: e.g. Tag: Visual edit
Line 4: This tutorial focuses on demonstrating various Scenario and Event management options. In TUFLOW terminology: * Scenario = A topographic or model configuration feature. <br> :(ege.g. existing catchment topography, development scenario topography, cell size etc.)<br> * Event = An input associated with a forcing boundary condition. Examples include: <br> :* Event magnitude: (ege.g. 10, 20, 50, 100 year ARI etc.) <br> :* Storm duration (ege.g. 1,2,3,6,12, 24, 36 hours etc.) <br> :* Design storm temporal pattern (ege.g. Australian Rainfall and Runoff 1 to 10)<br> :* Tail water condition (ege.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>

Tutorial Module10 Archive: Difference between revisions