Revision as of 16:25, 30 April 2020 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,392 edits No edit summary ← Older edit		Revision as of 16:32, 30 April 2020 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,392 edits →Package a TUFLOW model Newer edit →
Line 127: : The addition of the “L” flag (e.g. -pmL) list the files to be copied into an output file, but don’t copy.<br> ;* “ini” (file.ini)<br> : The addition of the “ini” flag (e.g. -pmini) provides a .ini file with user defined options. ~~Valid commands in the~~A .ini file ~~are~~can ~~Base~~be ~~Folder~~used ==to ~~<folder>~~overwrite the default base and ~~Copy~~destination folders, and specify events/scenarios for models with events/scenarios in filenames. Valid options should be separated by ~~Destination~~a ==vertical ~~<folder>~~bar.<br> Combinations of the above are also valid, with the order of the optional switches not being important (-pmAllL would be treated the same as -pmLAll).<br> When using package model the default destination folder is created in the same directory as the .tcf file, with the prefix “pm_”. For example, C:\Projects\Modelling\TUFLOW\runs\Run_001.tcf will create a package in the folder “C:\Projects\Modelling\TUFLOW\runs\pm_Run_001\.<br> Three options are also available for handling of the binary processed files created by TUFLOW to speed up the simulation start. These options are:<br> ;* “-xf0”;<br> : Do not copy .xf files, only the original inputs are copied.<br> ;* “-xf1”; and<br> : Copy both raw input files and .xf files.<br> ;* “-xf2”<br> : Copy only .xf files, if xf files exist for an input only the xf will be copied.<br> ===GPU Solver Control===

Run TUFLOW From a Batch-file: Difference between revisions