TUFLOW crashing: Difference between revisions

Content deleted Content added
Line 107:
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 ampleenough 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.
* 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 support@tuflow.com.
* If the output drive does have more than enough space, insert "pause" at the end of the batch file and remove any start "TUFLOW", -b and/or -t switch to keep the console window open and send a snapshot of the console window and .tlf and .hpc.tlf to support@tuflow.com. <u>[[Run_TUFLOW_From_a_Batch-file#Batch_file_for_Tutorial_Model_Module_1 | Simple batch file]]</u> should be used if looping batch file doesn't keep the console window open even with the suggested changes.<br>
<br>