Tutorial Module01 Archive: Difference between revisions

Browse history interactively

← Older edit

Content deleted Content added

VisualWikitext

Revision as of 10:35, 23 September 2024 view source Emilie Nielsen (talk \| contribs) Administrators 6,125 edits No edit summary ← Older edit		Latest revision as of 16:04, 18 April 2025 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,342 edits No edit summary
(5 intermediate revisions by 3 users not shown)
Line 120: <br> <li> Start TUFLOW from a batch file using the TCF file we have created ('''M01_5m_001.tcf'''). Follow the steps outlined in, <u>[[Run TUFLOW From a Batch-file \| Running TUFLOW from a Batch-file]]</u> to create the batch file. <li> Double click the created batch file (.bat) from Windows Explorer to execute the simulation. A console ~~(DOS)~~ window should appear as shown below:<br> [[File:Tute M01 DOS Empties.png\|frame\|none]] <br> Line 409: === TUFLOW Log file === The first place to look is at the final output in the ~~DOS~~console window. If you missed this, for example if the model was run in batch mode this information is contained in the TUFLOW Log File (.tlf). Earlier on we add the following command to the TCF:<br> <font color="blue"><tt>Log Folder </tt></font> <font color="red"><tt>==</tt></font> <tt>Log</tt><br> Line 463: === TUFLOW Messages Layers === TUFLOW writes a number of messages, in increasing order of severity these are: Check --> Warning --> Error. Each of the messages generated by TUFLOW has a four digit ID code. A description of each of these messages is given in the message database section of this wiki: <u>[[~~TUFLOW_Message_How_To~~TUFLOW_Messages \| (TUFLOW Messages Database)]]</u>. When a numerical model such as TUFLOW struggles to converge to a solution, spurious results such as negative depths can be generated. When this occurs TUFLOW creates a warning and writes this to the _messages.csv file and also to a GIS file. This can be opened in excel, or your GIS package. <ol> Line 507: ==Troubleshooting== This section contains links to some common issues that may occur when progressing through the first module of the TUFLOW tutorial model. If you experience an issue that is not detailed on here please either send an email to [mailto:support@tuflow.com support@tuflow.com].<br> <u>[[Save_Date_Error_Archive\|Save date of .tab file is later than .mif or .mid]]</u><br> <u>[[Tutorial_Troubleshoot_2014\|ERROR 2014 - No active cells within SA inflow polygon]]</u> <u>[[~~Only_TUFLOW_DOS_Window_Archive~~Only_TUFLOW_Console_Window_Archive \| Why does the TUFLOW ~~DOS~~console ~~Window~~window open, though the TCF isn’t read and the simulation doesn’t execute?]]</u> == Advanced - Model Resolution (Optional) == Line 559: == Advanced - HPC Solver (Optional) == This section will introduce how to run the model TUFLOW’s HPC (Heavily Parallelised Compute) solver, and how to fix some common issues that may occur when trying to run a simulation using Graphics Processing Unit (GPU) hardware. Please see [[HPC_Features_Archive \| HPC Features Archive]] for more information on TUFLOW HPC features supported in the 2017 release. TUFLOW HPC can run between 10 and 100 times faster than TUFLOW Classic using NVidia Graphics Processing Units (GPU)(depending on the model configuration and hardware performance). <br><br> Line 582: ===Results=== Using the methods described above in the <u>[[Tutorial_Module01_Archive#Viewing_Results \| Viewing Results]]</u> section. Check the simulation logs in the ~~DOS~~console window, .tlf and .hpc.tlf log files. * View the results in your preferred package. Do the logs and results appear different? Did the simulation run faster using the GPU hardware? For more information about computer hardware and simulation speed, please refer to the <u>[[Hardware_Benchmarking \| Hardware Benchmarking Page]]</u>. Line 601: </ol> <br> If you experience an issue that is not detailed above please send an email to [mailto:support@tuflow.com support@tuflow.com]<br>