TUFLOW crashing: Difference between revisions
Content deleted Content added
| (8 intermediate revisions by 3 users not shown) | |||
Line 14:
=How to keep simulation console window open=
* To ensure the console window remains open, add pause at the end of the batch file and remove any Start "TUFLOW", -b, or -t switches. If the console window still closes, use a simplified batch file like the example below.
**The simulation console window is the one stating with the TUFLOW build, for example "TUFLOW Build: 2020-10-AD-iSP-w64" in the header's top left corner.▼
pause
▲
:[[File:TUFLOW Simulation Console with Build Info Displayed.png|frameless|600x600px]]
:If start "TUFLOW" is included in the batch file, the console window will instead show "C:\WINDOWS\system32\cmd.exe" in the window header and will not display the desired simulation output, as shown below.
:[[File:Batch File Console Showing CMD Header Only.png|frameless|600x600px]]
* Or, let the console window be written to a text file. This will redirect console output messages as well as the standard error stream to the “dump.txt” file, and it will likely record more error information than the usual .tlf file.
<pre>"C:\TUFLOW\Releases\2020-10-AD\TUFLOW_iSP_w64.exe" "M01_5m_001.tcf" > dump.txt</pre>
=Simulation console window flashes and disappears=
Line 79 ⟶ 85:
=TUFLOW crashes at the end of the simulation before writing out maximum results=
The output drive might not have enough free space to write out the full results. If multiple TUFLOW simulations run in parallel, the free space might be filling up faster than expected. There can also be other processes filling up the drive, e.g. other software, backups, other users copying data. The target drive should never
'''Suggestions:'''
* Ensure storage locations that outputs are written to have enough free space. Depending on the infrastructure, reported free space may not be accurate, or performance of storage may substantially degrade as it nears being full.
Line 99 ⟶ 105:
Once a year (usually after mid-year) a new TUFLOW release will need the licence to be updated. This will show in the .tlf file as "Unmaintained since <year>". Follow <u>[[WIBU_Licence_Update_Request | WIBU Licence Update Request]]</u> to get the licence updated.
==Console window lists all licences
If the console window
During the licence check, one licence from each available module is temporarily reserved. These are released either immediately by pressing Enter, or automatically after a few minutes when the console window is closed.
Once the licences are released by pressing Enter, the console window displays "Not licenced or no local licence free". This confirms that the licences are no longer reserved by the licence check and are available for running TUFLOW models.<ol> [[File: Licence_Check_2.png | 600px]]</ol>
The licence check is performed in the following situations:
* Double clicking a TUFLOW executable.
* Running a batch file
* Running TUFLOW from Notepad++
Suggestions to run a TUFLOW model:
* Include the model .tcf name in the batch file. See <u>[[Running_TUFLOW | Running TUFLOW model]]</u> for further guidance.
Line 116 ⟶ 125:
==No TUFLOW dongle and licence settings files found (.lcf and .dcf)==
Some users might mistake this sentence in the .tlf file as there is an issue with the licence. The "No TUFLOW licence settings files found" sentence is followed by "Default settings applied" and the default settings are listed on the next three lines, e.g. WIBU Retry Time, WIBU Retry Count, WIBU Dongles Only. Only if these settings are required to be different, the licence control file (.lcf) or dongle control file (.dcf) would be
==Technical licence issues==
Line 150 ⟶ 159:
)
pause</pre>
{{Tips Navigation
|uplink=[[TUFLOW_Modelling_Guidance | Back to TUFLOW Modelling Guidance]]
}}
| |||