Flood Modeller to TUFLOW: Difference between revisions

It is also possible to use the cross-sections from the Flood Modeller <b>.dat</b> file directly within a TUFLOW/ESTRY simulation. This means that for some simpler models, particularly those without structures, that conversion of the Flood Modeller model to an ESTRY format is not required with the cross-section data being used in a TUFLOW 1D /ESTRY model directly from the <b>.dat</b> file. Please, see the [https://docs.tuflow.com/classic-hpc/manual/2023-03/ECFCommands-1.html#ecfXSDatabase <font color="blue"><tt>XS Database</tt></font> <font color="red"><tt>==</tt></font> command] in the [https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW user manual] for more information which can be downloaded from here: .

When there is a requirement to convert a Flood Modeller 1D network, or part of a network, to TUFLOW ESTRY format this can be time consuming. A set of tools have been provided for you to assist this process. Currently, the tools are restricted to network geometry but if there is user-demand, this can be extended to boundary conditions, logical rules and the production of TUFLOW control files. There are two approaches, using either an executable or a Python tool, both of which undertake the same conversion. The advantage of the Python tool is that it is possible to add user-specified support for additional structures which are not supported currently. Once the Flood Modeller network has been converted to a set of ESTRY layers, these should be checked for connectivity and brought together in the ESTRY Control File to read into a TUFLOW?-ESTRY simulation.