Naming Convention: Difference between revisions

Content deleted Content added
No edit summary
Line 9:
Additionally, a sound naming convention can significantly reduce the time taken to locate files, especially in folders where hundreds of files are present, which may be the case for large modelling projects. Once a naming and numbering convention is adopted, then a <u>[[TUFLOW_Modelling_Log|modelling log]]</u> can more easily be kept.<br>
<br>
There is some simple advice on naming conventions in Section 11.2 of the <u>[httphttps://downloads.tuflow.com/Tuflow_archive/TUFLOW/Releases/2018-03/TUFLOW%20Documentation20Manual.aspx 20162018-03.pdf 2018 TUFLOW Manual]</u>.<br>
Most modelling these days incorporates use of the TUFLOW scenario and event management feature. This allows for wildcards to be incorporated in the file name as shown in Section 11.3 of the Manual. <u>[[TUFLOW Example Models|Example models]]</u> are available which demonstrate Scenario/Event management. You can then set up <u>[[ Run_TUFLOW_From_a_Batch-file#Looping_in_a_batch_file|batch file]]</u> to run various scenario combinations from the one TUFLOW Control File (TCF).<br>
<br>
The below sections provide information on the recommended naming convention for clearly identifying different types of TUFLOW input files. Guidance is also provided on a version numbering convention for control and input files during model development.<br>