Difference between revisions of "Running TUFLOW"
Chris Huxley (talk | contribs) |
Chris Huxley (talk | contribs) |
||
Line 48: | Line 48: | ||
== Cloud Computing == | == Cloud Computing == | ||
− | The "Cloud" is an excellent project execution environment option in situations where large | + | The "Cloud" is an excellent project execution environment option in situations where large simulation volumes require completion within a short timeframe (eg. Monte Carlo runs).<br> |
Three options are available. Click the links below for more information:<br> | Three options are available. Click the links below for more information:<br> |
Revision as of 13:56, 27 September 2019
Introduction
TUFLOW is a standalone console application. As such, it doesn't require installation to run. The standard TUFLOW setup steps are listed below.
- Free DEMO and Tutorial Version of TUFLOW:
- Download the latest TUFLOW executable from the Tuflow website: Tuflow Release Download
- Download the TUFLOW Tutorial and Demo models: Tutorial Model Download
- Run TUFLOW using any of the options listed below. User documentation for the tutorial models is available from the Tutorial Model section of the Wiki.
- Licensed Version of TUFLOW:
- Download the latest TUFLOW executable from the Tuflow website: Tuflow Release Download
- Download and install the Licensing Dongle Drivers: Installing Licensing Software
- Run TUFLOW using any of the options listed below.
Executable Management Advice
Save a copy of the downloaded TUFLOW executable files to a dedicated location (eg. C:\TUFLOW\Releases\)
A TUFLOW release consists of two different versions of the executable as follows:
- TUFLOW_iSP_w64.exe - Single Precision Windows 64-bit
- TUFLOW_iDP_w64.exe - Double Precision Windows 64-bit
Refer to the TUFLOW Executable Section of the TUFLOW manual for advice when best to use the different TUFLOW versions. Each version of TUFLOW also has four TUFLOW .dll files and several system .dll files included in the download. Do not delete or relocate these dlls. All .exe and .dll files must be placed in the same folder and kept together at all times.
When replacing TUFLOW with a new build, we recommend archiving the past .exe and .dll files by creating a folder of the same name as the Build ID (e.g. 2013-12-AA-iSP-w64), and placing all files in this folder. Build ID information is appears in the top bar of the Console window when TUFLOW is executed, and is reported in the header of the .tlf file.
Run Options
Single Simulation Execution
There are a number of ways TUFLOW can be started, in each case the TUFLOW executable is started with the TUFLOW control file (.tcf) as the input. There are a number of optional switches that can be used to control advanced features as outlined in the TUFLOW manual.
Common ways of initialising a TUFLOW simulation are:
- Using a Batch-file
- Running TUFLOW from UltraEdit
- Run TUFLOW through the command window
- Running TUFLOW from Notepad++
- Textpad Instructions Including Running TUFLOW (Provided by CHM2Hill / Halcrow)
- Running TUFLOW from Windows Explorer (Pre-Windows 7)
- From QGIS with the TUFLOW QGIS Plugin
- From ArcMap with the ArcTUFLOW Toolbox
- For miTools users, please see the miTools manual for instructions.
Multiple Simulation Management
- Using a Batch-file
- TUFLOW Run Interface Manager (TRIM)
- For miTools users, please see the miTools manual for instructions.
Scheduling Simulations
Cloud Computing
The "Cloud" is an excellent project execution environment option in situations where large simulation volumes require completion within a short timeframe (eg. Monte Carlo runs).
Three options are available. Click the links below for more information:
- Organisation Cloud Software Execution
Organisations with access to Cloud hardware may host Network Licences within their own cloud domain (private or public). - TUFLOW Cloud Simulation Service
Let BMT help you manage your TUFLOW simulation execution on the cloud. This service is designed for bulk simulation of any TUFLOW product (Classic, HPC or FV).
- Software licences are scaled to meet your project demand (i.e. this is independent of any in-house licences you may own).
- The BMT service offers flexibility regarding the Microsoft Azure Cloud hardware available for your project. We tailor the hardware and storage resource specification to suit your project requirements (based on project size, model size and also the simulation type).
- This service has no limitations in terms of hardware type. We offer simulation on both CPU and GPU virtual machines.
- Jacobs Flood Cloud
Powered by Parallel Works, Jacobs have developed Flood Cloud. Flood Cloud gives the modeller full simulation control on the cloud.- Flood Cloud includes a dashboard to assist users with all model upload, simulation run, simulation monitoring and result download tasks (requiring no external support from Jacob staff).
- Software licences are scaled to meet your project demand (i.e. this is independent of any in-house licences you may own).
- The service links to pre-defined high performance CPU cloud hardware. This specific hardware type was selected following extensive hydraulic model benchmarking.
- The Jacobs Flood Cloud offering is limited to TUFLOW Classic simulations. TUFLOW HPC GPU and TUFLOW FV simulations are not supported.