TUFLOW crashing: Difference between revisions
Content deleted Content added
Teegan.Burke (talk | contribs) Tag: Manual revert |
|||
| (7 intermediate revisions by 3 users not shown) | |||
Line 52:
</ol>
<br>
=TUFLOW pauses at any time during simulation=
'''Causes''':
*Ctrl+S shortcut has been activated.
*Windows 10 Quick Edit Mode is active.
'''Suggestions:'''<br>
See <u>[[Console_Window_Simulation_Paused]]</u> for further guidance.
=TUFLOW crashes during model initialisation=
Line 71 ⟶ 79:
* The output drive might not have enough free space seemingly crashing at random time (at any map output interval).
* Something might be preventing the simulation from writing to network drive such as scheduled backup, updates, restart, deduplication or other scheduled processes. This would often happen at the similar time during the day or week seemingly stopping TUFLOW simulations at random simulation time. TUFLOW is not releasing the licence at the end of the simulation, rather CodeMeter system is determining that the TUFLOW application is no longer running and is therefore releasing the licence. This would show as “Handle xxx automatically released. The application is no longer available.” in the <u>[[WIBU_create_cmDust | cmDust file]]</u>.
* Using Windows Terminal (now default on Windows 11) instead of Windows Console Host. This has come up a few times intermittently as causing issues for users, but the TUFLOW team haven’t yet isolated the conditions that cause it.
'''Suggestions''':
* Unstable network:
** Use TUFLOW executable saved on a local drive.
** Set a local drive as the output drive for all checks, results and logs. This can be done using <font color="blue"><tt>Output Drive</tt></font> command in the .tcf. All outputs can be copied back to the network drive at the simulation end if required. Robocopy can be added to the end of the .bat file, example <u>[[TUFLOW_crashing#Robocopy_example_to_automatically_copy_outputs_on_network_drive_after_model_runs | here]]</u>.
* Insufficient storage:
** 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.
*Windows Terminal on Windows 11:
**If after investigating other possible reasons for TUFLOW crashing it is believed running the simulation on Windows Terminal may be the problem, please run the [[WIBU create cmDust|cmDust file]] utility and send [mailto:support@tuflow.com support@tuflow.com] the resulting log from the user profile folder. This may help to narrow down the conditions that may cause TUFLOW to crash.
**The Windows Terminal provides useful features, and it is not recommend avoiding its use altogether - it ''can'' be disabled altogether, but a lot of functionality would be lost. Instead, we have developed a utility that allows forcing a specific application to start in the Windows Console Host, which is what the Command Prompt used to use by default. The utility is called `tustart` and a copy can be downloaded here: https://downloads.tuflow.com/Utilities/TUStart/tustart.msi.
**Note: a browser warning is likely to occur that this file is not commonly downloaded, and depending on the browser, the user may need to instruct it to ‘Keep’ or ‘Keep anyway’ to be able to complete the download of the `tustart.msi` file. This is due to the file currently not being available from the main site. It is being consider for inclusion as part of a future TULFOW Installer application.
**With admin privileges (elevation) on the relevant computer, this utility should be able to installed for all users in one go, which is the recommended way of installing. Without admin privileges, it can be installed just by a given user, but keep in mind that other users would have to separately install it as well. If the solution of forcing TUFLOW to run in Windows Console Host works to prevent unexpected crashed, it is recommend requesting your organisation's IT staff to deploy it properly to relevant modelling machines for all users. The application is packaged in a .msi and digitally signed, so IT staff should not have too many practical issues to install it safely and securely.
**Once installed, a model can be run like this: <pre>tustart.exe conhost -t “Some title” “C:\Path\to\your\tuflow.exe” -b -e1 event -s1 scenario my_~e1~_~s1~.tcf</pre>
**Please contact [mailto:support@tuflow.com support@tuflow.com] should any issues arise.
**If the utility does not actually resolve TUFLOW crashing, it is recommended to uninstall 'tustart', since it won’t have other benefits.
*Other processes:
** Check with IT whether such processes are occurring and if reasonable limits/preferences/priorities can be set to reduce resource use (disk/network), to allow other processes to run in parallel.
** Run models locally if it is known the runs will coincide with such processes.
* If you need further help, send the .tlf, .hpc.tlf and <u>[[TUFLOW_crashing#How_to_keep_simulation_console_window_open | snapshot of the console window]]</u> to [mailto:support@tuflow.com support@tuflow.com].
=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 119 ⟶ 135:
* 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>
* See detailed steps on how to run a TUFLOW model in the <u>[[Tutorial_M01#Running_the_Simulation | Tutorial model]]</u>.
==Running very old TUFLOW releases==
Line 125 ⟶ 142:
==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 159 ⟶ 176:
)
pause</pre>
{{Tips Navigation
|uplink=[[TUFLOW_Modelling_Guidance | Back to TUFLOW Modelling Guidance]]
}}
| |||