Tuflow

TUFLOW crashing: Difference between revisions

Browse history interactively
← Older edit
Content deleted Content added
VisualWikitext
No edit summary
 
(10 intermediate revisions by 3 users not shown)
Line 14:
 
=How to keep simulation console window open=
SimulationThe simulation console window can display errors not written into the .tlf file and provideoften moreprovides additional information useful for troubleshooting:
 
* Insert "pause" at the end of the batch file and remove any Start "TUFLOW", -b and/or -t switch. Simple batch file as below should be used if current batch file doesn't keep the console window open even with the suggested changes.
* 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.▼
 
**The batch file console window stating "C:\WINDOWS\system32\cmd.exe" in the header's top left corner won't provide desired information.
<pre> "C:\TUFLOW\Releases\2020-10-AD\TUFLOW_iSP_w64.exe" "M01_5m_001.tcf"
pause</pre>
 
▲**:The simulation console window is the one statingthat withdisplays the TUFLOW build, for example(e.g. "TUFLOW Build: 2020-10-AD2025.0.3-iSP-w64") in the header's top -left corner of the window header, as shown in the image below.
:[[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>
<br>
 
=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 be planned to be filled to the brim, as performance will suffer for all processes.<br>
'''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, after pressing Enter the licences are released and model doesn't run==
If the console window appears as shown below and ends with the line "Press ENTER to Release WIBU Licences", this indicates a licence check was performed. When a licence check is run, the TUFLOW model does not execute, and a .tlf file is not produced.
What happened here is a licence check which doesn't run a TUFLOW model and doesn't produce a .tlf file. Licence check temporarily takes one licence from every available module until the licences are released by pressing Enter (released immediately) or by closing the console window (released after a couple of minutes). Once licenses are released by pressing Enter, the console window shows “Not licenced or no local licence free”. This means the licences are no longer taken by the licence check and can be used for running models.<br>
 
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 withthat only specifies the TUFLOW executable specified.
* Running TUFLOW from Notepad++, when insertingwith only the TUFLOW executable inserted into the Run windowfunction text box.<br>
Suggestions to run a TUFLOW model:
Check these Wiki pages on how to <u>[[Running_TUFLOW | run TUFLOW model]]</u> and how to setup <u>[[NotepadPlusPlus_Run_TUFLOW | running TUFLOW from Notepad++]]</u>.
* Include the model .tcf name in the batch file. See <u>[[Running_TUFLOW | Running TUFLOW model]]</u> for further guidance.
* Insert the full required text (example line below) into Notepad++ Run function text box. See <u>[[NotepadPlusPlus_Run_TUFLOW | Running TUFLOW from Notepad++]]</u> for further guidance.
<ol> "C:\TUFLOW\2025.0.3\TUFLOW_iSP_w64.exe" "$(FULL_CURRENT_PATH)" </ol>
 
==Running very old TUFLOW releases==
Line 112 ⟶ 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 createdrequired. Not having these licence files doesn't prevent TUFLOW from running, it would automatically use the default licence settings. The .tlf should continue past these lines and if there is an error, it would be written as the bottom of the .tlf.
 
==Technical licence issues==
Line 146 ⟶ 159:
)
pause</pre>
 
 
{{Tips Navigation
|uplink=[[TUFLOW_Modelling_Guidance | Back to TUFLOW Modelling Guidance]]
}}
Retrieved from "https://wiki.tuflow.com/TUFLOW_crashing"