Running TUFLOW: Difference between revisions
Content deleted Content added
Chris Huxley (talk | contribs) No edit summary |
RobertWright (talk | contribs) |
||
| (72 intermediate revisions by 10 users not shown) | |||
Line 2:
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
# Download the latest TUFLOW executable from the
# Download the TUFLOW Tutorial and Demo models:
# Run TUFLOW using any of the options listed below. User documentation for the tutorial models is available from the [[
* '''Licensed
# Download the latest TUFLOW executable from the
# Download and install the Licensing Dongle Drivers: [[TUFLOW_Licensing|Installing Licensing Software]]
# Run TUFLOW using any of the options listed below.
= Executable Management Advice =
== Run Options==▼
Save a copy of the downloaded TUFLOW executable files to a dedicated location (eg. C:\TUFLOW\Releases\)<br><br>
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.<br>▼
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 <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u> for advice when best to use the different TUFLOW versions. Do not delete or relocate any files in the TUFLOW release folder. All files must be placed in the same folder and kept together at all times. <br>
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.
<br>[[File:Executable_File_Management_001.png|600px]]
==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 <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW
Common ways of initialising a TUFLOW simulation are:
* [[Run TUFLOW From a Batch-file|Using a Batch-file]]
* [[TUFLOW Runner|Using the TUFLOW Runner]]
* [[Run TUFLOW From PowerShell|Using PowerShell]]
* [[Run TUFLOW From UltraEdit|Running TUFLOW from UltraEdit]]
* [[Run TUFLOW through the command window|Run TUFLOW through the command window]]
* [[NotepadPlusPlus_Run_TUFLOW | Running TUFLOW from Notepad++]]
* [
* [[Running_TUFLOW_from_Explorer | Running TUFLOW from Windows Explorer (Pre-Windows 7)]]
* [[QGIS_TUFLOW_Run_TUFLOW | From QGIS with the TUFLOW QGIS Plugin]]
Line 28 ⟶ 43:
==Multiple Simulation Management==
* [[Run TUFLOW From a Batch-file|Using a Batch-file]]
* [[TUFLOW Runner|Using the TUFLOW Runner]]
* [[TRIM_Tips| TUFLOW Run Interface Manager (TRIM)]]
* For miTools users, please see the miTools manual for instructions.
==Scheduling Simulations==
* [[Using_Task_Scheduler_to_Run_Batch_Files|Using Task Scheduler]]
= Cloud Computing =
Organisations with access to Cloud hardware may host Network Licences within their own cloud domain (private or public).<br>
Click For Details: [[Organisation_Cloud_Software_Execution| Organisation Cloud Software Execution]]. <br>
| |||