Difference between revisions of "Batch File Not Running"

From Tuflow
Jump to navigation Jump to search
Line 5: Line 5:
  
 
=Suggestions=
 
=Suggestions=
There could be a number of reasons this occurs, check the following:
+
This is most likely caused by inadvertently adding a " "(space) before and/or after the "=" in the batch file<br>
* The correct .tcf file was started;
+
Wrong format:
* The .tcf has been updated to point to the new geometry (.tgc) / boundary (.tbc) files;
+
{| class="wikitable "
* Check files are being written (Write Check Files == command occurs in the .tcf / .ecf);
+
|-
 
+
Another good check is to import the messages layer, and view the TUFLOW log file (.tlf) for any checks or warnings. It is often useful to search the .tlf for an input file name, for example, if breakline changes are not seen, search the .tlf to ensure the input file e.g. "2d_zsh_M03_thalweg" is being read in.
+
<tt>set TUFLOWEXE = C:\TUFLOW\Releases\2017-09-AC\w64\TUFLOW_iSP_w64.exe</tt>
 +
|}
 +
Correct format:
 +
{| class="wikitable "
 +
|-
 +
 +
<tt>set TUFLOWEXE=C:\TUFLOW\Releases\2017-09-AC\w64\TUFLOW_iSP_w64.exe</tt>
 +
|}
 +
To solve this issue, please ensure that the batch file does't have " "(space) before and after the "=".

Revision as of 09:50, 1 February 2018

Description

When running TUFLOW with a batch file, the command prompt shows error before running any model, or opens a new file Explorer.
Batch File Not Running.png

Suggestions

This is most likely caused by inadvertently adding a " "(space) before and/or after the "=" in the batch file
Wrong format:

set TUFLOWEXE = C:\TUFLOW\Releases\2017-09-AC\w64\TUFLOW_iSP_w64.exe

Correct format:

set TUFLOWEXE=C:\TUFLOW\Releases\2017-09-AC\w64\TUFLOW_iSP_w64.exe

To solve this issue, please ensure that the batch file does't have " "(space) before and after the "=".