Revision as of 16:30, 20 February 2025 view source Emilie Nielsen (talk \| contribs) Administrators 6,125 edits →Troubleshooting ← Older edit		Revision as of 14:44, 17 April 2025 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,365 edits No edit summary Newer edit →
Line 149: <li>After this command in the .tcf, add the following command to link the new 1D control file:</li> <font color="blue"><tt>ESTRY Control File </tt></font> <font color="red"><tt>== </tt></font> <tt>..\model\M04_1d_001.ecf</tt><br> <li>Depending on the speed of your computer, you may have noticed in the previous three modules that when TUFLOW is running, it is hard to read the TUFLOW console output because it updates too quickly. We can reduce the frequency of output to the ~~DOS~~console ~~screen~~window and also the TUFLOW Log File (.tlf). Include the following command at the end of the .tcf with the other output commands:<br> <font color="blue"><tt>Screen/Log Display Interval </tt></font> <font color="red"><tt>== </tt></font> <tt>40</tt><br> TUFLOW will write the output every 40 timesteps. For the 1.5 second timestep this means we will get output every 60 seconds of simulation time.<br> Line 288: [[TUFLOW_Message_2060 \| Error 2060 - Could not find a CN connection snapped to the end of HX line]] [[TUFLOW_Message_2024 \| Error 2024 - Could not find a 1D node snapped to CN line.]] [[Only_TUFLOW_DOS_Window_Archive \| Why does the TUFLOW ~~DOS~~console ~~Window~~window open, though the TCF isn’t read and the simulation doesn’t execute?]] = Advanced - HPC Solver (Optional) = Line 309: ==Results== Using the methods described above in the <u>[[Tutorial_Module01_Archive#Viewing_Results \| Viewing Results]]</u> section of Module 1. Check the simulation logs in the ~~DOS~~console window, .tlf and .hpc.tlf log files. * View the results in your preferred package. Do the logs and results appear different to the TUFLOW Classic simulation?

Tutorial Module04 Archive: Difference between revisions