Tuflow - User contributions [en]

TUFLOW Empty Files

2024-08-16T13:33:24Z

Angelos Livogiannis: /* TUFLOW Geometry Control file (TGC) */

=Introduction=

The native non-Graphical User Interface (GUI) form of TUFLOW uses Geographic Information System (GIS) files for its spatial inputs. TUFLOW requires precise GIS file formats associated with specific TUFLOW commands. The required fields for each input type are listed in the [https://downloads.tuflow.com/_archive/TUFLOW/Releases/2018-03/TUFLOW%20Manual.2018-03.pdf TUFLOW Manual]. For example, the '''2d_zsh_empty''' file associated with the <tt>Read GIS Z Shape</tt> <tt>==</tt> command requires the following data fields and types in the order shown below: 

<center>[[File:2d zsh fields.png]] </center>
 
Because of this file format requirement, the first task in any modelling project is to write template (empty) GIS files in the specific model projection system (as demonstrated in [[Tutorial_M01#Project_Initialisation|Tutorial Module 1]]). 

This page of the TUFLOW Wiki provides a reference list of the template (empty) GIS files, the associated TUFLOW command and a basic description of their function. 

Note: when using the shapefile format TUFLOW creates a dummy entry when creating empty files. Importing an empty layer into QGIS using the [[QGIS_TUFLOW_Import_Empty | Import Empty]] tool, will remove this dummy entry. Opening a template empty file directly in QGIS (without using the [[QGIS_TUFLOW_Import_Empty | Import Empty]] tool), the dummy entry will remain in the layer and garbled text shown in the attribute fields.

==TUFLOW Control file (TCF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_at_empty''' || <tt>Read GIS Auto Terminate</tt> <tt>==</tt> || Used to define locations where auto terminate tracking is desired.
|-
| rowspan=2| '''2d_cyc_empty''' || <tt>Read GIS Cyclone</tt> <tt>==</tt> ||rowspan=2| Used to apply a cyclone or hurricane boundary within TUFLOW, capturing the effects of wind and pressure fields created by severe storms, which can affect flooding and inundation in coastal area.
|-
| <tt>Read GIS Hurricane</tt> <tt>==</tt>
|-
| '''2d_fc_empty''' || <tt>Read GIS FC</tt> <tt>==</tt> || Used for 2D flow constrictions, representing additional losses associated with bridges or box culverts. This command has been superseded with the TGC commands: <tt>Read GIS FC Shape</tt> <tt>Read GIS Layered FC Shape</tt>. 
The template file and command only remain for the purpose of version backward compatibility.
|-
| '''2d_glo_empty''' || <tt>Read GIS GLO</tt> <tt>==</tt> || Used to define gauge level output (2d_glo) locations. The GLO command controls map output based on the height of the water at a specified location within the model domain.
|-
| '''2d_iwl_empty''' || <tt>Read GIS IWL</tt> <tt>==</tt> || Sets the initial water level in the model at the start of the simulation. The initial water level can vary spatially within the model. An equivalent initial Water level command also exists in the TGC.
|-
| '''2d_lp_empty''' || <tt>Read GIS LP</tt> <tt>==</tt> || This file contains details on the location of longitudinal profile outputs.
|-
| '''2d_oz_empty''' || <tt>Read GIS Output Zone</tt> <tt>==</tt> || This file contains one or more polygons defining the 2D regions to be output. This model input is used with the command <tt>Model Output Zones</tt> and the <tt>Define Output Zone</tt>/<tt>End Define</tt> definition block.
|-
| '''2d_po_empty''' || <tt>Read GIS PO</tt> <tt>==</tt> || This file contains lines and points defining plot output (PO) locations for 2D result time series graphs in Excel. PO only extracts results from 2D portions of the model. 1D results are ignored.
|-
| '''0d_rl_empty''' || <tt>Read GIS Reporting Location</tt> <tt>==</tt> || This file contains lines and points defining Reporting Location(s) (RL) for 1D and 2D result time series graphs in Excel.
|-
| rowspan=2| '''1d_wllp_empty''' || <tt>Read GIS XP WLL Points</tt> <tt>==</tt> ||rowspan=2| Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
|-
| <tt>Read GIS ISIS WLL Points</tt> <tt>==</tt>
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==ESTRY Control file (ECF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''1d_bc_empty''' || <tt>Read GIS BC </tt> <tt>==</tt> || Used to define the location and type of 1D boundary condition input.
|-
| '''1d_iwl_empty''' || <tt>Read GIS IWL </tt> <tt>==</tt> || Used to set the initial water level within a 1D channel or node at the start of a simulation.
|-
| '''1d_lc_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Used to provide links to tabular data of loss versus height coefficients at a structure. The LC stands for Loss Coefficients.
|-
| '''1d_mh_empty''' || <tt>Read GIS Manhole </tt> <tt>==</tt> || Used to define manhole locations and attributes.
|-
| '''1d_na_empty''' || <tt>Read GIS Node </tt> <tt>==</tt> || Used to set nodal surface areas.
|-
| '''1d_nd_empty''' || <tt>Read GIS Node </tt> <tt>==</tt> || Used to define 1D node locations and attributes.
|-
| '''1d_nwk_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define channel and node locations and attributes. Common channel types include, open channels, culverts, bridges, weirs.
|-
| '''1d_nwkb_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define channel and node locations and attributes. Common channel types include, open channels, culverts, bridges, weirs. The difference between the 1d_nwkb and standard 1d_nwk is that the pblockage attribute field accepts characters allowing the user to input matrix blockage.
|-
| '''1d_nwke_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define grouped structure locations and attributes. For example, weirs representing overtopping of a bridge or culvert structure can be specified using a single GIS feature in the 1d_nwke file. By comparison, multiple line features would be required if the same input was defined in a 1d_nwk file.
|-
| '''1d_pit_empty''' || <tt>Read GIS Pits </tt> <tt>==</tt> || Defines the location and attributes associated with virtual pipes for a GPU model.
|-
| '''1d_tab_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Reads links to tabular inputs associated with cross-section profiles (1d_xs), nodal surface areas (1d_na) and bridge loss coefficients (1d_bg).
|-
| '''1d_WLL_empty''' || <tt>Read GIS WLL </tt> <tt>==</tt> || Used to translate 1D results into 2D map output for viewing in SMS, WaterRide, Blue Kenu and GIS Software.
|-
| '''1d_wllp_empty''' || <tt>Read GIS WLL Points </tt> <tt>==</tt> || Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
|-
| '''1d_xs_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Used to set cross-section profiles and hydraulic properties.
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Geometry Control file (TGC)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| rowspan=2|'''2d_bc_empty''' || <tt>Read GIS Code BC</tt> <tt>==</tt> || Used to set the code status of a cell (active or inactive). 
''This is an alternative method to: "2d_code_empty / <tt>Read GIS Code</tt> <tt>==</tt>". ''
''Note: "2d_bc_empty" '''CANNOT''' be used with <tt>Read GIS Code</tt> <tt>==</tt>''
|-
| <tt>Read GIS Z HX Line</tt> <tt>==</tt> || Used in combination with 2d_bc (HX) layer from the TBC to set the cell elevations along HX lines at the interface between 1D channels nested with a 2D domain.
|-
| '''2d_bg_empty''' || rowspan=2| <tt>Read GIS BG Shape</tt> <tt>==</tt> || rowspan=2| Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| '''2d_bg_empty_pts'''
|-.
|-
| rowspan=2|'''2d_code_empty''' || <tt>Read GIS Code</tt> <tt>==</tt> || Used to set the code status of a cell (1 = active or 0 = inactive).
|-
| <tt>Read GIS Code INVERT</tt> <tt>==</tt> || Used to set the code status of a cell (active or inactive). The inverse value defined by the <tt>Read GIS Code</tt> <tt>==</tt> is applied. This feature is most commonly used during in multiple domain 2D2D models, as discussed in [[TUFLOW_2D2D_BC_Advice|Multiple 2D Modelling Advice]].
|-
|'''2d_cwf_empty''' || <tt>Read GIS CWF</tt> <tt>==</tt> || Used to define location to reduced 2D cell flow width.
|-
| '''2d_fcsh_empty''' || <tt>Read GIS FC Shape</tt> <tt>==</tt> || Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input only account for flow below the bridge obvert (soffit).
|-
| '''2d_flc_empty''' || <tt>Read GIS FLC </tt> <tt>==</tt> || Used to apply an additional energy loss at the 2D cell side. The form or energy loss can be applied as fixed values or on a form loss per unit length basis.
|-
| rowspan=2|'''2d_gw_empty''' || <tt>Read GIS GWL</tt> <tt>==</tt> || rowspan=2| Ground water level inputs.
|-
| <tt>Read GIS GWD</tt> <tt>==</tt>
|-
| '''2d_hx_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the locations of 2D boundaries and 2D/1D dynamic links. For large models it may be wise to separate the boundary conditions from the 1D/2D links, in which case the 2d_bc prefix can be substituted with 2d_hx_ and 2d_sx_. Cell code values may also be defined in this layer.
|-
| '''2d_iwl_empty''' || <tt>Read GIS IWL</tt> <tt>==</tt> || Sets the initial water level in the model at the start of the simulation. The initial water level can vary spatially within the model. An equivalent initial Water level command also exists in the TCF.
|-
| '''2d_Ifcsh_empty''' || rowspan=2| <tt>Read GIS Layered FC Shape</tt> <tt>==</tt> || rowspan=2| Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| '''2d_lfcsh_empty_pts'''
|-.
| '''2d_loc_empty''' || <tt>Read GIS Location</tt> <tt>==</tt> || Used to define the 2D mesh (grid) origin and orientation.
|-
| '''2d_mat_empty''' || <tt>Read GIS MAT</tt> <tt>==</tt>|| Used to define 2D materials (land use) inputs.
|-
| '''2d_obj_empty''' || <tt>Read GIS Objects</tt> <tt>==</tt>|| Used to represent receptors (such as properties or buildings). TUFLOW records the flood level and simulation time at one or more gauge(s) when receptors are first inundated above their trigger inundation levels (e.g. floor levels).
|-
| '''2d_rec_empty''' || <tt>Read GIS Objects</tt> <tt>==</tt>|| Used to represent receptors (such as properties or buildings). TUFLOW records the flood level and simulation time at one or more gauge(s) when receptors are first inundated above their trigger inundation levels (e.g. floor levels).
|-
| '''2d_soil_empty''' || <tt>Read GIS Soil</tt> <tt>==</tt> || Used to define 2D soil type inputs for infiltration parameterisation.
|-
| '''2d_sx_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the locations of 2D boundaries and 2D/1D dynamic links. For large models it may be wise to separate the boundary conditions from the 1D/2D links, in which case the 2d_bc prefix can be substituted with 2d_hx_ and 2d_sx_. Cell code values may also be defined in this layer.
|-
| '''2d_vzsh_empty''' || <tt>Read GIS Variable Z Shape</tt> <tt>==</tt> || Used to define the final 3D shape of the Zpts at the completion of a breach, or other change in topographic shape, during a simulation.
|-
| '''2d_wrf_empty''' || <tt>Read GIS Wrf</tt> <tt>==</tt> || Used to adjust the weir factor locally, e.g. faces along a road embankment.
|-
| '''2d_z_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). This command has been superseded with the TGC commands: <tt>Read GIS GIS Z Shape</tt> 
The template file and command only remain for the purpose of version backward compatibility.
|-
| '''2d_za_empty''' || <tt>Read GIS Zpts</tt> <tt>==</tt> || Used to define areas (polygons) of elevations at a constant height. This file is typically created by renaming the 2d_z__empty file
|-
| '''2d_zlg_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zln_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zlr_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zpt_empty''' || <tt>Read GIS Zpts</tt> <tt>==</tt> || Used to define the elevations at the 2D cells mid-sides, corners and centres.
|-
| '''2d_zsh_empty''' || <tt>Read GIS Z Shape</tt> <tt>==</tt> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). Polygons and point features can be used to create TINs which are either independent of, or alternatively merge with the surrounding topography.
|-
| '''2d_zshr_empty''' || <tt>Read GIS Z Shape Route</tt> <tt>==</tt> || Used to provide output on the degree of inundation along evacuation routes. This feature is useful during flood evacuation assessments. The model output includes details on warning time, flood hazard (e.g. depth and velocity) and duration that an evacuation route is isolated.
|-
| '''2d_ztin_empty''' || <tt>Read Grid Zpts</tt> <tt>==</tt> || Used to define 2D and 3D shapes for changing the elevations. Lines can be specified with a width (thickness), and polygons are used as the boundaries for creating TINs (triangulations).
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Boundary Control file (TBC)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_bc_empty''' || <tt>Read GIS BC</tt> <tt>==</tt> || Used to define the location and attributes of 2D model boundary conditions. Including:
* External flow verse time boundaries
* External flow verse water level boundaries
* External water level verse time boundaries
* Internal 1D/2D connections
* Internal 2D/2D connections
|-
| '''2d_rf_empty''' || <tt>Read GIS RF</tt> <tt>==</tt> || Used for ''"direct rainfall"'' modelling, also called ''"rainfall on grid"'' or ''"distributed hydrology"'' modelling.
|-
| rowspan=2| '''2d_sa_empty''' || <tt>Read GIS SA</tt> <tt>==</tt> || rowspan=2| Used to define the location of internal source area flow verse time boundaries.
|-
| <tt>Read GIS Streams</tt> <tt>==</tt>
|-
| '''2d_sa_rf_empty''' || <tt>Read GIS SA RF</tt> <tt>==</tt> ||Used to define the location of internal source area flow verse time boundaries. The model input is specified using rainfall hyetographs (mm versus hours) instead of flow hydrographs (flow verse time).
|-
| '''2d_sa_tr_empty''' || <tt>Read GIS SA Trigger</tt> <tt>==</tt> || Used to define the polygons of sub-catchment areas for applying a source (flow) or rainfall directly onto 2D domains. 2d_sa_tr includes additional attributes required for the SA Trigger option.
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Quadtree Control File (QCF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_qnl_empty''' || <tt>Read GIS Nesting </tt> <tt>==</tt> || Used to define polygons of mesh refinement (different levels).
|-

| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

 
 
{{Tips Navigation
|uplink=[[ TUFLOW_Modelling_Guidance | Back to TUFLOW Modelling Guidance]]
}}

TUFLOW Empty Files

2024-08-15T17:40:57Z

Angelos Livogiannis:

=Introduction=

The native non-Graphical User Interface (GUI) form of TUFLOW uses Geographic Information System (GIS) files for its spatial inputs. TUFLOW requires precise GIS file formats associated with specific TUFLOW commands. The required fields for each input type are listed in the [https://downloads.tuflow.com/_archive/TUFLOW/Releases/2018-03/TUFLOW%20Manual.2018-03.pdf TUFLOW Manual]. For example, the '''2d_zsh_empty''' file associated with the <tt>Read GIS Z Shape</tt> <tt>==</tt> command requires the following data fields and types in the order shown below: 

<center>[[File:2d zsh fields.png]] </center>
 
Because of this file format requirement, the first task in any modelling project is to write template (empty) GIS files in the specific model projection system (as demonstrated in [[Tutorial_M01#Project_Initialisation|Tutorial Module 1]]). 

This page of the TUFLOW Wiki provides a reference list of the template (empty) GIS files, the associated TUFLOW command and a basic description of their function. 

Note: when using the shapefile format TUFLOW creates a dummy entry when creating empty files. Importing an empty layer into QGIS using the [[QGIS_TUFLOW_Import_Empty | Import Empty]] tool, will remove this dummy entry. Opening a template empty file directly in QGIS (without using the [[QGIS_TUFLOW_Import_Empty | Import Empty]] tool), the dummy entry will remain in the layer and garbled text shown in the attribute fields.

==TUFLOW Control file (TCF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_at_empty''' || <tt>Read GIS Auto Terminate</tt> <tt>==</tt> || Used to define locations where auto terminate tracking is desired.
|-
| rowspan=2| '''2d_cyc_empty''' || <tt>Read GIS Cyclone</tt> <tt>==</tt> ||rowspan=2| Used to apply a cyclone or hurricane boundary within TUFLOW, capturing the effects of wind and pressure fields created by severe storms, which can affect flooding and inundation in coastal area.
|-
| <tt>Read GIS Hurricane</tt> <tt>==</tt>
|-
| '''2d_fc_empty''' || <tt>Read GIS FC</tt> <tt>==</tt> || Used for 2D flow constrictions, representing additional losses associated with bridges or box culverts. This command has been superseded with the TGC commands: <tt>Read GIS FC Shape</tt> <tt>Read GIS Layered FC Shape</tt>. 
The template file and command only remain for the purpose of version backward compatibility.
|-
| '''2d_glo_empty''' || <tt>Read GIS GLO</tt> <tt>==</tt> || Used to define gauge level output (2d_glo) locations. The GLO command controls map output based on the height of the water at a specified location within the model domain.
|-
| '''2d_iwl_empty''' || <tt>Read GIS IWL</tt> <tt>==</tt> || Sets the initial water level in the model at the start of the simulation. The initial water level can vary spatially within the model. An equivalent initial Water level command also exists in the TGC.
|-
| '''2d_lp_empty''' || <tt>Read GIS LP</tt> <tt>==</tt> || This file contains details on the location of longitudinal profile outputs.
|-
| '''2d_oz_empty''' || <tt>Read GIS Output Zone</tt> <tt>==</tt> || This file contains one or more polygons defining the 2D regions to be output. This model input is used with the command <tt>Model Output Zones</tt> and the <tt>Define Output Zone</tt>/<tt>End Define</tt> definition block.
|-
| '''2d_po_empty''' || <tt>Read GIS PO</tt> <tt>==</tt> || This file contains lines and points defining plot output (PO) locations for 2D result time series graphs in Excel. PO only extracts results from 2D portions of the model. 1D results are ignored.
|-
| '''0d_rl_empty''' || <tt>Read GIS Reporting Location</tt> <tt>==</tt> || This file contains lines and points defining Reporting Location(s) (RL) for 1D and 2D result time series graphs in Excel.
|-
| rowspan=2| '''1d_wllp_empty''' || <tt>Read GIS XP WLL Points</tt> <tt>==</tt> ||rowspan=2| Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
|-
| <tt>Read GIS ISIS WLL Points</tt> <tt>==</tt>
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==ESTRY Control file (ECF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''1d_bc_empty''' || <tt>Read GIS BC </tt> <tt>==</tt> || Used to define the location and type of 1D boundary condition input.
|-
| '''1d_iwl_empty''' || <tt>Read GIS IWL </tt> <tt>==</tt> || Used to set the initial water level within a 1D channel or node at the start of a simulation.
|-
| '''1d_lc_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Used to provide links to tabular data of loss versus height coefficients at a structure. The LC stands for Loss Coefficients.
|-
| '''1d_mh_empty''' || <tt>Read GIS Manhole </tt> <tt>==</tt> || Used to define manhole locations and attributes.
|-
| '''1d_na_empty''' || <tt>Read GIS Node </tt> <tt>==</tt> || Used to set nodal surface areas.
|-
| '''1d_nd_empty''' || <tt>Read GIS Node </tt> <tt>==</tt> || Used to define 1D node locations and attributes.
|-
| '''1d_nwk_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define channel and node locations and attributes. Common channel types include, open channels, culverts, bridges, weirs.
|-
| '''1d_nwkb_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define channel and node locations and attributes. Common channel types include, open channels, culverts, bridges, weirs. The difference between the 1d_nwkb and standard 1d_nwk is that the pblockage attribute field accepts characters allowing the user to input matrix blockage.
|-
| '''1d_nwke_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define grouped structure locations and attributes. For example, weirs representing overtopping of a bridge or culvert structure can be specified using a single GIS feature in the 1d_nwke file. By comparison, multiple line features would be required if the same input was defined in a 1d_nwk file.
|-
| '''1d_pit_empty''' || <tt>Read GIS Pits </tt> <tt>==</tt> || Defines the location and attributes associated with virtual pipes for a GPU model.
|-
| '''1d_tab_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Reads links to tabular inputs associated with cross-section profiles (1d_xs), nodal surface areas (1d_na) and bridge loss coefficients (1d_bg).
|-
| '''1d_WLL_empty''' || <tt>Read GIS WLL </tt> <tt>==</tt> || Used to translate 1D results into 2D map output for viewing in SMS, WaterRide, Blue Kenu and GIS Software.
|-
| '''1d_wllp_empty''' || <tt>Read GIS WLL Points </tt> <tt>==</tt> || Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
|-
| '''1d_xs_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Used to set cross-section profiles and hydraulic properties.
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Geometry Control file (TGC)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| rowspan=2|'''2d_bc_empty''' || <tt>Read GIS Code BC</tt> <tt>==</tt> || Used to set the code status of a cell (active or inactive). 
''This is an alternative method to: "2d_code_empty / <tt>Read GIS Code</tt> <tt>==</tt>". ''
''Note: "2d_bc_empty" '''CANNOT''' be used with <tt>Read GIS Code</tt> <tt>==</tt>''
|-
| <tt>Read GIS Z HX Line</tt> <tt>==</tt> || Used in combination with 2d_bc (HX) layer from the TBC to set the cell elevations along HX lines at the interface between 1D channels nested with a 2D domain.
|-
| '''2d_bg_empty''' || rowspan=2| <tt>Read GIS BG Shape</tt> <tt>==</tt> || rowspan=2| Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| '''2d_bg_empty_pts'''
|-.
|-
| rowspan=2|'''2d_code_empty''' || <tt>Read GIS Code</tt> <tt>==</tt> || Used to set the code status of a cell (1 = active or 0 = inactive).
|-
| <tt>Read GIS Code INVERT</tt> <tt>==</tt> || Used to set the code status of a cell (active or inactive). The inverse value defined by the <tt>Read GIS Code</tt> <tt>==</tt> is applied. This feature is most commonly used during in multiple domain 2D2D models, as discussed in [[TUFLOW_2D2D_BC_Advice|Multiple 2D Modelling Advice]].
|-
| rowspan=2| '''2d_cwf_empty''' || <tt>Read GIS CWF</tt> <tt>==</tt> ||rowspan=2| Used to define location to reduced 2D cell flow width.
|-
| <tt>Read GRID CWF</tt> <tt>==</tt>
|-
| '''2d_fcsh_empty''' || <tt>Read GIS FC Shape</tt> <tt>==</tt> || Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input only account for flow below the bridge obvert (soffit).
|-
| '''2d_flc_empty''' || <tt>Read GIS FLC </tt> <tt>==</tt> || Used to apply an additional energy loss at the 2D cell side. The form or energy loss can be applied as fixed values or on a form loss per unit length basis.
|-
| rowspan=2|'''2d_gw_empty''' || <tt>Read GIS GWL</tt> <tt>==</tt> || rowspan=2| Ground water level inputs.
|-
| <tt>Read GIS GWD</tt> <tt>==</tt>
|-
| '''2d_hx_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the locations of 2D boundaries and 2D/1D dynamic links. For large models it may be wise to separate the boundary conditions from the 1D/2D links, in which case the 2d_bc prefix can be substituted with 2d_hx_ and 2d_sx_. Cell code values may also be defined in this layer.
|-
| '''2d_iwl_empty''' || <tt>Read GIS IWL</tt> <tt>==</tt> || Sets the initial water level in the model at the start of the simulation. The initial water level can vary spatially within the model. An equivalent initial Water level command also exists in the TCF.
|-
| '''2d_Ifcsh_empty''' || rowspan=2| <tt>Read GIS Layered FC Shape</tt> <tt>==</tt> || rowspan=2| Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| '''2d_lfcsh_empty_pts'''
|-.
| '''2d_loc_empty''' || <tt>Read GIS Location</tt> <tt>==</tt> || Used to define the 2D mesh (grid) origin and orientation.
|-
| '''2d_mat_empty''' || <tt>Read GIS MAT</tt> <tt>==</tt>|| Used to define 2D materials (land use) inputs.
|-
| '''2d_obj_empty''' || <tt>Read GIS Objects</tt> <tt>==</tt>|| Used to represent receptors (such as properties or buildings). TUFLOW records the flood level and simulation time at one or more gauge(s) when receptors are first inundated above their trigger inundation levels (e.g. floor levels).
|-
| '''2d_rec_empty''' || <tt>Read GIS Objects</tt> <tt>==</tt>|| Used to represent receptors (such as properties or buildings). TUFLOW records the flood level and simulation time at one or more gauge(s) when receptors are first inundated above their trigger inundation levels (e.g. floor levels).
|-
| '''2d_soil_empty''' || <tt>Read GIS Soil</tt> <tt>==</tt> || Used to define 2D soil type inputs for infiltration parameterisation.
|-
| '''2d_sx_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the locations of 2D boundaries and 2D/1D dynamic links. For large models it may be wise to separate the boundary conditions from the 1D/2D links, in which case the 2d_bc prefix can be substituted with 2d_hx_ and 2d_sx_. Cell code values may also be defined in this layer.
|-
| '''2d_vzsh_empty''' || <tt>Read GIS Variable Z Shape</tt> <tt>==</tt> || Used to define the final 3D shape of the Zpts at the completion of a breach, or other change in topographic shape, during a simulation.
|-
| '''2d_wrf_empty''' || <tt>Read GIS Wrf</tt> <tt>==</tt> || Used to adjust the weir factor locally, e.g. faces along a road embankment.
|-
| '''2d_z_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). This command has been superseded with the TGC commands: <tt>Read GIS GIS Z Shape</tt> 
The template file and command only remain for the purpose of version backward compatibility.
|-
| '''2d_za_empty''' || <tt>Read GIS Zpts</tt> <tt>==</tt> || Used to define areas (polygons) of elevations at a constant height. This file is typically created by renaming the 2d_z__empty file
|-
| '''2d_zlg_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zln_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zlr_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zpt_empty''' || <tt>Read GIS Zpts</tt> <tt>==</tt> || Used to define the elevations at the 2D cells mid-sides, corners and centres.
|-
| '''2d_zsh_empty''' || <tt>Read GIS Z Shape</tt> <tt>==</tt> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). Polygons and point features can be used to create TINs which are either independent of, or alternatively merge with the surrounding topography.
|-
| '''2d_zshr_empty''' || <tt>Read GIS Z Shape Route</tt> <tt>==</tt> || Used to provide output on the degree of inundation along evacuation routes. This feature is useful during flood evacuation assessments. The model output includes details on warning time, flood hazard (e.g. depth and velocity) and duration that an evacuation route is isolated.
|-
| '''2d_ztin_empty''' || <tt>Read Grid Zpts</tt> <tt>==</tt> || Used to define 2D and 3D shapes for changing the elevations. Lines can be specified with a width (thickness), and polygons are used as the boundaries for creating TINs (triangulations).
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Boundary Control file (TBC)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_bc_empty''' || <tt>Read GIS BC</tt> <tt>==</tt> || Used to define the location and attributes of 2D model boundary conditions. Including:
* External flow verse time boundaries
* External flow verse water level boundaries
* External water level verse time boundaries
* Internal 1D/2D connections
* Internal 2D/2D connections
|-
| '''2d_rf_empty''' || <tt>Read GIS RF</tt> <tt>==</tt> || Used for ''"direct rainfall"'' modelling, also called ''"rainfall on grid"'' or ''"distributed hydrology"'' modelling.
|-
| rowspan=2| '''2d_sa_empty''' || <tt>Read GIS SA</tt> <tt>==</tt> || rowspan=2| Used to define the location of internal source area flow verse time boundaries.
|-
| <tt>Read GIS Streams</tt> <tt>==</tt>
|-
| '''2d_sa_rf_empty''' || <tt>Read GIS SA RF</tt> <tt>==</tt> ||Used to define the location of internal source area flow verse time boundaries. The model input is specified using rainfall hyetographs (mm versus hours) instead of flow hydrographs (flow verse time).
|-
| '''2d_sa_tr_empty''' || <tt>Read GIS SA Trigger</tt> <tt>==</tt> || Used to define the polygons of sub-catchment areas for applying a source (flow) or rainfall directly onto 2D domains. 2d_sa_tr includes additional attributes required for the SA Trigger option.
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Quadtree Control File (QCF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_qnl_empty''' || <tt>Read GIS Nesting </tt> <tt>==</tt> || Used to define polygons of mesh refinement (different levels).
|-

| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

 
 
{{Tips Navigation
|uplink=[[ TUFLOW_Modelling_Guidance | Back to TUFLOW Modelling Guidance]]
}}

TUFLOW Empty Files

2024-08-15T17:02:21Z

Angelos Livogiannis: /* TUFLOW Geometry Control file (TGC) */

=Introduction=

The native non-Graphical User Interface (GUI) form of TUFLOW uses Geographic Information System (GIS) files for its spatial inputs. TUFLOW requires precise GIS file formats associated with specific TUFLOW commands. The required fields for each input type are listed in the [https://downloads.tuflow.com/_archive/TUFLOW/Releases/2018-03/TUFLOW%20Manual.2018-03.pdf TUFLOW Manual]. For example, the '''2d_zsh_empty''' file associated with the <tt>Read GIS Z Shape</tt> <tt>==</tt> command requires the following data fields and types in the order shown below: 

<center>[[File:2d zsh fields.png]] </center>
 
Because of this file format requirement, the first task in any modelling project is to write template (empty) GIS files in the specific model projection system (as demonstrated in [[Tutorial_M01#Project_Initialisation|Tutorial Module 1]]). 

This page of the TUFLOW Wiki provides a reference list of the template (empty) GIS files, the associated TUFLOW command and a basic description of their function. 

Note: when using the shapefile format TUFLOW creates a dummy entry when creating empty files. Importing an empty layer into QGIS using the [[QGIS_TUFLOW_Import_Empty | Import Empty]] tool, will remove this dummy entry. Opening a template empty file directly in QGIS (without using the [[QGIS_TUFLOW_Import_Empty | Import Empty]] tool), the dummy entry will remain in the layer and garbled text shown in the attribute fields.

==TUFLOW Control file (TCF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_at_empty''' || <tt>Read GIS Auto Terminate</tt> <tt>==</tt> || Used to define locations where auto terminate tracking is desired
|-
| rowspan=2| '''2d_cyc_empty''' || <tt>Read GIS Cyclone</tt> <tt>==</tt> ||rowspan=2| Used to apply a cyclone or hurricane boundary within TUFLOW, capturing the effects of wind and pressure fields created by severe storms, which can affect flooding and inundation in coastal area.
|-
| <tt>Read GIS Hurricane</tt> <tt>==</tt>
|-
| '''2d_fc_empty''' || <tt>Read GIS FC</tt> <tt>==</tt> || Used for 2D flow constrictions, representing additional losses associated with bridges or box culverts. This command has been superseded with the TGC commands: <tt>Read GIS FC Shape</tt> <tt>Read GIS Layered FC Shape</tt>. 
The template file and command only remain for the purpose of version backward compatibility.
|-
| '''2d_glo_empty''' || <tt>Read GIS GLO</tt> <tt>==</tt> || Used to define gauge level output (2d_glo) locations. The GLO command controls map output based on the height of the water at a specified location within the model domain.
|-
| '''2d_iwl_empty''' || <tt>Read GIS IWL</tt> <tt>==</tt> || Sets the initial water level in the model at the start of the simulation. The initial water level can vary spatially within the model. An equivalent initial Water level command also exists in the TGC.
|-
| '''2d_lp_empty''' || <tt>Read GIS LP</tt> <tt>==</tt> || This file contains details on the location of longitudinal profile outputs.
|-
| '''2d_oz_empty''' || <tt>Read GIS Output Zone</tt> <tt>==</tt> || This file contains one or more polygons defining the 2D regions to be output. This model input is used with the command <tt>Model Output Zones</tt> and the <tt>Define Output Zone</tt>/<tt>End Define</tt> definition block.
|-
| '''2d_po_empty''' || <tt>Read GIS PO</tt> <tt>==</tt> || This file contains lines and points defining plot output (PO) locations for 2D result time series graphs in Excel. PO only extracts results from 2D portions of the model. 1D results are ignored.
|-
| '''0d_rl_empty''' || <tt>Read GIS Reporting Location</tt> <tt>==</tt> || This file contains lines and points defining Reporting Location(s) (RL) for 1D and 2D result time series graphs in Excel.
|-
| rowspan=2| '''1d_wllp_empty''' || <tt>Read GIS XP WLL Points</tt> <tt>==</tt> ||rowspan=2| Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
|-
| <tt>Read GIS ISIS WLL Points</tt> <tt>==</tt>
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==ESTRY Control file (ECF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''1d_bc_empty''' || <tt>Read GIS BC </tt> <tt>==</tt> || Used to define the location and type of 1D boundary condition input
|-
| '''1d_iwl_empty''' || <tt>Read GIS IWL </tt> <tt>==</tt> || Used to set the initial water level within a 1D channel or node at the start of a simulation.
|-
| '''1d_lc_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Used to provide links to tabular data of loss versus height coefficients at a structure. The LC stands for Loss Coefficients.
|-
| '''1d_mh_empty''' || <tt>Read GIS Manhole </tt> <tt>==</tt> || Used to define manhole locations and attributes.
|-
| '''1d_na_empty''' || <tt>Read GIS Node </tt> <tt>==</tt> || Used to set nodal surface areas.
|-
| '''1d_nd_empty''' || <tt>Read GIS Node </tt> <tt>==</tt> || Used to define 1D node locations and attributes.
|-
| '''1d_nwk_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define channel and node locations and attributes. Common channel types include, open channels, culverts, bridges, weirs.
|-
| '''1d_nwkb_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define channel and node locations and attributes. Common channel types include, open channels, culverts, bridges, weirs. The difference between the 1d_nwkb and standard 1d_nwk is that the pblockage attribute field accepts characters allowing the user to input matrix blockage.
|-
| '''1d_nwke_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define grouped structure locations and attributes. For example, weirs representing overtopping of a bridge or culvert structure can be specified using a single GIS feature in the 1d_nwke file. By comparison, multiple line features would be required if the same input was defined in a 1d_nwk file.
|-
| '''1d_pit_empty''' || <tt>Read GIS Pits </tt> <tt>==</tt> || Defines the location and attributes associated with virtual pipes for a GPU model.
|-
| '''1d_tab_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Reads links to tabular inputs associated with cross-section profiles (1d_xs), nodal surface areas (1d_na) and bridge loss coefficients (1d_bg).
|-
| '''1d_WLL_empty''' || <tt>Read GIS WLL </tt> <tt>==</tt> || Used to translate 1D results into 2D map output for viewing in SMS, WaterRide, Blue Kenu and GIS Software.
|-
| '''1d_wllp_empty''' || <tt>Read GIS WLL Points </tt> <tt>==</tt> || Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
|-
| '''1d_xs_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Used to set cross-section profiles and hydraulic properties.
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Geometry Control file (TGC)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| rowspan=2|'''2d_bc_empty''' || <tt>Read GIS Code BC</tt> <tt>==</tt> || Used to set the code status of a cell (active or inactive). 
''This is an alternative method to: "2d_code_empty / <tt>Read GIS Code</tt> <tt>==</tt>". ''
''Note: "2d_bc_empty" '''CANNOT''' be used with <tt>Read GIS Code</tt> <tt>==</tt>''
|-
| <tt>Read GIS Z HX Line</tt> <tt>==</tt> || Used in combination with 2d_bc (HX) layer from the TBC to set the cell elevations along HX lines at the interface between 1D channels nested with a 2D domain.
|-
| '''2d_bg_empty''' || rowspan=2| <tt>Read GIS BG Shape</tt> <tt>==</tt> || rowspan=2| Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| '''2d_bg_empty_pts'''
|-.
|-
| rowspan=2|'''2d_code_empty''' || <tt>Read GIS Code</tt> <tt>==</tt> || Used to set the code status of a cell (1 = active or 0 = inactive).
|-
| <tt>Read GIS Code INVERT</tt> <tt>==</tt> || Used to set the code status of a cell (active or inactive). The inverse value defined by the <tt>Read GIS Code</tt> <tt>==</tt> is applied. This feature is most commonly used during in multiple domain 2D2D models, as discussed in [[TUFLOW_2D2D_BC_Advice|Multiple 2D Modelling Advice]].
|-
| rowspan=2| '''2d_cwf_empty''' || <tt>Read GIS CWF</tt> <tt>==</tt> ||rowspan=2| Used to define location to reduced 2D cell flow width.
|-
| <tt>Read GRID CWF</tt> <tt>==</tt>
|-
| '''2d_fcsh_empty''' || <tt>Read GIS FC Shape</tt> <tt>==</tt> || Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input only account for flow below the bridge obvert (soffit).
|-
| '''2d_flc_empty''' || <tt>Read GIS FLC </tt> <tt>==</tt> || Used to apply an additional energy loss at the 2D cell side. The form or energy loss can be applied as fixed values or on a form loss per unit length basis.
|-
| rowspan=2|'''2d_gw_empty''' || <tt>Read GIS GWL</tt> <tt>==</tt> || rowspan=2| Ground water level inputs.
|-
| <tt>Read GIS GWD</tt> <tt>==</tt>
|-
| '''2d_hx_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the locations of 2D boundaries and 2D/1D dynamic links. For large models it may be wise to separate the boundary conditions from the 1D/2D links, in which case the 2d_bc prefix can be substituted with 2d_hx_ and 2d_sx_. Cell code values may also be defined in this layer.
|-
| '''2d_iwl_empty''' || <tt>Read GIS IWL</tt> <tt>==</tt> || Sets the initial water level in the model at the start of the simulation. The initial water level can vary spatially within the model. An equivalent initial Water level command also exists in the TCF.
|-
| '''2d_Ifcsh_empty''' || rowspan=2| <tt>Read GIS Layered FC Shape</tt> <tt>==</tt> || rowspan=2| Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| '''2d_lfcsh_empty_pts'''
|-.
| '''2d_loc_empty''' || <tt>Read GIS Location</tt> <tt>==</tt> || Used to define the 2D mesh (grid) origin and orientation.
|-
| '''2d_mat_empty''' || <tt>Read GIS MAT</tt> <tt>==</tt>|| Used to define 2D materials (land use) inputs.
|-
| '''2d_obj_empty''' || <tt>Read GIS Objects</tt> <tt>==</tt>|| Used to represent receptors (such as properties or buildings). TUFLOW records the flood level and simulation time at one or more gauge(s) when receptors are first inundated above their trigger inundation levels (e.g. floor levels).
|-
| '''2d_rec_empty''' || <tt>Read GIS Objects</tt> <tt>==</tt>|| Used to represent receptors (such as properties or buildings). TUFLOW records the flood level and simulation time at one or more gauge(s) when receptors are first inundated above their trigger inundation levels (e.g. floor levels).
|-
| '''2d_soil_empty''' || <tt>Read GIS Soil</tt> <tt>==</tt> || Used to define 2D soil type inputs for infiltration parameterisation
|-
| '''2d_sx_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the locations of 2D boundaries and 2D/1D dynamic links. For large models it may be wise to separate the boundary conditions from the 1D/2D links, in which case the 2d_bc prefix can be substituted with 2d_hx_ and 2d_sx_. Cell code values may also be defined in this layer.
|-
| '''2d_vzsh_empty''' || <tt>Read GIS Variable Z Shape</tt> <tt>==</tt> || Used to define the final 3D shape of the Zpts at the completion of a breach, or other change in topographic shape, during a simulation.
|-
| '''2d_wrf_empty''' || <tt>Read GIS Wrf</tt> <tt>==</tt> || Used to adjust the weir factor locally, e.g. faces along a road embankment.
|-
| '''2d_z_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). This command has been superseded with the TGC commands: <tt>Read GIS GIS Z Shape</tt> 
The template file and command only remain for the purpose of version backward compatibility.
|-
| '''2d_za_empty''' || <tt>Read GIS Zpts</tt> <tt>==</tt> || Used to define areas (polygons) of elevations at a constant height. This file is typically created by renaming the 2d_z__empty file
|-
| '''2d_zlg_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zln_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zlr_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zpt_empty''' || <tt>Read GIS Zpts</tt> <tt>==</tt> || Used to define the elevations at the 2D cells mid-sides, corners and centres.
|-
| '''2d_zsh_empty''' || <tt>Read GIS Z Shape</tt> <tt>==</tt> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). Polygons and point features can be used to create TINs which are either independent of, or alternatively merge with the surrounding topography.
|-
| '''2d_zshr_empty''' || <tt>Read GIS Z Shape Route</tt> <tt>==</tt> || Used to provide output on the degree of inundation along evacuation routes. This feature is useful during flood evacuation assessments. The model output includes details on warning time, flood hazard (e.g. depth and velocity) and duration that an evacuation route is isolated.
|-
| '''2d_ztin_empty''' || <tt>Read Grid Zpts</tt> <tt>==</tt> || Used to define 2D and 3D shapes for changing the elevations. Lines can be specified with a width (thickness), and polygons are used as the boundaries for creating TINs (triangulations).
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Boundary Control file (TBC)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_bc_empty''' || <tt>Read GIS BC</tt> <tt>==</tt> || Used to define the location and attributes of 2D model boundary conditions. Including:
* External flow verse time boundaries
* External flow verse water level boundaries
* External water level verse time boundaries
* Internal 1D/2D connections
* Internal 2D/2D connections
|-
| '''2d_rf_empty''' || <tt>Read GIS RF</tt> <tt>==</tt> || Used for ''"direct rainfall"'' modelling, also called ''"rainfall on grid"'' or ''"distributed hydrology"'' modelling.
|-
| rowspan=2| '''2d_sa_empty''' || <tt>Read GIS SA</tt> <tt>==</tt> || rowspan=2| Used to define the location of internal source area flow verse time boundaries.
|-
| <tt>Read GIS Streams</tt> <tt>==</tt>
|-
| '''2d_sa_rf_empty''' || <tt>Read GIS SA RF</tt> <tt>==</tt> ||Used to define the location of internal source area flow verse time boundaries. The model input is specified using rainfall hyetographs (mm versus hours) instead of flow hydrographs (flow verse time).
|-
| '''2d_sa_tr_empty''' || <tt>Read GIS SA Trigger</tt> <tt>==</tt> || Used to define the polygons of sub-catchment areas for applying a source (flow) or rainfall directly onto 2D domains. 2d_sa_tr includes additional attributes required for the SA Trigger option.
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Quadtree Control File (QCF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_qnl_empty''' || <tt>Read GIS Nesting </tt> <tt>==</tt> || Used to define polygons of mesh refinement (different levels).
|-

| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

 
 
{{Tips Navigation
|uplink=[[ TUFLOW_Modelling_Guidance | Back to TUFLOW Modelling Guidance]]
}}

TUFLOW Empty Files

2024-08-15T16:54:27Z

Angelos Livogiannis: /* ESTRY Control file (ECF) */

=Introduction=

The native non-Graphical User Interface (GUI) form of TUFLOW uses Geographic Information System (GIS) files for its spatial inputs. TUFLOW requires precise GIS file formats associated with specific TUFLOW commands. The required fields for each input type are listed in the [https://downloads.tuflow.com/_archive/TUFLOW/Releases/2018-03/TUFLOW%20Manual.2018-03.pdf TUFLOW Manual]. For example, the '''2d_zsh_empty''' file associated with the <tt>Read GIS Z Shape</tt> <tt>==</tt> command requires the following data fields and types in the order shown below: 

<center>[[File:2d zsh fields.png]] </center>
 
Because of this file format requirement, the first task in any modelling project is to write template (empty) GIS files in the specific model projection system (as demonstrated in [[Tutorial_M01#Project_Initialisation|Tutorial Module 1]]). 

This page of the TUFLOW Wiki provides a reference list of the template (empty) GIS files, the associated TUFLOW command and a basic description of their function. 

Note: when using the shapefile format TUFLOW creates a dummy entry when creating empty files. Importing an empty layer into QGIS using the [[QGIS_TUFLOW_Import_Empty | Import Empty]] tool, will remove this dummy entry. Opening a template empty file directly in QGIS (without using the [[QGIS_TUFLOW_Import_Empty | Import Empty]] tool), the dummy entry will remain in the layer and garbled text shown in the attribute fields.

==TUFLOW Control file (TCF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_at_empty''' || <tt>Read GIS Auto Terminate</tt> <tt>==</tt> || Used to define locations where auto terminate tracking is desired
|-
| rowspan=2| '''2d_cyc_empty''' || <tt>Read GIS Cyclone</tt> <tt>==</tt> ||rowspan=2| Used to apply a cyclone or hurricane boundary within TUFLOW, capturing the effects of wind and pressure fields created by severe storms, which can affect flooding and inundation in coastal area.
|-
| <tt>Read GIS Hurricane</tt> <tt>==</tt>
|-
| '''2d_fc_empty''' || <tt>Read GIS FC</tt> <tt>==</tt> || Used for 2D flow constrictions, representing additional losses associated with bridges or box culverts. This command has been superseded with the TGC commands: <tt>Read GIS FC Shape</tt> <tt>Read GIS Layered FC Shape</tt>. 
The template file and command only remain for the purpose of version backward compatibility.
|-
| '''2d_glo_empty''' || <tt>Read GIS GLO</tt> <tt>==</tt> || Used to define gauge level output (2d_glo) locations. The GLO command controls map output based on the height of the water at a specified location within the model domain.
|-
| '''2d_iwl_empty''' || <tt>Read GIS IWL</tt> <tt>==</tt> || Sets the initial water level in the model at the start of the simulation. The initial water level can vary spatially within the model. An equivalent initial Water level command also exists in the TGC.
|-
| '''2d_lp_empty''' || <tt>Read GIS LP</tt> <tt>==</tt> || This file contains details on the location of longitudinal profile outputs.
|-
| '''2d_oz_empty''' || <tt>Read GIS Output Zone</tt> <tt>==</tt> || This file contains one or more polygons defining the 2D regions to be output. This model input is used with the command <tt>Model Output Zones</tt> and the <tt>Define Output Zone</tt>/<tt>End Define</tt> definition block.
|-
| '''2d_po_empty''' || <tt>Read GIS PO</tt> <tt>==</tt> || This file contains lines and points defining plot output (PO) locations for 2D result time series graphs in Excel. PO only extracts results from 2D portions of the model. 1D results are ignored.
|-
| '''0d_rl_empty''' || <tt>Read GIS Reporting Location</tt> <tt>==</tt> || This file contains lines and points defining Reporting Location(s) (RL) for 1D and 2D result time series graphs in Excel.
|-
| rowspan=2| '''1d_wllp_empty''' || <tt>Read GIS XP WLL Points</tt> <tt>==</tt> ||rowspan=2| Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
|-
| <tt>Read GIS ISIS WLL Points</tt> <tt>==</tt>
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==ESTRY Control file (ECF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''1d_bc_empty''' || <tt>Read GIS BC </tt> <tt>==</tt> || Used to define the location and type of 1D boundary condition input
|-
| '''1d_iwl_empty''' || <tt>Read GIS IWL </tt> <tt>==</tt> || Used to set the initial water level within a 1D channel or node at the start of a simulation.
|-
| '''1d_lc_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Used to provide links to tabular data of loss versus height coefficients at a structure. The LC stands for Loss Coefficients.
|-
| '''1d_mh_empty''' || <tt>Read GIS Manhole </tt> <tt>==</tt> || Used to define manhole locations and attributes.
|-
| '''1d_na_empty''' || <tt>Read GIS Node </tt> <tt>==</tt> || Used to set nodal surface areas.
|-
| '''1d_nd_empty''' || <tt>Read GIS Node </tt> <tt>==</tt> || Used to define 1D node locations and attributes.
|-
| '''1d_nwk_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define channel and node locations and attributes. Common channel types include, open channels, culverts, bridges, weirs.
|-
| '''1d_nwkb_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define channel and node locations and attributes. Common channel types include, open channels, culverts, bridges, weirs. The difference between the 1d_nwkb and standard 1d_nwk is that the pblockage attribute field accepts characters allowing the user to input matrix blockage.
|-
| '''1d_nwke_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define grouped structure locations and attributes. For example, weirs representing overtopping of a bridge or culvert structure can be specified using a single GIS feature in the 1d_nwke file. By comparison, multiple line features would be required if the same input was defined in a 1d_nwk file.
|-
| '''1d_pit_empty''' || <tt>Read GIS Pits </tt> <tt>==</tt> || Defines the location and attributes associated with virtual pipes for a GPU model.
|-
| '''1d_tab_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Reads links to tabular inputs associated with cross-section profiles (1d_xs), nodal surface areas (1d_na) and bridge loss coefficients (1d_bg).
|-
| '''1d_WLL_empty''' || <tt>Read GIS WLL </tt> <tt>==</tt> || Used to translate 1D results into 2D map output for viewing in SMS, WaterRide, Blue Kenu and GIS Software.
|-
| '''1d_wllp_empty''' || <tt>Read GIS WLL Points </tt> <tt>==</tt> || Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
|-
| '''1d_xs_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Used to set cross-section profiles and hydraulic properties.
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Geometry Control file (TGC)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| rowspan=2|'''2d_bc_empty''' || <tt>Read GIS Code BC</tt> <tt>==</tt> || Used to set the code status of a cell (active or inactive). 
''This is an alternative method to: "2d_code_empty / <tt>Read GIS Code</tt> <tt>==</tt>". ''
''Note: "2d_bc_empty" '''CANNOT''' be used with <tt>Read GIS Code</tt> <tt>==</tt>''
|-
| <tt>Read GIS Z HX Line</tt> <tt>==</tt> || Used in combination with 2d_bc (HX) layer from the TBC to set the cell elevations along HX lines at the interface between 1D channels nested with a 2D domain.
|-
| '''2d_bg_empty''' || rowspan=2| <tt>Read GIS BG Shape</tt> <tt>==</tt> || rowspan=2| Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| '''2d_bg_empty_pts'''
|-.
|-
| rowspan=2|'''2d_code_empty''' || <tt>Read GIS Code</tt> <tt>==</tt> || Used to set the code status of a cell (1 = active or 0 = inactive).
|-
| <tt>Read GIS Code INVERT</tt> <tt>==</tt> || Used to set the code status of a cell (active or inactive). The inverse value defined by the <tt>Read GIS Code</tt> <tt>==</tt> is applied. This feature is most commonly used during in multiple domain 2D2D models, as discussed in [[TUFLOW_2D2D_BC_Advice|Multiple 2D Modelling Advice]].
|-
| rowspan=2| '''2d_cwf_empty''' || <tt>Read GIS CWF</tt> <tt>==</tt> ||rowspan=2| Used to define location to reduced 2D cell flow width.
|-
| <tt>Read GRID CWF</tt> <tt>==</tt>
|-
| '''2d_fcsh_empty''' || <tt>Read GIS FC Shape</tt> <tt>==</tt> || Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input only account for flow below the bridge obvert (soffit).
|-
| '''2d_flc_empty''' || <tt>Read GIS FLC </tt> <tt>==</tt> || Used to apply an additional energy loss at the 2D cell side. The form or energy loss can be applied as fixed values or on a form loss per unit length basis.
|-
| rowspan=2|'''2d_gw_empty''' || <tt>Read GIS GWL</tt> <tt>==</tt> || rowspan=2| Ground water level inputs.
|-
| <tt>Read GIS GWD</tt> <tt>==</tt>
|-
| '''2d_hx_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the locations of 2D boundaries and 2D/1D dynamic links. For large models it may be wise to separate the boundary conditions from the 1D/2D links, in which case the 2d_bc prefix can be substituted with 2d_hx_ and 2d_sx_. Cell code values may also be defined in this layer.
|-
| '''2d_sx_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the locations of 2D boundaries and 2D/1D dynamic links. For large models it may be wise to separate the boundary conditions from the 1D/2D links, in which case the 2d_bc prefix can be substituted with 2d_hx_ and 2d_sx_. Cell code values may also be defined in this layer.
|-
| '''2d_iwl_empty''' || <tt>Read GIS IWL</tt> <tt>==</tt> || Sets the initial water level in the model at the start of the simulation. The initial water level can vary spatially within the model. An equivalent initial Water level command also exists in the TCF.
|-
| '''2d_Ifcsh_empty''' || rowspan=2| <tt>Read GIS Layered FC Shape</tt> <tt>==</tt> || rowspan=2| Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| '''2d_lfcsh_empty_pts'''
|-.
| '''2d_loc_empty''' || <tt>Read GIS Location</tt> <tt>==</tt> || Used to define the 2D mesh (grid) origin and orientation.
|-
| '''2d_mat_empty''' || <tt>Read GIS MAT</tt> <tt>==</tt>|| Used to define 2D materials (land use) inputs.
|-
| '''2d_obj_empty''' || <tt>Read GIS Objects</tt> <tt>==</tt>|| Used to represent receptors (such as properties or buildings). TUFLOW records the flood level and simulation time at one or more gauge(s) when receptors are first inundated above their trigger inundation levels (e.g. floor levels).
|-
| '''2d_rec_empty''' || <tt>Read GIS Objects</tt> <tt>==</tt>|| Used to represent receptors (such as properties or buildings). TUFLOW records the flood level and simulation time at one or more gauge(s) when receptors are first inundated above their trigger inundation levels (e.g. floor levels).
|-
| '''2d_soil_empty''' || <tt>Read GIS Soil</tt> <tt>==</tt> || Used to define 2D soil type inputs for infiltration parameterisation
|-
| '''2d_vzsh_empty''' || <tt>Read GIS Variable Z Shape</tt> <tt>==</tt> || Used to define the final 3D shape of the Zpts at the completion of a breach, or other change in topographic shape, during a simulation.
|-
| '''2d_wrf_empty''' || <tt>Read GIS Wrf</tt> <tt>==</tt> || Used to adjust the weir factor locally, e.g. faces along a road embankment.
|-
| '''2d_z_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). This command has been superseded with the TGC commands: <tt>Read GIS GIS Z Shape</tt> 
The template file and command only remain for the purpose of version backward compatibility.
|-
| '''2d_za_empty''' || <tt>Read GIS Zpts</tt> <tt>==</tt> || Used to define areas (polygons) of elevations at a constant height. This file is typically created by renaming the 2d_z__empty file
|-
| '''2d_zlg_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zln_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zlr_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zpt_empty''' || <tt>Read GIS Zpts</tt> <tt>==</tt> || Used to define the elevations at the 2D cells mid-sides, corners and centres.
|-
| '''2d_zsh_empty''' || <tt>Read GIS Z Shape</tt> <tt>==</tt> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). Polygons and point features can be used to create TINs which are either independent of, or alternatively merge with the surrounding topography.
|-
| '''2d_zshr_empty''' || <tt>Read GIS Z Shape Route</tt> <tt>==</tt> || Used to provide output on the degree of inundation along evacuation routes. This feature is useful during flood evacuation assessments. The model output includes details on warning time, flood hazard (e.g. depth and velocity) and duration that an evacuation route is isolated.
|-
| '''2d_ztin_empty''' || <tt>Read Grid Zpts</tt> <tt>==</tt> || Used to define 2D and 3D shapes for changing the elevations. Lines can be specified with a width (thickness), and polygons are used as the boundaries for creating TINs (triangulations).
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Boundary Control file (TBC)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_bc_empty''' || <tt>Read GIS BC</tt> <tt>==</tt> || Used to define the location and attributes of 2D model boundary conditions. Including:
* External flow verse time boundaries
* External flow verse water level boundaries
* External water level verse time boundaries
* Internal 1D/2D connections
* Internal 2D/2D connections
|-
| '''2d_rf_empty''' || <tt>Read GIS RF</tt> <tt>==</tt> || Used for ''"direct rainfall"'' modelling, also called ''"rainfall on grid"'' or ''"distributed hydrology"'' modelling.
|-
| rowspan=2| '''2d_sa_empty''' || <tt>Read GIS SA</tt> <tt>==</tt> || rowspan=2| Used to define the location of internal source area flow verse time boundaries.
|-
| <tt>Read GIS Streams</tt> <tt>==</tt>
|-
| '''2d_sa_rf_empty''' || <tt>Read GIS SA RF</tt> <tt>==</tt> ||Used to define the location of internal source area flow verse time boundaries. The model input is specified using rainfall hyetographs (mm versus hours) instead of flow hydrographs (flow verse time).
|-
| '''2d_sa_tr_empty''' || <tt>Read GIS SA Trigger</tt> <tt>==</tt> || Used to define the polygons of sub-catchment areas for applying a source (flow) or rainfall directly onto 2D domains. 2d_sa_tr includes additional attributes required for the SA Trigger option.
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Quadtree Control File (QCF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_qnl_empty''' || <tt>Read GIS Nesting </tt> <tt>==</tt> || Used to define polygons of mesh refinement (different levels).
|-

| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

 
 
{{Tips Navigation
|uplink=[[ TUFLOW_Modelling_Guidance | Back to TUFLOW Modelling Guidance]]
}}

TUFLOW Empty Files

2024-08-15T13:01:15Z

Angelos Livogiannis: /* TUFLOW Geometry Control file (TGC) */

=Introduction=

The native non-Graphical User Interface (GUI) form of TUFLOW uses Geographic Information System (GIS) files for its spatial inputs. TUFLOW requires precise GIS file formats associated with specific TUFLOW commands. The required fields for each input type are listed in the [https://downloads.tuflow.com/_archive/TUFLOW/Releases/2018-03/TUFLOW%20Manual.2018-03.pdf TUFLOW Manual]. For example, the '''2d_zsh_empty''' file associated with the <tt>Read GIS Z Shape</tt> <tt>==</tt> command requires the following data fields and types in the order shown below: 

<center>[[File:2d zsh fields.png]] </center>
 
Because of this file format requirement, the first task in any modelling project is to write template (empty) GIS files in the specific model projection system (as demonstrated in [[Tutorial_M01#Project_Initialisation|Tutorial Module 1]]). 

This page of the TUFLOW Wiki provides a reference list of the template (empty) GIS files, the associated TUFLOW command and a basic description of their function. 

Note: when using the shapefile format TUFLOW creates a dummy entry when creating empty files. Importing an empty layer into QGIS using the [[QGIS_TUFLOW_Import_Empty | Import Empty]] tool, will remove this dummy entry. Opening a template empty file directly in QGIS (without using the [[QGIS_TUFLOW_Import_Empty | Import Empty]] tool), the dummy entry will remain in the layer and garbled text shown in the attribute fields.

==TUFLOW Control file (TCF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_at_empty''' || <tt>Read GIS Auto Terminate</tt> <tt>==</tt> || Used to define locations where auto terminate tracking is desired
|-
| rowspan=2| '''2d_cyc_empty''' || <tt>Read GIS Cyclone</tt> <tt>==</tt> ||rowspan=2| Used to apply a cyclone or hurricane boundary within TUFLOW, capturing the effects of wind and pressure fields created by severe storms, which can affect flooding and inundation in coastal area.
|-
| <tt>Read GIS Hurricane</tt> <tt>==</tt>
|-
| '''2d_fc_empty''' || <tt>Read GIS FC</tt> <tt>==</tt> || Used for 2D flow constrictions, representing additional losses associated with bridges or box culverts. This command has been superseded with the TGC commands: <tt>Read GIS FC Shape</tt> <tt>Read GIS Layered FC Shape</tt>. 
The template file and command only remain for the purpose of version backward compatibility.
|-
| '''2d_glo_empty''' || <tt>Read GIS GLO</tt> <tt>==</tt> || Used to define gauge level output (2d_glo) locations. The GLO command controls map output based on the height of the water at a specified location within the model domain.
|-
| '''2d_iwl_empty''' || <tt>Read GIS IWL</tt> <tt>==</tt> || Sets the initial water level in the model at the start of the simulation. The initial water level can vary spatially within the model. An equivalent initial Water level command also exists in the TGC.
|-
| '''2d_lp_empty''' || <tt>Read GIS LP</tt> <tt>==</tt> || This file contains details on the location of longitudinal profile outputs.
|-
| '''2d_oz_empty''' || <tt>Read GIS Output Zone</tt> <tt>==</tt> || This file contains one or more polygons defining the 2D regions to be output. This model input is used with the command <tt>Model Output Zones</tt> and the <tt>Define Output Zone</tt>/<tt>End Define</tt> definition block.
|-
| '''2d_po_empty''' || <tt>Read GIS PO</tt> <tt>==</tt> || This file contains lines and points defining plot output (PO) locations for 2D result time series graphs in Excel. PO only extracts results from 2D portions of the model. 1D results are ignored.
|-
| '''0d_rl_empty''' || <tt>Read GIS Reporting Location</tt> <tt>==</tt> || This file contains lines and points defining Reporting Location(s) (RL) for 1D and 2D result time series graphs in Excel.
|-
| rowspan=2| '''1d_wllp_empty''' || <tt>Read GIS XP WLL Points</tt> <tt>==</tt> ||rowspan=2| Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
|-
| <tt>Read GIS ISIS WLL Points</tt> <tt>==</tt>
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==ESTRY Control file (ECF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''1d_bc_empty''' || <tt>Read GIS BC </tt> <tt>==</tt> || Used to define the location and type of 1D boundary condition input
|-
| '''1d_iwl_empty''' || <tt>Read GIS IWL </tt> <tt>==</tt> || Used to set the initial water level within a 1D channel or node at the start of a simulation.
|-
| '''1d_mh_empty''' || <tt>Read GIS Manhole </tt> <tt>==</tt> || Used to define manhole locations and attributes.
|-
| '''1d_na_empty''' || <tt>Read GIS Node </tt> <tt>==</tt> || Used to set nodal surface areas.
|-
| '''1d_nd_empty''' || <tt>Read GIS Node </tt> <tt>==</tt> || Used to define 1D node locations and attributes.
|-
| '''1d_nwk_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define channel and node locations and attributes. Common channel types include, open channels, culverts, bridges, weirs.
|-
| '''1d_nwkb_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define channel and node locations and attributes. Common channel types include, open channels, culverts, bridges, weirs. The difference between the 1d_nwkb and standard 1d_nwk is that the pblockage attribute field accepts characters allowing the user to input matrix blockage.
|-
| '''1d_nwke_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define grouped structure locations and attributes. For example, weirs representing overtopping of a bridge or culvert structure can be specified using a single GIS feature in the 1d_nwke file. By comparison, multiple line features would be required if the same input was defined in a 1d_nwk file.
|-
| '''1d_pit_empty''' || <tt>Read GIS Pits </tt> <tt>==</tt> || Defines the location and attributes associated with virtual pipes for a GPU model.
|-
| '''1d_tab_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Reads links to tabular inputs associated with cross-section profiles (1d_xs), nodal surface areas (1d_na) and bridge loss coefficients (1d_bg).
|-
| '''1d_WLL_empty''' || <tt>Read GIS WLL </tt> <tt>==</tt> || Used to translate 1D results into 2D map output for viewing in SMS, WaterRide, Blue Kenu and GIS Software.
|-
| '''1d_xs_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Used to set cross-section profiles and hydraulic properties.
|-
| '''1d_lc_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Used to provide links to tabular data of loss versus height coefficients at a structure. The LC stands for Loss Coefficients.
|-
| '''1d_wllp_empty''' || <tt>Read GIS WLL Points </tt> <tt>==</tt> || Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Geometry Control file (TGC)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| rowspan=2|'''2d_bc_empty''' || <tt>Read GIS Code BC</tt> <tt>==</tt> || Used to set the code status of a cell (active or inactive). 
''This is an alternative method to: "2d_code_empty / <tt>Read GIS Code</tt> <tt>==</tt>". ''
''Note: "2d_bc_empty" '''CANNOT''' be used with <tt>Read GIS Code</tt> <tt>==</tt>''
|-
| <tt>Read GIS Z HX Line</tt> <tt>==</tt> || Used in combination with 2d_bc (HX) layer from the TBC to set the cell elevations along HX lines at the interface between 1D channels nested with a 2D domain.
|-
| '''2d_bg_empty''' || rowspan=2| <tt>Read GIS BG Shape</tt> <tt>==</tt> || rowspan=2| Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| '''2d_bg_empty_pts'''
|-.
|-
| rowspan=2|'''2d_code_empty''' || <tt>Read GIS Code</tt> <tt>==</tt> || Used to set the code status of a cell (1 = active or 0 = inactive).
|-
| <tt>Read GIS Code INVERT</tt> <tt>==</tt> || Used to set the code status of a cell (active or inactive). The inverse value defined by the <tt>Read GIS Code</tt> <tt>==</tt> is applied. This feature is most commonly used during in multiple domain 2D2D models, as discussed in [[TUFLOW_2D2D_BC_Advice|Multiple 2D Modelling Advice]].
|-
| rowspan=2| '''2d_cwf_empty''' || <tt>Read GIS CWF</tt> <tt>==</tt> ||rowspan=2| Used to define location to reduced 2D cell flow width.
|-
| <tt>Read GRID CWF</tt> <tt>==</tt>
|-
| '''2d_fcsh_empty''' || <tt>Read GIS FC Shape</tt> <tt>==</tt> || Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input only account for flow below the bridge obvert (soffit).
|-
| '''2d_flc_empty''' || <tt>Read GIS FLC </tt> <tt>==</tt> || Used to apply an additional energy loss at the 2D cell side. The form or energy loss can be applied as fixed values or on a form loss per unit length basis.
|-
| rowspan=2|'''2d_gw_empty''' || <tt>Read GIS GWL</tt> <tt>==</tt> || rowspan=2| Ground water level inputs.
|-
| <tt>Read GIS GWD</tt> <tt>==</tt>
|-
| '''2d_hx_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the locations of 2D boundaries and 2D/1D dynamic links. For large models it may be wise to separate the boundary conditions from the 1D/2D links, in which case the 2d_bc prefix can be substituted with 2d_hx_ and 2d_sx_. Cell code values may also be defined in this layer.
|-
| '''2d_sx_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the locations of 2D boundaries and 2D/1D dynamic links. For large models it may be wise to separate the boundary conditions from the 1D/2D links, in which case the 2d_bc prefix can be substituted with 2d_hx_ and 2d_sx_. Cell code values may also be defined in this layer.
|-
| '''2d_iwl_empty''' || <tt>Read GIS IWL</tt> <tt>==</tt> || Sets the initial water level in the model at the start of the simulation. The initial water level can vary spatially within the model. An equivalent initial Water level command also exists in the TCF.
|-
| '''2d_Ifcsh_empty''' || rowspan=2| <tt>Read GIS Layered FC Shape</tt> <tt>==</tt> || rowspan=2| Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| '''2d_lfcsh_empty_pts'''
|-.
| '''2d_loc_empty''' || <tt>Read GIS Location</tt> <tt>==</tt> || Used to define the 2D mesh (grid) origin and orientation.
|-
| '''2d_mat_empty''' || <tt>Read GIS MAT</tt> <tt>==</tt>|| Used to define 2D materials (land use) inputs.
|-
| '''2d_obj_empty''' || <tt>Read GIS Objects</tt> <tt>==</tt>|| Used to represent receptors (such as properties or buildings). TUFLOW records the flood level and simulation time at one or more gauge(s) when receptors are first inundated above their trigger inundation levels (e.g. floor levels).
|-
| '''2d_rec_empty''' || <tt>Read GIS Objects</tt> <tt>==</tt>|| Used to represent receptors (such as properties or buildings). TUFLOW records the flood level and simulation time at one or more gauge(s) when receptors are first inundated above their trigger inundation levels (e.g. floor levels).
|-
| '''2d_soil_empty''' || <tt>Read GIS Soil</tt> <tt>==</tt> || Used to define 2D soil type inputs for infiltration parameterisation
|-
| '''2d_vzsh_empty''' || <tt>Read GIS Variable Z Shape</tt> <tt>==</tt> || Used to define the final 3D shape of the Zpts at the completion of a breach, or other change in topographic shape, during a simulation.
|-
| '''2d_wrf_empty''' || <tt>Read GIS Wrf</tt> <tt>==</tt> || Used to adjust the weir factor locally, e.g. faces along a road embankment.
|-
| '''2d_z_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). This command has been superseded with the TGC commands: <tt>Read GIS GIS Z Shape</tt> 
The template file and command only remain for the purpose of version backward compatibility.
|-
| '''2d_za_empty''' || <tt>Read GIS Zpts</tt> <tt>==</tt> || Used to define areas (polygons) of elevations at a constant height. This file is typically created by renaming the 2d_z__empty file
|-
| '''2d_zlg_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zln_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zlr_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to define the crest of ridges (e.g. levees, embankments) or thalweg of gullies (e.g. drains, creeks). Ridges and gullies cannot occur in the same layer so 2d_zlr_ is often used for ridges and 2d_zlg_ for gullies. These files are typically created by renaming the 2d_z__empty file.
|-
| '''2d_zpt_empty''' || <tt>Read GIS Zpts</tt> <tt>==</tt> || Used to define the elevations at the 2D cells mid-sides, corners and centres.
|-
| '''2d_zsh_empty''' || <tt>Read GIS Z Shape</tt> <tt>==</tt> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). Polygons and point features can be used to create TINs which are either independent of, or alternatively merge with the surrounding topography.
|-
| '''2d_zshr_empty''' || <tt>Read GIS Z Shape Route</tt> <tt>==</tt> || Used to provide output on the degree of inundation along evacuation routes. This feature is useful during flood evacuation assessments. The model output includes details on warning time, flood hazard (e.g. depth and velocity) and duration that an evacuation route is isolated.
|-
| '''2d_ztin_empty''' || <tt>Read Grid Zpts</tt> <tt>==</tt> || Used to define 2D and 3D shapes for changing the elevations. Lines can be specified with a width (thickness), and polygons are used as the boundaries for creating TINs (triangulations).
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Boundary Control file (TBC)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_bc_empty''' || <tt>Read GIS BC</tt> <tt>==</tt> || Used to define the location and attributes of 2D model boundary conditions. Including:
* External flow verse time boundaries
* External flow verse water level boundaries
* External water level verse time boundaries
* Internal 1D/2D connections
* Internal 2D/2D connections
|-
| '''2d_rf_empty''' || <tt>Read GIS RF</tt> <tt>==</tt> || Used for ''"direct rainfall"'' modelling, also called ''"rainfall on grid"'' or ''"distributed hydrology"'' modelling.
|-
| rowspan=2| '''2d_sa_empty''' || <tt>Read GIS SA</tt> <tt>==</tt> || rowspan=2| Used to define the location of internal source area flow verse time boundaries.
|-
| <tt>Read GIS Streams</tt> <tt>==</tt>
|-
| '''2d_sa_rf_empty''' || <tt>Read GIS SA RF</tt> <tt>==</tt> ||Used to define the location of internal source area flow verse time boundaries. The model input is specified using rainfall hyetographs (mm versus hours) instead of flow hydrographs (flow verse time).
|-
| '''2d_sa_tr_empty''' || <tt>Read GIS SA Trigger</tt> <tt>==</tt> || Used to define the polygons of sub-catchment areas for applying a source (flow) or rainfall directly onto 2D domains. 2d_sa_tr includes additional attributes required for the SA Trigger option.
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Quadtree Control File (QCF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_qnl_empty''' || <tt>Read GIS Nesting </tt> <tt>==</tt> || Used to define polygons of mesh refinement (different levels).
|-

| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

 
 
{{Tips Navigation
|uplink=[[ TUFLOW_Modelling_Guidance | Back to TUFLOW Modelling Guidance]]
}}

TUFLOW Empty Files

2024-08-15T11:27:24Z

Angelos Livogiannis:

=Introduction=

The native non-Graphical User Interface (GUI) form of TUFLOW uses Geographic Information System (GIS) files for its spatial inputs. TUFLOW requires precise GIS file formats associated with specific TUFLOW commands. The required fields for each input type are listed in the [https://downloads.tuflow.com/_archive/TUFLOW/Releases/2018-03/TUFLOW%20Manual.2018-03.pdf TUFLOW Manual]. For example, the '''2d_zsh_empty''' file associated with the <tt>Read GIS Z Shape</tt> <tt>==</tt> command requires the following data fields and types in the order shown below: 

<center>[[File:2d zsh fields.png]] </center>
 
Because of this file format requirement, the first task in any modelling project is to write template (empty) GIS files in the specific model projection system (as demonstrated in [[Tutorial_M01#Project_Initialisation|Tutorial Module 1]]). 

This page of the TUFLOW Wiki provides a reference list of the template (empty) GIS files, the associated TUFLOW command and a basic description of their function. 

Note: when using the shapefile format TUFLOW creates a dummy entry when creating empty files. Importing an empty layer into QGIS using the [[QGIS_TUFLOW_Import_Empty | Import Empty]] tool, will remove this dummy entry. Opening a template empty file directly in QGIS (without using the [[QGIS_TUFLOW_Import_Empty | Import Empty]] tool), the dummy entry will remain in the layer and garbled text shown in the attribute fields.

==TUFLOW Control file (TCF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_at_empty''' || <tt>Read GIS Auto Terminate</tt> <tt>==</tt> || Used to define locations where auto terminate tracking is desired
|-
| rowspan=2| '''2d_cyc_empty''' || <tt>Read GIS Cyclone</tt> <tt>==</tt> ||rowspan=2| Used to apply a cyclone or hurricane boundary within TUFLOW, capturing the effects of wind and pressure fields created by severe storms, which can affect flooding and inundation in coastal area.
|-
| <tt>Read GIS Hurricane</tt> <tt>==</tt>
|-
| '''2d_fc_empty''' || <tt>Read GIS FC</tt> <tt>==</tt> || Used for 2D flow constrictions, representing additional losses associated with bridges or box culverts. This command has been superseded with the TGC commands: <tt>Read GIS FC Shape</tt> <tt>Read GIS Layered FC Shape</tt>. 
The template file and command only remain for the purpose of version backward compatibility.
|-
| '''2d_glo_empty''' || <tt>Read GIS GLO</tt> <tt>==</tt> || Used to define gauge level output (2d_glo) locations. The GLO command controls map output based on the height of the water at a specified location within the model domain.
|-
| '''2d_iwl_empty''' || <tt>Read GIS IWL</tt> <tt>==</tt> || Sets the initial water level in the model at the start of the simulation. The initial water level can vary spatially within the model. An equivalent initial Water level command also exists in the TGC.
|-
| '''2d_lp_empty''' || <tt>Read GIS LP</tt> <tt>==</tt> || This file contains details on the location of longitudinal profile outputs.
|-
| '''2d_oz_empty''' || <tt>Read GIS Output Zone</tt> <tt>==</tt> || This file contains one or more polygons defining the 2D regions to be output. This model input is used with the command <tt>Model Output Zones</tt> and the <tt>Define Output Zone</tt>/<tt>End Define</tt> definition block.
|-
| '''2d_po_empty''' || <tt>Read GIS PO</tt> <tt>==</tt> || This file contains lines and points defining plot output (PO) locations for 2D result time series graphs in Excel. PO only extracts results from 2D portions of the model. 1D results are ignored.
|-
| '''0d_rl_empty''' || <tt>Read GIS Reporting Location</tt> <tt>==</tt> || This file contains lines and points defining Reporting Location(s) (RL) for 1D and 2D result time series graphs in Excel.
|-
| rowspan=2| '''1d_wllp_empty''' || <tt>Read GIS XP WLL Points</tt> <tt>==</tt> ||rowspan=2| Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
|-
| <tt>Read GIS ISIS WLL Points</tt> <tt>==</tt>
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==ESTRY Control file (ECF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''1d_bc_empty''' || <tt>Read GIS BC </tt> <tt>==</tt> || Used to define the location and type of 1D boundary condition input
|-
| '''1d_iwl_empty''' || <tt>Read GIS IWL </tt> <tt>==</tt> || Used to set the initial water level within a 1D channel or node at the start of a simulation.
|-
| '''1d_mh_empty''' || <tt>Read GIS Manhole </tt> <tt>==</tt> || Used to define manhole locations and attributes.
|-
| '''1d_na_empty''' || <tt>Read GIS Node </tt> <tt>==</tt> || Used to set nodal surface areas.
|-
| '''1d_nd_empty''' || <tt>Read GIS Node </tt> <tt>==</tt> || Used to define 1D node locations and attributes.
|-
| '''1d_nwk_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define channel and node locations and attributes. Common channel types include, open channels, culverts, bridges, weirs.
|-
| '''1d_nwkb_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define channel and node locations and attributes. Common channel types include, open channels, culverts, bridges, weirs. The difference between the 1d_nwkb and standard 1d_nwk is that the pblockage attribute field accepts characters allowing the user to input matrix blockage.
|-
| '''1d_nwke_empty''' || <tt>Read GIS Network </tt> <tt>==</tt> || Used to define grouped structure locations and attributes. For example, weirs representing overtopping of a bridge or culvert structure can be specified using a single GIS feature in the 1d_nwke file. By comparison, multiple line features would be required if the same input was defined in a 1d_nwk file.
|-
| '''1d_pit_empty''' || <tt>Read GIS Pits </tt> <tt>==</tt> || Defines the location and attributes associated with virtual pipes for a GPU model.
|-
| '''1d_tab_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Reads links to tabular inputs associated with cross-section profiles (1d_xs), nodal surface areas (1d_na) and bridge loss coefficients (1d_bg).
|-
| '''1d_WLL_empty''' || <tt>Read GIS WLL </tt> <tt>==</tt> || Used to translate 1D results into 2D map output for viewing in SMS, WaterRide, Blue Kenu and GIS Software.
|-
| '''1d_xs_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Used to set cross-section profiles and hydraulic properties.
|-
| '''1d_lc_empty''' || <tt>Read GIS Table Links </tt> <tt>==</tt> || Used to provide links to tabular data of loss versus height coefficients at a structure. The LC stands for Loss Coefficients.
|-
| '''1d_wllp_empty''' || <tt>Read GIS WLL Points </tt> <tt>==</tt> || Used to define the elevations (usually from a DTM) and material values across the WLLs. This offers high quality viewing and mapping of the 1D domains.
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Geometry Control file (TGC)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| rowspan=2|'''2d_bc_empty''' || <tt>Read GIS Code BC</tt> <tt>==</tt> || Used to set the code status of a cell (active or inactive). 
''This is an alternative method to: "2d_code_empty / <tt>Read GIS Code</tt> <tt>==</tt>". ''
''Note: "2d_bc_empty" '''CANNOT''' be used with <tt>Read GIS Code</tt> <tt>==</tt>''
|-
| <tt>Read GIS Z HX Line</tt> <tt>==</tt> || Used in combination with 2d_bc (HX) layer from the TBC to set the cell elevations along HX lines at the interface between 1D channels nested with a 2D domain.
|-
| '''2d_bg_empty''' || <tt>Read GIS BG Shape</tt> <tt>==</tt> || Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| '''2d_bg_empty_pts''' || <tt>Read GIS BG Shape</tt> <tt>==</tt> || Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| rowspan=2|'''2d_code_empty''' || <tt>Read GIS Code</tt> <tt>==</tt> || Used to set the code status of a cell (1 = active or 0 = inactive).
|-
| <tt>Read GIS Code INVERT</tt> <tt>==</tt> || Used to set the code status of a cell (active or inactive). The inverse value defined by the <tt>Read GIS Code</tt> <tt>==</tt> is applied. This feature is most commonly used during in multiple domain 2D2D models, as discussed in [[TUFLOW_2D2D_BC_Advice|Multiple 2D Modelling Advice]].
|-
| rowspan=2| '''2d_cwf_empty''' || <tt>Read GIS CWF</tt> <tt>==</tt> ||rowspan=2| Used to define location to reduced 2D cell flow width.
|-
| <tt>Read GRID CWF</tt> <tt>==</tt>
|-
| '''2d_fcsh_empty''' || <tt>Read GIS FC Shape</tt> <tt>==</tt> || Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input only account for flow below the bridge obvert (soffit).
|-
| '''2d_flc_empty''' || <tt>Read GIS FLC </tt> <tt>==</tt> || Used to apply an additional energy loss at the 2D cell side. The form or energy loss can be applied as fixed values or on a form loss per unit length basis.
|-
| rowspan=2|'''2d_gw_empty''' || <tt>Read GIS GWL</tt> <tt>==</tt> || rowspan=2| Ground water level inputs.
|-
| <tt>Read GIS GWD</tt> <tt>==</tt>
|-
| '''2d_iwl_empty''' || <tt>Read GIS IWL</tt> <tt>==</tt> || Sets the initial water level in the model at the start of the simulation. The initial water level can vary spatially within the model. An equivalent initial Water level command also exists in the TCF.
|-
| '''2d_Ifcsh_empty''' || rowspan=2| <tt>Read GIS Layered FC Shape</tt> <tt>==</tt> || rowspan=2| Used for 2D flow constrictions to represent additional losses associated with bridges or box culverts. This input includes accounts for flow above and below the bridge obvert (soffit).
|-
| '''2d_lfcsh_empty_pts'''
|-.
| '''2d_loc_empty''' || <tt>Read GIS Location</tt> <tt>==</tt> || Used to define the 2D mesh (grid) origin and orientation.
|-
| '''2d_mat_empty''' || <tt>Read GIS MAT</tt> <tt>==</tt>|| Used to define 2D materials (land use) inputs.
|-
| '''2d_obj_empty''' || <tt>Read GIS Objects</tt> <tt>==</tt>|| Used to represent receptors (such as properties or buildings). TUFLOW records the flood level and simulation time at one or more gauge(s) when receptors are first inundated above their trigger inundation levels (e.g. floor levels).
|-
| '''2d_rec_empty''' || <tt>Read GIS Objects</tt> <tt>==</tt>|| Used to represent receptors (such as properties or buildings). TUFLOW records the flood level and simulation time at one or more gauge(s) when receptors are first inundated above their trigger inundation levels (e.g. floor levels).
|-
| '''2d_soil_empty''' || <tt>Read GIS Soil</tt> <tt>==</tt> || Used to define 2D soil type inputs for infiltration parameterisation
|-
| '''2d_vzsh_empty''' || <tt>Read GIS Variable Z Shape</tt> <tt>==</tt> || Used to define the final 3D shape of the Zpts at the completion of a breach, or other change in topographic shape, during a simulation.
|-
| '''2d_wrf_empty''' || <tt>Read GIS Wrf</tt> <tt>==</tt> || Used to adjust the weir factor locally, e.g. faces along a road embankment.
|-
| '''2d_z_empty''' || <tt>Read GIS Z Line</tt> <tt>==</tt> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). This command has been superseded with the TGC commands: <tt>Read GIS GIS Z Shape</tt> 
The template file and command only remain for the purpose of version backward compatibility.
|-
| '''2d_zsh_empty''' || <tt>Read GIS Z Shape</tt> <tt>==</tt> || Used to update topography within a model. Polylines are treated as breaklines in the model’s topography (with the breakline height or elevation varying along its length). Polygons and point features can be used to create TINs which are either independent of, or alternatively merge with the surrounding topography.
|-
| '''2d_zshr_empty''' || <tt>Read GIS Z Shape Route</tt> <tt>==</tt> || Used to provide output on the degree of inundation along evacuation routes. This feature is useful during flood evacuation assessments. The model output includes details on warning time, flood hazard (e.g. depth and velocity) and duration that an evacuation route is isolated.
|-
| '''2d_ztin_empty''' || <tt>Read Grid Zpts</tt> <tt>==</tt> || Used to define 2D and 3D shapes for changing the elevations. Lines can be specified with a width (thickness), and polygons are used as the boundaries for creating TINs (triangulations).
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Boundary Control file (TBC)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_bc_empty''' || <tt>Read GIS BC</tt> <tt>==</tt> || Used to define the location and attributes of 2D model boundary conditions. Including:
* External flow verse time boundaries
* External flow verse water level boundaries
* External water level verse time boundaries
* Internal 1D/2D connections
* Internal 2D/2D connections
|-
| '''2d_rf_empty''' || <tt>Read GIS RF</tt> <tt>==</tt> || Used for ''"direct rainfall"'' modelling, also called ''"rainfall on grid"'' or ''"distributed hydrology"'' modelling.
|-
| rowspan=2| '''2d_sa_empty''' || <tt>Read GIS SA</tt> <tt>==</tt> || rowspan=2| Used to define the location of internal source area flow verse time boundaries.
|-
| <tt>Read GIS Streams</tt> <tt>==</tt>
|-
| '''2d_sa_rf_empty''' || <tt>Read GIS SA RF</tt> <tt>==</tt> ||Used to define the location of internal source area flow verse time boundaries. The model input is specified using rainfall hyetographs (mm versus hours) instead of flow hydrographs (flow verse time).
|-
| '''2d_sa_tr_empty''' || <tt>Read GIS SA Trigger</tt> <tt>==</tt> || Used to define the polygons of sub-catchment areas for applying a source (flow) or rainfall directly onto 2D domains. 2d_sa_tr includes additional attributes required for the SA Trigger option.
|-
| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

==TUFLOW Quadtree Control File (QCF)==
{| class="wikitable" width="75%"
! style="background-color:#005581; font-weight:bold; color:white;" width=20%| Template (empty) GIS File
! style="background-color:#005581; font-weight:bold; color:white;" width=25%| Compatible TUFLOW Commands
! style="background-color:#005581; font-weight:bold; color:white"| File / Command Function
|-
| '''2d_qnl_empty''' || <tt>Read GIS Nesting </tt> <tt>==</tt> || Used to define polygons of mesh refinement (different levels).
|-

| colspan=3| ''Note: Template shapefiles will also include a suffix describing the object type: 
''_L = Lines features'' 
''_P = Point features'' 
''_R = Region (polygon) features'' 
|-
|}

 
 
{{Tips Navigation
|uplink=[[ TUFLOW_Modelling_Guidance | Back to TUFLOW Modelling Guidance]]
}}

Hardware Benchmarking - Results

2024-08-15T09:28:10Z

Angelos Livogiannis:

=CPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m Classic and HPC CPU runtimes, with the fastest computers at the top of the table.
 
'''Runtimes for CPU benchmarks'''
{| align="center" class="wikitable"

! style="background-color:#005581; font-weight:bold; color:white;"| Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Processor Frequency (GHz)**
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM size (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM frequency (MHz)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Classic 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | HPC CPU 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Runtime Combined (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||128||5200||32.7||108.6||141.3||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||64||5600||36.7||114.2||150.9||TM1
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||2.0||128||4000||41.2||124.1||165.3||AW1
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs)||3.2||128||4800||38.5||127.0||165.5||SB1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz||4.5||64||4800||33.4||136.0||169.4||PSM
|-
|12th Gen Intel(R) Core(TM) i9-12900K||3.2||128||3200||40.7||129.9||170.6||DD2
|-
|12th Gen Intel(R) Core(TM) i7-12700 (20 CPUs) @ ~2.1GHz||2.1||64||4800||41||137.2||178.2||RB1
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs) @ ~4.2GHz||4.2||32||4800||35.5||162.8||198.3||LC1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs)||2.5||16||3200||48.4||170.5||218.9||TS1
|-
|Intel(R) Xeon(R) w5-2455X (24 CPUs) @ ~3.2GHz||3.2||64||4800||53.3||169.1||222.4||CHR
|-
|Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz||3.7||128||3200||56.9||173.8||230.7||CH1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz)||(5.1)||16||4000||58.2||179.9||238.1||RRB
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||3000||55.7||186.2||241.9||RH1
|-
|AMD Ryzen 9 3900X 12-Core Processor||3.8||64||3200||45.9||203.1||249.0||CH3
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz||3.1||32||2666||61.7||190.0||251.7||CB1
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz||3.6||32||2133||61.4||190.4||251.8||RH2
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||3.6||64||2133||62.7||191.1||253.8||PA1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||32||2933||62.1||192.8||254.9||DS2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||71.2||184.3||255.5||ABA
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||62.1||193.7||255.8||MA2
|-
|AMD Ryzen Threadripper 3970X 32-Core Processor||3.7||256||2400||49.5||212.1||261.6||CH2
|-
|AMD Ryzen 9 3950X 16-Core Processor||3.5||128||2800||55.9||210.0||265.9||TRO
|-
|AMD EPYC 74F3 24-Core Processor (6 CPUs) @ 3.2GHz||3.2||56||N/A||49.1||218.9||268||RBR
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||2133||67.0||202.5||269.5||RL1
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz||3.5||128||2133||72.7||202.1||274.8||MBL
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||67.5||208.6||276.1||SKI
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||68.5||208.8||277.3||PM2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||66.8||211.6||278.1||MA1
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz||3.2||16||2667||68.2||211.8||280.0||CR2
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||68.0||216.0||284.0||RL3
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||67.7||219.1||286.8||RL2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||70.5||218.8||289.3||PM1
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||2.9||16||2667||77.5||212.6||290.1||KTC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||3.7||32||2933||75.2||219.8||295||BL-DT01001
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor||3.5||128||2666||67.9||230.8||298.7||JGR
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||3.5||128||2666||66.3||234.7||301||JG3
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||32||2400||80.5||221.9||302.4||JM1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz||3.6||16||2400||72.8||230.6||303.4||RSH
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||85.4||218.8||304.2||JPI
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||83.7||225.2||308.9||HNM
|-
|Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz||4.0||32||2400||91.2||223.3||314.5||BRD
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz||3.7||64||2400||84.5||236.6||321.2||DS1
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz||3.2||128||2133||83.4||243.1||326.5||BLK
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||3.7||64||2933||95.4||231.3||326.7||JB2
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz||3.4||128||2400||85.3||247.7||332.9||615
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2400||106.3||226.7||333.0||MRT
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||16||2133||80.7||253.4||334.1||VHD
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz||2.1||64||2666||83.9||251.2||335.1||AR2
|-
|AMD EPYC 7V12 64-Core Processor (16 CPUs) ||2.4||57||NA||63.5||277.6||341.1||CS2
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor||3.4||16||2666||81.9||277.3||359.2||CEV
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz||3.0||32||2400||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||64||2133||82.3||289.8||372.1||JIW
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz||3.4||32||1666||108.9||270.0||378.9||AR1
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||3.8||64||3200||87.8||294.2||382||HDR-A2000
|-
|AMD Ryzen 9 5950X 16-Core Processor||3.4||32||3400||39.7||343.0||382.7||JG2
|-
|Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz||2.8||32||1600||119.7||280.8||400.5||SBC
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz||3.3||64||2133||118.2||287.8||406.0||ZDO
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz||2.7||16||2133||90.4||321.7||412.1||EAS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||16||2133||84.8||336.9||421.7||JM2
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2133||100.3||323||423.3||MON
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz||3.4||32||1600||126.4||299.7||426.1||MAV
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz ||3.0||4||986||84.0||351.4||435.4||TJS
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||3.5||16||1333||125.9||320.5||446.4||EFC
|-
|Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz||1.9||16||1800||100.1||347.0||447.1||SM1
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||2.9||16||2900||63.3||385.0||448.3||NCV
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||4.1||16||4104||62.7||386.6||449.3||GZH
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||2.4||128||2394||130.5||331.5||462||VDI
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||2.6||24||1600||100.5||378.6||479.1||CDH
|-
|Intel(R) Xeon(R) CPU E5-1650 0 @ 3.20GHz||3.2||32||1600||143.2||343.1||486.3||MPR
|-
|Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz||3.2||8||1600||142.0||349.4||491.4||CR1
|-
|Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz||3.3||16||N/A||196.8||331.5||528.3||Private Cloud
|-
|Intel(R) Core(TM) i7-4712HQ CPU @ 2.30GHz (Laptop)||2.3||8||1600||145.2||414.4||559.6||MNG
|-
|Intel(R) Xeon(R) CPU X5680 @ 3.33GHz||3.33||72||1333||165.7||400.6||566.3||WTM
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||2.4||8||1600||137.8||795.0||932.8||HMM
|-
|}
 

=GPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m and 10m runtimes with the fastest computers at the top of the table.
 
The HPC GPU benchmark only uses a single GPU card. TUFLOW HPC GPU can be run across multiple NVIDIA GPU devices. However, the benefits of these are typically more noticeable for larger models with more than 1 million cells.
 
'''Runtimes for GPU benchmarks'''
{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 10m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz ||NVIDIA GeForce RTX 4090||24||16384||2.4||11.6||14.0||JW1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4090||24||16384||2.5||12.1||14.6||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz ||NVIDIA GeForce RTX 4090||24||16384||2.7||12.7||15.4||TA1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||2.9||12.7||15.6||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||3.1||13.3||16.4||CR4
|-
|Intel(R) Core(TM) i9-14900K (32 CPUs) @ ~3.2GHz||NVIDIA GeForce RTX 4080 Super||16||10240||2.8||14.5||17.3||DF2
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||TM1
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||JM3
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||NVIDIA GeForce RTX 4080||16||9728||3.2||15.0||18.2||AW1
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs)@ ~4.2GHz||NVIDIA GeForce RTX 4080 SUPER||16||10240||3.2||15.7||18.9||LC1
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||NVIDIA RTX 6000 Ada Generation||48||18176||4.9||14.2||19.1||JG3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||3.4||18.5||21.9||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||3.8||19.2||23.0||RS1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||3.7||19.4||23.1||DD2
|-
|12th Gen Intel(R) Core(TM) i7-12700F
|NVIDIA GeForce RTX 3080 Ti
|12
|10240
|3.75
|19.57
|23.32
|AUBNE1PC6602
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||4.0||19.6||23.6||GP1
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA A40||48||10752||3.5||20.3||23.8||Lenovo SR650 V2
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.1||20.1||24.2||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.4||20.4||24.8||CH3
|-
|12th Gen Intel(R) Core(TM) i7-12700 (20 CPUs) @ ~2.1GHz ||NVIDIA GeForce RTX 3080||10||8704||4.3||23.7||28||RB1
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||4.6||23.5||28.1||KW2
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs) ||NVIDIA RTX A5000||24||8192||4.4||24.1||28.5||SB1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 3080||10||8704||4.7||24.0||28.7||CPM
|-
|Intel(R) Xeon(R) W-2223 CPU @ 3.60GHz ||NVIDIA GeForce RTX 3090||24||10496||5.3||24.3||29.6||SSM2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||4.7||25.7||30.4||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||5.7||25.2||30.9||JGR
|-
|AMD Ryzen Threadripper 2920X 12-Core Processor (24 CPUs) @ 3.5GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.1||25.9||31||CR5
|-
|AMD Ryzen 9 3950X 16-Core Processor ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.3||26.4||31.7||TRO
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||27.4||32.8||PY2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||27.7||33.4||VLD
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||NVIDIA GeForce RTX 3070||8||5888||5.0||28.8||33.8||NCV
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.5||28.4||33.9||RL1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||5.5||28.7||34.2||RRB
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.8||28.8||34.6||MA1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||29.2||34.9||MA2
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||5.5||29.7||35.2||JG2
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.6||29.9||35.5||MBL
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||6.4||29.5||35.9||JPI
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P100||16||3584||6.1||30.8||36.9||Google Cloud: Tesla P100
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||5.7||31.9||37.6||RH2
|-
|Intel(R) Xeon(R) Gold 6230R CPU @ 2.10GHz ||NVIDIA GRID RTX8000P-48Q||48||4608||6.8||31.0||37.8||VJ1
|-
|Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 CPUs) ||NVIDIA RTX A4000||16||6144||5.8||32.0||37.8||JS2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080||8||2944||6.0||31.9||37.9||ANK
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||6.0||32.0||38.0||EFC
|-
|AMD EPYC 74F3 24-Core Processor (36 CPUs) @ 3.2GHz ||NVIDIA A10-24Q||24||8192||7.2||31.4||38.6||CS1
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||33.3||38.7||PA1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce RTX 3060 Ti (LHR) ||8||4864||5.7||33.3||39.0||DF1
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||NVIDIA GeForce RTX 2060 SUPER (core 1647MHz, mem 1750MHz)||8||2176||5.6||33.4||39.1||GZH
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||5.6||34.3||40.7||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||6.9||34.6||41.6||FLC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||35.1||41.6||JB2
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.4||35.8||42.2||JS1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080||8||2944||6.5||36.0||42.5||ABA
|-
|Intel(R) Xeon(R) w5-2455X (24 CPUs) @ ~3.2GHz ||NVIDIA RTX A4000||16||6144||7.2||35.3||42.5||CHR
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.1||37.1||43.2||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||37.4||43.8||PM1
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA GeForce GTX 2070||8||2304||7.4||38.8||46.2||MMR
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz ||NVIDIA Quadro RTX 4000||8||2304||6.6||39.8||46.4||CB1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.8||39.1||46.9||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||8.0||39.3||47.3||RCD
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.6||41.1||48.7||HNM
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||NVIDIA GRID RTX6000P-4Q||24||4608||10.5||39.3||49.8||VDI
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (Laptop) ||NVIDIA GeForce RTX 2070||8||2304||7.7||42.8||50.5||ERX
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA Tesla T4||16||2560||6.8||45.2||52.0||RJ1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz
|NVIDIA GeForce RTX 3060
|8
|3584
|7.68
|45.92
|53.6
|AUBNEW1DQ54G3
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||8.0||47.4||55.3||BLK
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla T4||16||2560||7.3||48.3||55.6||FM-NODE: Tesla T4
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz ||NVIDIA GeForce GTX 1080||8||2560||8.5||48.9||57.3||JM1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||8.2||51.9||60.0||SKI
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz ||NVIDIA Quadro P5000||16||2560||9.6||51.8||61.4||AR2
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||NVIDIA RTX A2000||6||3328||9.1||54.4||63.5||HDR-A2000
|-
|Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz ||NVIDIA GeForce GTX 1070||8||1920||8.9||54.9||63.8||PY1
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz ||NVIDIA GeForce GTX 1070||8||1920||10.3||59.3||69.5||DS1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA Quadro P4000||8||1792||10.0||62.3||72.3||DS2
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce GTX 1650 SUPER||4||1280||10.3||64.6||74.9||TS1
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P4||8||2560||10.4||69.0||79.4||Google Cloud: Tesla P4
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz ||NVIDIA GeForce GTX 980||4||2048||11.8||70.6||82.3||ZDO
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz ||NVIDIA GeForce GTX TITAN Black||6||2880||13.1||76.1||89.2||AR1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz ||NVIDIA GeForce GTX 1060||6||1280||13.0||77.1||90.1||RSH
|-
|Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz (64 CPUs), ~2.3GHz||NVIDIA Tesla M60||16||4096||12||82.7||94.7||SM2
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla K80||12||2496||11.3||83.5||94.8||Google Cloud: Tesla K80
|-
|Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz ||NVIDIA Tesla K40c||12||2880||12.3||83.1||95.3||NWE
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA Quadro T2000||4||1024||13.3||85.2||95.5||SSM
|-
|Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (Laptop) ||NVIDIA GeForce GTX 980||4||2048||17.5||84.2||101.7||MRT
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||NVIDIA Quadro P2000||5||1024||14.2||96||110.2||BL-DT01001
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz ||NVIDIA Quadro P2000||5||1024||15.8||100.1||115.9||CR2
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz ||NVIDIA GeForce GTX 690||2||3072||18.4||114.4||132.8||MAV
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor ||NVIDIA GeForce GTX 960||4||1024||18.6||123.3||141.6||CEV
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA GeForce GTX 960||4||1024||19.9||127.2||147.1||VHD
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz||NVIDIA GeForce GTX 1050 Ti||4||768||21.1||133.8||154.9||MJS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||NVIDIA GeForce GTX 1050||2||640||20.6||139.1||159.7||JM2
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||NVIDIA Quadro P2000||5||1024||22.1||142.5||164.6||KTC
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||NVIDIA Quadro P2000||5||1024||23.0||149.3||172.3||RL2
|-
|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz||NVIDIA Quadro M2200||4||1024||23.2||198.7||222.0||GYB
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz||NVIDIA T500||4||986||29.3||197.5||226.8||TJS
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz ||NVIDIA Quadro P1000||4||640||30.3||203.7||234.0||RL3
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA Quadro K2200||4||640||32.5||211.3||243.8||JIW
|-
|AMD EPYC 74F3 24-Core Processor (6 CPUs) @ 3.2GHz||NVIDIA A10-4Q||24||8192||44.5||212.6||257.1||RBR
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz ||NVIDIA Quadro M1200||4||640||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz ||NVIDIA GeForce GTX 940MX||2||384||65.6||479.0||544.6||EAS
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||NVIDIA GeForce 840M||2||384||70.6||526.3||595.9||CDH
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||NVIDIA GeForce GT 740M||2||384||102.3||694.0||796.3||HMM
|-
|}
 

=High End GPU Results=
A number of additional benchmarking tests have been completed on a 5m and 2.5m model on a single GPU card.

{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 2.5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||NVIDIA GeForce RTX 4090||24||16384||103.3||811.2||914.5||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz||NVIDIA GeForce RTX 4090||24||16384||105.9||813.7||919.6||TA1
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz||NVIDIA GeForce RTX 4090||24||16384||103.7||824.3||928.0||JW1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||108.2||821.5||929.7||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||106.8||875.5||982.3||CR4
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz ||NVIDIA RTX 6000 Ada Generation||48||18176||119.6||877.8||997.4||JG3
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||139.5||1115.1||1254.6||JM3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||155.2||1172.9||1328.1||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||155.5||1176.2||1331.7||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||158||1192.2||1350.2||CH3
|-
|Intel(R) Core(TM) i9-10900F CPU @ 3.70GHz ||NVIDIA GeForce RTX 3090||24||10496||162.3||1192.4||1354.7||LJA
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||159.7||1216.2||1375.9||GP1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||160.9||1240||1400.9||DD2
|-
|Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz ||NVIDIA GeForce RTX 3090||24||10496||172.9||1249.8||1422.7||SIP
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||178.9||1363.9||1542.8||KW2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||203.8||1523.9||1727.7||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||201.2||1548.1||1749.3||JGR
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||220.0||1634.5||1854.5||MA1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||222.2||1648.7||1870.9||JPI
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||215.9||1678.7||1894.6||PA2
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||241.2||1863.5||2104.7||RRB
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||248.7||1928.6||2177.3||JG2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||257.3||1957.7||2215.0||RH2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||275.1||2147.4||2422.5||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||296.0||2218.4||2514.4||FLC
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||298.9||2290.1||2589.0||JS1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.3||2345.1||2656.4||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||310.3||2377.2||2687.5||RCD
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||308.7||2384.7||2693.4||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.9||2404.9||2716.7||PM1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||324.8||2475.3||2800.1||HNM
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||439.0||3379.3||3818.2||BLK
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||475.5||3788.2||4263.7||SKI
|-
|}
<pre> * it is noted that the number of CUDA cores is not provided as an output from the '''dxdiag''' command and this information has been sourced from the nvidia website.
** The output cpu.txt only provides the 'out of the box' processor speed. If you have overclocked your cpu and/or gpu, please send these details to TUFLOW Support so we can add the overclocked data in brackets. </pre>

{{Tips Navigation
|uplink=[[Hardware_Benchmarking_(2018-03-AA) | Back to TUFLOW Benchmarking]]
}}

Hardware Benchmarking - Results

2024-08-06T11:44:21Z

Angelos Livogiannis:

=CPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m Classic and HPC CPU runtimes, with the fastest computers at the top of the table.
 
'''Runtimes for CPU benchmarks'''
{| align="center" class="wikitable"

! style="background-color:#005581; font-weight:bold; color:white;"| Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Processor Frequency (GHz)**
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM size (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM frequency (MHz)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Classic 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | HPC CPU 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Runtime Combined (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||128||5200||32.7||108.6||141.3||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||64||5600||36.7||114.2||150.9||TM1
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||2.0||128||4000||41.2||124.1||165.3||AW1
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs)||3.2||128||4800||38.5||127.0||165.5||SB1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz||4.5||64||4800||33.4||136.0||169.4||PSM
|-
|12th Gen Intel(R) Core(TM) i9-12900K||3.2||128||3200||40.7||129.9||170.6||DD2
|-
|12th Gen Intel(R) Core(TM) i7-12700 (20 CPUs) @ ~2.1GHz||2.1||64||4800||41||137.2||178.2||RB1
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs) @ ~4.2GHz||4.2||32||4800||35.5||162.8||198.3||LC1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs)||2.5||16||3200||48.4||170.5||218.9||TS1
|-
|Intel(R) Xeon(R) w5-2455X (24 CPUs) @ ~3.2GHz||3.2||64||4800||53.3||169.1||222.4||CHR
|-
|Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz||3.7||128||3200||56.9||173.8||230.7||CH1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz)||(5.1)||16||4000||58.2||179.9||238.1||RRB
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||3000||55.7||186.2||241.9||RH1
|-
|AMD Ryzen 9 3900X 12-Core Processor||3.8||64||3200||45.9||203.1||249.0||CH3
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz||3.1||32||2666||61.7||190.0||251.7||CB1
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz||3.6||32||2133||61.4||190.4||251.8||RH2
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||3.6||64||2133||62.7||191.1||253.8||PA1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||32||2933||62.1||192.8||254.9||DS2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||71.2||184.3||255.5||ABA
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||62.1||193.7||255.8||MA2
|-
|AMD Ryzen Threadripper 3970X 32-Core Processor||3.7||256||2400||49.5||212.1||261.6||CH2
|-
|AMD Ryzen 9 3950X 16-Core Processor||3.5||128||2800||55.9||210.0||265.9||TRO
|-
|AMD EPYC 74F3 24-Core Processor (6 CPUs) @ 3.2GHz||3.2||56||N/A||49.1||218.9||268||RBR
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||2133||67.0||202.5||269.5||RL1
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz||3.5||128||2133||72.7||202.1||274.8||MBL
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||67.5||208.6||276.1||SKI
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||68.5||208.8||277.3||PM2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||66.8||211.6||278.1||MA1
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz||3.2||16||2667||68.2||211.8||280.0||CR2
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||68.0||216.0||284.0||RL3
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||67.7||219.1||286.8||RL2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||70.5||218.8||289.3||PM1
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||2.9||16||2667||77.5||212.6||290.1||KTC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||3.7||32||2933||75.2||219.8||295||BL-DT01001
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor||3.5||128||2666||67.9||230.8||298.7||JGR
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||3.5||128||2666||66.3||234.7||301||JG3
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||32||2400||80.5||221.9||302.4||JM1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz||3.6||16||2400||72.8||230.6||303.4||RSH
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||85.4||218.8||304.2||JPI
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||83.7||225.2||308.9||HNM
|-
|Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz||4.0||32||2400||91.2||223.3||314.5||BRD
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz||3.7||64||2400||84.5||236.6||321.2||DS1
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz||3.2||128||2133||83.4||243.1||326.5||BLK
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||3.7||64||2933||95.4||231.3||326.7||JB2
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz||3.4||128||2400||85.3||247.7||332.9||615
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2400||106.3||226.7||333.0||MRT
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||16||2133||80.7||253.4||334.1||VHD
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz||2.1||64||2666||83.9||251.2||335.1||AR2
|-
|AMD EPYC 7V12 64-Core Processor (16 CPUs) ||2.4||57||NA||63.5||277.6||341.1||CS2
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor||3.4||16||2666||81.9||277.3||359.2||CEV
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz||3.0||32||2400||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||64||2133||82.3||289.8||372.1||JIW
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz||3.4||32||1666||108.9||270.0||378.9||AR1
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||3.8||64||3200||87.8||294.2||382||HDR-A2000
|-
|AMD Ryzen 9 5950X 16-Core Processor||3.4||32||3400||39.7||343.0||382.7||JG2
|-
|Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz||2.8||32||1600||119.7||280.8||400.5||SBC
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz||3.3||64||2133||118.2||287.8||406.0||ZDO
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz||2.7||16||2133||90.4||321.7||412.1||EAS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||16||2133||84.8||336.9||421.7||JM2
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2133||100.3||323||423.3||MON
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz||3.4||32||1600||126.4||299.7||426.1||MAV
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz ||3.0||4||986||84.0||351.4||435.4||TJS
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||3.5||16||1333||125.9||320.5||446.4||EFC
|-
|Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz||1.9||16||1800||100.1||347.0||447.1||SM1
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||2.9||16||2900||63.3||385.0||448.3||NCV
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||4.1||16||4104||62.7||386.6||449.3||GZH
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||2.4||128||2394||130.5||331.5||462||VDI
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||2.6||24||1600||100.5||378.6||479.1||CDH
|-
|Intel(R) Xeon(R) CPU E5-1650 0 @ 3.20GHz||3.2||32||1600||143.2||343.1||486.3||MPR
|-
|Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz||3.2||8||1600||142.0||349.4||491.4||CR1
|-
|Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz||3.3||16||N/A||196.8||331.5||528.3||Private Cloud
|-
|Intel(R) Core(TM) i7-4712HQ CPU @ 2.30GHz (Laptop)||2.3||8||1600||145.2||414.4||559.6||MNG
|-
|Intel(R) Xeon(R) CPU X5680 @ 3.33GHz||3.33||72||1333||165.7||400.6||566.3||WTM
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||2.4||8||1600||137.8||795.0||932.8||HMM
|-
|}
 

=GPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m and 10m runtimes with the fastest computers at the top of the table.
 
The HPC GPU benchmark only uses a single GPU card. TUFLOW HPC GPU can be run across multiple NVIDIA GPU devices. However, the benefits of these are typically more noticeable for larger models with more than 1 million cells.
 
'''Runtimes for GPU benchmarks'''
{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 10m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz ||NVIDIA GeForce RTX 4090||24||16384||2.4||11.6||14.0||JW1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4090||24||16384||2.5||12.1||14.6||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz ||NVIDIA GeForce RTX 4090||24||16384||2.7||12.7||15.4||TA1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||2.9||12.7||15.6||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||3.1||13.3||16.4||CR4
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||TM1
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||JM3
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||NVIDIA GeForce RTX 4080||16||9728||3.2||15.0||18.2||AW1
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs)@ ~4.2GHz||NVIDIA GeForce RTX 4080 SUPER||16||10240||3.2||15.7||18.9||LC1
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||NVIDIA RTX 6000 Ada Generation||48||18176||4.9||14.2||19.1||JG3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||3.4||18.5||21.9||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||3.8||19.2||23.0||RS1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||3.7||19.4||23.1||DD2
|-
|12th Gen Intel(R) Core(TM) i7-12700F
|NVIDIA GeForce RTX 3080 Ti
|12
|10240
|3.75
|19.57
|23.32
|AUBNE1PC6602
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||4.0||19.6||23.6||GP1
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA A40||48||10752||3.5||20.3||23.8||Lenovo SR650 V2
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.1||20.1||24.2||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.4||20.4||24.8||CH3
|-
|12th Gen Intel(R) Core(TM) i7-12700 (20 CPUs) @ ~2.1GHz ||NVIDIA GeForce RTX 3080||10||8704||4.3||23.7||28||RB1
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||4.6||23.5||28.1||KW2
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs) ||NVIDIA RTX A5000||24||8192||4.4||24.1||28.5||SB1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 3080||10||8704||4.7||24.0||28.7||CPM
|-
|Intel(R) Xeon(R) W-2223 CPU @ 3.60GHz ||NVIDIA GeForce RTX 3090||24||10496||5.3||24.3||29.6||SSM2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||4.7||25.7||30.4||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||5.7||25.2||30.9||JGR
|-
|AMD Ryzen Threadripper 2920X 12-Core Processor (24 CPUs) @ 3.5GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.1||25.9||31||CR5
|-
|AMD Ryzen 9 3950X 16-Core Processor ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.3||26.4||31.7||TRO
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||27.4||32.8||PY2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||27.7||33.4||VLD
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||NVIDIA GeForce RTX 3070||8||5888||5.0||28.8||33.8||NCV
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.5||28.4||33.9||RL1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||5.5||28.7||34.2||RRB
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.8||28.8||34.6||MA1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||29.2||34.9||MA2
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||5.5||29.7||35.2||JG2
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.6||29.9||35.5||MBL
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||6.4||29.5||35.9||JPI
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P100||16||3584||6.1||30.8||36.9||Google Cloud: Tesla P100
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||5.7||31.9||37.6||RH2
|-
|Intel(R) Xeon(R) Gold 6230R CPU @ 2.10GHz ||NVIDIA GRID RTX8000P-48Q||48||4608||6.8||31.0||37.8||VJ1
|-
|Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 CPUs) ||NVIDIA RTX A4000||16||6144||5.8||32.0||37.8||JS2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080||8||2944||6.0||31.9||37.9||ANK
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||6.0||32.0||38.0||EFC
|-
|AMD EPYC 74F3 24-Core Processor (36 CPUs) @ 3.2GHz ||NVIDIA A10-24Q||24||8192||7.2||31.4||38.6||CS1
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||33.3||38.7||PA1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce RTX 3060 Ti (LHR) ||8||4864||5.7||33.3||39.0||DF1
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||NVIDIA GeForce RTX 2060 SUPER (core 1647MHz, mem 1750MHz)||8||2176||5.6||33.4||39.1||GZH
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||5.6||34.3||40.7||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||6.9||34.6||41.6||FLC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||35.1||41.6||JB2
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.4||35.8||42.2||JS1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080||8||2944||6.5||36.0||42.5||ABA
|-
|Intel(R) Xeon(R) w5-2455X (24 CPUs) @ ~3.2GHz ||NVIDIA RTX A4000||16||6144||7.2||35.3||42.5||CHR
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.1||37.1||43.2||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||37.4||43.8||PM1
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA GeForce GTX 2070||8||2304||7.4||38.8||46.2||MMR
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz ||NVIDIA Quadro RTX 4000||8||2304||6.6||39.8||46.4||CB1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.8||39.1||46.9||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||8.0||39.3||47.3||RCD
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.6||41.1||48.7||HNM
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||NVIDIA GRID RTX6000P-4Q||24||4608||10.5||39.3||49.8||VDI
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (Laptop) ||NVIDIA GeForce RTX 2070||8||2304||7.7||42.8||50.5||ERX
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA Tesla T4||16||2560||6.8||45.2||52.0||RJ1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz
|NVIDIA GeForce RTX 3060
|8
|3584
|7.68
|45.92
|53.6
|AUBNEW1DQ54G3
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||8.0||47.4||55.3||BLK
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla T4||16||2560||7.3||48.3||55.6||FM-NODE: Tesla T4
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz ||NVIDIA GeForce GTX 1080||8||2560||8.5||48.9||57.3||JM1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||8.2||51.9||60.0||SKI
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz ||NVIDIA Quadro P5000||16||2560||9.6||51.8||61.4||AR2
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||NVIDIA RTX A2000||6||3328||9.1||54.4||63.5||HDR-A2000
|-
|Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz ||NVIDIA GeForce GTX 1070||8||1920||8.9||54.9||63.8||PY1
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz ||NVIDIA GeForce GTX 1070||8||1920||10.3||59.3||69.5||DS1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA Quadro P4000||8||1792||10.0||62.3||72.3||DS2
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce GTX 1650 SUPER||4||1280||10.3||64.6||74.9||TS1
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P4||8||2560||10.4||69.0||79.4||Google Cloud: Tesla P4
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz ||NVIDIA GeForce GTX 980||4||2048||11.8||70.6||82.3||ZDO
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz ||NVIDIA GeForce GTX TITAN Black||6||2880||13.1||76.1||89.2||AR1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz ||NVIDIA GeForce GTX 1060||6||1280||13.0||77.1||90.1||RSH
|-
|Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz (64 CPUs), ~2.3GHz||NVIDIA Tesla M60||16||4096||12||82.7||94.7||SM2
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla K80||12||2496||11.3||83.5||94.8||Google Cloud: Tesla K80
|-
|Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz ||NVIDIA Tesla K40c||12||2880||12.3||83.1||95.3||NWE
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA Quadro T2000||4||1024||13.3||85.2||95.5||SSM
|-
|Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (Laptop) ||NVIDIA GeForce GTX 980||4||2048||17.5||84.2||101.7||MRT
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||NVIDIA Quadro P2000||5||1024||14.2||96||110.2||BL-DT01001
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz ||NVIDIA Quadro P2000||5||1024||15.8||100.1||115.9||CR2
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz ||NVIDIA GeForce GTX 690||2||3072||18.4||114.4||132.8||MAV
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor ||NVIDIA GeForce GTX 960||4||1024||18.6||123.3||141.6||CEV
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA GeForce GTX 960||4||1024||19.9||127.2||147.1||VHD
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz||NVIDIA GeForce GTX 1050 Ti||4||768||21.1||133.8||154.9||MJS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||NVIDIA GeForce GTX 1050||2||640||20.6||139.1||159.7||JM2
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||NVIDIA Quadro P2000||5||1024||22.1||142.5||164.6||KTC
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||NVIDIA Quadro P2000||5||1024||23.0||149.3||172.3||RL2
|-
|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz||NVIDIA Quadro M2200||4||1024||23.2||198.7||222.0||GYB
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz||NVIDIA T500||4||986||29.3||197.5||226.8||TJS
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz ||NVIDIA Quadro P1000||4||640||30.3||203.7||234.0||RL3
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA Quadro K2200||4||640||32.5||211.3||243.8||JIW
|-
|AMD EPYC 74F3 24-Core Processor (6 CPUs) @ 3.2GHz||NVIDIA A10-4Q||24||8192||44.5||212.6||257.1||RBR
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz ||NVIDIA Quadro M1200||4||640||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz ||NVIDIA GeForce GTX 940MX||2||384||65.6||479.0||544.6||EAS
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||NVIDIA GeForce 840M||2||384||70.6||526.3||595.9||CDH
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||NVIDIA GeForce GT 740M||2||384||102.3||694.0||796.3||HMM
|-
|}
 

=High End GPU Results=
A number of additional benchmarking tests have been completed on a 5m and 2.5m model on a single GPU card.

{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 2.5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||NVIDIA GeForce RTX 4090||24||16384||103.3||811.2||914.5||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz||NVIDIA GeForce RTX 4090||24||16384||105.9||813.7||919.6||TA1
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz||NVIDIA GeForce RTX 4090||24||16384||103.7||824.3||928.0||JW1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||108.2||821.5||929.7||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||106.8||875.5||982.3||CR4
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz ||NVIDIA RTX 6000 Ada Generation||48||18176||119.6||877.8||997.4||JG3
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||139.5||1115.1||1254.6||JM3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||155.2||1172.9||1328.1||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||155.5||1176.2||1331.7||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||158||1192.2||1350.2||CH3
|-
|Intel(R) Core(TM) i9-10900F CPU @ 3.70GHz ||NVIDIA GeForce RTX 3090||24||10496||162.3||1192.4||1354.7||LJA
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||159.7||1216.2||1375.9||GP1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||160.9||1240||1400.9||DD2
|-
|Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz ||NVIDIA GeForce RTX 3090||24||10496||172.9||1249.8||1422.7||SIP
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||178.9||1363.9||1542.8||KW2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||203.8||1523.9||1727.7||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||201.2||1548.1||1749.3||JGR
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||220.0||1634.5||1854.5||MA1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||222.2||1648.7||1870.9||JPI
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||215.9||1678.7||1894.6||PA2
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||241.2||1863.5||2104.7||RRB
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||248.7||1928.6||2177.3||JG2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||257.3||1957.7||2215.0||RH2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||275.1||2147.4||2422.5||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||296.0||2218.4||2514.4||FLC
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||298.9||2290.1||2589.0||JS1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.3||2345.1||2656.4||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||310.3||2377.2||2687.5||RCD
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||308.7||2384.7||2693.4||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.9||2404.9||2716.7||PM1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||324.8||2475.3||2800.1||HNM
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||439.0||3379.3||3818.2||BLK
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||475.5||3788.2||4263.7||SKI
|-
|}
<pre> * it is noted that the number of CUDA cores is not provided as an output from the '''dxdiag''' command and this information has been sourced from the nvidia website.
** The output cpu.txt only provides the 'out of the box' processor speed. If you have overclocked your cpu and/or gpu, please send these details to TUFLOW Support so we can add the overclocked data in brackets. </pre>

{{Tips Navigation
|uplink=[[Hardware_Benchmarking_(2018-03-AA) | Back to TUFLOW Benchmarking]]
}}

HPC Modelling Guidance

2024-08-02T10:57:05Z

Angelos Livogiannis:

TUFLOW’s HPC solver was officially released in September 2017. It is a 1D and 2D fixed grid explicit solver with Graphics Processing Unit (GPU) compatibility. Its speed and exceptional stability are making it one of the most popular TUFLOW solvers. This is particularly the case in situations where the runtime benefits of the GPU Module mean models that were otherwise too computationally intensive to run on CPU can now be simulated within sensible timeframes. 
 
[[File:HPC Simulation Speed Up 002.PNG|700px]]

The following links provide useful HPC guidance to users. Further information is also available in the [https://www.tuflow.com/Tuflow%20Documentation.aspx TUFLOW Manual] (2017 and onwards) and in the [[Tutorial_Introduction |TUFLOW Tutorials]].

* [[HPC_Introduction | HPC Introduction]]
* [[HPC_Running_and_Converting_Models | HPC Running and Converting Models]]
* [[HPC_Adaptive_Timestepping | HPC Adaptive Timestepping]]
* [[HPC_Model_Review | HPC Model Review]]
* [[HPC_Impact_Assessment_Guidance | HPC Impact Assessment Guidance]]
* [[TUFLOW_1D2D_SX_Advice | HPC 1D/2D SX Stability Guidance]]
* [[HPC_FAQ | HPC Common Questions / Answers]]
* [[Quadtree_and_Sub-Grid_Sampling_FAQ | HPC Quadtree and Sub-Grid Sampling Questions / Answers]]
* [[HPC_Turbulance_FAQ | HPC Turbulence Questions / Answers]]
'''Further Support''' 
If you experience an issue that is not detailed in one of our HPC Modelling Guidance pages please send an email to support@tuflow.com
 
 
{{Tips Navigation
|uplink=[[ TUFLOW_Modelling_Guidance | Back to TUFLOW Modelling Guidance]]
}}

Hardware Benchmarking - Results

2024-08-01T10:20:37Z

Angelos Livogiannis:

=CPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m Classic and HPC CPU runtimes, with the fastest computers at the top of the table.
 
'''Runtimes for CPU benchmarks'''
{| align="center" class="wikitable"

! style="background-color:#005581; font-weight:bold; color:white;"| Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Processor Frequency (GHz)**
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM size (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM frequency (MHz)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Classic 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | HPC CPU 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Runtime Combined (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||128||5200||32.7||108.6||141.3||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||64||5600||36.7||114.2||150.9||TM1
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||2.0||128||4000||41.2||124.1||165.3||AW1
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs)||3.2||128||4800||38.5||127.0||165.5||SB1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz||4.5||64||4800||33.4||136.0||169.4||PSM
|-
|12th Gen Intel(R) Core(TM) i9-12900K||3.2||128||3200||40.7||129.9||170.6||DD2
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs) @ ~4.2GHz||4.2||32||4800||35.5||162.8||198.3||LC1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs)||2.5||16||3200||48.4||170.5||218.9||TS1
|-
|Intel(R) Xeon(R) w5-2455X (24 CPUs) @ ~3.2GHz||3.2||64||4800||53.3||169.1||222.4||CHR
|-
|Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz||3.7||128||3200||56.9||173.8||230.7||CH1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz)||(5.1)||16||4000||58.2||179.9||238.1||RRB
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||3000||55.7||186.2||241.9||RH1
|-
|AMD Ryzen 9 3900X 12-Core Processor||3.8||64||3200||45.9||203.1||249.0||CH3
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz||3.1||32||2666||61.7||190.0||251.7||CB1
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz||3.6||32||2133||61.4||190.4||251.8||RH2
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||3.6||64||2133||62.7||191.1||253.8||PA1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||32||2933||62.1||192.8||254.9||DS2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||71.2||184.3||255.5||ABA
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||62.1||193.7||255.8||MA2
|-
|AMD Ryzen Threadripper 3970X 32-Core Processor||3.7||256||2400||49.5||212.1||261.6||CH2
|-
|AMD Ryzen 9 3950X 16-Core Processor||3.5||128||2800||55.9||210.0||265.9||TRO
|-
|AMD EPYC 74F3 24-Core Processor (6 CPUs) @ 3.2GHz||3.2||56||N/A||49.1||218.9||268||RBR
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||2133||67.0||202.5||269.5||RL1
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz||3.5||128||2133||72.7||202.1||274.8||MBL
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||67.5||208.6||276.1||SKI
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||68.5||208.8||277.3||PM2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||66.8||211.6||278.1||MA1
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz||3.2||16||2667||68.2||211.8||280.0||CR2
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||68.0||216.0||284.0||RL3
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||67.7||219.1||286.8||RL2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||70.5||218.8||289.3||PM1
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||2.9||16||2667||77.5||212.6||290.1||KTC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||3.7||32||2933||75.2||219.8||295||BL-DT01001
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor||3.5||128||2666||67.9||230.8||298.7||JGR
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||3.5||128||2666||66.3||234.7||301||JG3
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||32||2400||80.5||221.9||302.4||JM1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz||3.6||16||2400||72.8||230.6||303.4||RSH
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||85.4||218.8||304.2||JPI
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||83.7||225.2||308.9||HNM
|-
|Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz||4.0||32||2400||91.2||223.3||314.5||BRD
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz||3.7||64||2400||84.5||236.6||321.2||DS1
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz||3.2||128||2133||83.4||243.1||326.5||BLK
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||3.7||64||2933||95.4||231.3||326.7||JB2
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz||3.4||128||2400||85.3||247.7||332.9||615
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2400||106.3||226.7||333.0||MRT
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||16||2133||80.7||253.4||334.1||VHD
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz||2.1||64||2666||83.9||251.2||335.1||AR2
|-
|AMD EPYC 7V12 64-Core Processor (16 CPUs) ||2.4||57||NA||63.5||277.6||341.1||CS2
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor||3.4||16||2666||81.9||277.3||359.2||CEV
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz||3.0||32||2400||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||64||2133||82.3||289.8||372.1||JIW
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz||3.4||32||1666||108.9||270.0||378.9||AR1
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||3.8||64||3200||87.8||294.2||382||HDR-A2000
|-
|AMD Ryzen 9 5950X 16-Core Processor||3.4||32||3400||39.7||343.0||382.7||JG2
|-
|Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz||2.8||32||1600||119.7||280.8||400.5||SBC
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz||3.3||64||2133||118.2||287.8||406.0||ZDO
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz||2.7||16||2133||90.4||321.7||412.1||EAS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||16||2133||84.8||336.9||421.7||JM2
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2133||100.3||323||423.3||MON
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz||3.4||32||1600||126.4||299.7||426.1||MAV
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz ||3.0||4||986||84.0||351.4||435.4||TJS
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||3.5||16||1333||125.9||320.5||446.4||EFC
|-
|Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz||1.9||16||1800||100.1||347.0||447.1||SM1
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||2.9||16||2900||63.3||385.0||448.3||NCV
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||4.1||16||4104||62.7||386.6||449.3||GZH
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||2.4||128||2394||130.5||331.5||462||VDI
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||2.6||24||1600||100.5||378.6||479.1||CDH
|-
|Intel(R) Xeon(R) CPU E5-1650 0 @ 3.20GHz||3.2||32||1600||143.2||343.1||486.3||MPR
|-
|Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz||3.2||8||1600||142.0||349.4||491.4||CR1
|-
|Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz||3.3||16||N/A||196.8||331.5||528.3||Private Cloud
|-
|Intel(R) Core(TM) i7-4712HQ CPU @ 2.30GHz (Laptop)||2.3||8||1600||145.2||414.4||559.6||MNG
|-
|Intel(R) Xeon(R) CPU X5680 @ 3.33GHz||3.33||72||1333||165.7||400.6||566.3||WTM
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||2.4||8||1600||137.8||795.0||932.8||HMM
|-
|}
 

=GPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m and 10m runtimes with the fastest computers at the top of the table.
 
The HPC GPU benchmark only uses a single GPU card. TUFLOW HPC GPU can be run across multiple NVIDIA GPU devices. However, the benefits of these are typically more noticeable for larger models with more than 1 million cells.
 
'''Runtimes for GPU benchmarks'''
{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 10m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz ||NVIDIA GeForce RTX 4090||24||16384||2.4||11.6||14.0||JW1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4090||24||16384||2.5||12.1||14.6||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz ||NVIDIA GeForce RTX 4090||24||16384||2.7||12.7||15.4||TA1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||2.9||12.7||15.6||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||3.1||13.3||16.4||CR4
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||TM1
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||JM3
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||NVIDIA GeForce RTX 4080||16||9728||3.2||15.0||18.2||AW1
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs)@ ~4.2GHz||NVIDIA GeForce RTX 4080 SUPER||16||10240||3.2||15.7||18.9||LC1
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||NVIDIA RTX 6000 Ada Generation||48||18176||4.9||14.2||19.1||JG3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||3.4||18.5||21.9||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||3.8||19.2||23.0||RS1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||3.7||19.4||23.1||DD2
|-
|12th Gen Intel(R) Core(TM) i7-12700F
|NVIDIA GeForce RTX 3080 Ti
|12
|10240
|3.75
|19.57
|23.32
|AUBNE1PC6602
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||4.0||19.6||23.6||GP1
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA A40||48||10752||3.5||20.3||23.8||Lenovo SR650 V2
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.1||20.1||24.2||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.4||20.4||24.8||CH3
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||4.6||23.5||28.1||KW2
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs) ||NVIDIA RTX A5000||24||8192||4.4||24.1||28.5||SB1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 3080||10||8704||4.7||24.0||28.7||CPM
|-
|Intel(R) Xeon(R) W-2223 CPU @ 3.60GHz ||NVIDIA GeForce RTX 3090||24||10496||5.3||24.3||29.6||SSM2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||4.7||25.7||30.4||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||5.7||25.2||30.9||JGR
|-
|AMD Ryzen Threadripper 2920X 12-Core Processor (24 CPUs) @ 3.5GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.1||25.9||31||CR5
|-
|AMD Ryzen 9 3950X 16-Core Processor ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.3||26.4||31.7||TRO
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||27.4||32.8||PY2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||27.7||33.4||VLD
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||NVIDIA GeForce RTX 3070||8||5888||5.0||28.8||33.8||NCV
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.5||28.4||33.9||RL1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||5.5||28.7||34.2||RRB
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.8||28.8||34.6||MA1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||29.2||34.9||MA2
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||5.5||29.7||35.2||JG2
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.6||29.9||35.5||MBL
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||6.4||29.5||35.9||JPI
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P100||16||3584||6.1||30.8||36.9||Google Cloud: Tesla P100
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||5.7||31.9||37.6||RH2
|-
|Intel(R) Xeon(R) Gold 6230R CPU @ 2.10GHz ||NVIDIA GRID RTX8000P-48Q||48||4608||6.8||31.0||37.8||VJ1
|-
|Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 CPUs) ||NVIDIA RTX A4000||16||6144||5.8||32.0||37.8||JS2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080||8||2944||6.0||31.9||37.9||ANK
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||6.0||32.0||38.0||EFC
|-
|AMD EPYC 74F3 24-Core Processor (36 CPUs) @ 3.2GHz ||NVIDIA A10-24Q||24||8192||7.2||31.4||38.6||CS1
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||33.3||38.7||PA1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce RTX 3060 Ti (LHR) ||8||4864||5.7||33.3||39.0||DF1
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||NVIDIA GeForce RTX 2060 SUPER (core 1647MHz, mem 1750MHz)||8||2176||5.6||33.4||39.1||GZH
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||5.6||34.3||40.7||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||6.9||34.6||41.6||FLC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||35.1||41.6||JB2
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.4||35.8||42.2||JS1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080||8||2944||6.5||36.0||42.5||ABA
|-
|Intel(R) Xeon(R) w5-2455X (24 CPUs) @ ~3.2GHz ||NVIDIA RTX A4000||16||6144||7.2||35.3||42.5||CHR
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.1||37.1||43.2||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||37.4||43.8||PM1
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA GeForce GTX 2070||8||2304||7.4||38.8||46.2||MMR
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz ||NVIDIA Quadro RTX 4000||8||2304||6.6||39.8||46.4||CB1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.8||39.1||46.9||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||8.0||39.3||47.3||RCD
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.6||41.1||48.7||HNM
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||NVIDIA GRID RTX6000P-4Q||24||4608||10.5||39.3||49.8||VDI
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (Laptop) ||NVIDIA GeForce RTX 2070||8||2304||7.7||42.8||50.5||ERX
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA Tesla T4||16||2560||6.8||45.2||52.0||RJ1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz
|NVIDIA GeForce RTX 3060
|8
|3584
|7.68
|45.92
|53.6
|AUBNEW1DQ54G3
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||8.0||47.4||55.3||BLK
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla T4||16||2560||7.3||48.3||55.6||FM-NODE: Tesla T4
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz ||NVIDIA GeForce GTX 1080||8||2560||8.5||48.9||57.3||JM1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||8.2||51.9||60.0||SKI
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz ||NVIDIA Quadro P5000||16||2560||9.6||51.8||61.4||AR2
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||NVIDIA RTX A2000||6||3328||9.1||54.4||63.5||HDR-A2000
|-
|Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz ||NVIDIA GeForce GTX 1070||8||1920||8.9||54.9||63.8||PY1
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz ||NVIDIA GeForce GTX 1070||8||1920||10.3||59.3||69.5||DS1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA Quadro P4000||8||1792||10.0||62.3||72.3||DS2
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce GTX 1650 SUPER||4||1280||10.3||64.6||74.9||TS1
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P4||8||2560||10.4||69.0||79.4||Google Cloud: Tesla P4
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz ||NVIDIA GeForce GTX 980||4||2048||11.8||70.6||82.3||ZDO
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz ||NVIDIA GeForce GTX TITAN Black||6||2880||13.1||76.1||89.2||AR1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz ||NVIDIA GeForce GTX 1060||6||1280||13.0||77.1||90.1||RSH
|-
|Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz (64 CPUs), ~2.3GHz||NVIDIA Tesla M60||16||4096||12||82.7||94.7||SM2
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla K80||12||2496||11.3||83.5||94.8||Google Cloud: Tesla K80
|-
|Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz ||NVIDIA Tesla K40c||12||2880||12.3||83.1||95.3||NWE
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA Quadro T2000||4||1024||13.3||85.2||95.5||SSM
|-
|Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (Laptop) ||NVIDIA GeForce GTX 980||4||2048||17.5||84.2||101.7||MRT
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||NVIDIA Quadro P2000||5||1024||14.2||96||110.2||BL-DT01001
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz ||NVIDIA Quadro P2000||5||1024||15.8||100.1||115.9||CR2
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz ||NVIDIA GeForce GTX 690||2||3072||18.4||114.4||132.8||MAV
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor ||NVIDIA GeForce GTX 960||4||1024||18.6||123.3||141.6||CEV
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA GeForce GTX 960||4||1024||19.9||127.2||147.1||VHD
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz||NVIDIA GeForce GTX 1050 Ti||4||768||21.1||133.8||154.9||MJS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||NVIDIA GeForce GTX 1050||2||640||20.6||139.1||159.7||JM2
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||NVIDIA Quadro P2000||5||1024||22.1||142.5||164.6||KTC
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||NVIDIA Quadro P2000||5||1024||23.0||149.3||172.3||RL2
|-
|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz||NVIDIA Quadro M2200||4||1024||23.2||198.7||222.0||GYB
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz||NVIDIA T500||4||986||29.3||197.5||226.8||TJS
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz ||NVIDIA Quadro P1000||4||640||30.3||203.7||234.0||RL3
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA Quadro K2200||4||640||32.5||211.3||243.8||JIW
|-
|AMD EPYC 74F3 24-Core Processor (6 CPUs) @ 3.2GHz||NVIDIA A10-4Q||24||8192||44.5||212.6||257.1||RBR
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz ||NVIDIA Quadro M1200||4||640||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz ||NVIDIA GeForce GTX 940MX||2||384||65.6||479.0||544.6||EAS
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||NVIDIA GeForce 840M||2||384||70.6||526.3||595.9||CDH
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||NVIDIA GeForce GT 740M||2||384||102.3||694.0||796.3||HMM
|-
|}
 

=High End GPU Results=
A number of additional benchmarking tests have been completed on a 5m and 2.5m model on a single GPU card.

{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 2.5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||NVIDIA GeForce RTX 4090||24||16384||103.3||811.2||914.5||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz||NVIDIA GeForce RTX 4090||24||16384||105.9||813.7||919.6||TA1
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz||NVIDIA GeForce RTX 4090||24||16384||103.7||824.3||928.0||JW1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||108.2||821.5||929.7||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||106.8||875.5||982.3||CR4
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz ||NVIDIA RTX 6000 Ada Generation||48||18176||119.6||877.8||997.4||JG3
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||139.5||1115.1||1254.6||JM3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||155.2||1172.9||1328.1||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||155.5||1176.2||1331.7||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||158||1192.2||1350.2||CH3
|-
|Intel(R) Core(TM) i9-10900F CPU @ 3.70GHz ||NVIDIA GeForce RTX 3090||24||10496||162.3||1192.4||1354.7||LJA
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||159.7||1216.2||1375.9||GP1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||160.9||1240||1400.9||DD2
|-
|Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz ||NVIDIA GeForce RTX 3090||24||10496||172.9||1249.8||1422.7||SIP
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||178.9||1363.9||1542.8||KW2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||203.8||1523.9||1727.7||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||201.2||1548.1||1749.3||JGR
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||220.0||1634.5||1854.5||MA1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||222.2||1648.7||1870.9||JPI
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||215.9||1678.7||1894.6||PA2
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||241.2||1863.5||2104.7||RRB
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||248.7||1928.6||2177.3||JG2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||257.3||1957.7||2215.0||RH2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||275.1||2147.4||2422.5||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||296.0||2218.4||2514.4||FLC
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||298.9||2290.1||2589.0||JS1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.3||2345.1||2656.4||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||310.3||2377.2||2687.5||RCD
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||308.7||2384.7||2693.4||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.9||2404.9||2716.7||PM1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||324.8||2475.3||2800.1||HNM
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||439.0||3379.3||3818.2||BLK
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||475.5||3788.2||4263.7||SKI
|-
|}
<pre> * it is noted that the number of CUDA cores is not provided as an output from the '''dxdiag''' command and this information has been sourced from the nvidia website.
** The output cpu.txt only provides the 'out of the box' processor speed. If you have overclocked your cpu and/or gpu, please send these details to TUFLOW Support so we can add the overclocked data in brackets. </pre>

{{Tips Navigation
|uplink=[[Hardware_Benchmarking_(2018-03-AA) | Back to TUFLOW Benchmarking]]
}}

TUFLOW Message 1253

2024-07-23T10:30:35Z

Angelos Livogiannis:

{{TUFLOW_Message
|tuflow_message=WARNING 1253 - Unused 1d_ta line with attributes: ",a,",
|alt_msg=NA
|type=[[WARNING]]
|message_desc=Unused data in table links (<tt>Read GIS Table Links == </tt>). A unused link to tabular input has been found, tabular data can include cross-section profiles, cross-section hydraulic parameters, nodal surface areas or bridge loss coefficients.
This can occur if:
* A 1d_ta element with three or more vertices isn't snapped to a 1D network (1d_nwk) node
* A 1d_ta element with two vertices does not intersect 1D network (1d_nwk) line
* A channel in the 1D network has both end and mid cross sections
* Two or more 1d_ta elements exist in the same location
|suggestions=
* Check if the 1d_ta object is linked to the 1D network (either snapped for a 1d_ta object with 3 or more vertices or just intersecting if the 1d_ta object has only 2 vertices)
* Check if the 1D network channel has both mid- and end- cross-sections. If both mid- and end- sections exist, TUFLOW will ignore the end-cross-sections in favour of the mid-cross-sections (Refer to the Mid Cross-Section and End Cross-section Chapters of the TUFLOW Manual)
* Check if cross-sections are both in the same location
* Check if the cross-section is snapped to a 1D network with overlapping vertices upstream/downstream. In QGIS, a green cross will be displayed if there are overlapping vertices. For example:
<ol>[[File:1d Network Overlapping Vertex.jpg||500px|]] </ol>

|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]]
}}

TUFLOW Message 1253

2024-07-23T10:07:39Z

Angelos Livogiannis:

{{TUFLOW_Message
|tuflow_message=WARNING 1253 - Unused 1d_ta line with attributes: ",a,",
|alt_msg=NA
|type=[[WARNING]]
|message_desc=Unused data in table links (<tt>Read GIS Table Links == </tt>). A unused link to tabular input has been found, tabular data can include cross-section profiles, cross-section hydraulic parameters, nodal surface areas or bridge loss coefficients.
This can occur if:
* A 1d_ta element with three or more vertices isn't snapped to a 1D network (1d_nwk) node
* A 1d_ta element with two vertices does not intersect 1D network (1d_nwk) line
* A channel in the 1D network has both end and mid cross sections
* Two or more 1d_ta elements exist in the same location
|suggestions=
* Check if the 1d_ta object is linked to the 1D network (either snapped for a 1d_ta object with 3 or more vertices or just intersecting if the 1d_ta object has only 2 vertices)
* Check if the 1D network channel has both mid- and end- cross-sections. If both mid- and end- sections exist, TUFLOW will ignore the end-cross-sections in favour of the mid-cross-sections (Refer to the Mid Cross-Section and End Cross-section Chapters of the TUFLOW Manual)
* Check if cross-sections are both in the same location
* Check if the cross-section is snapped to a 1D network with overlapping vertices upstream/downstream. If there is an overlapping vertex, in QGIS it will show as green. Please, see the example image below:

 [[File:1d Network Overlapping Vertex.jpg||500px|]] 

|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]]
}}

File:1d Network Overlapping Vertex.jpg

2024-07-23T10:05:42Z

Angelos Livogiannis:

1d Network Overlapping Vertex

TUFLOW Message 1253

2024-07-23T09:44:32Z

Angelos Livogiannis:

{{TUFLOW_Message
|tuflow_message=WARNING 1253 - Unused 1d_ta line with attributes: ",a,",
|alt_msg=NA
|type=[[WARNING]]
|message_desc=Unused data in table links (<tt>Read GIS Table Links == </tt>). A unused link to tabular input has been found, tabular data can include cross-section profiles, cross-section hydraulic parameters, nodal surface areas or bridge loss coefficients.
This can occur if:
* A 1d_ta element with three or more vertices isn't snapped to a 1D network (1d_nwk) node
* A 1d_ta element with two vertices does not intersect 1D network (1d_nwk) line
* A channel in the 1D network has both end and mid cross sections
* Two or more 1d_ta elements exist in the same location
|suggestions=
* Check if the 1d_ta object is linked to the 1D network (either snapped for a 1d_ta object with 3 or more vertices or just intersecting if the 1d_ta object has only 2 vertices)
* Check if the 1D network channel has both mid- and end- cross-sections. If both mid- and end- sections exist, TUFLOW will ignore the end-cross-sections in favour of the mid-cross-sections (Refer to the Mid Cross-Section and End Cross-section Chapters of the TUFLOW Manual)
* Check if cross-sections are both in the same location
* Check if the cross-section is snapped to a 1D network with overwrapping vertices upstream/downstream

|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]]
}}

TUFLOW to GIS

2024-07-19T10:16:29Z

Angelos Livogiannis:

=Introduction=
The TUFLOW_to_GIS.exe is a utility available on the TUFLOW website ([https://www.tuflow.com/downloads/#utilities Download TUFLOW utilities]).
 
The utility can be used to convert TUFLOW outputs (.xmdf and .dat) into formats that can be imported into GIS packages such as MapInfo, ArcGIS, and QGIS.
 
'''Note''' That as per the 2013 version of TUFLOW, TUFLOW can now write directly to the gridded formats (.asc and .flt). This avoids the need for a separate conversion step. This is outlined in the [https://www.tuflow.com/Download/TUFLOW/Releases/2013-12/Doc/TUFLOW%20Release%20Notes.2013-12.pdf release notes]. 
 
The output frequency and data types can now be specified independently for each data output format. An example is given below: 
<tt>Map Output Data Format == XMDF ASC 
XMDF Map Output Data Types == h v d dt 
XMDF Map Output Interval == 300 
ASC Map Output Data Types == h v d Z0 
ASC Map Output Interval == 0 </tt>
In the example above, both .xmdf and .asc are written directly by TUFLOW. For the .xmdf output the water levels, velocity, depth and mass balance output are written every 300 seconds (5 minutes). For the .asc format the water levels, velocities, depths and hazard (velocity depth product) are written. These are written only for the maximum (ASC Map Output Interval == 0).

The TUFLOW to GIS utility can output to grid format and also MapInfo and Shapefile format. For the MapInfo and Shapefile format this can be either as points, or as arrows.

 

=Running TUFLOW_to_GIS=
Simply double clicking on the TUFLOW_to_GIS executable will bring up a DOS prompt that that gives you some instructions on running the utility. 
The most common way to run the utility is from a batch file. This allows the user to process multiple outputs at once. A batch file is simply a plain text file containing one or more lines that execute a utility as per the example sections below. 
 
For more common tasks a right click function can be setup in Windows to perform a particular conversion. FileMenuTools can be used to set custom right click functionality, the method is described in the [[Windows_Right_Click_Functionality| Windows Right Click Functionality]]. The '''Program''' input should refer to the location of the TUFLOW_to_GIS executable and the '''Arguments''' input should contain the desired option and then %FILENAMES%. For example <tt>-b -asc -typeAll -max %FILENAMES%</tt> could be used to convert all of the "Maximums" data into gridded .asc format.

 

=Output Options=
== Gridded Data ==
Gridded (raster) data is outputted in the ESRI ASCII grid format. This is plain text format and is very widely recognised and used by a variety of GIS software including ArcGIS (requires Spatial Analyst), QGIS, and MapInfo (requires Vertical Mapper or Encom Discover). This is specified with the flag '''-asc'''. 

The TUFLOW to GIS utility uses the same approach as TUFLOW for interpolating a raster. That is, each cell is split into 4 triangles with a common vertex at the cell centre. An ASCII grid output directly from TUFLOW will use the calculated value at the cell centre (ZC). For an ASCII grid output using the TUFLOW to GIS utility, the centre used is the average of the corners. For this reason, the grids will not be exactly the same.

==Point and Vector Data==
Vector outputs (e.g. velocity or flow) can be written as either points or arrows. Scalar outputs (e.g. depth or level) can be written as points. These can currently be written out in either MapInfo format (.mif) or shapefiles (.shp). The '''-mif''' flag is used to output in MapInfo format and '''-shp''' to output in shapefile format. Only one type (-mif or -shp) can be processed at a time, to output in both formats, use two entries in a batch file.

 

=Switches (Input Flags)=
==General Input Switches==
A list of the input switches is provided below:
{| align="center" class="wikitable"

! Switch
! width=90% | Description
|-
|"-b"|| Run the utility in batch mode, this suppresses the prompt to press enter at the end of processing. Used in .bat files where two or more files are to be processed.
|-
|"-asc"|| The output file will be in ESRI ASCII Grid format, a text format recognised by most 3D grid modelling software (including Vertical Mapper and QGIS)
|-
|"-mif"|| The output format will be the MapInfo Interchange format (.mif/.mid) recognised by most GIS software
|-
|"-shp"|| The output format will be the shapefile format. This can be opened directly in QGIS and ArcMap (and most GIS software)
|-
|"-vector" or "-arrows"|| The output will contain arrows as polygons to display vector data (eg. velocities and unit flows) in GIS. Must be used with the -mif or -shp option.
|-
|"-slant<slant factor>"|| Changes the arrow head slant in the vector GIS output above. The default is -slant12 which gives 30 degree arrow head according to the equation ((180/slant)*2)
|-
|"-t<output time>"|| Converts the data at the specified timestep, for example -t2 to convert output time 2 hours. If this switch is omitted the utility will display a list of available times and prompt for an input. Use -t99999 or -max to convert the maximums.
|-
|"-tAll"|| Converts all output times from the .xmdf or .dat file.
|-
|"-max" or "-t99999"|| The maximums will be converted. The maximums must have been written to be able to convert using the -max or -t99999 switch. See the .tcf file command (Store Maximums and Minimums == ON MAXIMUMS ONLY).
|-
|"-sf<scale factor>"|| Scale factor to scale the size of the arrows. The default is sf = 1, which means the cell size of the first 2D domain in the .tcf file is equivalent in length to an arrow of 1m/s for velocity datasets or 1m3/s for unit flow datasets.
|-
|"-2dm <.2dm file>"|| To explicitly specify a .2dm file. By default TUFLOW_to_GIS assumes the .2dm file has the same name as the .xmdf file. Must be a space between -2dm and “<2dm_file>”.
|-
|"-grid<dist>"|| The output will be on a regular north-south aligned grid of spacing <dist> metres. If no <dist> is specified the user is prompted to enter a distance (e.g. "-grid"). If no grid input is used with a -mif or -shp conversion the data is converted at the cell corners. For a "-asc" output if no grid input is specified the default is 1/2 of the 2D cell size. 
For -asc output it sets the raster cell size of the 3D ESRI ASCII grid. 
For -mif or -shp output sets the interval in metres for the output on a north-south alignment.
|-
|"-cd<depth>"|| Sets the cutoff depth for use with -mif or -shp output, this is used when processing the water level and depth outputs. The default is 0.01m (or 0.01ft if the results are in feet).
|-
|"-prec.< d >"|| Sets the output precision for -asc, -mif and -shp options. For example -prec6.3 would output 6 units (or 5 units if number is negative) (ie. from -99,999 to 999,999) with 3 decimal places.
|-
|"-sec"|| Display and enter times in seconds (default = hours).
|-
|"-out<output file name, without file extension>"|| To specify the name of the output files. Extension added based on output format. Note: not applicable when converting multiple outputs (eg. multiple times).
|-
|"-sgs"|| Suppresses the grid size from the output file name. For example Run_h_g005_max.asc will become Run_h_max.asc
|-
|"-rmp<mesh_part>" || Removes a mesh part from the output. <mesh_part> must be the same name as appears in the .2dm file. The .tcf command Meshparts == ON must have been specified.
|-
|"-ttf<TT_Factor>" || Scales the thickness of arrow tails (default = 0). It will produce arrows suitable for ArcGIS if TT_factor is non-zero. 
+ve value(eg. -ttf.01): Thickness is TT_Factor times the arrow size. 
-ve value(eg. -ttf-.01): Thickness is TT_Factor times the cell size.
|-
|"-vmax<vmax>"|| The max vector magnitude for scaling vector arrow points.Default is no scaling except for _V.dat files which it is 10.
|-
|" -wld "|| It is used for creating a .wld file from a .tab file. The .tab file must be one created using the Save Window As...option in MapInfo to geo-reference a screen image.
|-
|"-pts<pt types>"|| Outputs only the specified out locations. Note: only valid with -mif or -shp output. Default is All. Any combination of the following: 
C - 2D cell centres 
H - 2D cell corners 
UV - 2D cell sides 
T - 1D Water Level Line triangles 
T - 1D Water Level Line triangles 
Eg: -ptsCT would output only 2D cell centres and 1D water level line points
|-
|"-region"||Outputs a region object, for each 2D cell the output value is the cell centre output. Note: only valid with -mif or -shp output.
|}

==XMDF Switches==
When working with the .xmdf outputs from TUFLOW, there are some additional input switches are available. This is because the .xmdf file uses a folder structure and multiple output parameters are stored in the same .xmdf file. When converting you can control which dataset is converted using the switches below. These switches are not valid for .dat files as these contain a single parameter for each file. E.g. the _d.dat contains only depth information. 
In the xmdf file, the data is stored in the following structure: 
<tt>Simulation ID/Folder/Dataset</tt>. Some examples for simulation "M01_5m_001" are: 
<tt>M01_5m_001/Maximums/ZAEM1</tt> 
<tt>M01_5m_001/Temporal/Depth</tt> 

The xmdf specific switches are outlined in the table below: 
{| align="center" class="wikitable"
! Switch
! width=80% | Description
|-

|"-type<output type>"|| Converts the specified output type in an xmdf file. Output types should be specified as per the output type in the .tcf e.g. h (water level), v (velocity), q (unit flow) or d (depth). Output types other than h, v, q and d are not predefined with the -type switch and should be called with -v and/or -s switch.
|-
|"-typeAll"|| Converts all available output types in an xmdf file.
|-
|"-s<output id(integer)>"|| Converts the specified scalar dataset in an xmdf file. For example, <tt>-s1</tt> will convert the first scalar dataset. A summary of the available datasets is listed within the DOS window when TUFLOW_to_GIS is preprocessing results. Check [[TUFLOW_to_GIS#XMDF_Dataset_Example | XMDF Dataset Example]]. To keep the DOS window open write "pause" at the end of the processing batch file and remove -b switch.
|-
|"-v<output id(integer)>"|| Converts the specified vector dataset in an xmdf file. For example, <tt>-v1</tt> will convert the first vector dataset. A summary of the available datasets is listed within the DOS window when TUFLOW_to_GIS is preprocessing results. Check [[TUFLOW_to_GIS#XMDF_Dataset_Example | XMDF Dataset Example]]. To keep the DOS window open write "pause" at the end of the processing batch file and remove -b switch.
|-
|"-Folder<Folder Name>"|| Converts all datasets within a particular xmdf file. For example, <tt>-Folder"Maximums"</tt> will convert all datasets in the \Maximums\ folder.
|-
|"-path<path name>"||Converts a dataset based on the path in the .xmdf file. For example, <tt>-path"Maximums/ZAEM1"</tt> would convert the dataset Maximum ZAEM1 dataset. This can be a full path in the .xmdf file or a partial match. E.g.: 
<tt>-path"Maximums/ZAEM1" M01_5m_001.xmdf</tt> 
<tt>-path"M01_5m_001/Maximums/ZAEM1" M01_5m_001.xmdf</tt> 
|}
===XMDF Dataset Example===
For example, to convert the maximum Z1 output from “M01_5m_002_mult.xmdf” the DOS window shows us that this is the fifth scalar dataset and the below command would be used: 
<tt>TUFLOW_to_GIS_w64.exe -asc -s5 -max M01_5m_002_mult.xmdf </tt> 
Another way to extract the same dataset using the -path switch is: 
<tt>TUFLOW_to_GIS_w64.exe -asc -path"Maximums/Z1" M01_5m_002_mult.xmdf</tt> 

[[File: xmdf_dataset_example.png]] 
 

==Calibration Point and Longitudinal Profile Switches==

{| align="center" class="wikitable"

! Switch
! width=90% | Description
|-
|"-cp<cp_file>"|| For appending the value from a .xmdf or .dat file to a .shp or .mif file. The cp_file contains points representing locations where results are extracted from TUFLOW. The file format includes two attributes. The first attribute is a numeric field containing the recorded value. The second field is a char(100) text field containing the cp name. The cp_file is also used to find calibration points near any longitudinal profile.
'Note: requires a space after -cp. Quotes should be used if spaces existing within the filename.'
|-
|"-cpsd<sd>"|| The search distance for finding calibration points near a longitudinal profile.
|-
|"-lpmd<md>"|| The distance between LP chainage markers along a longitudinal profile.
|-
|"-lp<lp_file>"|| For longitudinal profile output. The lp_file contains polyline(s) representing the lp alignments(s). The first and only attribute within the file is a char(100) containing the lp name. One <lp_name>.csv file for each polyline is produced.
'Note: requires a space after -lp. Quotes should be used if spaces existing within the filename.'
|-
|"-fso"|| Free Surface Only, sets 1D water levels in pipes to the obvert/soffit level if running full
|}

=Examples=
== Converting to 3D grids==
Probably the most common use of the TUFLOW_to_GIS utility is to convert the maximum results to a 3D surface. A number of examples are given below: 
<ol>
<li>Convert water level maximums to a 3D grid: 
*<tt>TUFLOW_to_GIS.exe -b -asc -max -typeH M01_5m_001.xmdf</tt> 
*Description: Using batch mode (-b), convert to a 3D grid (-asc), converting the maximums (-max) for the water level results (-typeH). 
 
<li>Convert to a 3D grid at a specific time: 
*<tt>TUFLOW_to_GIS.exe -b -asc -t3 -typeH M01_5m_001.xmdf</tt> 
*Description: As per example 1, except conversion at time 3 hours (-t3) instead of the maximums. 
 
<li>Convert to a 3D grid of specified grid cell size: 
*<tt>TUFLOW_to_GIS.exe -b -asc -max -grid1 -typeH M01_5m_001.xmdf</tt> 
*Description: As per example 1, except the raster cell size is specified at 1m instead of being half the 2D cell size. 
 
<li>Convert velocity maximums to a 3D grid: 
*<tt>TUFLOW_to_GIS.exe -b -asc -max -typeV M01_5m_001.xmdf</tt> 
*Description: As per example 1, except the velocity results (-typeV) are processed instead of water level (-typeH). 
 
<li>Convert Z1 hazard maximums to a 3D grid: 
*<tt>TUFLOW_to_GIS.exe -b -asc -max -s5 M01_5m_001.xmdf</tt> 
*Description: As per example 1, except the Z1 hazard (-s5 based on the [[TUFLOW_to_GIS#XMDF_Dataset_Example | XMDF Dataset Example]]) are processed instead of water level (-typeH). 
</ol>

== Converting to Points ==
To output to a points file specify either a shapefiles output with the "-shp" switch or MapInfo output with the "-mif" output. To output at cell corners only:
<ol start="6">
<li>Convert maximums to a shapefile points file at cell corners: 
*<tt>TUFLOW_to_GIS.exe -b -shp -max -typeH M01_5m_001.xmdf</tt> 
*Description: Using batch mode (-b), convert to a shapefile format (-shp), converting the maximums (-max) for the water level results (-typeH). 
 
<li>Convert maximums to a shapefile points file on a regular grid: 
*<tt>TUFLOW_to_GIS.exe -b -shp -max -grid2 -typeH M01_5m_001.xmdf</tt> 
*Description: Using batch mode (-b), convert to a shapefile format (-shp), converting the maximums (-max), on a regular 2m grid (-grid2) for the water level results (-typeH). 
 
<li>Convert velocity at time 2 hours to shapefile points file: 
*<tt>TUFLOW_to_GIS.exe -b -shp -t2 -typeV M01_5m_001.xmdf</tt> 
*Description: Using batch mode (-b), convert to a shapefile format (-shp), at time of 2 hours (-t2), converting the velocity output (-typeV). 
 
<li>Convert the model topography to shapefile points file format: 
*<tt>TUFLOW_to_GIS.exe -b -shp M01_5m_001.2dm</tt> 
*Description: Using batch mode (-b), convert to a shapefile format (-shp), converting the model topography. 
</ol>

== Converting to Arrows ==
To output to vectors file specify either a shapefiles "-shp" or MapInfo "-mif" output type and the "-vector" option. This will create a vector dataset, with the vectors stored as polygon objects. 
The size of the vectors can be controlled with the scale factor ("-sf") switch. 
'''NOTE:''' If using input .dat file the dataset type must be a vector dataset, such as velocity or unit flow. 
<ol start="10">
<li>Convert output time 2 to a shapefile at cell corners: 
*<tt>TUFLOW_to_GIS.exe -b -shp -vector -t2 -typeV M01_5m_001.xmdf</tt> 
*Description: Using batch mode (-b), convert to a shapefile format (-shp), using vector outputs (-vector), and converting at time 2 hours (-t2) for the velocity results (-typeV). 
 
<li>Convert output time 2 to a shapefile at cell corners: 
*<tt>TUFLOW_to_GIS.exe -b -shp -vector -t2 -sf0.5 -typeV M01_5m_001.xmdf</tt> 
*Description: As above with a scale factor of 0.5, so that the arrows will be half the length. 
 
<li>Convert output time 2 to a shapefile on a regular grid of 2m spacing for unit flow: 
*<tt>TUFLOW_to_GIS.exe -b -shp -vector -t2 -sf0.5 -grid2 -typeq M01_5m_001.xmdf</tt> 
*Description: As above on a regular 2 metre grid (-grid2) for the unit flow results (-typeq). 
 
Note: When using processed maxmax xmdf from RES_to_RES utility the -typeV switch needs to be replaced with -v1 switch. -v1 switch calls for the first vector dataset. 
</ol>

== Calibration Points and Longitudinal Profiles ==
These command options are used to extract longitudinal profile information from model results. Input format requirements for the CP and LP files are provided in the calibration point and longitudinal profile commands table within the 'Input Flags' section of this page. 
<ol start="13">
<li>Compute difference between recorded high water mark (in shp or mif format) and modelled maximum flood level: 
*<tt>TUFLOW_to_GIS.exe -cp "CP_File.shp" -typeH -max M03_5m_003.xmdf</tt> 
*<tt>TUFLOW_to_GIS.exe -cp "CP_File.mif" -typeH -max M03_5m_003.xmdf</tt> 

The CP file inputs, flood model result and difference in peak flood level relative to the recorded level is output to a GIS file (eg. '<CP_filename>_<TUFLOW_model_filename>.shp') 
 
[[File: T2G_Longsection_001.PNG|300px]] 
 

<li>Compute longitudinal profiles of maximum flood level model results. Associate recorded high water marks (in shp or mif format) with the profile if the point location is within a defined radius of the longitudinal profile line. 
*<tt>TUFLOW_to_GIS.exe -cp "CP_File.shp" -lp "LP_File.shp" -cpsd100 -lpmd2500 -typeH -max M03_5m_003.xmdf</tt> 
*<tt>TUFLOW_to_GIS.exe -cp "CP_File.mif" -lp "LP_File.mif" -cpsd100 -lpmd2500 -typeH -max M03_5m_003.xmdf</tt> 

The longitude profile results are output to a csv file. The output increment matches the resolution of vertices along the longitudinal profile line. The GIS dataset defines the longitudinal profile chainage at a regular (specified) increment. 
 
[[File: T2G_Longsection_005.PNG|950px]]
[[File: T2G_Longsection_004.PNG|500px]]
 
</ol>
 
{{Tips Navigation
|uplink=[[TUFLOW_Utilities | Back to TUFLOW Utilities]]
}}

Hardware Benchmarking - Results

2024-06-24T10:05:08Z

Angelos Livogiannis: /* GPU Results */

=CPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m Classic and HPC CPU runtimes, with the fastest computers at the top of the table.
 
'''Runtimes for CPU benchmarks'''
{| align="center" class="wikitable"

! style="background-color:#005581; font-weight:bold; color:white;"| Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Processor Frequency (GHz)**
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM size (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM frequency (MHz)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Classic 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | HPC CPU 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Runtime Combined (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||128||5200||32.7||108.6||141.3||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||64||5600||36.7||114.2||150.9||TM1
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||2.0||128||4000||41.2||124.1||165.3||AW1
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs)||3.2||128||4800||38.5||127.0||165.5||SB1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz||4.5||64||4800||33.4||136.0||169.4||PSM
|-
|12th Gen Intel(R) Core(TM) i9-12900K||3.2||128||3200||40.7||129.9||170.6||DD2
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs) @ ~4.2GHz||4.2||32||4800||35.5||162.8||198.3||LC1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs)||2.5||16||3200||48.4||170.5||218.9||TS1
|-
|Intel(R) Xeon(R) w5-2455X (24 CPUs) @ ~3.2GHz||3.2||64||4800||53.3||169.1||222.4||CHR
|-
|Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz||3.7||128||3200||56.9||173.8||230.7||CH1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz)||(5.1)||16||4000||58.2||179.9||238.1||RRB
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||3000||55.7||186.2||241.9||RH1
|-
|AMD Ryzen 9 3900X 12-Core Processor||3.8||64||3200||45.9||203.1||249.0||CH3
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz||3.1||32||2666||61.7||190.0||251.7||CB1
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz||3.6||32||2133||61.4||190.4||251.8||RH2
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||3.6||64||2133||62.7||191.1||253.8||PA1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||32||2933||62.1||192.8||254.9||DS2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||71.2||184.3||255.5||ABA
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||62.1||193.7||255.8||MA2
|-
|AMD Ryzen Threadripper 3970X 32-Core Processor||3.7||256||2400||49.5||212.1||261.6||CH2
|-
|AMD Ryzen 9 3950X 16-Core Processor||3.5||128||2800||55.9||210.0||265.9||TRO
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||2133||67.0||202.5||269.5||RL1
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz||3.5||128||2133||72.7||202.1||274.8||MBL
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||67.5||208.6||276.1||SKI
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||68.5||208.8||277.3||PM2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||66.8||211.6||278.1||MA1
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz||3.2||16||2667||68.2||211.8||280.0||CR2
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||68.0||216.0||284.0||RL3
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||67.7||219.1||286.8||RL2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||70.5||218.8||289.3||PM1
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||2.9||16||2667||77.5||212.6||290.1||KTC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||3.7||32||2933||75.2||219.8||295||BL-DT01001
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor||3.5||128||2666||67.9||230.8||298.7||JGR
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||3.5||128||2666||66.3||234.7||301||JG3
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||32||2400||80.5||221.9||302.4||JM1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz||3.6||16||2400||72.8||230.6||303.4||RSH
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||85.4||218.8||304.2||JPI
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||83.7||225.2||308.9||HNM
|-
|Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz||4.0||32||2400||91.2||223.3||314.5||BRD
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz||3.7||64||2400||84.5||236.6||321.2||DS1
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz||3.2||128||2133||83.4||243.1||326.5||BLK
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||3.7||64||2933||95.4||231.3||326.7||JB2
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz||3.4||128||2400||85.3||247.7||332.9||615
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2400||106.3||226.7||333.0||MRT
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||16||2133||80.7||253.4||334.1||VHD
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz||2.1||64||2666||83.9||251.2||335.1||AR2
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor||3.4||16||2666||81.9||277.3||359.2||CEV
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz||3.0||32||2400||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||64||2133||82.3||289.8||372.1||JIW
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz||3.4||32||1666||108.9||270.0||378.9||AR1
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||3.8||64||3200||87.8||294.2||382||HDR-A2000
|-
|AMD Ryzen 9 5950X 16-Core Processor||3.4||32||3400||39.7||343.0||382.7||JG2
|-
|Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz||2.8||32||1600||119.7||280.8||400.5||SBC
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz||3.3||64||2133||118.2||287.8||406.0||ZDO
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz||2.7||16||2133||90.4||321.7||412.1||EAS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||16||2133||84.8||336.9||421.7||JM2
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2133||100.3||323||423.3||MON
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz||3.4||32||1600||126.4||299.7||426.1||MAV
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz ||3.0||4||986||84.0||351.4||435.4||TJS
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||3.5||16||1333||125.9||320.5||446.4||EFC
|-
|Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz||1.9||16||1800||100.1||347.0||447.1||SM1
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||2.9||16||2900||63.3||385.0||448.3||NCV
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||4.1||16||4104||62.7||386.6||449.3||GZH
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||2.4||128||2394||130.5||331.5||462||VDI
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||2.6||24||1600||100.5||378.6||479.1||CDH
|-
|Intel(R) Xeon(R) CPU E5-1650 0 @ 3.20GHz||3.2||32||1600||143.2||343.1||486.3||MPR
|-
|Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz||3.2||8||1600||142.0||349.4||491.4||CR1
|-
|Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz||3.3||16||N/A||196.8||331.5||528.3||Private Cloud
|-
|Intel(R) Core(TM) i7-4712HQ CPU @ 2.30GHz (Laptop)||2.3||8||1600||145.2||414.4||559.6||MNG
|-
|Intel(R) Xeon(R) CPU X5680 @ 3.33GHz||3.33||72||1333||165.7||400.6||566.3||WTM
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||2.4||8||1600||137.8||795.0||932.8||HMM
|-
|}
 

=GPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m and 10m runtimes with the fastest computers at the top of the table.
 
The HPC GPU benchmark only uses a single GPU card. TUFLOW HPC GPU can be run across multiple NVIDIA GPU devices. However, the benefits of these are typically more noticeable for larger models with more than 1 million cells.
 
'''Runtimes for GPU benchmarks'''
{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 10m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz ||NVIDIA GeForce RTX 4090||24||16384||2.4||11.6||14.0||JW1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4090||24||16384||2.5||12.1||14.6||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz ||NVIDIA GeForce RTX 4090||24||16384||2.7||12.7||15.4||TA1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||2.9||12.7||15.6||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||3.1||13.3||16.4||CR4
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||TM1
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||JM3
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||NVIDIA GeForce RTX 4080||16||9728||3.2||15.0||18.2||AW1
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs)@ ~4.2GHz||NVIDIA GeForce RTX 4080 SUPER||16||10240||3.2||15.7||18.9||LC1
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||NVIDIA RTX 6000 Ada Generation||48||18176||4.9||14.2||19.1||JG3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||3.4||18.5||21.9||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||3.8||19.2||23.0||RS1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||3.7||19.4||23.1||DD2
|-
|12th Gen Intel(R) Core(TM) i7-12700F
|NVIDIA GeForce RTX 3080 Ti
|12
|10240
|3.75
|19.57
|23.32
|AUBNE1PC6602
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||4.0||19.6||23.6||GP1
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA A40||48||10752||3.5||20.3||23.8||Lenovo SR650 V2
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.1||20.1||24.2||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.4||20.4||24.8||CH3
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||4.6||23.5||28.1||KW2
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs) ||NVIDIA RTX A5000||24||8192||4.4||24.1||28.5||SB1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 3080||10||8704||4.7||24.0||28.7||CPM
|-
|Intel(R) Xeon(R) W-2223 CPU @ 3.60GHz ||NVIDIA GeForce RTX 3090||24||10496||5.3||24.3||29.6||SSM2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||4.7||25.7||30.4||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||5.7||25.2||30.9||JGR
|-
|AMD Ryzen Threadripper 2920X 12-Core Processor (24 CPUs) @ 3.5GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.1||25.9||31||CR5
|-
|AMD Ryzen 9 3950X 16-Core Processor ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.3||26.4||31.7||TRO
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||27.4||32.8||PY2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||27.7||33.4||VLD
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||NVIDIA GeForce RTX 3070||8||5888||5.0||28.8||33.8||NCV
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.5||28.4||33.9||RL1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||5.5||28.7||34.2||RRB
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.8||28.8||34.6||MA1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||29.2||34.9||MA2
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||5.5||29.7||35.2||JG2
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.6||29.9||35.5||MBL
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||6.4||29.5||35.9||JPI
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P100||16||3584||6.1||30.8||36.9||Google Cloud: Tesla P100
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||5.7||31.9||37.6||RH2
|-
|Intel(R) Xeon(R) Gold 6230R CPU @ 2.10GHz ||NVIDIA GRID RTX8000P-48Q||48||4608||6.8||31.0||37.8||VJ1
|-
|Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 CPUs) ||NVIDIA RTX A4000||16||6144||5.8||32.0||37.8||JS2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080||8||2944||6.0||31.9||37.9||ANK
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||6.0||32.0||38.0||EFC
|-
|AMD EPYC 74F3 24-Core Processor (36 CPUs) @ 3.2GHz ||NVIDIA A10-24Q||24||8192||7.2||31.4||38.6||CS1
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||33.3||38.7||PA1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce RTX 3060 Ti (LHR) ||8||4864||5.7||33.3||39.0||DF1
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||NVIDIA GeForce RTX 2060 SUPER (core 1647MHz, mem 1750MHz)||8||2176||5.6||33.4||39.1||GZH
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||5.6||34.3||40.7||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||6.9||34.6||41.6||FLC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||35.1||41.6||JB2
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.4||35.8||42.2||JS1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080||8||2944||6.5||36.0||42.5||ABA
|-
|Intel(R) Xeon(R) w5-2455X (24 CPUs) @ ~3.2GHz ||NVIDIA RTX A4000||16||6144||7.2||35.3||42.5||CHR
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.1||37.1||43.2||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||37.4||43.8||PM1
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA GeForce GTX 2070||8||2304||7.4||38.8||46.2||MMR
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz ||NVIDIA Quadro RTX 4000||8||2304||6.6||39.8||46.4||CB1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.8||39.1||46.9||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||8.0||39.3||47.3||RCD
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.6||41.1||48.7||HNM
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||NVIDIA GRID RTX6000P-4Q||24||4608||10.5||39.3||49.8||VDI
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (Laptop) ||NVIDIA GeForce RTX 2070||8||2304||7.7||42.8||50.5||ERX
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA Tesla T4||16||2560||6.8||45.2||52.0||RJ1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz
|NVIDIA GeForce RTX 3060
|8
|3584
|7.68
|45.92
|53.6
|AUBNEW1DQ54G3
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||8.0||47.4||55.3||BLK
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla T4||16||2560||7.3||48.3||55.6||FM-NODE: Tesla T4
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz ||NVIDIA GeForce GTX 1080||8||2560||8.5||48.9||57.3||JM1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||8.2||51.9||60.0||SKI
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz ||NVIDIA Quadro P5000||16||2560||9.6||51.8||61.4||AR2
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||NVIDIA RTX A2000||6||3328||9.1||54.4||63.5||HDR-A2000
|-
|Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz ||NVIDIA GeForce GTX 1070||8||1920||8.9||54.9||63.8||PY1
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz ||NVIDIA GeForce GTX 1070||8||1920||10.3||59.3||69.5||DS1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA Quadro P4000||8||1792||10.0||62.3||72.3||DS2
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce GTX 1650 SUPER||4||1280||10.3||64.6||74.9||TS1
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P4||8||2560||10.4||69.0||79.4||Google Cloud: Tesla P4
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz ||NVIDIA GeForce GTX 980||4||2048||11.8||70.6||82.3||ZDO
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz ||NVIDIA GeForce GTX TITAN Black||6||2880||13.1||76.1||89.2||AR1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz ||NVIDIA GeForce GTX 1060||6||1280||13.0||77.1||90.1||RSH
|-
|Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz (64 CPUs), ~2.3GHz||NVIDIA Tesla M60||16||4096||12||82.7||94.7||SM2
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla K80||12||2496||11.3||83.5||94.8||Google Cloud: Tesla K80
|-
|Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz ||NVIDIA Tesla K40c||12||2880||12.3||83.1||95.3||NWE
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA Quadro T2000||4||1024||13.3||85.2||95.5||SSM
|-
|Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (Laptop) ||NVIDIA GeForce GTX 980||4||2048||17.5||84.2||101.7||MRT
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||NVIDIA Quadro P2000||5||1024||14.2||96||110.2||BL-DT01001
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz ||NVIDIA Quadro P2000||5||1024||15.8||100.1||115.9||CR2
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz ||NVIDIA GeForce GTX 690||2||3072||18.4||114.4||132.8||MAV
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor ||NVIDIA GeForce GTX 960||4||1024||18.6||123.3||141.6||CEV
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA GeForce GTX 960||4||1024||19.9||127.2||147.1||VHD
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz||NVIDIA GeForce GTX 1050 Ti||4||768||21.1||133.8||154.9||MJS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||NVIDIA GeForce GTX 1050||2||640||20.6||139.1||159.7||JM2
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||NVIDIA Quadro P2000||5||1024||22.1||142.5||164.6||KTC
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||NVIDIA Quadro P2000||5||1024||23.0||149.3||172.3||RL2
|-
|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz||NVIDIA Quadro M2200||4||1024||23.2||198.7||222.0||GYB
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz||NVIDIA T500||4||986||29.3||197.5||226.8||TJS
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz ||NVIDIA Quadro P1000||4||640||30.3||203.7||234.0||RL3
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA Quadro K2200||4||640||32.5||211.3||243.8||JIW
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz ||NVIDIA Quadro M1200||4||640||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz ||NVIDIA GeForce GTX 940MX||2||384||65.6||479.0||544.6||EAS
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||NVIDIA GeForce 840M||2||384||70.6||526.3||595.9||CDH
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||NVIDIA GeForce GT 740M||2||384||102.3||694.0||796.3||HMM
|-
|}
 

=High End GPU Results=
A number of additional benchmarking tests have been completed on a 5m and 2.5m model on a single GPU card.

{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 2.5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||NVIDIA GeForce RTX 4090||24||16384||103.3||811.2||914.5||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz||NVIDIA GeForce RTX 4090||24||16384||105.9||813.7||919.6||TA1
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz||NVIDIA GeForce RTX 4090||24||16384||103.7||824.3||928.0||JW1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||108.2||821.5||929.7||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||106.8||875.5||982.3||CR4
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz ||NVIDIA RTX 6000 Ada Generation||48||18176||119.6||877.8||997.4||JG3
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||139.5||1115.1||1254.6||JM3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||155.2||1172.9||1328.1||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||155.5||1176.2||1331.7||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||158||1192.2||1350.2||CH3
|-
|Intel(R) Core(TM) i9-10900F CPU @ 3.70GHz ||NVIDIA GeForce RTX 3090||24||10496||162.3||1192.4||1354.7||LJA
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||159.7||1216.2||1375.9||GP1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||160.9||1240||1400.9||DD2
|-
|Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz ||NVIDIA GeForce RTX 3090||24||10496||172.9||1249.8||1422.7||SIP
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||178.9||1363.9||1542.8||KW2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||203.8||1523.9||1727.7||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||201.2||1548.1||1749.3||JGR
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||220.0||1634.5||1854.5||MA1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||222.2||1648.7||1870.9||JPI
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||215.9||1678.7||1894.6||PA2
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||241.2||1863.5||2104.7||RRB
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||248.7||1928.6||2177.3||JG2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||257.3||1957.7||2215.0||RH2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||275.1||2147.4||2422.5||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||296.0||2218.4||2514.4||FLC
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||298.9||2290.1||2589.0||JS1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.3||2345.1||2656.4||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||310.3||2377.2||2687.5||RCD
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||308.7||2384.7||2693.4||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.9||2404.9||2716.7||PM1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||324.8||2475.3||2800.1||HNM
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||439.0||3379.3||3818.2||BLK
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||475.5||3788.2||4263.7||SKI
|-
|}
<pre> * it is noted that the number of CUDA cores is not provided as an output from the '''dxdiag''' command and this information has been sourced from the nvidia website.
** The output cpu.txt only provides the 'out of the box' processor speed. If you have overclocked your cpu and/or gpu, please send these details to TUFLOW Support so we can add the overclocked data in brackets. </pre>

{{Tips Navigation
|uplink=[[Hardware_Benchmarking_(2018-03-AA) | Back to TUFLOW Benchmarking]]
}}

Hardware Benchmarking - Results

2024-05-24T16:29:05Z

Angelos Livogiannis:

=CPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m Classic and HPC CPU runtimes, with the fastest computers at the top of the table.
 
'''Runtimes for CPU benchmarks'''
{| align="center" class="wikitable"

! style="background-color:#005581; font-weight:bold; color:white;"| Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Processor Frequency (GHz)**
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM size (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM frequency (MHz)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Classic 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | HPC CPU 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Runtime Combined (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||128||5200||32.7||108.6||141.3||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||64||5600||36.7||114.2||150.9||TM1
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||2.0||128||4000||41.2||124.1||165.3||AW1
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs)||3.2||128||4800||38.5||127.0||165.5||SB1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz||4.5||64||4800||33.4||136.0||169.4||PSM
|-
|12th Gen Intel(R) Core(TM) i9-12900K||3.2||128||3200||40.7||129.9||170.6||DD2
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs) @ ~4.2GHz||4.2||32||4800||35.5||162.8||198.3||LC1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs)||2.5||16||3200||48.4||170.5||218.9||TS1
|-
|Intel(R) Xeon(R) w5-2455X (24 CPUs) @ ~3.2GHz||3.2||64||4800||53.3||169.1||222.4||CHR
|-
|Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz||3.7||128||3200||56.9||173.8||230.7||CH1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz)||(5.1)||16||4000||58.2||179.9||238.1||RRB
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||3000||55.7||186.2||241.9||RH1
|-
|AMD Ryzen 9 3900X 12-Core Processor||3.8||64||3200||45.9||203.1||249.0||CH3
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz||3.1||32||2666||61.7||190.0||251.7||CB1
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz||3.6||32||2133||61.4||190.4||251.8||RH2
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||3.6||64||2133||62.7||191.1||253.8||PA1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||32||2933||62.1||192.8||254.9||DS2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||71.2||184.3||255.5||ABA
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||62.1||193.7||255.8||MA2
|-
|AMD Ryzen Threadripper 3970X 32-Core Processor||3.7||256||2400||49.5||212.1||261.6||CH2
|-
|AMD Ryzen 9 3950X 16-Core Processor||3.5||128||2800||55.9||210.0||265.9||TRO
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||2133||67.0||202.5||269.5||RL1
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz||3.5||128||2133||72.7||202.1||274.8||MBL
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||67.5||208.6||276.1||SKI
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||68.5||208.8||277.3||PM2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||66.8||211.6||278.1||MA1
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz||3.2||16||2667||68.2||211.8||280.0||CR2
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||68.0||216.0||284.0||RL3
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||67.7||219.1||286.8||RL2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||70.5||218.8||289.3||PM1
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||2.9||16||2667||77.5||212.6||290.1||KTC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||3.7||32||2933||75.2||219.8||295||BL-DT01001
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor||3.5||128||2666||67.9||230.8||298.7||JGR
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||3.5||128||2666||66.3||234.7||301||JG3
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||32||2400||80.5||221.9||302.4||JM1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz||3.6||16||2400||72.8||230.6||303.4||RSH
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||85.4||218.8||304.2||JPI
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||83.7||225.2||308.9||HNM
|-
|Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz||4.0||32||2400||91.2||223.3||314.5||BRD
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz||3.7||64||2400||84.5||236.6||321.2||DS1
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz||3.2||128||2133||83.4||243.1||326.5||BLK
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||3.7||64||2933||95.4||231.3||326.7||JB2
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz||3.4||128||2400||85.3||247.7||332.9||615
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2400||106.3||226.7||333.0||MRT
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||16||2133||80.7||253.4||334.1||VHD
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz||2.1||64||2666||83.9||251.2||335.1||AR2
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor||3.4||16||2666||81.9||277.3||359.2||CEV
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz||3.0||32||2400||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||64||2133||82.3||289.8||372.1||JIW
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz||3.4||32||1666||108.9||270.0||378.9||AR1
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||3.8||64||3200||87.8||294.2||382||HDR-A2000
|-
|AMD Ryzen 9 5950X 16-Core Processor||3.4||32||3400||39.7||343.0||382.7||JG2
|-
|Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz||2.8||32||1600||119.7||280.8||400.5||SBC
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz||3.3||64||2133||118.2||287.8||406.0||ZDO
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz||2.7||16||2133||90.4||321.7||412.1||EAS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||16||2133||84.8||336.9||421.7||JM2
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2133||100.3||323||423.3||MON
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz||3.4||32||1600||126.4||299.7||426.1||MAV
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz ||3.0||4||986||84.0||351.4||435.4||TJS
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||3.5||16||1333||125.9||320.5||446.4||EFC
|-
|Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz||1.9||16||1800||100.1||347.0||447.1||SM1
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||2.9||16||2900||63.3||385.0||448.3||NCV
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||4.1||16||4104||62.7||386.6||449.3||GZH
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||2.4||128||2394||130.5||331.5||462||VDI
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||2.6||24||1600||100.5||378.6||479.1||CDH
|-
|Intel(R) Xeon(R) CPU E5-1650 0 @ 3.20GHz||3.2||32||1600||143.2||343.1||486.3||MPR
|-
|Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz||3.2||8||1600||142.0||349.4||491.4||CR1
|-
|Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz||3.3||16||N/A||196.8||331.5||528.3||Private Cloud
|-
|Intel(R) Core(TM) i7-4712HQ CPU @ 2.30GHz (Laptop)||2.3||8||1600||145.2||414.4||559.6||MNG
|-
|Intel(R) Xeon(R) CPU X5680 @ 3.33GHz||3.33||72||1333||165.7||400.6||566.3||WTM
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||2.4||8||1600||137.8||795.0||932.8||HMM
|-
|}
 

=GPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m and 10m runtimes with the fastest computers at the top of the table.
 
The HPC GPU benchmark only uses a single GPU card. TUFLOW HPC GPU can be run across multiple NVIDIA GPU devices. However, the benefits of these are typically more noticeable for larger models with more than 1 million cells.
 
'''Runtimes for GPU benchmarks'''
{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 10m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz ||NVIDIA GeForce RTX 4090||24||16384||2.4||11.6||14.0||JW1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4090||24||16384||2.5||12.1||14.6||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz ||NVIDIA GeForce RTX 4090||24||16384||2.7||12.7||15.4||TA1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||2.9||12.7||15.6||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||3.1||13.3||16.4||CR4
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||TM1
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||JM3
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||NVIDIA GeForce RTX 4080||16||9728||3.2||15.0||18.2||AW1
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs)@ ~4.2GHz||NVIDIA GeForce RTX 4080 SUPER||16||10240||3.2||15.7||18.9||LC1
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||NVIDIA RTX 6000 Ada Generation||48||18176||4.9||14.2||19.1||JG3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||3.4||18.5||21.9||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||3.8||19.2||23.0||RS1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||3.7||19.4||23.1||DD2
|-
|12th Gen Intel(R) Core(TM) i7-12700F
|NVIDIA GeForce RTX 3080 Ti
|12
|10240
|3.75
|19.57
|23.32
|AUBNE1PC6602
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||4.0||19.6||23.6||GP1
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA A40||48||10752||3.5||20.3||23.8||Lenovo SR650 V2
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.1||20.1||24.2||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.4||20.4||24.8||CH3
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||4.6||23.5||28.1||KW2
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs) ||NVIDIA RTX A5000||24||8192||4.4||24.1||28.5||SB1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 3080||10||8704||4.7||24.0||28.7||CPM
|-
|Intel(R) Xeon(R) W-2223 CPU @ 3.60GHz ||NVIDIA GeForce RTX 3090||24||10496||5.3||24.3||29.6||SSM2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||4.7||25.7||30.4||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||5.7||25.2||30.9||JGR
|-
|AMD Ryzen Threadripper 2920X 12-Core Processor (24 CPUs) @ 3.5GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.1||25.9||31||CR5
|-
|AMD Ryzen 9 3950X 16-Core Processor ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.3||26.4||31.7||TRO
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||27.4||32.8||PY2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||27.7||33.4||VLD
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||NVIDIA GeForce RTX 3070||8||5888||5.0||28.8||33.8||NCV
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.5||28.4||33.9||RL1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||5.5||28.7||34.2||RRB
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.8||28.8||34.6||MA1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||29.2||34.9||MA2
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||5.5||29.7||35.2||JG2
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.6||29.9||35.5||MBL
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||6.4||29.5||35.9||JPI
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P100||16||3584||6.1||30.8||36.9||Google Cloud: Tesla P100
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||5.7||31.9||37.6||RH2
|-
|Intel(R) Xeon(R) Gold 6230R CPU @ 2.10GHz ||NVIDIA GRID RTX8000P-48Q||48||4608||6.8||31.0||37.8||VJ1
|-
|Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 CPUs) ||NVIDIA RTX A4000||16||6144||5.8||32.0||37.8||JS2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080||8||2944||6.0||31.9||37.9||ANK
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||6.0||32.0||38.0||EFC
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||33.3||38.7||PA1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce RTX 3060 Ti (LHR) ||8||4864||5.7||33.3||39.0||DF1
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||NVIDIA GeForce RTX 2060 SUPER (core 1647MHz, mem 1750MHz)||8||2176||5.6||33.4||39.1||GZH
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||5.6||34.3||40.7||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||6.9||34.6||41.6||FLC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||35.1||41.6||JB2
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.4||35.8||42.2||JS1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080||8||2944||6.5||36.0||42.5||ABA
|-
|Intel(R) Xeon(R) w5-2455X (24 CPUs) @ ~3.2GHz ||NVIDIA RTX A4000||16||6144||7.2||35.3||42.5||CHR
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.1||37.1||43.2||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||37.4||43.8||PM1
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA GeForce GTX 2070||8||2304||7.4||38.8||46.2||MMR
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz ||NVIDIA Quadro RTX 4000||8||2304||6.6||39.8||46.4||CB1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.8||39.1||46.9||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||8.0||39.3||47.3||RCD
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.6||41.1||48.7||HNM
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||NVIDIA GRID RTX6000P-4Q||24||4608||10.5||39.3||49.8||VDI
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (Laptop) ||NVIDIA GeForce RTX 2070||8||2304||7.7||42.8||50.5||ERX
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA Tesla T4||16||2560||6.8||45.2||52.0||RJ1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz
|NVIDIA GeForce RTX 3060
|8
|3584
|7.68
|45.92
|53.6
|AUBNEW1DQ54G3
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||8.0||47.4||55.3||BLK
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla T4||16||2560||7.3||48.3||55.6||FM-NODE: Tesla T4
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz ||NVIDIA GeForce GTX 1080||8||2560||8.5||48.9||57.3||JM1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||8.2||51.9||60.0||SKI
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz ||NVIDIA Quadro P5000||16||2560||9.6||51.8||61.4||AR2
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||NVIDIA RTX A2000||6||3328||9.1||54.4||63.5||HDR-A2000
|-
|Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz ||NVIDIA GeForce GTX 1070||8||1920||8.9||54.9||63.8||PY1
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz ||NVIDIA GeForce GTX 1070||8||1920||10.3||59.3||69.5||DS1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA Quadro P4000||8||1792||10.0||62.3||72.3||DS2
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce GTX 1650 SUPER||4||1280||10.3||64.6||74.9||TS1
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P4||8||2560||10.4||69.0||79.4||Google Cloud: Tesla P4
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz ||NVIDIA GeForce GTX 980||4||2048||11.8||70.6||82.3||ZDO
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz ||NVIDIA GeForce GTX TITAN Black||6||2880||13.1||76.1||89.2||AR1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz ||NVIDIA GeForce GTX 1060||6||1280||13.0||77.1||90.1||RSH
|-
|Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz (64 CPUs), ~2.3GHz||NVIDIA Tesla M60||16||4096||12||82.7||94.7||SM2
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla K80||12||2496||11.3||83.5||94.8||Google Cloud: Tesla K80
|-
|Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz ||NVIDIA Tesla K40c||12||2880||12.3||83.1||95.3||NWE
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA Quadro T2000||4||1024||13.3||85.2||95.5||SSM
|-
|Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (Laptop) ||NVIDIA GeForce GTX 980||4||2048||17.5||84.2||101.7||MRT
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||NVIDIA Quadro P2000||5||1024||14.2||96||110.2||BL-DT01001
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz ||NVIDIA Quadro P2000||5||1024||15.8||100.1||115.9||CR2
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz ||NVIDIA GeForce GTX 690||2||3072||18.4||114.4||132.8||MAV
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor ||NVIDIA GeForce GTX 960||4||1024||18.6||123.3||141.6||CEV
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA GeForce GTX 960||4||1024||19.9||127.2||147.1||VHD
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz||NVIDIA GeForce GTX 1050 Ti||4||768||21.1||133.8||154.9||MJS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||NVIDIA GeForce GTX 1050||2||640||20.6||139.1||159.7||JM2
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||NVIDIA Quadro P2000||5||1024||22.1||142.5||164.6||KTC
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||NVIDIA Quadro P2000||5||1024||23.0||149.3||172.3||RL2
|-
|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz||NVIDIA Quadro M2200||4||1024||23.2||198.7||222.0||GYB
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz||NVIDIA T500||4||986||29.3||197.5||226.8||TJS
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz ||NVIDIA Quadro P1000||4||640||30.3||203.7||234.0||RL3
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA Quadro K2200||4||640||32.5||211.3||243.8||JIW
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz ||NVIDIA Quadro M1200||4||640||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz ||NVIDIA GeForce GTX 940MX||2||384||65.6||479.0||544.6||EAS
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||NVIDIA GeForce 840M||2||384||70.6||526.3||595.9||CDH
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||NVIDIA GeForce GT 740M||2||384||102.3||694.0||796.3||HMM
|-
|}
 

=High End GPU Results=
A number of additional benchmarking tests have been completed on a 5m and 2.5m model on a single GPU card.

{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 2.5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||NVIDIA GeForce RTX 4090||24||16384||103.3||811.2||914.5||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz||NVIDIA GeForce RTX 4090||24||16384||105.9||813.7||919.6||TA1
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz||NVIDIA GeForce RTX 4090||24||16384||103.7||824.3||928.0||JW1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||108.2||821.5||929.7||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||106.8||875.5||982.3||CR4
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz ||NVIDIA RTX 6000 Ada Generation||48||18176||119.6||877.8||997.4||JG3
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||139.5||1115.1||1254.6||JM3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||155.2||1172.9||1328.1||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||155.5||1176.2||1331.7||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||158||1192.2||1350.2||CH3
|-
|Intel(R) Core(TM) i9-10900F CPU @ 3.70GHz ||NVIDIA GeForce RTX 3090||24||10496||162.3||1192.4||1354.7||LJA
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||159.7||1216.2||1375.9||GP1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||160.9||1240||1400.9||DD2
|-
|Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz ||NVIDIA GeForce RTX 3090||24||10496||172.9||1249.8||1422.7||SIP
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||178.9||1363.9||1542.8||KW2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||203.8||1523.9||1727.7||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||201.2||1548.1||1749.3||JGR
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||220.0||1634.5||1854.5||MA1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||222.2||1648.7||1870.9||JPI
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||215.9||1678.7||1894.6||PA2
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||241.2||1863.5||2104.7||RRB
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||248.7||1928.6||2177.3||JG2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||257.3||1957.7||2215.0||RH2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||275.1||2147.4||2422.5||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||296.0||2218.4||2514.4||FLC
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||298.9||2290.1||2589.0||JS1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.3||2345.1||2656.4||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||310.3||2377.2||2687.5||RCD
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||308.7||2384.7||2693.4||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.9||2404.9||2716.7||PM1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||324.8||2475.3||2800.1||HNM
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||439.0||3379.3||3818.2||BLK
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||475.5||3788.2||4263.7||SKI
|-
|}
<pre> * it is noted that the number of CUDA cores is not provided as an output from the '''dxdiag''' command and this information has been sourced from the nvidia website.
** The output cpu.txt only provides the 'out of the box' processor speed. If you have overclocked your cpu and/or gpu, please send these details to TUFLOW Support so we can add the overclocked data in brackets. </pre>

{{Tips Navigation
|uplink=[[Hardware_Benchmarking_(2018-03-AA) | Back to TUFLOW Benchmarking]]
}}

Hardware Benchmarking - Results

2024-05-24T16:00:13Z

Angelos Livogiannis:

=CPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m Classic and HPC CPU runtimes, with the fastest computers at the top of the table.
 
'''Runtimes for CPU benchmarks'''
{| align="center" class="wikitable"

! style="background-color:#005581; font-weight:bold; color:white;"| Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Processor Frequency (GHz)**
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM size (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM frequency (MHz)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Classic 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | HPC CPU 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Runtime Combined (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||128||5200||32.7||108.6||141.3||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||64||5600||36.7||114.2||150.9||TM1
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||2.0||128||4000||41.2||124.1||165.3||AW1
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs)||3.2||128||4800||38.5||127.0||165.5||SB1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz||4.5||64||4800||33.4||136.0||169.4||PSM
|-
|12th Gen Intel(R) Core(TM) i9-12900K||3.2||128||3200||40.7||129.9||170.6||DD2
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs) @ ~4.2GHz||4.2||32||4800||35.5||162.8||198.3||LC1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs)||2.5||16||3200||48.4||170.5||218.9||TS1
|-
|Intel(R) Xeon(R) w5-2455X (24 CPUs) @ ~3.2GHz||3.2||64||4800||53.3||169.1||222.4||CHR
|-
|Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz||3.7||128||3200||56.9||173.8||230.7||CH1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz)||(5.1)||16||4000||58.2||179.9||238.1||RRB
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||3000||55.7||186.2||241.9||RH1
|-
|AMD Ryzen 9 3900X 12-Core Processor||3.8||64||3200||45.9||203.1||249.0||CH3
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz||3.1||32||2666||61.7||190.0||251.7||CB1
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz||3.6||32||2133||61.4||190.4||251.8||RH2
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||3.6||64||2133||62.7||191.1||253.8||PA1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||32||2933||62.1||192.8||254.9||DS2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||71.2||184.3||255.5||ABA
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||62.1||193.7||255.8||MA2
|-
|AMD Ryzen Threadripper 3970X 32-Core Processor||3.7||256||2400||49.5||212.1||261.6||CH2
|-
|AMD Ryzen 9 3950X 16-Core Processor||3.5||128||2800||55.9||210.0||265.9||TRO
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||2133||67.0||202.5||269.5||RL1
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz||3.5||128||2133||72.7||202.1||274.8||MBL
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||67.5||208.6||276.1||SKI
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||68.5||208.8||277.3||PM2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||66.8||211.6||278.1||MA1
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz||3.2||16||2667||68.2||211.8||280.0||CR2
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||68.0||216.0||284.0||RL3
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||67.7||219.1||286.8||RL2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||70.5||218.8||289.3||PM1
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||2.9||16||2667||77.5||212.6||290.1||KTC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||3.7||32||2933||75.2||219.8||295||BL-DT01001
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor||3.5||128||2666||67.9||230.8||298.7||JGR
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||3.5||128||2666||66.3||234.7||301||JG3
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||32||2400||80.5||221.9||302.4||JM1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz||3.6||16||2400||72.8||230.6||303.4||RSH
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||85.4||218.8||304.2||JPI
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||83.7||225.2||308.9||HNM
|-
|Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz||4.0||32||2400||91.2||223.3||314.5||BRD
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz||3.7||64||2400||84.5||236.6||321.2||DS1
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz||3.2||128||2133||83.4||243.1||326.5||BLK
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||3.7||64||2933||95.4||231.3||326.7||JB2
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz||3.4||128||2400||85.3||247.7||332.9||615
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2400||106.3||226.7||333.0||MRT
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||16||2133||80.7||253.4||334.1||VHD
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz||2.1||64||2666||83.9||251.2||335.1||AR2
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor||3.4||16||2666||81.9||277.3||359.2||CEV
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz||3.0||32||2400||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||64||2133||82.3||289.8||372.1||JIW
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz||3.4||32||1666||108.9||270.0||378.9||AR1
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||3.8||64||3200||87.8||294.2||382||HDR-A2000
|-
|AMD Ryzen 9 5950X 16-Core Processor||3.4||32||3400||39.7||343.0||382.7||JG2
|-
|Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz||2.8||32||1600||119.7||280.8||400.5||SBC
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz||3.3||64||2133||118.2||287.8||406.0||ZDO
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz||2.7||16||2133||90.4||321.7||412.1||EAS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||16||2133||84.8||336.9||421.7||JM2
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2133||100.3||323||423.3||MON
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz||3.4||32||1600||126.4||299.7||426.1||MAV
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz ||3.0||4||986||84.0||351.4||435.4||TJS
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||3.5||16||1333||125.9||320.5||446.4||EFC
|-
|Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz||1.9||16||1800||100.1||347.0||447.1||SM1
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||2.9||16||2900||63.3||385.0||448.3||NCV
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||4.1||16||4104||62.7||386.6||449.3||GZH
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||2.4||128||2394||130.5||331.5||462||VDI
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||2.6||24||1600||100.5||378.6||479.1||CDH
|-
|Intel(R) Xeon(R) CPU E5-1650 0 @ 3.20GHz||3.2||32||1600||143.2||343.1||486.3||MPR
|-
|Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz||3.2||8||1600||142.0||349.4||491.4||CR1
|-
|Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz||3.3||16||N/A||196.8||331.5||528.3||Private Cloud
|-
|Intel(R) Core(TM) i7-4712HQ CPU @ 2.30GHz (Laptop)||2.3||8||1600||145.2||414.4||559.6||MNG
|-
|Intel(R) Xeon(R) CPU X5680 @ 3.33GHz||3.33||72||1333||165.7||400.6||566.3||WTM
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||2.4||8||1600||137.8||795.0||932.8||HMM
|-
|}
 

=GPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m and 10m runtimes with the fastest computers at the top of the table.
 
The HPC GPU benchmark only uses a single GPU card. TUFLOW HPC GPU can be run across multiple NVIDIA GPU devices. However, the benefits of these are typically more noticeable for larger models with more than 1 million cells.
 
'''Runtimes for GPU benchmarks'''
{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 10m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz ||NVIDIA GeForce RTX 4090||24||16384||2.4||11.6||14.0||JW1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4090||24||16384||2.5||12.1||14.6||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz ||NVIDIA GeForce RTX 4090||24||16384||2.7||12.7||15.4||TA1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||2.9||12.7||15.6||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||3.1||13.3||16.4||CR4
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||TM1
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||JM3
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||NVIDIA GeForce RTX 4080||16||9728||3.2||15.0||18.2||AW1
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs)@ ~4.2GHz||NVIDIA GeForce RTX 4080 SUPER||16||10240||3.2||15.7||18.9||LC1
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||NVIDIA RTX 6000 Ada Generation||48||18176||4.9||14.2||19.1||JG3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||3.4||18.5||21.9||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||3.8||19.2||23.0||RS1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||3.7||19.4||23.1||DD2
|-
|12th Gen Intel(R) Core(TM) i7-12700F
|NVIDIA GeForce RTX 3080 Ti
|12
|10240
|3.75
|19.57
|23.32
|AUBNE1PC6602
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||4.0||19.6||23.6||GP1
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA A40||48||10752||3.5||20.3||23.8||Lenovo SR650 V2
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.1||20.1||24.2||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.4||20.4||24.8||CH3
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||4.6||23.5||28.1||KW2
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs) ||NVIDIA RTX A5000||24||8192||4.4||24.1||28.5||SB1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 3080||10||8704||4.7||24.0||28.7||CPM
|-
|Intel(R) Xeon(R) W-2223 CPU @ 3.60GHz ||NVIDIA GeForce RTX 3090||24||10496||5.3||24.3||29.6||SSM2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||4.7||25.7||30.4||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||5.7||25.2||30.9||JGR
|-
|AMD Ryzen Threadripper 2920X 12-Core Processor (24 CPUs) @ 3.5GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.1||25.9||31||CR5
|-
|AMD Ryzen 9 3950X 16-Core Processor ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.3||26.4||31.7||TRO
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||27.4||32.8||PY2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||27.7||33.4||VLD
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||NVIDIA GeForce RTX 3070||8||5888||5.0||28.8||33.8||NCV
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.5||28.4||33.9||RL1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||5.5||28.7||34.2||RRB
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.8||28.8||34.6||MA1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||29.2||34.9||MA2
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||5.5||29.7||35.2||JG2
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.6||29.9||35.5||MBL
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||6.4||29.5||35.9||JPI
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P100||16||3584||6.1||30.8||36.9||Google Cloud: Tesla P100
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||5.7||31.9||37.6||RH2
|-
|Intel(R) Xeon(R) Gold 6230R CPU @ 2.10GHz ||NVIDIA GRID RTX8000P-48Q||48||4608||6.8||31.0||37.8||VJ1
|-
|Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 CPUs) ||NVIDIA RTX A4000||16||6144||5.8||32.0||37.8||JS2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080||8||2944||6.0||31.9||37.9||ANK
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||6.0||32.0||38.0||EFC
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||33.3||38.7||PA1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce RTX 3060 Ti (LHR) ||8||4864||5.7||33.3||39.0||DF1
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||NVIDIA GeForce RTX 2060 SUPER (core 1647MHz, mem 1750MHz)||8||2176||5.6||33.4||39.1||GZH
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||5.6||34.3||40.7||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||6.9||34.6||41.6||FLC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||35.1||41.6||JB2
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.4||35.8||42.2||JS1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080||8||2944||6.5||36.0||42.5||ABA
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA RTX A4000||16||6144||7.2||35.3||42.5||CHR
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.1||37.1||43.2||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||37.4||43.8||PM1
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA GeForce GTX 2070||8||2304||7.4||38.8||46.2||MMR
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz ||NVIDIA Quadro RTX 4000||8||2304||6.6||39.8||46.4||CB1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.8||39.1||46.9||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||8.0||39.3||47.3||RCD
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.6||41.1||48.7||HNM
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||NVIDIA GRID RTX6000P-4Q||24||4608||10.5||39.3||49.8||VDI
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (Laptop) ||NVIDIA GeForce RTX 2070||8||2304||7.7||42.8||50.5||ERX
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA Tesla T4||16||2560||6.8||45.2||52.0||RJ1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz
|NVIDIA GeForce RTX 3060
|8
|3584
|7.68
|45.92
|53.6
|AUBNEW1DQ54G3
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||8.0||47.4||55.3||BLK
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla T4||16||2560||7.3||48.3||55.6||FM-NODE: Tesla T4
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz ||NVIDIA GeForce GTX 1080||8||2560||8.5||48.9||57.3||JM1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||8.2||51.9||60.0||SKI
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz ||NVIDIA Quadro P5000||16||2560||9.6||51.8||61.4||AR2
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||NVIDIA RTX A2000||6||3328||9.1||54.4||63.5||HDR-A2000
|-
|Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz ||NVIDIA GeForce GTX 1070||8||1920||8.9||54.9||63.8||PY1
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz ||NVIDIA GeForce GTX 1070||8||1920||10.3||59.3||69.5||DS1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA Quadro P4000||8||1792||10.0||62.3||72.3||DS2
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce GTX 1650 SUPER||4||1280||10.3||64.6||74.9||TS1
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P4||8||2560||10.4||69.0||79.4||Google Cloud: Tesla P4
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz ||NVIDIA GeForce GTX 980||4||2048||11.8||70.6||82.3||ZDO
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz ||NVIDIA GeForce GTX TITAN Black||6||2880||13.1||76.1||89.2||AR1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz ||NVIDIA GeForce GTX 1060||6||1280||13.0||77.1||90.1||RSH
|-
|Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz (64 CPUs), ~2.3GHz||NVIDIA Tesla M60||16||4096||12||82.7||94.7||SM2
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla K80||12||2496||11.3||83.5||94.8||Google Cloud: Tesla K80
|-
|Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz ||NVIDIA Tesla K40c||12||2880||12.3||83.1||95.3||NWE
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA Quadro T2000||4||1024||13.3||85.2||95.5||SSM
|-
|Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (Laptop) ||NVIDIA GeForce GTX 980||4||2048||17.5||84.2||101.7||MRT
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||NVIDIA Quadro P2000||5||1024||14.2||96||110.2||BL-DT01001
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz ||NVIDIA Quadro P2000||5||1024||15.8||100.1||115.9||CR2
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz ||NVIDIA GeForce GTX 690||2||3072||18.4||114.4||132.8||MAV
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor ||NVIDIA GeForce GTX 960||4||1024||18.6||123.3||141.6||CEV
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA GeForce GTX 960||4||1024||19.9||127.2||147.1||VHD
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz||NVIDIA GeForce GTX 1050 Ti||4||768||21.1||133.8||154.9||MJS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||NVIDIA GeForce GTX 1050||2||640||20.6||139.1||159.7||JM2
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||NVIDIA Quadro P2000||5||1024||22.1||142.5||164.6||KTC
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||NVIDIA Quadro P2000||5||1024||23.0||149.3||172.3||RL2
|-
|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz||NVIDIA Quadro M2200||4||1024||23.2||198.7||222.0||GYB
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz||NVIDIA T500||4||986||29.3||197.5||226.8||TJS
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz ||NVIDIA Quadro P1000||4||640||30.3||203.7||234.0||RL3
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA Quadro K2200||4||640||32.5||211.3||243.8||JIW
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz ||NVIDIA Quadro M1200||4||640||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz ||NVIDIA GeForce GTX 940MX||2||384||65.6||479.0||544.6||EAS
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||NVIDIA GeForce 840M||2||384||70.6||526.3||595.9||CDH
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||NVIDIA GeForce GT 740M||2||384||102.3||694.0||796.3||HMM
|-
|}
 

=High End GPU Results=
A number of additional benchmarking tests have been completed on a 5m and 2.5m model on a single GPU card.

{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 2.5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||NVIDIA GeForce RTX 4090||24||16384||103.3||811.2||914.5||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz||NVIDIA GeForce RTX 4090||24||16384||105.9||813.7||919.6||TA1
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz||NVIDIA GeForce RTX 4090||24||16384||103.7||824.3||928.0||JW1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||108.2||821.5||929.7||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||106.8||875.5||982.3||CR4
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz ||NVIDIA RTX 6000 Ada Generation||48||18176||119.6||877.8||997.4||JG3
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||139.5||1115.1||1254.6||JM3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||155.2||1172.9||1328.1||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||155.5||1176.2||1331.7||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||158||1192.2||1350.2||CH3
|-
|Intel(R) Core(TM) i9-10900F CPU @ 3.70GHz ||NVIDIA GeForce RTX 3090||24||10496||162.3||1192.4||1354.7||LJA
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||159.7||1216.2||1375.9||GP1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||160.9||1240||1400.9||DD2
|-
|Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz ||NVIDIA GeForce RTX 3090||24||10496||172.9||1249.8||1422.7||SIP
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||178.9||1363.9||1542.8||KW2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||203.8||1523.9||1727.7||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||201.2||1548.1||1749.3||JGR
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||220.0||1634.5||1854.5||MA1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||222.2||1648.7||1870.9||JPI
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||215.9||1678.7||1894.6||PA2
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||241.2||1863.5||2104.7||RRB
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||248.7||1928.6||2177.3||JG2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||257.3||1957.7||2215.0||RH2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||275.1||2147.4||2422.5||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||296.0||2218.4||2514.4||FLC
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||298.9||2290.1||2589.0||JS1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.3||2345.1||2656.4||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||310.3||2377.2||2687.5||RCD
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||308.7||2384.7||2693.4||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.9||2404.9||2716.7||PM1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||324.8||2475.3||2800.1||HNM
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||439.0||3379.3||3818.2||BLK
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||475.5||3788.2||4263.7||SKI
|-
|}
<pre> * it is noted that the number of CUDA cores is not provided as an output from the '''dxdiag''' command and this information has been sourced from the nvidia website.
** The output cpu.txt only provides the 'out of the box' processor speed. If you have overclocked your cpu and/or gpu, please send these details to TUFLOW Support so we can add the overclocked data in brackets. </pre>

{{Tips Navigation
|uplink=[[Hardware_Benchmarking_(2018-03-AA) | Back to TUFLOW Benchmarking]]
}}

Hardware Benchmarking - Results

2024-05-24T14:35:18Z

Angelos Livogiannis:

=CPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m Classic and HPC CPU runtimes, with the fastest computers at the top of the table.
 
'''Runtimes for CPU benchmarks'''
{| align="center" class="wikitable"

! style="background-color:#005581; font-weight:bold; color:white;"| Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Processor Frequency (GHz)**
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM size (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM frequency (MHz)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Classic 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | HPC CPU 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Runtime Combined (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||128||5200||32.7||108.6||141.3||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||64||5600||36.7||114.2||150.9||TM1
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||2.0||128||4000||41.2||124.1||165.3||AW1
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs)||3.2||128||4800||38.5||127.0||165.5||SB1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz||4.5||64||4800||33.4||136.0||169.4||PSM
|-
|12th Gen Intel(R) Core(TM) i9-12900K||3.2||128||3200||40.7||129.9||170.6||DD2
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs) @ ~4.2GHz||4.2||32||4800||35.5||162.8||198.3||LC1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs)||2.5||16||3200||48.4||170.5||218.9||TS1
|-
|Intel(R) Xeon(R) w5-2455X (24 CPUs) @ ~3.2GHz||3.2||64||4800||53.3||169.1||222.4||CHR1
|-
|Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz||3.7||128||3200||56.9||173.8||230.7||CH1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz)||(5.1)||16||4000||58.2||179.9||238.1||RRB
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||3000||55.7||186.2||241.9||RH1
|-
|AMD Ryzen 9 3900X 12-Core Processor||3.8||64||3200||45.9||203.1||249.0||CH3
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz||3.1||32||2666||61.7||190.0||251.7||CB1
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz||3.6||32||2133||61.4||190.4||251.8||RH2
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||3.6||64||2133||62.7||191.1||253.8||PA1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||32||2933||62.1||192.8||254.9||DS2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||71.2||184.3||255.5||ABA
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||62.1||193.7||255.8||MA2
|-
|AMD Ryzen Threadripper 3970X 32-Core Processor||3.7||256||2400||49.5||212.1||261.6||CH2
|-
|AMD Ryzen 9 3950X 16-Core Processor||3.5||128||2800||55.9||210.0||265.9||TRO
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||2133||67.0||202.5||269.5||RL1
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz||3.5||128||2133||72.7||202.1||274.8||MBL
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||67.5||208.6||276.1||SKI
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||68.5||208.8||277.3||PM2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||66.8||211.6||278.1||MA1
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz||3.2||16||2667||68.2||211.8||280.0||CR2
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||68.0||216.0||284.0||RL3
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||67.7||219.1||286.8||RL2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||70.5||218.8||289.3||PM1
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||2.9||16||2667||77.5||212.6||290.1||KTC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||3.7||32||2933||75.2||219.8||295||BL-DT01001
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor||3.5||128||2666||67.9||230.8||298.7||JGR
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||3.5||128||2666||66.3||234.7||301||JG3
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||32||2400||80.5||221.9||302.4||JM1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz||3.6||16||2400||72.8||230.6||303.4||RSH
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||85.4||218.8||304.2||JPI
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||83.7||225.2||308.9||HNM
|-
|Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz||4.0||32||2400||91.2||223.3||314.5||BRD
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz||3.7||64||2400||84.5||236.6||321.2||DS1
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz||3.2||128||2133||83.4||243.1||326.5||BLK
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||3.7||64||2933||95.4||231.3||326.7||JB2
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz||3.4||128||2400||85.3||247.7||332.9||615
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2400||106.3||226.7||333.0||MRT
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||16||2133||80.7||253.4||334.1||VHD
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz||2.1||64||2666||83.9||251.2||335.1||AR2
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor||3.4||16||2666||81.9||277.3||359.2||CEV
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz||3.0||32||2400||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||64||2133||82.3||289.8||372.1||JIW
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz||3.4||32||1666||108.9||270.0||378.9||AR1
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||3.8||64||3200||87.8||294.2||382||HDR-A2000
|-
|AMD Ryzen 9 5950X 16-Core Processor||3.4||32||3400||39.7||343.0||382.7||JG2
|-
|Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz||2.8||32||1600||119.7||280.8||400.5||SBC
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz||3.3||64||2133||118.2||287.8||406.0||ZDO
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz||2.7||16||2133||90.4||321.7||412.1||EAS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||16||2133||84.8||336.9||421.7||JM2
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2133||100.3||323||423.3||MON
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz||3.4||32||1600||126.4||299.7||426.1||MAV
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz ||3.0||4||986||84.0||351.4||435.4||TJS
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||3.5||16||1333||125.9||320.5||446.4||EFC
|-
|Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz||1.9||16||1800||100.1||347.0||447.1||SM1
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||2.9||16||2900||63.3||385.0||448.3||NCV
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||4.1||16||4104||62.7||386.6||449.3||GZH
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||2.4||128||2394||130.5||331.5||462||VDI
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||2.6||24||1600||100.5||378.6||479.1||CDH
|-
|Intel(R) Xeon(R) CPU E5-1650 0 @ 3.20GHz||3.2||32||1600||143.2||343.1||486.3||MPR
|-
|Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz||3.2||8||1600||142.0||349.4||491.4||CR1
|-
|Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz||3.3||16||N/A||196.8||331.5||528.3||Private Cloud
|-
|Intel(R) Core(TM) i7-4712HQ CPU @ 2.30GHz (Laptop)||2.3||8||1600||145.2||414.4||559.6||MNG
|-
|Intel(R) Xeon(R) CPU X5680 @ 3.33GHz||3.33||72||1333||165.7||400.6||566.3||WTM
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||2.4||8||1600||137.8||795.0||932.8||HMM
|-
|}
 

=GPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m and 10m runtimes with the fastest computers at the top of the table.
 
The HPC GPU benchmark only uses a single GPU card. TUFLOW HPC GPU can be run across multiple NVIDIA GPU devices. However, the benefits of these are typically more noticeable for larger models with more than 1 million cells.
 
'''Runtimes for GPU benchmarks'''
{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 10m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz ||NVIDIA GeForce RTX 4090||24||16384||2.4||11.6||14.0||JW1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4090||24||16384||2.5||12.1||14.6||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz ||NVIDIA GeForce RTX 4090||24||16384||2.7||12.7||15.4||TA1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||2.9||12.7||15.6||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||3.1||13.3||16.4||CR4
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||TM1
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||JM3
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||NVIDIA GeForce RTX 4080||16||9728||3.2||15.0||18.2||AW1
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs)@ ~4.2GHz||NVIDIA GeForce RTX 4080 SUPER||16||10240||3.2||15.7||18.9||LC1
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||NVIDIA RTX 6000 Ada Generation||48||18176||4.9||14.2||19.1||JG3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||3.4||18.5||21.9||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||3.8||19.2||23.0||RS1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||3.7||19.4||23.1||DD2
|-
|12th Gen Intel(R) Core(TM) i7-12700F
|NVIDIA GeForce RTX 3080 Ti
|12
|10240
|3.75
|19.57
|23.32
|AUBNE1PC6602
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||4.0||19.6||23.6||GP1
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA A40||48||10752||3.5||20.3||23.8||Lenovo SR650 V2
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.1||20.1||24.2||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.4||20.4||24.8||CH3
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||4.6||23.5||28.1||KW2
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs) ||NVIDIA RTX A5000||24||8192||4.4||24.1||28.5||SB1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 3080||10||8704||4.7||24.0||28.7||CPM
|-
|Intel(R) Xeon(R) W-2223 CPU @ 3.60GHz ||NVIDIA GeForce RTX 3090||24||10496||5.3||24.3||29.6||SSM2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||4.7||25.7||30.4||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||5.7||25.2||30.9||JGR
|-
|AMD Ryzen Threadripper 2920X 12-Core Processor (24 CPUs) @ 3.5GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.1||25.9||31||CR5
|-
|AMD Ryzen 9 3950X 16-Core Processor ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.3||26.4||31.7||TRO
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||27.4||32.8||PY2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||27.7||33.4||VLD
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||NVIDIA GeForce RTX 3070||8||5888||5.0||28.8||33.8||NCV
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.5||28.4||33.9||RL1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||5.5||28.7||34.2||RRB
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.8||28.8||34.6||MA1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||29.2||34.9||MA2
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||5.5||29.7||35.2||JG2
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.6||29.9||35.5||MBL
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||6.4||29.5||35.9||JPI
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P100||16||3584||6.1||30.8||36.9||Google Cloud: Tesla P100
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||5.7||31.9||37.6||RH2
|-
|Intel(R) Xeon(R) Gold 6230R CPU @ 2.10GHz ||NVIDIA GRID RTX8000P-48Q||48||4608||6.8||31.0||37.8||VJ1
|-
|Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 CPUs) ||NVIDIA RTX A4000||16||6144||5.8||32.0||37.8||JS2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080||8||2944||6.0||31.9||37.9||ANK
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||6.0||32.0||38.0||EFC
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||33.3||38.7||PA1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce RTX 3060 Ti (LHR) ||8||4864||5.7||33.3||39.0||DF1
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||NVIDIA GeForce RTX 2060 SUPER (core 1647MHz, mem 1750MHz)||8||2176||5.6||33.4||39.1||GZH
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||5.6||34.3||40.7||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||6.9||34.6||41.6||FLC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||35.1||41.6||JB2
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.4||35.8||42.2||JS1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080||8||2944||6.5||36.0||42.5||ABA
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA RTX A4000||16||6144||7.2||35.3||42.5||CHR1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.1||37.1||43.2||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||37.4||43.8||PM1
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA GeForce GTX 2070||8||2304||7.4||38.8||46.2||MMR
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz ||NVIDIA Quadro RTX 4000||8||2304||6.6||39.8||46.4||CB1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.8||39.1||46.9||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||8.0||39.3||47.3||RCD
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.6||41.1||48.7||HNM
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||NVIDIA GRID RTX6000P-4Q||24||4608||10.5||39.3||49.8||VDI
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (Laptop) ||NVIDIA GeForce RTX 2070||8||2304||7.7||42.8||50.5||ERX
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA Tesla T4||16||2560||6.8||45.2||52.0||RJ1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz
|NVIDIA GeForce RTX 3060
|8
|3584
|7.68
|45.92
|53.6
|AUBNEW1DQ54G3
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||8.0||47.4||55.3||BLK
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla T4||16||2560||7.3||48.3||55.6||FM-NODE: Tesla T4
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz ||NVIDIA GeForce GTX 1080||8||2560||8.5||48.9||57.3||JM1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||8.2||51.9||60.0||SKI
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz ||NVIDIA Quadro P5000||16||2560||9.6||51.8||61.4||AR2
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||NVIDIA RTX A2000||6||3328||9.1||54.4||63.5||HDR-A2000
|-
|Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz ||NVIDIA GeForce GTX 1070||8||1920||8.9||54.9||63.8||PY1
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz ||NVIDIA GeForce GTX 1070||8||1920||10.3||59.3||69.5||DS1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA Quadro P4000||8||1792||10.0||62.3||72.3||DS2
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce GTX 1650 SUPER||4||1280||10.3||64.6||74.9||TS1
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P4||8||2560||10.4||69.0||79.4||Google Cloud: Tesla P4
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz ||NVIDIA GeForce GTX 980||4||2048||11.8||70.6||82.3||ZDO
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz ||NVIDIA GeForce GTX TITAN Black||6||2880||13.1||76.1||89.2||AR1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz ||NVIDIA GeForce GTX 1060||6||1280||13.0||77.1||90.1||RSH
|-
|Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz (64 CPUs), ~2.3GHz||NVIDIA Tesla M60||16||4096||12||82.7||94.7||SM2
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla K80||12||2496||11.3||83.5||94.8||Google Cloud: Tesla K80
|-
|Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz ||NVIDIA Tesla K40c||12||2880||12.3||83.1||95.3||NWE
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA Quadro T2000||4||1024||13.3||85.2||95.5||SSM
|-
|Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (Laptop) ||NVIDIA GeForce GTX 980||4||2048||17.5||84.2||101.7||MRT
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||NVIDIA Quadro P2000||5||1024||14.2||96||110.2||BL-DT01001
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz ||NVIDIA Quadro P2000||5||1024||15.8||100.1||115.9||CR2
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz ||NVIDIA GeForce GTX 690||2||3072||18.4||114.4||132.8||MAV
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor ||NVIDIA GeForce GTX 960||4||1024||18.6||123.3||141.6||CEV
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA GeForce GTX 960||4||1024||19.9||127.2||147.1||VHD
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz||NVIDIA GeForce GTX 1050 Ti||4||768||21.1||133.8||154.9||MJS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||NVIDIA GeForce GTX 1050||2||640||20.6||139.1||159.7||JM2
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||NVIDIA Quadro P2000||5||1024||22.1||142.5||164.6||KTC
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||NVIDIA Quadro P2000||5||1024||23.0||149.3||172.3||RL2
|-
|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz||NVIDIA Quadro M2200||4||1024||23.2||198.7||222.0||GYB
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz||NVIDIA T500||4||986||29.3||197.5||226.8||TJS
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz ||NVIDIA Quadro P1000||4||640||30.3||203.7||234.0||RL3
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA Quadro K2200||4||640||32.5||211.3||243.8||JIW
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz ||NVIDIA Quadro M1200||4||640||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz ||NVIDIA GeForce GTX 940MX||2||384||65.6||479.0||544.6||EAS
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||NVIDIA GeForce 840M||2||384||70.6||526.3||595.9||CDH
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||NVIDIA GeForce GT 740M||2||384||102.3||694.0||796.3||HMM
|-
|}
 

=High End GPU Results=
A number of additional benchmarking tests have been completed on a 5m and 2.5m model on a single GPU card.

{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 2.5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||NVIDIA GeForce RTX 4090||24||16384||103.3||811.2||914.5||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz||NVIDIA GeForce RTX 4090||24||16384||105.9||813.7||919.6||TA1
|-
|13th Gen Intel(R) Core(TM) i7-13700KF (24 CPUs), @ 3.4GHz||NVIDIA GeForce RTX 4090||24||16384||103.7||824.3||928.0||JW1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||108.2||821.5||929.7||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||106.8||875.5||982.3||CR4
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz ||NVIDIA RTX 6000 Ada Generation||48||18176||119.6||877.8||997.4||JG3
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||139.5||1115.1||1254.6||JM3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||155.2||1172.9||1328.1||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||155.5||1176.2||1331.7||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||158||1192.2||1350.2||CH3
|-
|Intel(R) Core(TM) i9-10900F CPU @ 3.70GHz ||NVIDIA GeForce RTX 3090||24||10496||162.3||1192.4||1354.7||LJA
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||159.7||1216.2||1375.9||GP1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||160.9||1240||1400.9||DD2
|-
|Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz ||NVIDIA GeForce RTX 3090||24||10496||172.9||1249.8||1422.7||SIP
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||178.9||1363.9||1542.8||KW2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||203.8||1523.9||1727.7||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||201.2||1548.1||1749.3||JGR
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||220.0||1634.5||1854.5||MA1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||222.2||1648.7||1870.9||JPI
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||215.9||1678.7||1894.6||PA2
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||241.2||1863.5||2104.7||RRB
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||248.7||1928.6||2177.3||JG2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||257.3||1957.7||2215.0||RH2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||275.1||2147.4||2422.5||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||296.0||2218.4||2514.4||FLC
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||298.9||2290.1||2589.0||JS1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.3||2345.1||2656.4||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||310.3||2377.2||2687.5||RCD
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||308.7||2384.7||2693.4||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.9||2404.9||2716.7||PM1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||324.8||2475.3||2800.1||HNM
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||439.0||3379.3||3818.2||BLK
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||475.5||3788.2||4263.7||SKI
|-
|}
<pre> * it is noted that the number of CUDA cores is not provided as an output from the '''dxdiag''' command and this information has been sourced from the nvidia website.
** The output cpu.txt only provides the 'out of the box' processor speed. If you have overclocked your cpu and/or gpu, please send these details to TUFLOW Support so we can add the overclocked data in brackets. </pre>

{{Tips Navigation
|uplink=[[Hardware_Benchmarking_(2018-03-AA) | Back to TUFLOW Benchmarking]]
}}

QGIS TUFLOW Run TUFLOW

2024-04-19T13:27:26Z

Angelos Livogiannis:

==Run TUFLOW Simulation==
Start a TUFLOW simulation. The default control file is the most recent file in the '''TUFLOW\runs''' folder, the default executable is defined in the [[QGIS_TUFLOW_Create_Project | Configure / Create TUFLOW project]]. If the [[QGIS_TUFLOW_Create_Project | Configure / Create TUFLOW project]] tool has not been run, no default values exist, and you will need to select the TUFLOW executable and also the input control file. 

As of QGIS 3.6 the Plugin also has functionality to run TUFLOW FV models. The process to run a TUFLOW FV model is analagous to TUFLOW but pointing to the TUFLOWFV\runs folder, the relevant *.fvc file (not *.tcf) and the TUFLOW FV executable. 
 
[[File:QGIS Run TUFLOW.png]]
 

==TUFLOW Runner (TUFLOW QGIS Plugin version v3.11+)==
Starting with TUFLOW QGIS Plugin version v3.11 you can also '''manage TUFLOW simulations by launching the TUFLOW Runner''' by choosing '''Run -> Launch TUFLOW Runner''' from the TUFLOW plugin menu. For more details about the TUFLOW Runner, please visit: [https://wiki.tuflow.com/TUFLOW_Runner TUFLOW Runner]

{{Tips Navigation
|uplink=[[TUFLOW_QGIS_Plugin#Usage| Back to TUFLOW QGIS Plugin Main Page]]
}}

Running TUFLOW

2024-04-19T12:45:31Z

Angelos Livogiannis:

=Introduction=
TUFLOW is a standalone console application. As such, it doesn't require installation to run. The standard TUFLOW setup steps are listed below.

* '''Free DEMO and Tutorial Version''' of TUFLOW:
# Download the latest TUFLOW executable from the Tuflow website: [https://www.tuflow.com/Tuflow%20Latest%20Release.aspx Tuflow Release Download]
# Download the TUFLOW Tutorial and Demo models: [https://www.tuflow.com/Tuflow%20Tutorial%20Models.aspx Tutorial Model Download]
# Run TUFLOW using any of the options listed below. User documentation for the tutorial models is available from the [[Tutorial_Introduction | Tutorial Model Introduction]] section of the Wiki.

* '''Licensed Version''' of TUFLOW:
# Download the latest TUFLOW executable from the Tuflow website: [https://www.tuflow.com/Tuflow%20Latest%20Release.aspx Tuflow Release Download]
# Download and install the Licensing Dongle Drivers: [[TUFLOW_Licensing|Installing Licensing Software]]
# Run TUFLOW using any of the options listed below.

= Executable Management Advice =
Save a copy of the downloaded TUFLOW executable files to a dedicated location (eg. C:\TUFLOW\Releases\) 
A TUFLOW release consists of two different versions of the executable as follows:
# TUFLOW_iSP_w64.exe - Single Precision Windows 64-bit
# TUFLOW_iDP_w64.exe - Double Precision Windows 64-bit

Refer to the TUFLOW Executable Section of the TUFLOW manual for advice when best to use the different TUFLOW versions. Each version of TUFLOW also has four TUFLOW .dll files and several system .dll files included in the download. Do not delete or relocate these dlls. All .exe and .dll files must be placed in the same folder and kept together at all times. 

When replacing TUFLOW with a new build, we recommend archiving the past .exe and .dll files by creating a folder of the same name as the Build ID (e.g. 2013-12-AA-iSP-w64), and placing all files in this folder. Build ID information is appears in the top bar of the Console window when TUFLOW is executed, and is reported in the header of the .tlf file.
 [[File:Executable_File_Management_001.png|600px]]

= Run Options=
==Single Simulation Execution==
There are a number of ways TUFLOW can be started, in each case the TUFLOW executable is started with the TUFLOW control file (.tcf) as the input. There are a number of optional switches that can be used to control advanced features as outlined in the TUFLOW manual. 

Common ways of initialising a TUFLOW simulation are:

* [[Run TUFLOW From a Batch-file|Using a Batch-file]]
* [[TUFLOW Runner|Using the TUFLOW Runner]]
* [[Run TUFLOW From UltraEdit|Running TUFLOW from UltraEdit]]
* [[Run TUFLOW through the command window|Run TUFLOW through the command window]]
* [[NotepadPlusPlus_Run_TUFLOW | Running TUFLOW from Notepad++]]
* [[tuflow:images/d/dc/TextPad_TUFLOW_instructions.pdf |Textpad Instructions Including Running TUFLOW (Provided by CHM2Hill / Halcrow)]]
* [[Running_TUFLOW_from_Explorer | Running TUFLOW from Windows Explorer (Pre-Windows 7)]]
* [[QGIS_TUFLOW_Run_TUFLOW | From QGIS with the TUFLOW QGIS Plugin]]
* [[ArcTUFLOW_Run_TUFLOW_Simulation | From ArcMap with the ArcTUFLOW Toolbox]]
* For miTools users, please see the miTools manual for instructions.

==Multiple Simulation Management==
* [[Run TUFLOW From a Batch-file|Using a Batch-file]]
* [[TUFLOW Runner|Using the TUFLOW Runner]]
* [[TRIM_Tips| TUFLOW Run Interface Manager (TRIM)]]
* For miTools users, please see the miTools manual for instructions.

==Scheduling Simulations==
* [[Using_Task_Scheduler_to_Run_Batch_Files|Using Task Scheduler]]
= Cloud Computing =
The "Cloud" is an excellent project execution environment option in situations where large simulation volumes require completion within a short timeframe (e.g. Monte Carlo runs). Three options are available. Click the links below for more information:
== Execution On Your Own Cloud Environment ==
Organisations with access to Cloud hardware may host Network Licences within their own cloud domain (private or public). 
Click For Details: [[Organisation_Cloud_Software_Execution| Organisation Cloud Software Execution]]. 

== TUFLOW Cloud Simulation Service ==
Let BMT help you manage your TUFLOW simulation execution on the cloud. This service is designed for bulk simulation of any TUFLOW product (Classic, HPC or FV). 
* Software licences are scaled to meet your project demand (i.e. this is independent of any in-house licences you may own).
* The BMT service offers flexibility regarding the Microsoft Azure Cloud hardware available for your project. We tailor the hardware and storage resource specification to suit your project requirements (based on project size, model size and also the simulation type).
* This service has no limitations in terms of hardware type. We offer simulation on a range of CPU and GPU virtual machines. 
This service is well suited to mass production runs of an established model (often required for design event modelling or a Monte Carlo assessment). It is less suited to model build activities that require regular modeller/model interaction and iterations. We recommend model build activities be completed using a standard client licence as it is typically the most cost effective and time efficient option. 
Click For Details: [[TUFLOW_Cloud_Simulation_Service| TUFLOW Cloud Simulation Service]].

TUFLOW Runner

2024-04-19T12:43:41Z

Angelos Livogiannis:

==Introduction==
The TUFLOW Runner provides a simple GUI for creating a queue of TUFLOW and TUFLOW FV simulations which will be run depending on available licenses and resources. The runner is available from the [https://gitlab.com/tuflow-user-group/tuflow/simulation-management/tuflow-runner TUFLOW GitLAB User Group] and is also bundled with the TUFLOW QGIS plugin. The TUFLOW Runner can replace the need for batch files.

'''With TUFLOW Runner you can:'''
*Manage a queue of simulations to run (combination of TUFLOW/TUFLOW FV).
*Handle TUFLOW scenarios and events
*Add multiple simulations based upon a combination of scenarios and events.
*Run multiple simulations at a time dependent upon computer and plugin resources.
*Change priority of items in the run queue.
*Remove items from the run queue.
*Kill currently running items in the run queue.
*Rerun a previously run simulation from the run queue (right-click).

'''TUFLOW Runner has also the following features:'''
*Uses an extensible "plugin" approach so other processes (executables) can be managed in the same queue.
*Manages available computer CPU and GPU resources.
*Tracks progress of running simulation.
*TUFLOW provides graphical output (matplotlib) of simulation volume in and volume out through time.

'''Other advantages:'''
*Option to save and load a run queue to easily rerun a group of simulations.
*Plugins can define restrictions for licenses, GPUs and CPUs.
*Scenarios and events are remembered between simulations
*Simulation screen output for running or finished simulations (searchable).

==Setting up the TUFLOW Runner==
Launch the runner.
* If running from python, launch the "main.py" script.
* If running through the QGIS Plugin, in the QGIS menu select '''Plugins >> TUFLOW >> RUN >> Launch TUFLOW Runner'''.

To set up:
*Choose '''Settings''' option from the Menu.
[[File:Setting Runner 1.jpg|550px|]] 
*'''Specify''' the resources (CPU and GPU) and plugin information such as location of executables.
[[File:Setting Runner 2.jpg|550px|]] 
*Then, click '''OK'''.

==Running the tool==
'''Start''' a TUFLOW simulation by following the steps below:
*Select '''Run type''' (TUFLOW/TUFLOW FV).
*Identify the folder that contains the simulation files ('''Base folder''') and select the simulation file. This must be .tcf for TUFLOW Classic/HPC or .fvc for TUFLOW FV.
[[File:Running the tool 1.jpg|550px|]] 
*Click on the '''Add''' button to add a simulation to the queue. If a TUFLOW model includes Events (~e~) and/or Scenarios (~s~) by clicking on the '''Add''' button a '''dialog''' (please see image below) will come up to add model’s Scenarios and/or Events. ''' To add simulations, there must be selected scenarios and events in every category. You can use '_' or another placeholder as needed for default scenarios.''' The bottom of the window shows the combination of selected events and scenarios. To get the sub-list you are interested in, you may need to use the add command several times.
[[File:Running the tool 2.jpg|550px|]] 

'''Please note:''' For TUFLOW model which includes Scenario and/Events, the (~s~) and/or (~e~) must be included in the simulation filename.
*Then, toggle on '''Run''' to run the simulation.
[[File:Running the tool 3.jpg|750px]]

==Running Multiple Simulation==
If the resources and configurations (do not create more configurations than you have licenses for), allow for it, the Runner will launch multiple simulations at the same time as long as there are simulations in the queue able to be run. As simulations finish, the next available simulation that does not exceed available resources and configurations will be run.

==Troubleshooting==
If a TUFLOW model simulation with Events and/or Scenarios is not queued please check that these are specified in the Add Simulation '''dialog''' Window (please, see section: '''Running the tool''' – Step 3) as the runner requires an entry for each Scenario/Event.

If you have further queries or issues it is recommended contacting [mailto:support@tuflow.com support@tuflow.com].

{{Tips Navigation
|uplink=[[TUFLOW_QGIS_Plugin#Usage| Back to TUFLOW QGIS Plugin Main Page]]
}}

TUFLOW Runner

2024-04-19T10:21:03Z

Angelos Livogiannis:

===Page Under Construction===
==Introduction==
The TUFLOW Runner provides a simple GUI for creating a queue of TUFLOW and TUFLOW FV simulations which will be run depending on available licenses and resources. The runner is available from the [https://gitlab.com/tuflow-user-group/tuflow/simulation-management/tuflow-runner TUFLOW GitLAB User Group] and is also bundled with the TUFLOW QGIS plugin. The TUFLOW Runner can replace the need for batch files.

'''With TUFLOW Runner you can:'''
*Manage a queue of simulations to run (combination of TUFLOW/TUFLOW FV).
*Handle TUFLOW scenarios and events
*Add multiple simulations based upon a combination of scenarios and events.
*Run multiple simulations at a time dependent upon computer and plugin resources.
*Change priority of items in the run queue.
*Remove items from the run queue.
*Kill currently running items in the run queue.
*Rerun a previously run simulation from the run queue (right-click).

'''TUFLOW Runner has also the following features:'''
*Uses an extensible "plugin" approach so other processes (executables) can be managed in the same queue.
*Manages available computer CPU and GPU resources.
*Tracks progress of running simulation.
*TUFLOW provides graphical output (matplotlib) of simulation volume in and volume out through time.

'''Other advantages:'''
*Option to save and load a run queue to easily rerun a group of simulations.
*Plugins can define restrictions for licenses, GPUs and CPUs.
*Scenarios and events are remembered between simulations
*Simulation screen output for running or finished simulations (searchable).

==Setting up the TUFLOW Runner==
The tool can be found via the QGIS menu '''Plugins >> TUFLOW >> RUN >> Launch TUFLOW Runner'''. To set up:
*Choose '''Settings''' option from the Menu.
[[File:Setting Runner 1.jpg|550px|]] 
*'''Specify''' the resources (CPU and GPU) and plugin information such as location of executables.
[[File:Setting Runner 2.jpg|550px|]] 
*Then, click '''OK'''.

==Running the tool==
'''Start''' a TUFLOW simulation by following the steps below:
*Select '''Run type''' (TUFLOW/TUFLOW FV).
*Identify the folder that contains the simulation files ('''Base folder''') and select the simulation file. This must be .tcf for TUFLOW Classic/HPC or .fvc for TUFLOW FV.
[[File:Running the tool 1.jpg|550px|]] 
*Click on the '''Add''' button to add a simulation to the queue. If a TUFLOW model includes Events (~e~) and/or Scenarios (~s~) by clicking on the '''Add''' button a '''dialog''' (please see image below) will come up to add model’s Scenarios and/or Events.''' If default Scenarios are included, please use '_'.''' For each combination of Events and Scenarios a bunch of runs are shown up at the bottom of the window.
[[File:Running the tool 2.jpg|550px|]] 

'''Please note:''' For TUFLOW model which includes Scenario and/Events, the (~s~) and/or (~e~) must be included in the simulation filename.
*Then, toggle on '''Run''' to run the simulation.
[[File:Running the tool 3.jpg|750px]]

==Running Multiple Simulation==
Multiple simulations can be run with the TUFLOW Runner. To do so, follow the steps which are described in '''Running the tool''' section and before running, '''Add''' to the queue more than one simulation files. If a simulation runs and you need to queue a new simulation, choose your new simulation file, and just click on '''Add''' button. The new simulation will be queued, automatically showing waiting status. Also, while running other simulations, you can re-launch the TUFLOW Runner for creating new queues and start new simulations.

==Troubleshooting==
If a TUFLOW model simulation with Events and/or Scenarios is not queued please check that these are specified in the Add Simulation '''dialog''' Window (please, see section: '''Running the tool''' – Step 3) as the runner requires an entry for each Scenario/Event.

If you have further queries or issues it is recommended contacting [mailto:support@tuflow.com support@tuflow.com].

{{Tips Navigation
|uplink=[[TUFLOW_QGIS_Plugin#Usage| Back to TUFLOW QGIS Plugin Main Page]]
}}

QGIS TUFLOW Run TUFLOW

2024-04-19T09:44:15Z

Angelos Livogiannis:

Start a TUFLOW simulation. The default control file is the most recent file in the '''TUFLOW\runs''' folder, the default executable is defined in the [[QGIS_TUFLOW_Create_Project | Configure / Create TUFLOW project]]. If the [[QGIS_TUFLOW_Create_Project | Configure / Create TUFLOW project]] tool has not been run, no default values exist, and you will need to select the TUFLOW executable and also the input control file. 

As of QGIS 3.6 the Plugin also has functionality to run TUFLOW FV models. The process to run a TUFLOW FV model is analagous to TUFLOW but pointing to the TUFLOWFV\runs folder, the relevant *.fvc file (not *.tcf) and the TUFLOW FV executable. 
 
[[File:QGIS Run TUFLOW.png]]
 

==TUFLOW Runner (version v3.11+)==
Starting with version v3.11 you can also '''manage TUFLOW simulations by launching the TUFLOW Runner''' by choosing '''Run -> Launch TUFLOW Runner''' from the TUFLOW plugin menu. For more details about the TUFLOW Runner, please visit: [https://wiki.tuflow.com/TUFLOW_Runner TUFLOW Runner]

{{Tips Navigation
|uplink=[[TUFLOW_QGIS_Plugin#Usage| Back to TUFLOW QGIS Plugin Main Page]]
}}

Running TUFLOW

2024-04-19T09:41:29Z

Angelos Livogiannis:

=Introduction=
TUFLOW is a standalone console application. As such, it doesn't require installation to run. The standard TUFLOW setup steps are listed below.

* '''Free DEMO and Tutorial Version''' of TUFLOW:
# Download the latest TUFLOW executable from the Tuflow website: [https://www.tuflow.com/Tuflow%20Latest%20Release.aspx Tuflow Release Download]
# Download the TUFLOW Tutorial and Demo models: [https://www.tuflow.com/Tuflow%20Tutorial%20Models.aspx Tutorial Model Download]
# Run TUFLOW using any of the options listed below. User documentation for the tutorial models is available from the [[Tutorial_Introduction | Tutorial Model Introduction]] section of the Wiki.

* '''Licensed Version''' of TUFLOW:
# Download the latest TUFLOW executable from the Tuflow website: [https://www.tuflow.com/Tuflow%20Latest%20Release.aspx Tuflow Release Download]
# Download and install the Licensing Dongle Drivers: [[TUFLOW_Licensing|Installing Licensing Software]]
# Run TUFLOW using any of the options listed below.

= Executable Management Advice =
Save a copy of the downloaded TUFLOW executable files to a dedicated location (eg. C:\TUFLOW\Releases\) 
A TUFLOW release consists of two different versions of the executable as follows:
# TUFLOW_iSP_w64.exe - Single Precision Windows 64-bit
# TUFLOW_iDP_w64.exe - Double Precision Windows 64-bit

Refer to the TUFLOW Executable Section of the TUFLOW manual for advice when best to use the different TUFLOW versions. Each version of TUFLOW also has four TUFLOW .dll files and several system .dll files included in the download. Do not delete or relocate these dlls. All .exe and .dll files must be placed in the same folder and kept together at all times. 

When replacing TUFLOW with a new build, we recommend archiving the past .exe and .dll files by creating a folder of the same name as the Build ID (e.g. 2013-12-AA-iSP-w64), and placing all files in this folder. Build ID information is appears in the top bar of the Console window when TUFLOW is executed, and is reported in the header of the .tlf file.
 [[File:Executable_File_Management_001.png|600px]]

= Run Options=
==Single Simulation Execution==
There are a number of ways TUFLOW can be started, in each case the TUFLOW executable is started with the TUFLOW control file (.tcf) as the input. There are a number of optional switches that can be used to control advanced features as outlined in the TUFLOW manual. 

Common ways of initialising a TUFLOW simulation are:

* [[Run TUFLOW From a Batch-file|Using a Batch-file]]
* [[Run TUFLOW From UltraEdit|Running TUFLOW from UltraEdit]]
* [[Run TUFLOW through the command window|Run TUFLOW through the command window]]
* [[NotepadPlusPlus_Run_TUFLOW | Running TUFLOW from Notepad++]]
* [[tuflow:images/d/dc/TextPad_TUFLOW_instructions.pdf |Textpad Instructions Including Running TUFLOW (Provided by CHM2Hill / Halcrow)]]
* [[Running_TUFLOW_from_Explorer | Running TUFLOW from Windows Explorer (Pre-Windows 7)]]
* [[QGIS_TUFLOW_Run_TUFLOW | From QGIS with the TUFLOW QGIS Plugin]]
* [[TUFLOW Runner|From QGIS with the TUFLOW Runner]]
* [[ArcTUFLOW_Run_TUFLOW_Simulation | From ArcMap with the ArcTUFLOW Toolbox]]
* For miTools users, please see the miTools manual for instructions.

==Multiple Simulation Management==
* [[Run TUFLOW From a Batch-file|Using a Batch-file]]
* [[TRIM_Tips| TUFLOW Run Interface Manager (TRIM)]]
* For miTools users, please see the miTools manual for instructions.
* [[TUFLOW Runner|From QGIS with the TUFLOW Runner]]

==Scheduling Simulations==
* [[Using_Task_Scheduler_to_Run_Batch_Files|Using Task Scheduler]]
= Cloud Computing =
The "Cloud" is an excellent project execution environment option in situations where large simulation volumes require completion within a short timeframe (e.g. Monte Carlo runs). Three options are available. Click the links below for more information:
== Execution On Your Own Cloud Environment ==
Organisations with access to Cloud hardware may host Network Licences within their own cloud domain (private or public). 
Click For Details: [[Organisation_Cloud_Software_Execution| Organisation Cloud Software Execution]]. 

== TUFLOW Cloud Simulation Service ==
Let BMT help you manage your TUFLOW simulation execution on the cloud. This service is designed for bulk simulation of any TUFLOW product (Classic, HPC or FV). 
* Software licences are scaled to meet your project demand (i.e. this is independent of any in-house licences you may own).
* The BMT service offers flexibility regarding the Microsoft Azure Cloud hardware available for your project. We tailor the hardware and storage resource specification to suit your project requirements (based on project size, model size and also the simulation type).
* This service has no limitations in terms of hardware type. We offer simulation on a range of CPU and GPU virtual machines. 
This service is well suited to mass production runs of an established model (often required for design event modelling or a Monte Carlo assessment). It is less suited to model build activities that require regular modeller/model interaction and iterations. We recommend model build activities be completed using a standard client licence as it is typically the most cost effective and time efficient option. 
Click For Details: [[TUFLOW_Cloud_Simulation_Service| TUFLOW Cloud Simulation Service]].

QGIS TUFLOW Run TUFLOW

2024-04-19T09:41:10Z

Angelos Livogiannis:

Start a TUFLOW simulation. The default control file is the most recent file in the '''TUFLOW\runs''' folder, the default executable is defined in the [[QGIS_TUFLOW_Create_Project | Configure / Create TUFLOW project]]. If the [[QGIS_TUFLOW_Create_Project | Configure / Create TUFLOW project]] tool has not been run, no default values exist, and you will need to select the TUFLOW executable and also the input control file. 

As of QGIS 3.6 the Plugin also has functionality to run TUFLOW FV models. The process to run a TUFLOW FV model is analagous to TUFLOW but pointing to the TUFLOWFV\runs folder, the relevant *.fvc file (not *.tcf) and the TUFLOW FV executable. 
 
[[File:QGIS Run TUFLOW.png]]
 

==TUFLOW Runner (version v3.11+)==
Starting with version v3.11 you can also '''manage TUFLOW simulations by launching the TUFLOW Runner''' by choosing "Run -> Launch TUFLOW Runner" from the TUFLOW plugin menu. For more details about the TUFLOW Runner, please visit: [https://wiki.tuflow.com/TUFLOW_Runner TUFLOW Runner]

{{Tips Navigation
|uplink=[[TUFLOW_QGIS_Plugin#Usage| Back to TUFLOW QGIS Plugin Main Page]]
}}

TUFLOW Runner

2024-04-19T09:27:08Z

Angelos Livogiannis:

TUFLOW Runner

2024-04-19T09:02:51Z

Angelos Livogiannis:

===Page Under Construction===
==Introduction==
The TUFLOW Runner provides a simple GUI for creating a queue of TUFLOW and TUFLOW FV simulations which will be run depending on available licenses and resources. The runner is available from the [https://gitlab.com/tuflow-user-group/tuflow/simulation-management/tuflow-runner TUFLOW GitLAB User Group] and is also bundled with the TUFLOW QGIS plugin. The TUFLOW Runner can replace the need for batch files.

'''With TUFLOW Runner you can:'''
*Manage a queue of simulations to run (combination of TUFLOW/TUFLOW FV).
*Handle TUFLOW scenarios and events
*Add multiple simulations based upon a combination of scenarios and events.
*Run multiple simulations at a time dependent upon computer and plugin resources.
*Change priority of items in the run queue.
*Remove items from the run queue.
*Kill currently running items in the run queue.
*Rerun a previously run simulation from the run queue (right-click).

'''TUFLOW Runner has also the following features:'''
*Uses an extensible "plugin" approach so other processes (executables) can be managed in the same queue.
*Manages available computer CPU and GPU resources.
*Tracks progress of running simulation.
*TUFLOW provides graphical output (matplotlib) of simulation volume in and volume out through time.

'''Other advantages:'''
*Option to save and load a run queue to easily rerun a group of simulations.
*Plugins can define restrictions for licenses, GPUs and CPUs.
*Scenarios and events are remembered between simulations
*Simulation screen output for running or finished simulations (searchable).

==Setting up the TUFLOW Runner==
The tool can be found via the QGIS menu '''Plugins >> TUFLOW >> Launch TUFLOW Runner'''. To set up:
*Choose '''Settings''' option from the Menu.
[[File:Setting Runner 1.jpg|550px|]] 
*'''Specify''' the resources (CPU and GPU) and plugin information such as location of executables.
[[File:Setting Runner 2.jpg|550px|]] 
*Then, click '''OK'''.

==Running the tool==
'''Start''' a TUFLOW simulation by following the steps below:
*Select '''Run type''' (TUFLOW/TUFLOW FV).
*Identify the folder that contains the simulation files ('''Base folder''') and select the simulation file. This must be .tcf for TUFLOW Classic/HPC or .fvc for TUFLOW FV.
[[File:Running the tool 1.jpg|550px|]] 
*Click on the '''Add''' button to add a simulation to the queue. If a TUFLOW model includes Events (~e~) and/or Scenarios (~s~) by clicking on the '''Add''' button a '''dialog''' (please see image below) will come up to add model’s Scenarios and/or Events.''' If default Scenarios are included, please use '_'.''' For each combination of Events and Scenarios a bunch of runs are shown up in the bottom of the window.
[[File:Running the tool 2.jpg|550px|]] 

'''Please note:''' For TUFLOW model which includes scenario and/events, the (~s~) and/or (~e~) must be included in the simulation filename.
*Then, Toggle on '''Run''' to run the simulation.
[[File:Running the tool 3.jpg|750px]]

==Running Multiple Simulation==
Multiple simulations can be run with the TUFLOW Runner. To do so, follow the steps which are described in '''Running the tool''' section and before running, '''Add''' to the queue more than one simulation files. If a simulation runs and you need to queue a new simulation, choose your new simulation file, and just click on '''Add''' button. The new simulation will be queued, automatically showing waiting status. Also, while running other simulations, you can re-launch the TUFLOW Runner for creating new queues and start new simulations.

==Troubleshooting==
If a TUFLOW model simulation with Events and/or Scenarios is not queued please check that these are specified in the Add Simulation '''dialog''' Window (please, see section: '''Running the tool''' – Step 3) as the runner requires an entry for each Scenario/Event.

If you have further queries or issues it is recommended contacting [mailto:support@tuflow.com support@tuflow.com].

TUFLOW Runner

2024-04-19T08:57:46Z

Angelos Livogiannis: /* Troubleshooting */

===Page Under Construction===
==Introduction==
The TUFLOW Runner provides a simple GUI for creating a queue of TUFLOW and TUFLOW FV simulations which will be run depending on available licenses and resources. The runner is available from the [https://gitlab.com/tuflow-user-group/tuflow/simulation-management/tuflow-runner TUFLOW GitLAB User Group] and is also bundled with the TUFLOW QGIS plugin. The TUFLOW Runner can replace the need for batch files.

'''With TUFLOW Runner you can:'''
*Manage a queue of simulations to run (combination of TUFLOW/TUFLOW FV).
*Handle TUFLOW scenarios and events
*Add multiple simulations based upon a combination of scenarios and events.
*Run multiple simulations at a time dependent upon computer and plugin resources.
*Change priority of items in the run queue.
*Remove items from the run queue.
*Kill currently running items in the run queue.
*Rerun a previously run simulation from the run queue (right-click).

'''TUFLOW Runner has also the following features:'''
*Uses an extensible "plugin" approach so other processes (executables) can be managed in the same queue.
*Manages available computer CPU and GPU resources.
*Tracks progress of running simulation.
*TUFLOW provides graphical output (matplotlib) of simulation volume in and volume out through time.

'''Other advantages:'''
*Option to save and load a run queue to easily rerun a group of simulations.
*Plugins can define restrictions for licenses, GPUs and CPUs.
*Scenarios and events are remembered between simulations
*Simulation screen output for running or finished simulations (searchable).

==Setting up the TUFLOW Runner==
The tool can be found via the QGIS menu '''Plugins >> TUFLOW >> Launch TUFLOW Runner'''. To set up:
*Choose '''Settings''' option from the Menu.
[[File:Setting Runner 1.jpg|550px|]] 
*'''Specify''' the resources (CPU and GPU) and plugin information such as location of executables.
[[File:Setting Runner 2.jpg|550px|]] 
*Then, click '''OK'''.

==Running the tool==
'''Start''' a TUFLOW simulation by following the steps below:
*Select '''Run type''' (TUFLOW/TUFLOW FV).
*Identify the folder that contains the simulation files ('''Base folder''') and select the simulation file. This must be .tcf for TUFLOW Classic/HPC or .fvc for TUFLOW FV.
[[File:Running the tool 1.jpg|550px|]] 
*Click on the '''Add''' button to add a simulation to the queue. If a TUFLOW model includes Events (~e~) and/or Scenarios (~s~) by clicking on the '''Add''' button a '''dialog''' (please see image below) will come up to add model’s scenarios and/or events.''' If default scenarios are included, please use '_'.''' For each combination of events and scenarios a bunch of runs are shown up in the bottom of the window.
[[File:Running the tool 2.jpg|550px|]] 

'''Please note:''' For TUFLOW model which includes scenario and/events, the (~s~) and/or (~e~) must be included in the simulation filename.
*Then, Toggle on '''Run''' to run the simulation.
[[File:Running the tool 3.jpg|750px]]

==Running Multiple Simulation==
Multiple simulations can be run with the TUFLOW Runner. To do so, follow the steps which are described in '''Running the tool''' section and before running, '''Add''' to the queue more than one simulation files. If a simulation runs and you need to queue a new simulation, choose your new simulation file, and just click on '''Add''' button. The new simulation will be queued, automatically showing waiting status. Also, while running other simulations, you can re-launch the TUFLOW Runner for creating new queues and start new simulations.

==Troubleshooting==
If a TUFLOW model simulation with Events and/or Scenarios is not queued please check that these are specified in the Add Simulation '''dialog''' Window (please, see section: '''Running the tool''' – Step 3) as the runner requires an entry for each scenario/event.

If you have further queries or issues it is recommended contacting [mailto:support@tuflow.com support@tuflow.com].

TUFLOW Runner

2024-04-19T08:53:34Z

Angelos Livogiannis: Created page with "===Page Under Construction=== ==Introduction== The TUFLOW Runner provides a simple GUI for creating a queue of TUFLOW and TUFLOW FV simulations which will be run depending on..."

===Page Under Construction===
==Introduction==
The TUFLOW Runner provides a simple GUI for creating a queue of TUFLOW and TUFLOW FV simulations which will be run depending on available licenses and resources. The runner is available from the [https://gitlab.com/tuflow-user-group/tuflow/simulation-management/tuflow-runner TUFLOW GitLAB User Group] and is also bundled with the TUFLOW QGIS plugin. The TUFLOW Runner can replace the need for batch files.

'''With TUFLOW Runner you can:'''
*Manage a queue of simulations to run (combination of TUFLOW/TUFLOW FV).
*Handle TUFLOW scenarios and events
*Add multiple simulations based upon a combination of scenarios and events.
*Run multiple simulations at a time dependent upon computer and plugin resources.
*Change priority of items in the run queue.
*Remove items from the run queue.
*Kill currently running items in the run queue.
*Rerun a previously run simulation from the run queue (right-click).

'''TUFLOW Runner has also the following features:'''
*Uses an extensible "plugin" approach so other processes (executables) can be managed in the same queue.
*Manages available computer CPU and GPU resources.
*Tracks progress of running simulation.
*TUFLOW provides graphical output (matplotlib) of simulation volume in and volume out through time.

'''Other advantages:'''
*Option to save and load a run queue to easily rerun a group of simulations.
*Plugins can define restrictions for licenses, GPUs and CPUs.
*Scenarios and events are remembered between simulations
*Simulation screen output for running or finished simulations (searchable).

==Setting up the TUFLOW Runner==
The tool can be found via the QGIS menu '''Plugins >> TUFLOW >> Launch TUFLOW Runner'''. To set up:
*Choose '''Settings''' option from the Menu.
[[File:Setting Runner 1.jpg|550px|]] 
*'''Specify''' the resources (CPU and GPU) and plugin information such as location of executables.
[[File:Setting Runner 2.jpg|550px|]] 
*Then, click '''OK'''.

==Running the tool==
'''Start''' a TUFLOW simulation by following the steps below:
*Select '''Run type''' (TUFLOW/TUFLOW FV).
*Identify the folder that contains the simulation files ('''Base folder''') and select the simulation file. This must be .tcf for TUFLOW Classic/HPC or .fvc for TUFLOW FV.
[[File:Running the tool 1.jpg|550px|]] 
*Click on the '''Add''' button to add a simulation to the queue. If a TUFLOW model includes Events (~e~) and/or Scenarios (~s~) by clicking on the '''Add''' button a '''dialog''' (please see image below) will come up to add model’s scenarios and/or events.''' If default scenarios are included, please use '_'.''' For each combination of events and scenarios a bunch of runs are shown up in the bottom of the window.
[[File:Running the tool 2.jpg|550px|]] 

'''Please note:''' For TUFLOW model which includes scenario and/events, the (~s~) and/or (~e~) must be included in the simulation filename.
*Then, Toggle on '''Run''' to run the simulation.
[[File:Running the tool 3.jpg|750px]]

==Running Multiple Simulation==
Multiple simulations can be run with the TUFLOW Runner. To do so, follow the steps which are described in '''Running the tool''' section and before running, '''Add''' to the queue more than one simulation files. If a simulation runs and you need to queue a new simulation, choose your new simulation file, and just click on '''Add''' button. The new simulation will be queued, automatically showing waiting status. Also, while running other simulations, you can re-launch the TUFLOW Runner for creating new queues and start new simulations.

==Troubleshooting==
If a TUFLOW model simulation with Events and/or Scenarios is not queued please check that these are specified in the Add Simulation '''dialog''' Window (please, see section: '''Running the tool''' – Step 3) as the runner requires an entry for each scenario/event.

File:Setting Runner 2.jpg

2024-04-19T08:36:11Z

Angelos Livogiannis:

Setting Runner 2

File:Setting Runner 1.jpg

2024-04-19T08:32:11Z

Angelos Livogiannis:

Setting Runner 1

File:Running the tool 3.jpg

2024-04-19T08:18:41Z

Angelos Livogiannis:

Running the tool 3

File:Running the tool 2.jpg

2024-04-19T08:07:06Z

Angelos Livogiannis:

Running the tool 2

File:Running the tool 1.jpg

2024-04-19T07:58:21Z

Angelos Livogiannis:

Running the tool 1

TUFLOW Message 3517

2024-04-09T10:47:01Z

Angelos Livogiannis:

{{TUFLOW_Message
|tuflow_message=ERROR 3517: Z Shape Route not supported yet in SGS. Please contact support@tuflow.com.
 
|alt_msg=ERROR 3517: HX 2D BC not supported yet in SGS. Please contact support@tuflow.com. 
ERROR 3517: Interpolate ZUVH not supported yet in SGS. Please contact support@tuflow.com. 
ERROR 3517: ZC == MIN(ZU,ZV) not supported yet in SGS. Please contact support@tuflow.com. 
ERROR 3517: FC not supported yet in SGS. Please contact support@tuflow.com. 
ERROR 3517: "Read RowCol Zpt" not supported with Quadtree. 
etc
|type=[[ERROR]]
|message_desc=These commands/functions are not supported in either SGS or Quadtree (depending on the message received) with the used TUFLOW version. 
If the message received is "ERROR 3517 - "Read RowCol Zpt" not supported with Quadtree" this is because the GIS layer is cell size dependent therefore cannot be used in a Quadtree model, as they have multiple cell sizes.
|suggestions=
Use the latest version of TUFLOW available from the TUFLOW website. Alternatively, remove these features to run in SGS (or Quadtree depending on the message), or contact support@tuflow.com for further assistance.

If the message received is "ERROR 3517 - "FC" not supported yet in SGS" this is because a GIS 2d_fcsh layer is used. Change this to a 2d_lfcsh layer which is supported when using SGS.

If the message received is "ERROR 3517 - "Read RowCol Zpt" not supported with Quadtree" use the source that the layer was originally generated from. Alternatively, if you have both .mid/.mif it is possible to generate a raster within QGIS which can be read into TUFLOW instead. If there is no .mif file, this can be generated in TUFLOW using the following in the TGC (anywhere the zpt layer is not 99 will be the original sample points and elevations): 
<tt>Set Zpts<tt>== </tt> <tt>99</tt> 
<tt>Read MID Zpts<tt>== </tt> <tt>input_file.mid</tt> 
<tt>Write GIS Zpts<tt>== </tt> <tt>output_file.mif !or .shp, .gpkg</tt> 
<tt>Stop</tt> 

|uplink=[[3xxx_TUFLOW_Messages|3xxx Messages]]
}}

1D Pits

2024-04-03T08:24:53Z

Angelos Livogiannis:

=Introduction=
There are predominantly two types of stormwater pits (drains/gullies) used as inlets to collect overland runoff and transfer that water to the underlying drainage/culvert/pipe network;
* Grated inlets
* Kerb Inlets (side entry pits / lintel inlets).
This page of the Wiki describes how pit inlet data is incorporated into a TUFLOW model.

= Pit Inlet Types =
{|class="wikitable"
|-
! Inlet Type !! Example !! Description
|-
! Q
| [[File:Q pit inlet.jpg|thumb|none|300px|Depth-Discharge Pit or Channel]]|| width="300pt"|Depth-Discharge Pit or Channel, pit inlet inflow information is defined within TUFLOW via a user defined Pit Inlet Database and associated pit inlet curves. This approach allows for unlimited flexibility. Any pit design or configuration can be incorporated into a TUFLOW model if the inlet depth-discharge relationship is known.
|-
! R
| [[File:Side_Entry_pit.jpg|thumb|none|300px|Kerb Inlet]]|| width="300pt"|Kerb inlets, also know as side entry pits or lintels are common in Australia. The pit chamber can vary depending on overall depth, length and the addition of any haunched riser units.
|-
! C
| [[File:Circular pit inlet.jpg|thumb|none|300px|Circular Pit Inlet]]|| width="300pt"|Circular pit inlet
|-
! W
| [[File:Gully pit.jpg|thumb|none|300px|Grate (London, UK)]] || width="300pt"|Grates, also known as Gully Pits, are common in the United Kingdom and are generally a square grate on top of a circular chamber and a riser outlet. The outlet will then feed into a larger culvert that forms part of the larger urban drainage network.
|}

= Pit Inlet Data Sources =
Pit inlet depth-discharge data can be obtained from a variety of sources. The most common typically being from suppliers or local agencies who enforce consistent design standards within their jurisdiction. For demonstration purposes, examples from Sutherland Shire Council and Brisbane City Council are provided below.

== Sutherland Shire Council ==
The Sutherland Shire Council Urban Drainage Manual (1992) includes summary tables and graphs documenting pit grate and lintel capacity information (derived from Department of Main Roads testing). The guidelines are compatible with the standard pit grate and lintel design shown below: 
[[File: Pit_Inlet_Curves_SSC000.JPG|700px]] 
The capacity of a pit depends on three factors:
* The clear opening area of the grate
* The depth of water ponding over the grate
* The length of kerb inlet (lintel) opening
The following graphs summarise grate and lintel discharge estimates for a range of water depths and blockage factors, derived from the Sutherland Shire Council design standards. 
[[File: Pit_Inlet_Curves_SSC001.JPG|700px]]
[[File: Pit_Inlet_Curves_SSC002.JPG|700px]] 

The above graphs estimate unit length and area flow estimates. These unit values can be multiplied by real pit dimensions to define at site depth-discharge characteristics.

TUFLOW modelling requires the derivation of a unique depth-discharge curve for each pit type within the modelled area. An example is provided below for a single pit location. 

[[File: Pit_Inlet_Curves_SSC003.JPG|700px]]

== Brisbane City Council==
The pit inlet curve examples below originate from Brisbane City Council 8000 series standard drawings: https://www.brisbane.qld.gov.au/planning-building/planning-guidelines-tools/planning-guidelines/standard-drawings 
[[File: BCC_BSD-8077.JPG|border|700px]]
[[File: BCC_BSD-8051.JPG|border|700px]] 
[[File: BCC_BSD-8082.JPG|border|700px]]
[[File: BCC_BSD-8052.JPG|border|700px]] 

== South Australian Road Stormwater Drainage Inlets: Hydraulic Study (University of South Australia)==
The Urban Water Resources Centre (UWRC) at the University of South Australia conducted a comprehensive set of hydraulic studies, examining performance of the most common roads’ stormwater drainage inlets in use in South Australia. The study was carried out using the Centre's unique full-scale road surface drainage test rig. Links to the pipe inlets curves are provided in the following link and sections below: [https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/ Hydraulic Study (University of South Australia)]
=== Transport South Australia ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/transport-sa/ Transport South Australia Pit Inlet Curves]
=== City of Adelaide ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-adelaide/ City of Adelaide Pit Inlet Curves]
=== City of Campbelltown ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-campbeltown/ City of Campbelltown Pit Inlet Curves]
=== City of Charles Sturt ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-charles-sturt/ City of Charles Sturt Pit Inlet Curves]
=== City of Onkaparinga ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-onkaparinga/ City of Onkaparinga Pit Inlet Curves]
=== City of Playford ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-playford/ City of Playford Pit Inlet Curves]
=== City of Port Adelaide / Enfield ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-port-adelaideenfield/ City of Port Adelaide / Enfield Pit Inlet Curves]
=== City of Marion ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-marion/ City of Marion Pit Inlet Curves]
=== City of Mitcham ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-mitcham/ City of Mitcham Pit Inlet Curves]
=== City of Salisbury ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-salisbury/ City of Salisbury Pit Inlet Curves]
=== City of Tea Tree Gully ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-tea-tree-gully/ City of Tea Tree Gully Pit Inlet Curves]
=== City of West Torrens ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-west-torrens/ City of West Torrens Pit Inlet Curves]

== Spacing of Road Gullies (UK standards: BS EN 124 and BS7903) ==
The following section describes the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 Spacing of Road Gullies] guidance (UK standards: '''BS EN 124''' and '''BS 7903''') which provides a method for determining road gulley capture rates.

The method depends on the following '''Hydraulic parameters:'''
* Longitudinal gradient, ''SL'', along the length of the scheme (expressed as fraction).

* Cross-fall, ''Sc'' (also expressed as a fraction).

* Manning’s roughness coefficient, ''n''. Usually ''n'' = 0.017 for a conventional road surface. Other values are given in the following '''Table 1'''. (For more details, please see Section: 5, Table 5.3N of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance]).

'''Table 1:''' Values of Manning's ''n''
 [[File:Table1N.jpg|750px|]] 

* The grating type (P, Q, R, S or T), or the size and angle of kerb inlet.

* The maximum allowable flow width (as shown below by ''B'' in m) against the kerb.
 [[File:Figures 1 2.jpg|850px|]] 

'''Calculation of Gully Flow Capture Rates based on Equations'''
 The equations given in Appendix C (p.g: 25) of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance] can be used to determine flow capture rates at different depths, to determine the depth-discharge curve for use within TUFLOW. The method requires the calculations of the flow capacity of the kerb channel and flow collection efficiency of the gully grate.
*As a first step, a gully grate type: P, Q, R, S or T should be selected. The selection of the grating type will determine the design value ''Gd'' (grating parameter) from '''Table 2'''. (For more details, please see Table A.2, Appendix A of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance]).

'''Table 2:''' Determination of grating type ''Gd''
 [[File:Determination of grating type.jpg|650px|]] 

*Road (longitudinal) gradient (''SL''), Crossfall (''Sc'') and Manning's (''n'') should then be determined. Parameter values can be obtained from '''Table 3'''.

'''Table 3:''' Determination of ''SL'', ''Sc'' and Manning's ''n''
 [[File:Table SL SC N Range.jpg|750px|]] 

*Further, a Water Depth against the kerb ''H'' (m) range should be provided. (Please note: The depth range can be changed, but the following equations that are used to calculate the flow capacity are only valid up to the kerb height).

*With the above parameters, the calculations of the i) Flow width (''B'' in m), ii) Cross-sectional area (''Af'' in m2), iii) Hydraulic radius (''R'' in m), iv) Flow rate (''Q'' in m3/s) and v) Flow collection efficiency (''ŋ'' (%)) based on the Equations C.1-C.5 which are presented in Appendix C of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance] can be completed.

*Finally, the resulting depth-discharge data can be used in the TUFLOW pit inlet curves. 

The Gully Flow Capture Rates template [https://downloads.tuflow.com/Other/Inlet_Spreadsheets/Gully%20Flow%20Capture%20Rates_v3.xlsx here,] includes a calculation tab which can be used for the completion of the above calculation processes. Based on calculations and Equations C.6 and C.7 of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance] the maximum allowable spacings upstream of the gully can be further calculated (For more details, please see Appendix C, p.g: 25).

'''Key assumption''' '''Note:''' This method assumes that the route the flow takes around the trap limits the discharge from the gully pot to 10 l/s. This limit is effective in both directions, so any negative head on the gully would create -10 l/s flow back up through the gully and flood onto the road. 

== UK Water Industry Research (UKWIR) Inlet Capture Tool ==
In 2023, the UK Water Industry Research (UKWIR) Limited released the Modelling Sewer Inlet Capacity Restrictions Report [https://ukwir.org/modelling-sewer-inlet-capacity-restrictions Modelling Sewer Inlet Capacity Restrictions Report]. The main aim was to develop a sewer modelling methodology to enable the representation of inlet inflow restrictions, focusing on the development of a new 1D model approach to provide more accurate model sewer flooding predictions. The new modelling approach has been devised by combining the findings from a literature review and the development of semi-empirical relationships from academic studies which investigated factors affecting inlet capacity. The new approach allows for 2 types of gully response reflecting 2 flow conditions: Subcritical flow on a shallow road gradient and Supercritical flow on a steep road gradients. A threshold of 0.02 is used to distinguish between shallow and steep road gradients. The reported equations can be used for the production of input inlet curves for TUFLOW 1D pit inlet modelling.

A template for the generation of the UKWIR Inlet Curve can be downloaded from [https://downloads.tuflow.com/Other/Inlet_Spreadsheets/Inlet%20Curve%20Capture%20tool%20v4.xlsx here]. The template determines both Subcritical Head-Discharge and Supercritical Head-Discharge relationships obtained from the Modelling Sewer Inlet Capacity Restrictions Report based on user input values of water depth (in metres). Two sets of curves can be generated, curves based on default parameters, and those based on user-defined parameters.

== How to Translate On-Grade Approach Flow / Pit Capture Flow Curves to Depth / Discharge Curves for use in TUFLOW ==
Manning's equation calculations can be used to convert on-grade approach flow information to a water depth at the pit. ARR 2019 Guidelines (Section 5.6.1, Chapter 5, Book 9) recommends the use of the modified Mannings equation, the Izzard's equation, for gutter and roadway flow. 

After manually calculating the depth to flow relationship the user simply needs to associate these water depth values with the pit capture flow information typically included in on grade pit inlet curve datasets.

=TUFLOW Model Inputs=
The steps required to represent pit inlet information within a TUFLOW model is summarised below:
<ol>
<li> Import an empty 1d_nwk GIS file from the TUFLOW file template folder (model\gis\empty).
<li> Digitise points to represent pit locations. The points should be snapped to the start or end of 1d_nwk line features that define the underground pipe network.
<li> Update the field attributes for each Pit point. Refer to 5.12.2 of the 2016 TUFLOW Manual. The most commonly used attributes are:
* Type = Q (C, R and W are also options if pit inlets based on structure dimension is required instead of using a Pit Inlet Database approach).
* US_Invert = Used to specify the ground elevation of the pit. If Conn_1D_2D is set to “SXL”, US_Invert is used as the amount by which to lower the 2D cell and the pit channel invert is set to this level.
* DS_Invert = The bottom elevation of the pit. This input can also be used to set the upstream and downstream inverts of connected pipes/channels.
* Inlet_Type = For Q pit channels, the name of a pit inlet type in the Pit Inlet Database. Multiple Pits can use the same Inlet_Type ID if they have the same design dimensions.
* Conn_1D_2D = SXL can be specified to connect the 1D pit or node to the 2D domain and lower the 2D cell by the amount of the US_Invert attribute. The invert of the pit channel is set to the lowered 2D cell level. This is useful to help trap the water into the pit as it flows overland in the 2D domain. This feature works well in combination with the new Read GIS SA PITS option.
<li> Update the Estry Control File (*.ecf) to include reference to the new 1d_nwk GIS file. 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\Estry\1d_nwk_****.MIF</tt> 
<li> Create a Pit Inlet Database csv file. This file lists each type of pit (matching the names listed in the 1d_nwk "Inlet_Type" field). It also provides reference to the depth-discharge curve information. 
[[File:M05 pit inlet dbase 01.png]]
<li> Create the Source file referenced in the Pit Inlet Database. The source file defines the depth-discharge information for each pit (determined from the relevant design standards). The column headers must match the entries in the Pit Inlet Database. 
[[File:M05 pit inlet v2.png]]
<li> Update the Estry Control File (*.ecf) to include reference to the Pit Inlet Database. 
<tt>Pit Inlet Database</tt> <tt>==</tt><tt>..\pit_dbase\EG_pit_dbase.csv</tt> 
</ol>

An example model including Pits is available for download: https://wiki.tuflow.com/index.php?title=TUFLOW_Example_Models

==Pit Search Distance==
Some agency pit datasets may not have all pit point features snapped to the associated pipe line features. The *.ecf command "Pit Search Distance" can be useful in this instance. It automatically connects floating nodes to the 1D pipe network where connectors are not snapped to channel ends: 

<tt>Pit Search Distance</tt> <tt>==</tt><tt>xxx</tt> 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\1d_nwke_*****.MIF</tt> 
 
The order of the "Pit Search Distance" command is important as it can be repeated multiple times with different values that are assigned to the 1d_nwke(s) below the ''Pit Search Distance'' command. The pit search command should be included above the the GIS layer containing the pits.

To check if the ''Pit Search Distance'' is working as expected, import the [[Check_Files_1d_nwk_C | *_nwk_C_check]] file to visually see if the pits are automatically connecting to a culvert. The image below is an example of the *_nwk_C_check file and the connections TUFLOW has made to each pit. 

 
[[File:Pit_search_distance_check.JPG|border|500px]]

 
Any further questions please email TUFLOW support: [mailto:support@tuflow.com?Subject=TUFLOW%201D%20pits%20help support@tuflow.com]
 
{{Tips Navigation
|uplink=[[ TUFLOW 1D Channels and Hydraulic Structures | Back to 1D Channels and Hydraulic Structures]]
}}

TUFLOW Message 2061

2024-03-04T13:07:17Z

Angelos Livogiannis:

{{TUFLOW_Message
|tuflow_message=Error 2061 - Could not find a CN connection snapped to the end of HX line.
|alt_msg=NA
|type=[[ERROR]]
|message_desc=Could not find a connection (CN object) snapped to the end of the 1D/2D interface (HX) line. Check that any connection object is snapped; add a connection to the end of the 1D/2D interface; or edit the 1D/2D interface line. 1D/2D interface lines based on the HX type must have as a minimum a connection at each of its ends, otherwise it is not clear how to transfer the water level gradient from the 1D domain.
|suggestions=The messages.mif or messages_P.shp file should contain the location that this error is occurring. Zoom into the HX line and check that the connection line is snapped to the end vertices of the line. This line can have CN connections snapped to intermediate vertices, but must have a CN line snapped to each end.

'''Please note:''' If the model is a Flood Modeller-TUFLOW (FM-TUFLOW) model and you are trying to run as a TUFLOW only model, this is a common error message as TUFLOW cannot find the external 1D nodes which are linked through the CN line(s) to the HX line(s). For more details on running a FM-TUFLOW model please visit the WIKI page below: [https://wiki.tuflow.com/Running_linked_Flood_Modeller_-_TUFLOW_Models Running linked Flood modeller - TUFLOW Models]

|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
}}

TUFLOW Message 2024

2024-03-04T11:35:04Z

Angelos Livogiannis:

{{TUFLOW_Message
|tuflow_message=ERROR 2024 - Could not find a 1D node snapped to CN line.
|alt_msg=NA
|type=[[ERROR]]
|message_desc=Could not find a 1D node snapped to 2d_bc connection (CN) line.
|suggestions=Check snapping and location of 2d_bc "CN" type object. This should connect a 1D node to a 2D boundary condition, e.g. "HX" or "SX" type connection. The messages.mif or messages_P.shp file will contain the location of the error. 
Check that the "CN" line finishes at a 1D node. In the example below, a single line has been digitised from the HX line to the HX line. Whilst it is snapped to the 1D node, it does not terminate there and therefore will cause Error 2024 to be generated. 
Note that the direction the "CN" line is digitised is not important. 
[[File:Error 2024.PNG|500px]]
 
In the next image, this line has been split at the 1D node and the issue is resolved. 
[[File:Error 2024 fix.PNG|500px]]

'''Please note:''' If the model is a Flood Modeller-TUFLOW (FM-TUFLOW) model and you are trying to run as a TUFLOW only model, this is a common error message as TUFLOW cannot find the external 1D nodes. For more details on running a FM-TUFLOW model please visit the WIKI page below: [https://wiki.tuflow.com/Running_linked_Flood_Modeller_-_TUFLOW_Models Running linked Flood modeller - TUFLOW Models]

|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
}}

TUFLOW Message 2061

2024-03-04T11:21:31Z

Angelos Livogiannis:

{{TUFLOW_Message
|tuflow_message=Error 2061 - Could not find a CN connection snapped to the end of HX line.
|alt_msg=NA
|type=[[ERROR]]
|message_desc=Could not find a connection (CN object) snapped to the end of the 1D/2D interface (HX) line. Check that any connection object is snapped; add a connection to the end of the 1D/2D interface; or edit the 1D/2D interface line. 1D/2D interface lines based on the HX type must have as a minimum a connection at each of its ends, otherwise it is not clear how to transfer the water level gradient from the 1D domain.
|suggestions=The messages.mif or messages_P.shp file should contain the location that this error is occurring. Zoom into the HX line and check that the connection line is snapped to the end vertices of the line. This line can have CN connections snapped to intermediate vertices, but must have a CN line snapped to each end.

'''Please note:''' If the model is a Flood Modeller - TUFLOW (FM - TUFLOW) model and you are trying to run as a TUFLOW only model, this is a common error message. For more details on running a FM - TUFLOW model please visit the WIKI page below: [https://wiki.tuflow.com/Running_linked_Flood_Modeller_-_TUFLOW_Models Running linked Flood modeller - TUFLOW Models]

|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
}}

TUFLOW Message 2061

2024-03-04T11:21:16Z

Angelos Livogiannis:

{{TUFLOW_Message
|tuflow_message=Error 2061 - Could not find a CN connection snapped to the end of HX line.
|alt_msg=NA
|type=[[ERROR]]
|message_desc=Could not find a connection (CN object) snapped to the end of the 1D/2D interface (HX) line. Check that any connection object is snapped; add a connection to the end of the 1D/2D interface; or edit the 1D/2D interface line. 1D/2D interface lines based on the HX type must have as a minimum a connection at each of its ends, otherwise it is not clear how to transfer the water level gradient from the 1D domain.
|suggestions=The messages.mif or messages_P.shp file should contain the location that this error is occurring. Zoom into the HX line and check that the connection line is snapped to the end vertices of the line. This line can have CN connections snapped to intermediate vertices, but must have a CN line snapped to each end.

'''Please note:''' If the model is a Flood Modeller - TUFLOW (FM - TUFLOW) model and you are trying to run as a TUFLOW only model, this is a common error message. For more details on running a FM - TUFLOW model please visit the WIKI page below: [https://wiki.tuflow.com/Running_linked_Flood_Modeller_-_TUFLOW_Models Running linked Flood modeller - TUFLOW Models]

|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
}}

TUFLOW Message 2061

2024-03-04T10:59:31Z

Angelos Livogiannis:

{{TUFLOW_Message
|tuflow_message=Error 2061 - Could not find a CN connection snapped to the end of HX line.
|alt_msg=NA
|type=[[ERROR]]
|message_desc=Could not find a connection (CN object) snapped to the end of the 1D/2D interface (HX) line. Check that any connection object is snapped; add a connection to the end of the 1D/2D interface; or edit the 1D/2D interface line. 1D/2D interface lines based on the HX type must have as a minimum a connection at each of its ends, otherwise it is not clear how to transfer the water level gradient from the 1D domain.
|suggestions=The messages.mif or messages_P.shp file should contain the location that this error is occurring. Zoom into the HX line and check that the connection line is snapped to the end vertices of the line. This line can have CN connections snapped to intermediate vertices, but must have a CN line snapped to each end.

'''Please note:''' If the model is a Flood Modeller_TUFLOW (FM_TUFLOW) model and you are trying to run as a TUFLOW only model, this is a common error message. For more details on running a FM_TUFLOW model please visit the WIKI page below: [https://wiki.tuflow.com/Running_linked_Flood_Modeller_-_TUFLOW_Models Running linked Flood modeller - TUFLOW Models]

|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
}}

Hardware Benchmarking - Results

2024-02-12T17:37:51Z

Angelos Livogiannis:

=CPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m Classic and HPC CPU runtimes, with the fastest computers at the top of the table.
 
'''Runtimes for CPU benchmarks'''
{| align="center" class="wikitable"

! style="background-color:#005581; font-weight:bold; color:white;"| Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Processor Frequency (GHz)**
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM size (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | RAM frequency (MHz)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Classic 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | HPC CPU 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=10% | Runtime Combined (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||128||5200||32.7||108.6||141.3||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||3.2||64||5600||36.7||114.2||150.9||TM1
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||2.0||128||4000||41.2||124.1||165.3||AW1
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs)||3.2||128||4800||38.5||127.0||165.5||SB1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz||4.5||64||4800||33.4||136.0||169.4||PSM
|-
|12th Gen Intel(R) Core(TM) i9-12900K||3.2||128||3200||40.7||129.9||170.6||DD2
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs) @ ~4.2GHz||4.2||32||4800||35.5||162.8||198.3||LC1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs)||2.5||16||3200||48.4||170.5||218.9||TS1
|-
|Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz||3.7||128||3200||56.9||173.8||230.7||CH1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz)||(5.1)||16||4000||58.2||179.9||238.1||RRB
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||3000||55.7||186.2||241.9||RH1
|-
|AMD Ryzen 9 3900X 12-Core Processor||3.8||64||3200||45.9||203.1||249.0||CH3
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz||3.1||32||2666||61.7||190.0||251.7||CB1
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz||3.6||32||2133||61.4||190.4||251.8||RH2
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||3.6||64||2133||62.7||191.1||253.8||PA1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||32||2933||62.1||192.8||254.9||DS2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||71.2||184.3||255.5||ABA
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||62.1||193.7||255.8||MA2
|-
|AMD Ryzen Threadripper 3970X 32-Core Processor||3.7||256||2400||49.5||212.1||261.6||CH2
|-
|AMD Ryzen 9 3950X 16-Core Processor||3.5||128||2800||55.9||210.0||265.9||TRO
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz||3.7||64||2133||67.0||202.5||269.5||RL1
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz||3.5||128||2133||72.7||202.1||274.8||MBL
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||67.5||208.6||276.1||SKI
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||68.5||208.8||277.3||PM2
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz||3.6||32||2666||66.8||211.6||278.1||MA1
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz||3.2||16||2667||68.2||211.8||280.0||CR2
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||68.0||216.0||284.0||RL3
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||2.7||32||2667||67.7||219.1||286.8||RL2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz||4.2||64||2133||70.5||218.8||289.3||PM1
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||2.9||16||2667||77.5||212.6||290.1||KTC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||3.7||32||2933||75.2||219.8||295||BL-DT01001
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor||3.5||128||2666||67.9||230.8||298.7||JGR
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||3.5||128||2666||66.3||234.7||301||JG3
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||32||2400||80.5||221.9||302.4||JM1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz||3.6||16||2400||72.8||230.6||303.4||RSH
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||85.4||218.8||304.2||JPI
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz||3.6||64||2666||83.7||225.2||308.9||HNM
|-
|Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz||4.0||32||2400||91.2||223.3||314.5||BRD
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz||3.7||64||2400||84.5||236.6||321.2||DS1
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz||3.2||128||2133||83.4||243.1||326.5||BLK
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||3.7||64||2933||95.4||231.3||326.7||JB2
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz||3.4||128||2400||85.3||247.7||332.9||615
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2400||106.3||226.7||333.0||MRT
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||16||2133||80.7||253.4||334.1||VHD
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz||2.1||64||2666||83.9||251.2||335.1||AR2
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor||3.4||16||2666||81.9||277.3||359.2||CEV
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz||3.0||32||2400||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz||3.4||64||2133||82.3||289.8||372.1||JIW
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz||3.4||32||1666||108.9||270.0||378.9||AR1
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||3.8||64||3200||87.8||294.2||382||HDR-A2000
|-
|AMD Ryzen 9 5950X 16-Core Processor||3.4||32||3400||39.7||343.0||382.7||JG2
|-
|Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz||2.8||32||1600||119.7||280.8||400.5||SBC
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz||3.3||64||2133||118.2||287.8||406.0||ZDO
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz||2.7||16||2133||90.4||321.7||412.1||EAS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||3.3||16||2133||84.8||336.9||421.7||JM2
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz||3.0||64||2133||100.3||323||423.3||MON
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz||3.4||32||1600||126.4||299.7||426.1||MAV
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz ||3.0||4||986||84.0||351.4||435.4||TJS
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||3.5||16||1333||125.9||320.5||446.4||EFC
|-
|Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz||1.9||16||1800||100.1||347.0||447.1||SM1
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||2.9||16||2900||63.3||385.0||448.3||NCV
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||4.1||16||4104||62.7||386.6||449.3||GZH
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||2.4||128||2394||130.5||331.5||462||VDI
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||2.6||24||1600||100.5||378.6||479.1||CDH
|-
|Intel(R) Xeon(R) CPU E5-1650 0 @ 3.20GHz||3.2||32||1600||143.2||343.1||486.3||MPR
|-
|Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz||3.2||8||1600||142.0||349.4||491.4||CR1
|-
|Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz||3.3||16||N/A||196.8||331.5||528.3||Private Cloud
|-
|Intel(R) Core(TM) i7-4712HQ CPU @ 2.30GHz (Laptop)||2.3||8||1600||145.2||414.4||559.6||MNG
|-
|Intel(R) Xeon(R) CPU X5680 @ 3.33GHz||3.33||72||1333||165.7||400.6||566.3||WTM
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||2.4||8||1600||137.8||795.0||932.8||HMM
|-
|}
 

=GPU Results=
The following table summarises the runtimes for a range of computers. More will be added when additional results are obtained. The table is ordered based on the combined 20m and 10m runtimes with the fastest computers at the top of the table.
 
The HPC GPU benchmark only uses a single GPU card. TUFLOW HPC GPU can be run across multiple NVIDIA GPU devices. However, the benefits of these are typically more noticeable for larger models with more than 1 million cells.
 
'''Runtimes for GPU benchmarks'''
{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 20m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 10m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4090||24||16384||2.5||12.1||14.6||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz ||NVIDIA GeForce RTX 4090||24||16384||2.7||12.7||15.4||TA1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||2.9||12.7||15.6||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||3.1||13.3||16.4||CR4
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||TM1
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||2.8||14.7||17.5||JM3
|-
|13th Gen Intel(R) Core(TM) i9-13900F (32 CPUs) @ 2.0GHz ||NVIDIA GeForce RTX 4080||16||9728||3.2||15.0||18.2||AW1
|-
|AMD Ryzen 7 7800X3D 8-Core Processor (16 CPUs)@ ~4.2GHz||NVIDIA GeForce RTX 4080 SUPER||16||10240||3.2||15.7||18.9||LC1
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz||NVIDIA RTX 6000 Ada Generation||48||18176||4.9||14.2||19.1||JG3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||3.4||18.5||21.9||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||3.8||19.2||23.0||RS1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||3.7||19.4||23.1||DD2
|-
|12th Gen Intel(R) Core(TM) i7-12700F
|NVIDIA GeForce RTX 3080 Ti
|12
|10240
|3.75
|19.57
|23.32
|AUBNE1PC6602
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||4.0||19.6||23.6||GP1
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA A40||48||10752||3.5||20.3||23.8||Lenovo SR650 V2
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.1||20.1||24.2||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||4.4||20.4||24.8||CH3
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||4.6||23.5||28.1||KW2
|-
|12th Gen Intel(R) Core(TM) i9-12900K (24 CPUs) ||NVIDIA RTX A5000||24||8192||4.4||24.1||28.5||SB1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 3080||10||8704||4.7||24.0||28.7||CPM
|-
|Intel(R) Xeon(R) W-2223 CPU @ 3.60GHz ||NVIDIA GeForce RTX 3090||24||10496||5.3||24.3||29.6||SSM2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||4.7||25.7||30.4||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||5.7||25.2||30.9||JGR
|-
|AMD Ryzen Threadripper 2920X 12-Core Processor (24 CPUs) @ 3.5GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.1||25.9||31||CR5
|-
|AMD Ryzen 9 3950X 16-Core Processor ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.3||26.4||31.7||TRO
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||27.4||32.8||PY2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||27.7||33.4||VLD
|-
|Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz ||NVIDIA GeForce RTX 3070||8||5888||5.0||28.8||33.8||NCV
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.5||28.4||33.9||RL1
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||5.5||28.7||34.2||RRB
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.8||28.8||34.6||MA1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.7||29.2||34.9||MA2
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||5.5||29.7||35.2||JG2
|-
|Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||5.6||29.9||35.5||MBL
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||6.4||29.5||35.9||JPI
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P100||16||3584||6.1||30.8||36.9||Google Cloud: Tesla P100
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||5.7||31.9||37.6||RH2
|-
|Intel(R) Xeon(R) Gold 6230R CPU @ 2.10GHz ||NVIDIA GRID RTX8000P-48Q||48||4608||6.8||31.0||37.8||VJ1
|-
|Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 CPUs) ||NVIDIA RTX A4000||16||6144||5.8||32.0||37.8||JS2
|-
|Intel(R) Core(TM) i7-6700k @ 4.00GHz ||NVIDIA GeForce RTX 2080||8||2944||6.0||31.9||37.9||ANK
|-
|Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||6.0||32.0||38.0||EFC
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz||NVIDIA GeForce RTX 2080 Ti||11||4352||5.4||33.3||38.7||PA1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce RTX 3060 Ti (LHR) ||8||4864||5.7||33.3||39.0||DF1
|-
|Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz ||NVIDIA GeForce RTX 2060 SUPER (core 1647MHz, mem 1750MHz)||8||2176||5.6||33.4||39.1||GZH
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||5.6||34.3||40.7||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||6.9||34.6||41.6||FLC
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz (20 CPUs)||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||35.1||41.6||JB2
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.4||35.8||42.2||JS1
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080||8||2944||6.5||36.0||42.5||ABA
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.1||37.1||43.2||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||6.5||37.4||43.8||PM1
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA GeForce GTX 2070||8||2304||7.4||38.8||46.2||MMR
|-
|Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz ||NVIDIA Quadro RTX 4000||8||2304||6.6||39.8||46.4||CB1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.8||39.1||46.9||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||8.0||39.3||47.3||RCD
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||7.6||41.1||48.7||HNM
|-
|Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz ||NVIDIA GRID RTX6000P-4Q||24||4608||10.5||39.3||49.8||VDI
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (Laptop) ||NVIDIA GeForce RTX 2070||8||2304||7.7||42.8||50.5||ERX
|-
|Intel(R) Xeon(R) Gold 5317 CPU @ 3.00GHz (48 CPUs) ||NVIDIA Tesla T4||16||2560||6.8||45.2||52.0||RJ1
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz
|NVIDIA GeForce RTX 3060
|8
|3584
|7.68
|45.92
|53.6
|AUBNEW1DQ54G3
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||8.0||47.4||55.3||BLK
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla T4||16||2560||7.3||48.3||55.6||FM-NODE: Tesla T4
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz ||NVIDIA GeForce GTX 1080||8||2560||8.5||48.9||57.3||JM1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||8.2||51.9||60.0||SKI
|-
|Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz ||NVIDIA Quadro P5000||16||2560||9.6||51.8||61.4||AR2
|-
|Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz (12 CPUs)||NVIDIA RTX A2000||6||3328||9.1||54.4||63.5||HDR-A2000
|-
|Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz ||NVIDIA GeForce GTX 1070||8||1920||8.9||54.9||63.8||PY1
|-
|Intel(R) Xeon(R) CPU E5-1630 v4 @ 3.70GHz ||NVIDIA GeForce GTX 1070||8||1920||10.3||59.3||69.5||DS1
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA Quadro P4000||8||1792||10.0||62.3||72.3||DS2
|-
|11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz (16 CPUs) ||NVIDIA GeForce GTX 1650 SUPER||4||1280||10.3||64.6||74.9||TS1
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla P4||8||2560||10.4||69.0||79.4||Google Cloud: Tesla P4
|-
|Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz ||NVIDIA GeForce GTX 980||4||2048||11.8||70.6||82.3||ZDO
|-
|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz ||NVIDIA GeForce GTX TITAN Black||6||2880||13.1||76.1||89.2||AR1
|-
|Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz ||NVIDIA GeForce GTX 1060||6||1280||13.0||77.1||90.1||RSH
|-
|Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz (64 CPUs), ~2.3GHz||NVIDIA Tesla M60||16||4096||12||82.7||94.7||SM2
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla K80||12||2496||11.3||83.5||94.8||Google Cloud: Tesla K80
|-
|Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz ||NVIDIA Tesla K40c||12||2880||12.3||83.1||95.3||NWE
|-
|Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz ||NVIDIA Quadro T2000||4||1024||13.3||85.2||95.5||SSM
|-
|Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (Laptop) ||NVIDIA GeForce GTX 980||4||2048||17.5||84.2||101.7||MRT
|-
|Intel(R) Xeon(R) W-2255 CPU @ 3.70GHz||NVIDIA Quadro P2000||5||1024||14.2||96||110.2||BL-DT01001
|-
|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz ||NVIDIA Quadro P2000||5||1024||15.8||100.1||115.9||CR2
|-
|Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz ||NVIDIA GeForce GTX 690||2||3072||18.4||114.4||132.8||MAV
|-
|AMD Ryzen Threadripper 1950X 16-Core Processor ||NVIDIA GeForce GTX 960||4||1024||18.6||123.3||141.6||CEV
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA GeForce GTX 960||4||1024||19.9||127.2||147.1||VHD
|-
|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz||NVIDIA GeForce GTX 1050 Ti||4||768||21.1||133.8||154.9||MJS
|-
|Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz||NVIDIA GeForce GTX 1050||2||640||20.6||139.1||159.7||JM2
|-
|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz||NVIDIA Quadro P2000||5||1024||22.1||142.5||164.6||KTC
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz||NVIDIA Quadro P2000||5||1024||23.0||149.3||172.3||RL2
|-
|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz||NVIDIA Quadro M2200||4||1024||23.2||198.7||222.0||GYB
|-
|Intel(R) Core(TM) i7-1185G7 @ 3.00GHz||NVIDIA T500||4||986||29.3||197.5||226.8||TJS
|-
|Intel(R) Xeon(R) E-2176M CPU @ 2.70GHz ||NVIDIA Quadro P1000||4||640||30.3||203.7||234.0||RL3
|-
|Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz ||NVIDIA Quadro K2200||4||640||32.5||211.3||243.8||JIW
|-
|Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz ||NVIDIA Quadro M1200||4||640||84.9||278.4||363.3||GHY
|-
|Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz ||NVIDIA GeForce GTX 940MX||2||384||65.6||479.0||544.6||EAS
|-
|Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz||NVIDIA GeForce 840M||2||384||70.6||526.3||595.9||CDH
|-
|Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Laptop)||NVIDIA GeForce GT 740M||2||384||102.3||694.0||796.3||HMM
|-
|}
 

=High End GPU Results=
A number of additional benchmarking tests have been completed on a 5m and 2.5m model on a single GPU card.

{| align="center" class="wikitable"
! style="background-color:#005581; font-weight:bold; color:white;" | Processor Name
! style="background-color:#005581; font-weight:bold; color:white;" width=24% | Graphics Card**
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | GPU RAM (GB)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Number of CUDA Cores*
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Runtime 2.5m (mins)
! style="background-color:#005581; font-weight:bold; color:white;" width=8% | Combined Runtime (mins)
! style="background-color:#C5C5C5; font-weight:bold; color:white;" width=12% | System Name
|-
|13th Gen Intel(R) Core(TM) i9-13900KS (32 CPUs) @ 3.2GHz||NVIDIA GeForce RTX 4090||24||16384||103.3||811.2||914.5||JB1
|-
|13th Gen Intel(R) Core(TM) i9-13900K (32 CPUs) @ 3.0GHz||NVIDIA GeForce RTX 4090||24||16384||105.9||813.7||919.6||TA1
|-
|AMD Ryzen 9 7950X 16-Core Processor (32 CPUs) @ 4.5GHz ||NVIDIA GeForce RTX 4090||24||16384||108.2||821.5||929.7||PSM
|-
|AMD Ryzen 9 3900X 12-Core Processor (24 CPUs) @ 3.8GHz ||NVIDIA GeForce RTX 4090||24||16384||106.8||875.5||982.3||CR4
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor (32 CPUs) @ 3.5GHz ||NVIDIA RTX 6000 Ada Generation||48||18176||119.6||877.8||997.4||JG3
|-
|12th Gen Intel(R) Core(TM) i9-12900 (24 CPUs) @ 2.4GHz ||NVIDIA GeForce RTX 4080||16||9728||139.5||1115.1||1254.6||JM3
|-
|Intel(R) Xeon(R) CPU @ 2.30GHz ||NVIDIA Tesla V100||16||5120||155.2||1172.9||1328.1||FM-NODE: Tesla V100
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||155.5||1176.2||1331.7||JMM
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3090||24||10496||158||1192.2||1350.2||CH3
|-
|Intel(R) Core(TM) i9-10900F CPU @ 3.70GHz ||NVIDIA GeForce RTX 3090||24||10496||162.3||1192.4||1354.7||LJA
|-
|AMD Ryzen 9 5900X 12-Core Processor ||NVIDIA GeForce RTX 3080 Ti||12||10240||159.7||1216.2||1375.9||GP1
|-
|12th Gen Intel(R) Core(TM) i9-12900K ||NVIDIA GeForce RTX 3090||24||10496||160.9||1240||1400.9||DD2
|-
|Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz ||NVIDIA GeForce RTX 3090||24||10496||172.9||1249.8||1422.7||SIP
|-
|AMD Ryzen 9 3900X 12-Core Processor ||NVIDIA GeForce RTX 3080||10||8704||178.9||1363.9||1542.8||KW2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||203.8||1523.9||1727.7||ACH
|-
|AMD Ryzen Threadripper 2950X 16-Core Processor ||NVIDIA TITAN RTX||24||4608||201.2||1548.1||1749.3||JGR
|-
|Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||220.0||1634.5||1854.5||MA1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||222.2||1648.7||1870.9||JPI
|-
|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz ||NVIDIA GeForce RTX 2080 Ti||11||4352||215.9||1678.7||1894.6||PA2
|-
|Intel(R) Core(TM) i9-9900K CPU @ (5.10GHz) ||NVIDIA GeForce RTX 2080 (core 2100MHz, mem 8000MHz)||8||2944||241.2||1863.5||2104.7||RRB
|-
|AMD Ryzen 9 5950X 16-Core Processor ||NVIDIA GeForce RTX 3070||8||5888||248.7||1928.6||2177.3||JG2
|-
|Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz ||NVIDIA GeForce RTX 2080 SUPER||8||3072||257.3||1957.7||2215.0||RH2
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce RTX 2080||8||2944||275.1||2147.4||2422.5||PM2
|-
|AMD Ryzen Threadripper 2990WX 32-Core Processor ||NVIDIA TITAN Xp||12||3840||296.0||2218.4||2514.4||FLC
|-
|Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||298.9||2290.1||2589.0||JS1
|-
|Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.3||2345.1||2656.4||615
|-
|Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||310.3||2377.2||2687.5||RCD
|-
|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||308.7||2384.7||2693.4||RH1
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||311.9||2404.9||2716.7||PM1
|-
|Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz ||NVIDIA GeForce GTX 1080 Ti||11||3584||324.8||2475.3||2800.1||HNM
|-
|Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz ||NVIDIA GeForce GTX 1080||8||2560||439.0||3379.3||3818.2||BLK
|-
|Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz ||NVIDIA GeForce GTX 1070||8||1920||475.5||3788.2||4263.7||SKI
|-
|}
<pre> * it is noted that the number of CUDA cores is not provided as an output from the '''dxdiag''' command and this information has been sourced from the nvidia website.
** The output cpu.txt only provides the 'out of the box' processor speed. If you have overclocked your cpu and/or gpu, please send these details to TUFLOW Support so we can add the overclocked data in brackets. </pre>

{{Tips Navigation
|uplink=[[Hardware_Benchmarking_(2018-03-AA) | Back to TUFLOW Benchmarking]]
}}

1D Pits

2024-02-02T10:32:23Z

Angelos Livogiannis: /* UK Water Industry Research (UKWIR) Inlet Capture Tool */

=Introduction=
There are predominantly two types of stormwater pits (drains/gullies) used as inlets to collect overland runoff and transfer that water to the underlying drainage/culvert/pipe network;
* Grated inlets
* Kerb Inlets (side entry pits / lintel inlets).
This page of the Wiki describes how pit inlet data is incorporated into a TUFLOW model.

= Pit Inlet Types =
{|class="wikitable"
|-
! Inlet Type !! Example !! Description
|-
! Q
| [[File:Q pit inlet.jpg|thumb|none|300px|Depth-Discharge Pit or Channel]]|| width="300pt"|Depth-Discharge Pit or Channel, pit inlet inflow information is defined within TUFLOW via a user defined Pit Inlet Database and associated pit inlet curves. This approach allows for unlimited flexibility. Any pit design or configuration can be incorporated into a TUFLOW model if the inlet depth-discharge relationship is known.
|-
! R
| [[File:Side_Entry_pit.jpg|thumb|none|300px|Kerb Inlet]]|| width="300pt"|Kerb inlets, also know as side entry pits or lintels are common in Australia. The pit chamber can vary depending on overall depth, length and the addition of any haunched riser units.
|-
! C
| [[File:Circular pit inlet.jpg|thumb|none|300px|Circular Pit Inlet]]|| width="300pt"|Circular pit inlet
|-
! W
| [[File:Gully pit.jpg|thumb|none|300px|Grate (London, UK)]] || width="300pt"|Grates, also known as Gully Pits, are common in the United Kingdom and are generally a square grate on top of a circular chamber and a riser outlet. The outlet will then feed into a larger culvert that forms part of the larger urban drainage network.
|}

= Pit Inlet Data Sources =
Pit inlet depth-discharge data can be obtained from a variety of sources. The most common typically being from suppliers or local agencies who enforce consistent design standards within their jurisdiction. For demonstration purposes, examples from Sutherland Shire Council and Brisbane City Council are provided below.

== Sutherland Shire Council ==
The Sutherland Shire Council Urban Drainage Manual (1992) includes summary tables and graphs documenting pit grate and lintel capacity information (derived from Department of Main Roads testing). The guidelines are compatible with the standard pit grate and lintel design shown below: 
[[File: Pit_Inlet_Curves_SSC000.JPG|700px]] 
The capacity of a pit depends on three factors:
* The clear opening area of the grate
* The depth of water ponding over the grate
* The length of kerb inlet (lintel) opening
The following graphs summarise grate and lintel discharge estimates for a range of water depths and blockage factors, derived from the Sutherland Shire Council design standards. 
[[File: Pit_Inlet_Curves_SSC001.JPG|700px]]
[[File: Pit_Inlet_Curves_SSC002.JPG|700px]] 

The above graphs estimate unit length and area flow estimates. These unit values can be multiplied by real pit dimensions to define at site depth-discharge characteristics.

TUFLOW modelling requires the derivation of a unique depth-discharge curve for each pit type within the modelled area. An example is provided below for a single pit location. 

[[File: Pit_Inlet_Curves_SSC003.JPG|700px]]

== Brisbane City Council==
The pit inlet curve examples below originate from Brisbane City Council 8000 series standard drawings: https://www.brisbane.qld.gov.au/planning-building/planning-guidelines-tools/planning-guidelines/standard-drawings 
[[File: BCC_BSD-8077.JPG|border|700px]]
[[File: BCC_BSD-8051.JPG|border|700px]] 
[[File: BCC_BSD-8082.JPG|border|700px]]
[[File: BCC_BSD-8052.JPG|border|700px]] 

== South Australian Road Stormwater Drainage Inlets: Hydraulic Study (University of South Australia)==
The Urban Water Resources Centre (UWRC) at the University of South Australia conducted a comprehensive set of hydraulic studies, examining performance of the most common roads’ stormwater drainage inlets in use in South Australia. The study was carried out using the Centre's unique full-scale road surface drainage test rig. Links to the pipe inlets curves are provided in the following link and sections below: [https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/ Hydraulic Study (University of South Australia)]
=== Transport South Australia ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/transport-sa/ Transport South Australia Pit Inlet Curves]
=== City of Adelaide ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-adelaide/ City of Adelaide Pit Inlet Curves]
=== City of Campbelltown ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-campbeltown/ City of Campbelltown Pit Inlet Curves]
=== City of Charles Sturt ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-charles-sturt/ City of Charles Sturt Pit Inlet Curves]
=== City of Onkaparinga ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-onkaparinga/ City of Onkaparinga Pit Inlet Curves]
=== City of Playford ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-playford/ City of Playford Pit Inlet Curves]
=== City of Port Adelaide / Enfield ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-port-adelaideenfield/ City of Port Adelaide / Enfield Pit Inlet Curves]
=== City of Marion ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-marion/ City of Marion Pit Inlet Curves]
=== City of Mitcham ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-mitcham/ City of Mitcham Pit Inlet Curves]
=== City of Salisbury ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-salisbury/ City of Salisbury Pit Inlet Curves]
=== City of Tea Tree Gully ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-tea-tree-gully/ City of Tea Tree Gully Pit Inlet Curves]
=== City of West Torrens ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-west-torrens/ City of West Torrens Pit Inlet Curves]

== Page Under Construction (Section: Spacing of Road Gullies) ==
== Spacing of Road Gullies (UK standards: BS EN 124 and BS7903) ==
The following section describes the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 Spacing of Road Gullies] guidance (UK standards: '''BS EN 124''' and '''BS 7903''') which provides a method for determining road gulley capture rates.

The method depends on the following '''Hydraulic parameters:'''
* Longitudinal gradient, ''SL'', along the length of the scheme (expressed as fraction).

* Cross-fall, ''Sc'' (also expressed as a fraction).

* Manning’s roughness coefficient, ''n''. Usually ''n'' = 0.017 for a conventional road surface. Other values are given in the following '''Table 1'''. (For more details, please see Section: 5, Table 5.3N of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance]).

'''Table 1:''' Values of Manning's ''n''
 [[File:Table1N.jpg|750px|]] 

* The grating type (P, Q, R, S or T), or the size and angle of kerb inlet.

* The maximum allowable flow width (as shown below by ''B'' in m) against the kerb.
 [[File:Figures 1 2.jpg|850px|]] 

'''Calculation of Gully Flow Capture Rates based on Equations'''
 The equations given in Appendix C (p.g: 25) of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance] can be used to determine flow capture rates at different depths, to determine the depth-discharge curve for use within TUFLOW. The method requires the calculations of the flow capacity of the kerb channel and flow collection efficiency of the gully grate.
*As a first step, a gully grate type: P, Q, R, S or T should be selected. The selection of the grating type will determine the design value ''Gd'' (grating parameter) from '''Table 2'''. (For more details, please see Table A.2, Appendix A of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance]).

'''Table 2:''' Determination of grating type ''Gd''
 [[File:Determination of grating type.jpg|650px|]] 

*Road (longitudinal) gradient (''SL''), Crossfall (''Sc'') and Manning's (''n'') should then be determined. Parameter values can be obtained from '''Table 3'''.

'''Table 3:''' Determination of ''SL'', ''Sc'' and Manning's ''n''
 [[File:Table SL SC N Range.jpg|750px|]] 

*Further, a Water Depth against the kerb ''H'' (m) range should be provided. (Please note: The depth range can be changed, but the following equations that are used to calculate the flow capacity are only valid up to the kerb height).

*With the above parameters, the calculations of the i) Flow width (''B'' in m), ii) Cross-sectional area (''Af'' in m2), iii) Hydraulic radius (''R'' in m), iv) Flow rate (''Q'' in m3/s) and v) Flow collection efficiency (''ŋ'' (%)) based on the Equations C.1-C.5 which are presented in Appendix C of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance] can be completed.

*Finally, the resulting depth-discharge data can be used in the TUFLOW pit inlet curves. 

The Gully Flow Capture Rates template here:(Excel File) includes a calculation tab which can be used for the completion of the above calculation processes. Based on calculations and Equations C.6 and C.7 of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance] the maximum allowable spacings upstream of the gully can be further calculated (For more details, please see Appendix C, p.g: 25).

'''Key assumption''' '''Note:''' This method assumes that the route the flow takes around the trap limits the discharge from the gully pot to 10 l/s. This limit is effective in both directions, so any negative head on the gully would create -10 l/s flow back up through the gully and flood onto the road. 

== UK Water Industry Research (UKWIR) Inlet Capture Tool ==
In 2023, the UK Water Industry Research (UKWIR) Limited released the Modelling Sewer Inlet Capacity Restrictions Report [https://ukwir.org/modelling-sewer-inlet-capacity-restrictions Modelling Sewer Inlet Capacity Restrictions Report]. The main aim was to develop a sewer modelling methodology to enable the representation of inlet inflow restrictions, focusing on the development of a new 1D model approach to provide more accurate model sewer flooding predictions. The new modelling approach has been devised by combining the findings from a literature review and the development of semi-empirical relationships from academic studies which investigated factors affecting inlet capacity. The new approach allows for 2 types of gully response reflecting 2 flow conditions: Subcritical flow on a shallow road gradient and Supercritical flow on a steep road gradients. A threshold of 0.02 is used to distinguish between shallow and steep road gradients. The reported equations can be used for the production of input inlet curves for TUFLOW 1D pit inlet modelling.

A template for the generation of the UKWIR Inlet Curve can be downloaded from [https://downloads.tuflow.com/Other/Inlet_Spreadsheets/Inlet%20Curve%20Capture%20tool%20v4.xlsx here]. The template determines both Subcritical Head-Discharge and Supercritical Head-Discharge relationships obtained from the Modelling Sewer Inlet Capacity Restrictions Report based on user input values of water depth (in metres). Two sets of curves can be generated, curves based on default parameters, and those based on user-defined parameters.

== How to Translate On-Grade Approach Flow / Pit Capture Flow Curves to Depth / Discharge Curves for use in TUFLOW ==
Manning's equation calculations can be used to convert on-grade approach flow information to a water depth at the pit. After manually calculating the depth to flow relationship the user simply needs to associate these water depth values with the pit capture flow information typically included in on grade pit inlet curve datasets.

=TUFLOW Model Inputs=
The steps required to represent pit inlet information within a TUFLOW model is summarised below:
<ol>
<li> Import an empty 1d_nwk GIS file from the TUFLOW file template folder (model\gis\empty).
<li> Digitise points to represent pit locations. The points should be snapped to the start or end of 1d_nwk line features that define the underground pipe network.
<li> Update the field attributes for each Pit point. Refer to 5.12.2 of the 2016 TUFLOW Manual. The most commonly used attributes are:
* Type = Q (C, R and W are also options if pit inlets based on structure dimension is required instead of using a Pit Inlet Database approach).
* US_Invert = Used to specify the ground elevation of the pit. If Conn_1D_2D is set to “SXL”, US_Invert is used as the amount by which to lower the 2D cell and the pit channel invert is set to this level.
* DS_Invert = The bottom elevation of the pit. This input can also be used to set the upstream and downstream inverts of connected pipes/channels.
* Inlet_Type = For Q pit channels, the name of a pit inlet type in the Pit Inlet Database. Multiple Pits can use the same Inlet_Type ID if they have the same design dimensions.
* Conn_1D_2D = SXL can be specified to connect the 1D pit or node to the 2D domain and lower the 2D cell by the amount of the US_Invert attribute. The invert of the pit channel is set to the lowered 2D cell level. This is useful to help trap the water into the pit as it flows overland in the 2D domain. This feature works well in combination with the new Read GIS SA PITS option.
<li> Update the Estry Control File (*.ecf) to include reference to the new 1d_nwk GIS file. 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\Estry\1d_nwk_****.MIF</tt> 
<li> Create a Pit Inlet Database csv file. This file lists each type of pit (matching the names listed in the 1d_nwk "Inlet_Type" field). It also provides reference to the depth-discharge curve information. 
[[File:M05 pit inlet dbase 01.png]]
<li> Create the Source file referenced in the Pit Inlet Database. The source file defines the depth-discharge information for each pit (determined from the relevant design standards). The column headers must match the entries in the Pit Inlet Database. 
[[File:M05 pit inlet v2.png]]
<li> Update the Estry Control File (*.ecf) to include reference to the Pit Inlet Database. 
<tt>Pit Inlet Database</tt> <tt>==</tt><tt>..\pit_dbase\EG_pit_dbase.csv</tt> 
</ol>

An example model including Pits is available for download: https://wiki.tuflow.com/index.php?title=TUFLOW_Example_Models

==Pit Search Distance==
Some agency pit datasets may not have all pit point features snapped to the associated pipe line features. The *.ecf command "Pit Search Distance" can be useful in this instance. It automatically connects floating nodes to the 1D pipe network where connectors are not snapped to channel ends: 

<tt>Pit Search Distance</tt> <tt>==</tt><tt>xxx</tt> 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\1d_nwke_*****.MIF</tt> 
 
The order of the "Pit Search Distance" command is important as it can be repeated multiple times with different values that are assigned to the 1d_nwke(s) below the ''Pit Search Distance'' command. The pit search command should be included above the the GIS layer containing the pits.

To check if the ''Pit Search Distance'' is working as expected, import the [[Check_Files_1d_nwk_C | *_nwk_C_check]] file to visually see if the pits are automatically connecting to a culvert. The image below is an example of the *_nwk_C_check file and the connections TUFLOW has made to each pit. 

 
[[File:Pit_search_distance_check.JPG|border|500px]]

 
Any further questions please email TUFLOW support: [mailto:support@tuflow.com?Subject=TUFLOW%201D%20pits%20help support@tuflow.com]
 
{{Tips Navigation
|uplink=[[ TUFLOW 1D Channels and Hydraulic Structures | Back to 1D Channels and Hydraulic Structures]]
}}

1D Pits

2024-01-31T12:54:56Z

Angelos Livogiannis: /* Spacing of Road Gullies (UK standards: BS EN 124 and BS7903) */

=Introduction=
There are predominantly two types of stormwater pits (drains/gullies) used as inlets to collect overland runoff and transfer that water to the underlying drainage/culvert/pipe network;
* Grated inlets
* Kerb Inlets (side entry pits / lintel inlets).
This page of the Wiki describes how pit inlet data is incorporated into a TUFLOW model.

= Pit Inlet Types =
{|class="wikitable"
|-
! Inlet Type !! Example !! Description
|-
! Q
| [[File:Q pit inlet.jpg|thumb|none|300px|Depth-Discharge Pit or Channel]]|| width="300pt"|Depth-Discharge Pit or Channel, pit inlet inflow information is defined within TUFLOW via a user defined Pit Inlet Database and associated pit inlet curves. This approach allows for unlimited flexibility. Any pit design or configuration can be incorporated into a TUFLOW model if the inlet depth-discharge relationship is known.
|-
! R
| [[File:Side_Entry_pit.jpg|thumb|none|300px|Kerb Inlet]]|| width="300pt"|Kerb inlets, also know as side entry pits or lintels are common in Australia. The pit chamber can vary depending on overall depth, length and the addition of any haunched riser units.
|-
! C
| [[File:Circular pit inlet.jpg|thumb|none|300px|Circular Pit Inlet]]|| width="300pt"|Circular pit inlet
|-
! W
| [[File:Gully pit.jpg|thumb|none|300px|Grate (London, UK)]] || width="300pt"|Grates, also known as Gully Pits, are common in the United Kingdom and are generally a square grate on top of a circular chamber and a riser outlet. The outlet will then feed into a larger culvert that forms part of the larger urban drainage network.
|}

= Pit Inlet Data Sources =
Pit inlet depth-discharge data can be obtained from a variety of sources. The most common typically being from suppliers or local agencies who enforce consistent design standards within their jurisdiction. For demonstration purposes, examples from Sutherland Shire Council and Brisbane City Council are provided below.

== Sutherland Shire Council ==
The Sutherland Shire Council Urban Drainage Manual (1992) includes summary tables and graphs documenting pit grate and lintel capacity information (derived from Department of Main Roads testing). The guidelines are compatible with the standard pit grate and lintel design shown below: 
[[File: Pit_Inlet_Curves_SSC000.JPG|700px]] 
The capacity of a pit depends on three factors:
* The clear opening area of the grate
* The depth of water ponding over the grate
* The length of kerb inlet (lintel) opening
The following graphs summarise grate and lintel discharge estimates for a range of water depths and blockage factors, derived from the Sutherland Shire Council design standards. 
[[File: Pit_Inlet_Curves_SSC001.JPG|700px]]
[[File: Pit_Inlet_Curves_SSC002.JPG|700px]] 

The above graphs estimate unit length and area flow estimates. These unit values can be multiplied by real pit dimensions to define at site depth-discharge characteristics.

TUFLOW modelling requires the derivation of a unique depth-discharge curve for each pit type within the modelled area. An example is provided below for a single pit location. 

[[File: Pit_Inlet_Curves_SSC003.JPG|700px]]

== Brisbane City Council==
The pit inlet curve examples below originate from Brisbane City Council 8000 series standard drawings: https://www.brisbane.qld.gov.au/planning-building/planning-guidelines-tools/planning-guidelines/standard-drawings 
[[File: BCC_BSD-8077.JPG|border|700px]]
[[File: BCC_BSD-8051.JPG|border|700px]] 
[[File: BCC_BSD-8082.JPG|border|700px]]
[[File: BCC_BSD-8052.JPG|border|700px]] 

== South Australian Road Stormwater Drainage Inlets: Hydraulic Study (University of South Australia)==
The Urban Water Resources Centre (UWRC) at the University of South Australia conducted a comprehensive set of hydraulic studies, examining performance of the most common roads’ stormwater drainage inlets in use in South Australia. The study was carried out using the Centre's unique full-scale road surface drainage test rig. Links to the pipe inlets curves are provided in the following link and sections below: [https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/ Hydraulic Study (University of South Australia)]
=== Transport South Australia ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/transport-sa/ Transport South Australia Pit Inlet Curves]
=== City of Adelaide ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-adelaide/ City of Adelaide Pit Inlet Curves]
=== City of Campbelltown ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-campbeltown/ City of Campbelltown Pit Inlet Curves]
=== City of Charles Sturt ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-charles-sturt/ City of Charles Sturt Pit Inlet Curves]
=== City of Onkaparinga ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-onkaparinga/ City of Onkaparinga Pit Inlet Curves]
=== City of Playford ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-playford/ City of Playford Pit Inlet Curves]
=== City of Port Adelaide / Enfield ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-port-adelaideenfield/ City of Port Adelaide / Enfield Pit Inlet Curves]
=== City of Marion ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-marion/ City of Marion Pit Inlet Curves]
=== City of Mitcham ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-mitcham/ City of Mitcham Pit Inlet Curves]
=== City of Salisbury ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-salisbury/ City of Salisbury Pit Inlet Curves]
=== City of Tea Tree Gully ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-tea-tree-gully/ City of Tea Tree Gully Pit Inlet Curves]
=== City of West Torrens ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-west-torrens/ City of West Torrens Pit Inlet Curves]

== Page Under Construction (Section: Spacing of Road Gullies) ==
== Spacing of Road Gullies (UK standards: BS EN 124 and BS7903) ==
The following section describes the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 Spacing of Road Gullies] guidance (UK standards: '''BS EN 124''' and '''BS 7903''') which provides a method for determining road gulley capture rates.

The method depends on the following '''Hydraulic parameters:'''
* Longitudinal gradient, ''SL'', along the length of the scheme (expressed as fraction).

* Cross-fall, ''Sc'' (also expressed as a fraction).

* Manning’s roughness coefficient, ''n''. Usually ''n'' = 0.017 for a conventional road surface. Other values are given in the following '''Table 1'''. (For more details, please see Section: 5, Table 5.3N of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance]).

'''Table 1:''' Values of Manning's ''n''
 [[File:Table1N.jpg|750px|]] 

* The grating type (P, Q, R, S or T), or the size and angle of kerb inlet.

* The maximum allowable flow width (as shown below by ''B'' in m) against the kerb.
 [[File:Figures 1 2.jpg|850px|]] 

'''Calculation of Gully Flow Capture Rates based on Equations'''
 The equations given in Appendix C (p.g: 25) of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance] can be used to determine flow capture rates at different depths, to determine the depth-discharge curve for use within TUFLOW. The method requires the calculations of the flow capacity of the kerb channel and flow collection efficiency of the gully grate.
*As a first step, a gully grate type: P, Q, R, S or T should be selected. The selection of the grating type will determine the design value ''Gd'' (grating parameter) from '''Table 2'''. (For more details, please see Table A.2, Appendix A of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance]).

'''Table 2:''' Determination of grating type ''Gd''
 [[File:Determination of grating type.jpg|650px|]] 

*Road (longitudinal) gradient (''SL''), Crossfall (''Sc'') and Manning's (''n'') should then be determined. Parameter values can be obtained from '''Table 3'''.

'''Table 3:''' Determination of ''SL'', ''Sc'' and Manning's ''n''
 [[File:Table SL SC N Range.jpg|750px|]] 

*Further, a Water Depth against the kerb ''H'' (m) range should be provided. (Please note: The depth range can be changed, but the following equations that are used to calculate the flow capacity are only valid up to the kerb height).

*With the above parameters, the calculations of the i) Flow width (''B'' in m), ii) Cross-sectional area (''Af'' in m2), iii) Hydraulic radius (''R'' in m), iv) Flow rate (''Q'' in m3/s) and v) Flow collection efficiency (''ŋ'' (%)) based on the Equations C.1-C.5 which are presented in Appendix C of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance] can be completed.

*Finally, the resulting depth-discharge data can be used in the TUFLOW pit inlet curves. 

The Gully Flow Capture Rates template here:(Excel File) includes a calculation tab which can be used for the completion of the above calculation processes. Based on calculations and Equations C.6 and C.7 of the [https://www.standardsforhighways.co.uk/tses/attachments/a869ed8e-4470-4286-aef4-7d11af24a597 guidance] the maximum allowable spacings upstream of the gully can be further calculated (For more details, please see Appendix C, p.g: 25).

'''Key assumption''' '''Note:''' This method assumes that the route the flow takes around the trap limits the discharge from the gully pot to 10 l/s. This limit is effective in both directions, so any negative head on the gully would create -10 l/s flow back up through the gully and flood onto the road. 

== UK Water Industry Research (UKWIR) Inlet Capture Tool ==
In 2023, the UK Water Industry Research (UKWIR) Limited released the Modelling Sewer Inlet Capacity Restrictions Report [https://ukwir.org/modelling-sewer-inlet-capacity-restrictions/ Modelling Sewer Inlet Capacity Restrictions Report]. The main aim was to develop a sewer modelling methodology to enable the representation of inlet inflow restrictions, focusing on the development of a new 1D model approach to provide more accurate model sewer flooding predictions. The new modelling approach has been devised by combining the findings from a literature review and the development of semi-empirical relationships from academic studies which investigated factors affecting inlet capacity. The new approach allows for 2 types of gully response reflecting 2 flow conditions: Subcritical flow on a shallow road gradient and Supercritical flow on a steep road gradients. A threshold of 0.02 is used to distinguish between shallow and steep road gradients. The reported equations can be used for the production of input inlet curves for TUFLOW 1D pit inlet modelling.

A template for the generation of the UKWIR Inlet Curve can be downloaded from [https://downloads.tuflow.com/Other/Inlet_Spreadsheets/Inlet%20Curve%20Capture%20tool%20v4.xlsx here]. The template determines both Subcritical Head-Discharge and Supercritical Head-Discharge relationships obtained from the Modelling Sewer Inlet Capacity Restrictions Report based on user input values of water depth (in metres). Two sets of curves can be generated, curves based on default parameters, and those based on user-defined parameters.

== How to Translate On-Grade Approach Flow / Pit Capture Flow Curves to Depth / Discharge Curves for use in TUFLOW ==
Manning's equation calculations can be used to convert on-grade approach flow information to a water depth at the pit. After manually calculating the depth to flow relationship the user simply needs to associate these water depth values with the pit capture flow information typically included in on grade pit inlet curve datasets.

=TUFLOW Model Inputs=
The steps required to represent pit inlet information within a TUFLOW model is summarised below:
<ol>
<li> Import an empty 1d_nwk GIS file from the TUFLOW file template folder (model\gis\empty).
<li> Digitise points to represent pit locations. The points should be snapped to the start or end of 1d_nwk line features that define the underground pipe network.
<li> Update the field attributes for each Pit point. Refer to 5.12.2 of the 2016 TUFLOW Manual. The most commonly used attributes are:
* Type = Q (C, R and W are also options if pit inlets based on structure dimension is required instead of using a Pit Inlet Database approach).
* US_Invert = Used to specify the ground elevation of the pit. If Conn_1D_2D is set to “SXL”, US_Invert is used as the amount by which to lower the 2D cell and the pit channel invert is set to this level.
* DS_Invert = The bottom elevation of the pit. This input can also be used to set the upstream and downstream inverts of connected pipes/channels.
* Inlet_Type = For Q pit channels, the name of a pit inlet type in the Pit Inlet Database. Multiple Pits can use the same Inlet_Type ID if they have the same design dimensions.
* Conn_1D_2D = SXL can be specified to connect the 1D pit or node to the 2D domain and lower the 2D cell by the amount of the US_Invert attribute. The invert of the pit channel is set to the lowered 2D cell level. This is useful to help trap the water into the pit as it flows overland in the 2D domain. This feature works well in combination with the new Read GIS SA PITS option.
<li> Update the Estry Control File (*.ecf) to include reference to the new 1d_nwk GIS file. 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\Estry\1d_nwk_****.MIF</tt> 
<li> Create a Pit Inlet Database csv file. This file lists each type of pit (matching the names listed in the 1d_nwk "Inlet_Type" field). It also provides reference to the depth-discharge curve information. 
[[File:M05 pit inlet dbase 01.png]]
<li> Create the Source file referenced in the Pit Inlet Database. The source file defines the depth-discharge information for each pit (determined from the relevant design standards). The column headers must match the entries in the Pit Inlet Database. 
[[File:M05 pit inlet v2.png]]
<li> Update the Estry Control File (*.ecf) to include reference to the Pit Inlet Database. 
<tt>Pit Inlet Database</tt> <tt>==</tt><tt>..\pit_dbase\EG_pit_dbase.csv</tt> 
</ol>

An example model including Pits is available for download: https://wiki.tuflow.com/index.php?title=TUFLOW_Example_Models

==Pit Search Distance==
Some agency pit datasets may not have all pit point features snapped to the associated pipe line features. The *.ecf command "Pit Search Distance" can be useful in this instance. It automatically connects floating nodes to the 1D pipe network where connectors are not snapped to channel ends: 

<tt>Pit Search Distance</tt> <tt>==</tt><tt>xxx</tt> 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\1d_nwke_*****.MIF</tt> 
 
The order of the "Pit Search Distance" command is important as it can be repeated multiple times with different values that are assigned to the 1d_nwke(s) below the ''Pit Search Distance'' command. The pit search command should be included above the the GIS layer containing the pits.

To check if the ''Pit Search Distance'' is working as expected, import the [[Check_Files_1d_nwk_C | *_nwk_C_check]] file to visually see if the pits are automatically connecting to a culvert. The image below is an example of the *_nwk_C_check file and the connections TUFLOW has made to each pit. 

 
[[File:Pit_search_distance_check.JPG|border|500px]]

 
Any further questions please email TUFLOW support: [mailto:support@tuflow.com?Subject=TUFLOW%201D%20pits%20help support@tuflow.com]
 
{{Tips Navigation
|uplink=[[ TUFLOW 1D Channels and Hydraulic Structures | Back to 1D Channels and Hydraulic Structures]]
}}

File:Table1N.jpg

2024-01-31T10:47:08Z

Angelos Livogiannis:

Table5.3N:Values of Manning's n

1D Pits

2024-01-30T11:33:38Z

Angelos Livogiannis: /* Spacing of Road Gullies (UK adoption BS EN 124 and BS7903) */

=Introduction=
There are predominantly two types of stormwater pits (drains/gullies) used as inlets to collect overland runoff and transfer that water to the underlying drainage/culvert/pipe network;
* Grated inlets
* Kerb Inlets (side entry pits / lintel inlets).
This page of the Wiki describes how pit inlet data is incorporated into a TUFLOW model.

= Pit Inlet Types =
{|class="wikitable"
|-
! Inlet Type !! Example !! Description
|-
! Q
| [[File:Q pit inlet.jpg|thumb|none|300px|Depth-Discharge Pit or Channel]]|| width="300pt"|Depth-Discharge Pit or Channel, pit inlet inflow information is defined within TUFLOW via a user defined Pit Inlet Database and associated pit inlet curves. This approach allows for unlimited flexibility. Any pit design or configuration can be incorporated into a TUFLOW model if the inlet depth-discharge relationship is known.
|-
! R
| [[File:Side_Entry_pit.jpg|thumb|none|300px|Kerb Inlet]]|| width="300pt"|Kerb inlets, also know as side entry pits or lintels are common in Australia. The pit chamber can vary depending on overall depth, length and the addition of any haunched riser units.
|-
! C
| [[File:Circular pit inlet.jpg|thumb|none|300px|Circular Pit Inlet]]|| width="300pt"|Circular pit inlet
|-
! W
| [[File:Gully pit.jpg|thumb|none|300px|Grate (London, UK)]] || width="300pt"|Grates, also known as Gully Pits, are common in the United Kingdom and are generally a square grate on top of a circular chamber and a riser outlet. The outlet will then feed into a larger culvert that forms part of the larger urban drainage network.
|}

= Pit Inlet Data Sources =
Pit inlet depth-discharge data can be obtained from a variety of sources. The most common typically being from suppliers or local agencies who enforce consistent design standards within their jurisdiction. For demonstration purposes, examples from Sutherland Shire Council and Brisbane City Council are provided below.

== Sutherland Shire Council ==
The Sutherland Shire Council Urban Drainage Manual (1992) includes summary tables and graphs documenting pit grate and lintel capacity information (derived from Department of Main Roads testing). The guidelines are compatible with the standard pit grate and lintel design shown below: 
[[File: Pit_Inlet_Curves_SSC000.JPG|700px]] 
The capacity of a pit depends on three factors:
* The clear opening area of the grate
* The depth of water ponding over the grate
* The length of kerb inlet (lintel) opening
The following graphs summarise grate and lintel discharge estimates for a range of water depths and blockage factors, derived from the Sutherland Shire Council design standards. 
[[File: Pit_Inlet_Curves_SSC001.JPG|700px]]
[[File: Pit_Inlet_Curves_SSC002.JPG|700px]] 

The above graphs estimate unit length and area flow estimates. These unit values can be multiplied by real pit dimensions to define at site depth-discharge characteristics.

TUFLOW modelling requires the derivation of a unique depth-discharge curve for each pit type within the modelled area. An example is provided below for a single pit location. 

[[File: Pit_Inlet_Curves_SSC003.JPG|700px]]

== Brisbane City Council==
The pit inlet curve examples below originate from Brisbane City Council 8000 series standard drawings: https://www.brisbane.qld.gov.au/planning-building/planning-guidelines-tools/planning-guidelines/standard-drawings 
[[File: BCC_BSD-8077.JPG|border|700px]]
[[File: BCC_BSD-8051.JPG|border|700px]] 
[[File: BCC_BSD-8082.JPG|border|700px]]
[[File: BCC_BSD-8052.JPG|border|700px]] 

== South Australian Road Stormwater Drainage Inlets: Hydraulic Study (University of South Australia)==
The Urban Water Resources Centre (UWRC) at the University of South Australia conducted a comprehensive set of hydraulic studies, examining performance of the most common roads’ stormwater drainage inlets in use in South Australia. The study was carried out using the Centre's unique full-scale road surface drainage test rig. Links to the pipe inlets curves are provided in the following link and sections below: [https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/ Hydraulic Study (University of South Australia)]
=== Transport South Australia ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/transport-sa/ Transport South Australia Pit Inlet Curves]
=== City of Adelaide ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-adelaide/ City of Adelaide Pit Inlet Curves]
=== City of Campbelltown ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-campbeltown/ City of Campbelltown Pit Inlet Curves]
=== City of Charles Sturt ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-charles-sturt/ City of Charles Sturt Pit Inlet Curves]
=== City of Onkaparinga ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-onkaparinga/ City of Onkaparinga Pit Inlet Curves]
=== City of Playford ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-playford/ City of Playford Pit Inlet Curves]
=== City of Port Adelaide / Enfield ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-port-adelaideenfield/ City of Port Adelaide / Enfield Pit Inlet Curves]
=== City of Marion ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-marion/ City of Marion Pit Inlet Curves]
=== City of Mitcham ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-mitcham/ City of Mitcham Pit Inlet Curves]
=== City of Salisbury ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-salisbury/ City of Salisbury Pit Inlet Curves]
=== City of Tea Tree Gully ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-tea-tree-gully/ City of Tea Tree Gully Pit Inlet Curves]
=== City of West Torrens ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-west-torrens/ City of West Torrens Pit Inlet Curves]

== Page Under Construction (Section: Spacing of Road Gullies) ==
== Spacing of Road Gullies (UK standards: BS EN 124 and BS7903) ==
The following section describes the method to determine the spacing of road gratings, according to the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf Spacing of Road Gullies] guidance (UK standards: '''BS EN 124''' and '''BS 7903''').

The method depends on the following '''Hydraulic parameters:'''
* Longitudinal gradient, ''SL'', along the length of the scheme (expressed as fraction).

* Cross-fall, ''Sc'' (also expressed as a fraction).

* Manning’s roughness coefficient, ''n''. Usually ''n'' = 0.017 for a conventional road surface. Other values are given in the following '''Table 1'''. (For more details, please see Section: 4.3, Table 1 of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance]).

'''Table 1:''' Values of Manning's ''n''
 [[File:Table1.jpg|450px|]] 

* The grating type (P, Q, R, S or T), or the size and angle of kerb inlet.

* The maximum allowable flow width (as shown below by ''B'' in m) against the kerb.
 [[File:Figures 1 2.jpg|850px|]] 

'''A) Use of Tables for determining the flow capacity of gullies and maximum spacings for gully gratings''' 
Equations given in Section 5 of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance] are used for the calculation of the Spacing of Road Gullies. Design tables have been compiled to present a quick design approach. Tables can be found in Annex C.
Annex C includes design tables for the grating types: Types P, Q, R, S and T. The Design Tables C2-C6 in Annex C of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance] present the area that can be drained for an intermediate gully and a range of crossfall and gradient of flow widths. For the design tables a rainfall intensity of 50mm/h and Manning’s ''n'' = 0.017 are considered.

For ease of access, Tables C2-C6 are replicated in the Spacing of Road Gullies file here [Excel File]. Please see, tabs: Type P, Type Q, Type R, Type S and Type T. The Excel file provides tables like the following examples and their corresponding graphs.
 [[File:Tables C2-C6 of Annex C.jpg|950px|]] 

 '''Note:''' a) ''Tables C2 to C6 are for intermediate gullies on a uniform gradient and are not strictly accurate for gradients which vary greatly over short distances.''
b)''The Excel tables also present the flow collection efficiency η of the grating in % (in brackets)''. 

'''B) Calculation of Gully Spacings based on Equations'''
 Alternatively, the equations given in Sections 5 of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance] can be used for the Spacing of Road Gullies, directly. The method requires the calculations of the Flow capacity of the kerb channel and Flow collection efficiency of the gully grating.
*As a first step, a gully grate type: P, Q, R, S or T should be selected. The selection of the grating Type will determine the design value ''Gd'' (grating parameter) from '''Table 2'''. (For more details, please see Annex B of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance]).

'''Table 2:''' Determination of grating type ''Gd''
 [[File:Determination of grating type.jpg|650px|]] 

'''Note:''' ''According to the manual: The value of Gd should be used to calculate the maximum spacing between gullies.''

*Road (longitudinal) gradient (''SL''), Crossfall (''Sc'') and Manning's (''n'') should then be determined. Parameter values can be obtained from '''Table 3'''.

'''Table 3:''' Determination of ''SL'', ''Sc'' and Manning's ''n''
 [[File:Table SL SC N Range.jpg|750px|]] 

*Further, a Water Depth against the kerb ''H'' (m) range should be provided. (Please note: The depth range can be changed, but the following equations that are used to calculate the flow capacity are only valid up to the kerb height).

*With the above parameters, the calculations of i) The Flow width (''B'' in m), ii) the Cross-sectional area (''Af'' in m2), iii) Hydraulic radius (''R'' in m), iv) Flow rate (''Q'' in m3/s) and v) Flow collection efficiency (''ŋ'' (%)) based on the Equations 6-10 which are presented in Section 5 of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance] can be completed.

*Finally, the resulting depth-discharge data can be used in the pit inlet curves. 

The Spacing of Road Gullies Excel file above includes a calculation tab which can be used for the completion of the calculation process. Based on calculations and Equations (11) and (12) of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance] the maximum spacings for gully grating can be calculated.

'''Key assumption''' '''Note:''' This method assumes that the route the flow takes around the trap limits the discharge from the gully pot to 10 l/s. This limit is effective in both directions, so any number of negative head on the gully would create -10 l/s flow back up through the gully and flood onto the road. 

== UK Water Industry Research (UKWIR) Inlet Capture Tool ==
In 2023, the UK Water Industry Research (UKWIR) Limited released the Modelling Sewer Inlet Capacity Restrictions Report [https://ukwir.org/modelling-sewer-inlet-capacity-restrictions/ Modelling Sewer Inlet Capacity Restrictions Report]. The main aim was to develop a sewer modelling methodology to enable the representation of inlet inflow restrictions, focusing on the development of a new 1D model approach to provide more accurate model sewer flooding predictions. The new modelling approach has been devised by combining the findings from a literature review and the development of semi-empirical relationships from academic studies which investigated factors affecting inlet capacity. The new approach allows for 2 types of gully response reflecting 2 flow conditions: Subcritical flow on a shallow road gradient and Supercritical flow on a steep road gradients. A threshold of 0.02 is used to distinguish between shallow and steep road gradients. The reported equations can be used for the production of input inlet curves for TUFLOW 1D pit inlet modelling.

A template for the generation of the UKWIR Inlet Curve can be downloaded from [https://downloads.tuflow.com/Other/Inlet_Spreadsheets/Inlet%20Curve%20Capture%20tool%20v4.xlsx here]. The template determines both Subcritical Head-Discharge and Supercritical Head-Discharge relationships obtained from the Modelling Sewer Inlet Capacity Restrictions Report based on user input values of water depth (in metres). Two sets of curves can be generated, curves based on default parameters, and those based on user-defined parameters.

== How to Translate On-Grade Approach Flow / Pit Capture Flow Curves to Depth / Discharge Curves for use in TUFLOW ==
Manning's equation calculations can be used to convert on-grade approach flow information to a water depth at the pit. After manually calculating the depth to flow relationship the user simply needs to associate these water depth values with the pit capture flow information typically included in on grade pit inlet curve datasets.

=TUFLOW Model Inputs=
The steps required to represent pit inlet information within a TUFLOW model is summarised below:
<ol>
<li> Import an empty 1d_nwk GIS file from the TUFLOW file template folder (model\gis\empty).
<li> Digitise points to represent pit locations. The points should be snapped to the start or end of 1d_nwk line features that define the underground pipe network.
<li> Update the field attributes for each Pit point. Refer to 5.12.2 of the 2016 TUFLOW Manual. The most commonly used attributes are:
* Type = Q (C, R and W are also options if pit inlets based on structure dimension is required instead of using a Pit Inlet Database approach).
* US_Invert = Used to specify the ground elevation of the pit. If Conn_1D_2D is set to “SXL”, US_Invert is used as the amount by which to lower the 2D cell and the pit channel invert is set to this level.
* DS_Invert = The bottom elevation of the pit. This input can also be used to set the upstream and downstream inverts of connected pipes/channels.
* Inlet_Type = For Q pit channels, the name of a pit inlet type in the Pit Inlet Database. Multiple Pits can use the same Inlet_Type ID if they have the same design dimensions.
* Conn_1D_2D = SXL can be specified to connect the 1D pit or node to the 2D domain and lower the 2D cell by the amount of the US_Invert attribute. The invert of the pit channel is set to the lowered 2D cell level. This is useful to help trap the water into the pit as it flows overland in the 2D domain. This feature works well in combination with the new Read GIS SA PITS option.
<li> Update the Estry Control File (*.ecf) to include reference to the new 1d_nwk GIS file. 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\Estry\1d_nwk_****.MIF</tt> 
<li> Create a Pit Inlet Database csv file. This file lists each type of pit (matching the names listed in the 1d_nwk "Inlet_Type" field). It also provides reference to the depth-discharge curve information. 
[[File:M05 pit inlet dbase 01.png]]
<li> Create the Source file referenced in the Pit Inlet Database. The source file defines the depth-discharge information for each pit (determined from the relevant design standards). The column headers must match the entries in the Pit Inlet Database. 
[[File:M05 pit inlet v2.png]]
<li> Update the Estry Control File (*.ecf) to include reference to the Pit Inlet Database. 
<tt>Pit Inlet Database</tt> <tt>==</tt><tt>..\pit_dbase\EG_pit_dbase.csv</tt> 
</ol>

An example model including Pits is available for download: https://wiki.tuflow.com/index.php?title=TUFLOW_Example_Models

==Pit Search Distance==
Some agency pit datasets may not have all pit point features snapped to the associated pipe line features. The *.ecf command "Pit Search Distance" can be useful in this instance. It automatically connects floating nodes to the 1D pipe network where connectors are not snapped to channel ends: 

<tt>Pit Search Distance</tt> <tt>==</tt><tt>xxx</tt> 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\1d_nwke_*****.MIF</tt> 
 
The order of the "Pit Search Distance" command is important as it can be repeated multiple times with different values that are assigned to the 1d_nwke(s) below the ''Pit Search Distance'' command. The pit search command should be included above the the GIS layer containing the pits.

To check if the ''Pit Search Distance'' is working as expected, import the [[Check_Files_1d_nwk_C | *_nwk_C_check]] file to visually see if the pits are automatically connecting to a culvert. The image below is an example of the *_nwk_C_check file and the connections TUFLOW has made to each pit. 

 
[[File:Pit_search_distance_check.JPG|border|500px]]

 
Any further questions please email TUFLOW support: [mailto:support@tuflow.com?Subject=TUFLOW%201D%20pits%20help support@tuflow.com]
 
{{Tips Navigation
|uplink=[[ TUFLOW 1D Channels and Hydraulic Structures | Back to 1D Channels and Hydraulic Structures]]
}}

1D Pits

2024-01-30T11:26:44Z

Angelos Livogiannis:

=Introduction=
There are predominantly two types of stormwater pits (drains/gullies) used as inlets to collect overland runoff and transfer that water to the underlying drainage/culvert/pipe network;
* Grated inlets
* Kerb Inlets (side entry pits / lintel inlets).
This page of the Wiki describes how pit inlet data is incorporated into a TUFLOW model.

= Pit Inlet Types =
{|class="wikitable"
|-
! Inlet Type !! Example !! Description
|-
! Q
| [[File:Q pit inlet.jpg|thumb|none|300px|Depth-Discharge Pit or Channel]]|| width="300pt"|Depth-Discharge Pit or Channel, pit inlet inflow information is defined within TUFLOW via a user defined Pit Inlet Database and associated pit inlet curves. This approach allows for unlimited flexibility. Any pit design or configuration can be incorporated into a TUFLOW model if the inlet depth-discharge relationship is known.
|-
! R
| [[File:Side_Entry_pit.jpg|thumb|none|300px|Kerb Inlet]]|| width="300pt"|Kerb inlets, also know as side entry pits or lintels are common in Australia. The pit chamber can vary depending on overall depth, length and the addition of any haunched riser units.
|-
! C
| [[File:Circular pit inlet.jpg|thumb|none|300px|Circular Pit Inlet]]|| width="300pt"|Circular pit inlet
|-
! W
| [[File:Gully pit.jpg|thumb|none|300px|Grate (London, UK)]] || width="300pt"|Grates, also known as Gully Pits, are common in the United Kingdom and are generally a square grate on top of a circular chamber and a riser outlet. The outlet will then feed into a larger culvert that forms part of the larger urban drainage network.
|}

= Pit Inlet Data Sources =
Pit inlet depth-discharge data can be obtained from a variety of sources. The most common typically being from suppliers or local agencies who enforce consistent design standards within their jurisdiction. For demonstration purposes, examples from Sutherland Shire Council and Brisbane City Council are provided below.

== Sutherland Shire Council ==
The Sutherland Shire Council Urban Drainage Manual (1992) includes summary tables and graphs documenting pit grate and lintel capacity information (derived from Department of Main Roads testing). The guidelines are compatible with the standard pit grate and lintel design shown below: 
[[File: Pit_Inlet_Curves_SSC000.JPG|700px]] 
The capacity of a pit depends on three factors:
* The clear opening area of the grate
* The depth of water ponding over the grate
* The length of kerb inlet (lintel) opening
The following graphs summarise grate and lintel discharge estimates for a range of water depths and blockage factors, derived from the Sutherland Shire Council design standards. 
[[File: Pit_Inlet_Curves_SSC001.JPG|700px]]
[[File: Pit_Inlet_Curves_SSC002.JPG|700px]] 

The above graphs estimate unit length and area flow estimates. These unit values can be multiplied by real pit dimensions to define at site depth-discharge characteristics.

TUFLOW modelling requires the derivation of a unique depth-discharge curve for each pit type within the modelled area. An example is provided below for a single pit location. 

[[File: Pit_Inlet_Curves_SSC003.JPG|700px]]

== Brisbane City Council==
The pit inlet curve examples below originate from Brisbane City Council 8000 series standard drawings: https://www.brisbane.qld.gov.au/planning-building/planning-guidelines-tools/planning-guidelines/standard-drawings 
[[File: BCC_BSD-8077.JPG|border|700px]]
[[File: BCC_BSD-8051.JPG|border|700px]] 
[[File: BCC_BSD-8082.JPG|border|700px]]
[[File: BCC_BSD-8052.JPG|border|700px]] 

== South Australian Road Stormwater Drainage Inlets: Hydraulic Study (University of South Australia)==
The Urban Water Resources Centre (UWRC) at the University of South Australia conducted a comprehensive set of hydraulic studies, examining performance of the most common roads’ stormwater drainage inlets in use in South Australia. The study was carried out using the Centre's unique full-scale road surface drainage test rig. Links to the pipe inlets curves are provided in the following link and sections below: [https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/ Hydraulic Study (University of South Australia)]
=== Transport South Australia ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/transport-sa/ Transport South Australia Pit Inlet Curves]
=== City of Adelaide ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-adelaide/ City of Adelaide Pit Inlet Curves]
=== City of Campbelltown ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-campbeltown/ City of Campbelltown Pit Inlet Curves]
=== City of Charles Sturt ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-charles-sturt/ City of Charles Sturt Pit Inlet Curves]
=== City of Onkaparinga ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-onkaparinga/ City of Onkaparinga Pit Inlet Curves]
=== City of Playford ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-playford/ City of Playford Pit Inlet Curves]
=== City of Port Adelaide / Enfield ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-port-adelaideenfield/ City of Port Adelaide / Enfield Pit Inlet Curves]
=== City of Marion ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-marion/ City of Marion Pit Inlet Curves]
=== City of Mitcham ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-mitcham/ City of Mitcham Pit Inlet Curves]
=== City of Salisbury ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-salisbury/ City of Salisbury Pit Inlet Curves]
=== City of Tea Tree Gully ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-tea-tree-gully/ City of Tea Tree Gully Pit Inlet Curves]
=== City of West Torrens ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-west-torrens/ City of West Torrens Pit Inlet Curves]

== Page Under Construction (Section: Spacing of Road Gullies) ==
== Spacing of Road Gullies (UK adoption BS EN 124 and BS7903) ==
The following section describes the method to determine the spacing of road gratings, according to the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf Spacing of Road Gullies] guidance ('''BS EN 124''' and '''BS 7903''').

The method depends on the following '''Hydraulic parameters:'''
* Longitudinal gradient, ''SL'', along the length of the scheme (expressed as fraction).

* Cross-fall, ''Sc'' (also expressed as a fraction).

* Manning’s roughness coefficient, ''n''. Usually ''n'' = 0.017 for a conventional road surface. Other values are given in the following '''Table 1'''. (For more details, please see Section: 4.3, Table 1 of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance]).

'''Table 1:''' Values of Manning's ''n''
 [[File:Table1.jpg|450px|]] 

* The grating type (P, Q, R, S or T), or the size and angle of kerb inlet.

* The maximum allowable flow width (as shown below by ''B'' in m) against the kerb.
 [[File:Figures 1 2.jpg|850px|]] 

'''A) Use of Tables for determining the flow capacity of gullies and maximum spacings for gully gratings''' 
Equations given in Section 5 of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance] are used for the calculation of the Spacing of Road Gullies. Design tables have been compiled to present a quick design approach. Tables can be found in Annex C.
Annex C includes design tables for the grating types: Types P, Q, R, S and T. The Design Tables C2-C6 in Annex C of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance] present the area that can be drained for an intermediate gully and a range of crossfall and gradient of flow widths. For the design tables a rainfall intensity of 50mm/h and Manning’s ''n'' = 0.017 are considered.

For ease of access, Tables C2-C6 are replicated in the Spacing of Road Gullies file here [Excel File]. Please see, tabs: Type P, Type Q, Type R, Type S and Type T. The Excel file provides tables like the following examples and their corresponding graphs.
 [[File:Tables C2-C6 of Annex C.jpg|950px|]] 

 '''Note:''' a) ''Tables C2 to C6 are for intermediate gullies on a uniform gradient and are not strictly accurate for gradients which vary greatly over short distances.''
b)''The Excel tables also present the flow collection efficiency η of the grating in % (in brackets)''. 

'''B) Calculation of Gully Spacings based on Equations'''
 Alternatively, the equations given in Sections 5 of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance] can be used for the Spacing of Road Gullies, directly. The method requires the calculations of the Flow capacity of the kerb channel and Flow collection efficiency of the gully grating.
*As a first step, a gully grate type: P, Q, R, S or T should be selected. The selection of the grating Type will determine the design value ''Gd'' (grating parameter) from '''Table 2'''. (For more details, please see Annex B of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance]).

'''Table 2:''' Determination of grating type ''Gd''
 [[File:Determination of grating type.jpg|650px|]] 

'''Note:''' ''According to the manual: The value of Gd should be used to calculate the maximum spacing between gullies.''

*Road (longitudinal) gradient (''SL''), Crossfall (''Sc'') and Manning's (''n'') should then be determined. Parameter values can be obtained from '''Table 3'''.

'''Table 3:''' Determination of ''SL'', ''Sc'' and Manning's ''n''
 [[File:Table SL SC N Range.jpg|750px|]] 

*Further, a Water Depth against the kerb ''H'' (m) range should be provided. (Please note: The depth range can be changed, but the following equations that are used to calculate the flow capacity are only valid up to the kerb height).

*With the above parameters, the calculations of i) The Flow width (''B'' in m), ii) the Cross-sectional area (''Af'' in m2), iii) Hydraulic radius (''R'' in m), iv) Flow rate (''Q'' in m3/s) and v) Flow collection efficiency (''ŋ'' (%)) based on the Equations 6-10 which are presented in Section 5 of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance] can be completed.

*Finally, the resulting depth-discharge data can be used in the pit inlet curves. 

The Spacing of Road Gullies Excel file above includes a calculation tab which can be used for the completion of the calculation process. Based on calculations and Equations (11) and (12) of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf guidance] the maximum spacings for gully grating can be calculated.

'''Key assumption''' '''Note:''' This method assumes that the route the flow takes around the trap limits the discharge from the gully pot to 10 l/s. This limit is effective in both directions, so any number of negative head on the gully would create -10 l/s flow back up through the gully and flood onto the road. 

== UK Water Industry Research (UKWIR) Inlet Capture Tool ==
In 2023, the UK Water Industry Research (UKWIR) Limited released the Modelling Sewer Inlet Capacity Restrictions Report [https://ukwir.org/modelling-sewer-inlet-capacity-restrictions/ Modelling Sewer Inlet Capacity Restrictions Report]. The main aim was to develop a sewer modelling methodology to enable the representation of inlet inflow restrictions, focusing on the development of a new 1D model approach to provide more accurate model sewer flooding predictions. The new modelling approach has been devised by combining the findings from a literature review and the development of semi-empirical relationships from academic studies which investigated factors affecting inlet capacity. The new approach allows for 2 types of gully response reflecting 2 flow conditions: Subcritical flow on a shallow road gradient and Supercritical flow on a steep road gradients. A threshold of 0.02 is used to distinguish between shallow and steep road gradients. The reported equations can be used for the production of input inlet curves for TUFLOW 1D pit inlet modelling.

A template for the generation of the UKWIR Inlet Curve can be downloaded from [https://downloads.tuflow.com/Other/Inlet_Spreadsheets/Inlet%20Curve%20Capture%20tool%20v4.xlsx here]. The template determines both Subcritical Head-Discharge and Supercritical Head-Discharge relationships obtained from the Modelling Sewer Inlet Capacity Restrictions Report based on user input values of water depth (in metres). Two sets of curves can be generated, curves based on default parameters, and those based on user-defined parameters.

== How to Translate On-Grade Approach Flow / Pit Capture Flow Curves to Depth / Discharge Curves for use in TUFLOW ==
Manning's equation calculations can be used to convert on-grade approach flow information to a water depth at the pit. After manually calculating the depth to flow relationship the user simply needs to associate these water depth values with the pit capture flow information typically included in on grade pit inlet curve datasets.

=TUFLOW Model Inputs=
The steps required to represent pit inlet information within a TUFLOW model is summarised below:
<ol>
<li> Import an empty 1d_nwk GIS file from the TUFLOW file template folder (model\gis\empty).
<li> Digitise points to represent pit locations. The points should be snapped to the start or end of 1d_nwk line features that define the underground pipe network.
<li> Update the field attributes for each Pit point. Refer to 5.12.2 of the 2016 TUFLOW Manual. The most commonly used attributes are:
* Type = Q (C, R and W are also options if pit inlets based on structure dimension is required instead of using a Pit Inlet Database approach).
* US_Invert = Used to specify the ground elevation of the pit. If Conn_1D_2D is set to “SXL”, US_Invert is used as the amount by which to lower the 2D cell and the pit channel invert is set to this level.
* DS_Invert = The bottom elevation of the pit. This input can also be used to set the upstream and downstream inverts of connected pipes/channels.
* Inlet_Type = For Q pit channels, the name of a pit inlet type in the Pit Inlet Database. Multiple Pits can use the same Inlet_Type ID if they have the same design dimensions.
* Conn_1D_2D = SXL can be specified to connect the 1D pit or node to the 2D domain and lower the 2D cell by the amount of the US_Invert attribute. The invert of the pit channel is set to the lowered 2D cell level. This is useful to help trap the water into the pit as it flows overland in the 2D domain. This feature works well in combination with the new Read GIS SA PITS option.
<li> Update the Estry Control File (*.ecf) to include reference to the new 1d_nwk GIS file. 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\Estry\1d_nwk_****.MIF</tt> 
<li> Create a Pit Inlet Database csv file. This file lists each type of pit (matching the names listed in the 1d_nwk "Inlet_Type" field). It also provides reference to the depth-discharge curve information. 
[[File:M05 pit inlet dbase 01.png]]
<li> Create the Source file referenced in the Pit Inlet Database. The source file defines the depth-discharge information for each pit (determined from the relevant design standards). The column headers must match the entries in the Pit Inlet Database. 
[[File:M05 pit inlet v2.png]]
<li> Update the Estry Control File (*.ecf) to include reference to the Pit Inlet Database. 
<tt>Pit Inlet Database</tt> <tt>==</tt><tt>..\pit_dbase\EG_pit_dbase.csv</tt> 
</ol>

An example model including Pits is available for download: https://wiki.tuflow.com/index.php?title=TUFLOW_Example_Models

==Pit Search Distance==
Some agency pit datasets may not have all pit point features snapped to the associated pipe line features. The *.ecf command "Pit Search Distance" can be useful in this instance. It automatically connects floating nodes to the 1D pipe network where connectors are not snapped to channel ends: 

<tt>Pit Search Distance</tt> <tt>==</tt><tt>xxx</tt> 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\1d_nwke_*****.MIF</tt> 
 
The order of the "Pit Search Distance" command is important as it can be repeated multiple times with different values that are assigned to the 1d_nwke(s) below the ''Pit Search Distance'' command. The pit search command should be included above the the GIS layer containing the pits.

To check if the ''Pit Search Distance'' is working as expected, import the [[Check_Files_1d_nwk_C | *_nwk_C_check]] file to visually see if the pits are automatically connecting to a culvert. The image below is an example of the *_nwk_C_check file and the connections TUFLOW has made to each pit. 

 
[[File:Pit_search_distance_check.JPG|border|500px]]

 
Any further questions please email TUFLOW support: [mailto:support@tuflow.com?Subject=TUFLOW%201D%20pits%20help support@tuflow.com]
 
{{Tips Navigation
|uplink=[[ TUFLOW 1D Channels and Hydraulic Structures | Back to 1D Channels and Hydraulic Structures]]
}}

1D Pits

2024-01-30T11:22:41Z

Angelos Livogiannis:

=Introduction=
There are predominantly two types of stormwater pits (drains/gullies) used as inlets to collect overland runoff and transfer that water to the underlying drainage/culvert/pipe network;
* Grated inlets
* Kerb Inlets (side entry pits / lintel inlets).
This page of the Wiki describes how pit inlet data is incorporated into a TUFLOW model.

= Pit Inlet Types =
{|class="wikitable"
|-
! Inlet Type !! Example !! Description
|-
! Q
| [[File:Q pit inlet.jpg|thumb|none|300px|Depth-Discharge Pit or Channel]]|| width="300pt"|Depth-Discharge Pit or Channel, pit inlet inflow information is defined within TUFLOW via a user defined Pit Inlet Database and associated pit inlet curves. This approach allows for unlimited flexibility. Any pit design or configuration can be incorporated into a TUFLOW model if the inlet depth-discharge relationship is known.
|-
! R
| [[File:Side_Entry_pit.jpg|thumb|none|300px|Kerb Inlet]]|| width="300pt"|Kerb inlets, also know as side entry pits or lintels are common in Australia. The pit chamber can vary depending on overall depth, length and the addition of any haunched riser units.
|-
! C
| [[File:Circular pit inlet.jpg|thumb|none|300px|Circular Pit Inlet]]|| width="300pt"|Circular pit inlet
|-
! W
| [[File:Gully pit.jpg|thumb|none|300px|Grate (London, UK)]] || width="300pt"|Grates, also known as Gully Pits, are common in the United Kingdom and are generally a square grate on top of a circular chamber and a riser outlet. The outlet will then feed into a larger culvert that forms part of the larger urban drainage network.
|}

= Pit Inlet Data Sources =
Pit inlet depth-discharge data can be obtained from a variety of sources. The most common typically being from suppliers or local agencies who enforce consistent design standards within their jurisdiction. For demonstration purposes, examples from Sutherland Shire Council and Brisbane City Council are provided below.

== Sutherland Shire Council ==
The Sutherland Shire Council Urban Drainage Manual (1992) includes summary tables and graphs documenting pit grate and lintel capacity information (derived from Department of Main Roads testing). The guidelines are compatible with the standard pit grate and lintel design shown below: 
[[File: Pit_Inlet_Curves_SSC000.JPG|700px]] 
The capacity of a pit depends on three factors:
* The clear opening area of the grate
* The depth of water ponding over the grate
* The length of kerb inlet (lintel) opening
The following graphs summarise grate and lintel discharge estimates for a range of water depths and blockage factors, derived from the Sutherland Shire Council design standards. 
[[File: Pit_Inlet_Curves_SSC001.JPG|700px]]
[[File: Pit_Inlet_Curves_SSC002.JPG|700px]] 

The above graphs estimate unit length and area flow estimates. These unit values can be multiplied by real pit dimensions to define at site depth-discharge characteristics.

TUFLOW modelling requires the derivation of a unique depth-discharge curve for each pit type within the modelled area. An example is provided below for a single pit location. 

[[File: Pit_Inlet_Curves_SSC003.JPG|700px]]

== Brisbane City Council==
The pit inlet curve examples below originate from Brisbane City Council 8000 series standard drawings: https://www.brisbane.qld.gov.au/planning-building/planning-guidelines-tools/planning-guidelines/standard-drawings 
[[File: BCC_BSD-8077.JPG|border|700px]]
[[File: BCC_BSD-8051.JPG|border|700px]] 
[[File: BCC_BSD-8082.JPG|border|700px]]
[[File: BCC_BSD-8052.JPG|border|700px]] 

== South Australian Road Stormwater Drainage Inlets: Hydraulic Study (University of South Australia)==
The Urban Water Resources Centre (UWRC) at the University of South Australia conducted a comprehensive set of hydraulic studies, examining performance of the most common roads’ stormwater drainage inlets in use in South Australia. The study was carried out using the Centre's unique full-scale road surface drainage test rig. Links to the pipe inlets curves are provided in the following link and sections below: [https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/ Hydraulic Study (University of South Australia)]
=== Transport South Australia ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/transport-sa/ Transport South Australia Pit Inlet Curves]
=== City of Adelaide ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-adelaide/ City of Adelaide Pit Inlet Curves]
=== City of Campbelltown ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-campbeltown/ City of Campbelltown Pit Inlet Curves]
=== City of Charles Sturt ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-charles-sturt/ City of Charles Sturt Pit Inlet Curves]
=== City of Onkaparinga ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-onkaparinga/ City of Onkaparinga Pit Inlet Curves]
=== City of Playford ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-playford/ City of Playford Pit Inlet Curves]
=== City of Port Adelaide / Enfield ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-port-adelaideenfield/ City of Port Adelaide / Enfield Pit Inlet Curves]
=== City of Marion ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-marion/ City of Marion Pit Inlet Curves]
=== City of Mitcham ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-mitcham/ City of Mitcham Pit Inlet Curves]
=== City of Salisbury ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-salisbury/ City of Salisbury Pit Inlet Curves]
=== City of Tea Tree Gully ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-tea-tree-gully/ City of Tea Tree Gully Pit Inlet Curves]
=== City of West Torrens ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-west-torrens/ City of West Torrens Pit Inlet Curves]

== Page Under Construction (Section: Spacing of Road Gullies) ==
== Spacing of Road Gullies (UK adoption BS EN 124 and BS7903) ==
The following section describes the method to determine the spacing of road gratings, according to the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf/ Spacing of Road Gullies] guidance ('''BS EN 124''' and '''BS 7903''').

The method depends on the following '''Hydraulic parameters:'''
* Longitudinal gradient, ''SL'', along the length of the scheme (expressed as fraction).

* Cross-fall, ''Sc'' (also expressed as a fraction).

* Manning’s roughness coefficient, ''n''. Usually ''n'' = 0.017 for a conventional road surface. Other values are given in the following '''Table 1'''. (For more details, please see Section: 4.3, Table 1 of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf/ guidance]).

'''Table 1:''' Values of Manning's ''n''
 [[File:Table1.jpg|450px|]] 

* The grating type (P, Q, R, S or T), or the size and angle of kerb inlet.

* The maximum allowable flow width (as shown below by ''B'' in m) against the kerb.
 [[File:Figures 1 2.jpg|850px|]] 

'''A) Use of Tables for determining the flow capacity of gullies and maximum spacings for gully gratings''' 
Equations given in Section 5 of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf/ guidance] are used for the calculation of the Spacing of Road Gullies. Design tables have been compiled to present a quick design approach. Tables can be found in Annex C.
Annex C includes design tables for the grating types: Types P, Q, R, S and T. The Design Tables C2-C6 in Annex C of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf/ guidance] present the area that can be drained for an intermediate gully and a range of crossfall and gradient of flow widths. For the design tables a rainfall intensity of 50mm/h and Manning’s ''n'' = 0.017 are considered.

For ease of access, Tables C2-C6 are replicated in the Spacing of Road Gullies file here [Excel File]. Please see, tabs: Type P, Type Q, Type R, Type S and Type T. The Excel file provides tables like the following examples and their corresponding graphs.
 [[File:Tables C2-C6 of Annex C.jpg|950px|]] 

 '''Note:''' a) ''Tables C2 to C6 are for intermediate gullies on a uniform gradient and are not strictly accurate for gradients which vary greatly over short distances.''
b)''The Excel tables also present the flow collection efficiency η of the grating in % (in brackets)''. 

'''B) Calculation of Gully Spacings based on Equations'''
 Alternatively, the equations given in Sections 5 of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf/ guidance] can be used for the Spacing of Road Gullies, directly. The method requires the calculations of the Flow capacity of the kerb channel and Flow collection efficiency of the gully grating.
*As a first step, a gully grate type: P, Q, R, S or T should be selected. The selection of the grating Type will determine the design value ''Gd'' (grating parameter) from '''Table 2'''. (For more details, please see Annex B of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf/ guidance]).

'''Table 2:''' Determination of grating type ''Gd''
 [[File:Determination of grating type.jpg|650px|]] 

'''Note:''' ''According to the manual: The value of Gd should be used to calculate the maximum spacing between gullies.''

*Road (longitudinal) gradient (''SL''), Crossfall (''Sc'') and Manning's (''n'') should then be determined. Parameter values can be obtained from '''Table 3'''.

'''Table 3:''' Determination of ''SL'', ''Sc'' and Manning's ''n''
 [[File:Table SL SC N Range.jpg|750px|]] 

*Further, a Water Depth against the kerb ''H'' (m) range should be provided. (Please note: The depth range can be changed, but the following equations that are used to calculate the flow capacity are only valid up to the kerb height).

*With the above parameters, the calculations of i) The Flow width (''B'' in m), ii) the Cross-sectional area (''Af'' in m2), iii) Hydraulic radius (''R'' in m), iv) Flow rate (''Q'' in m3/s) and v) Flow collection efficiency (''ŋ'' (%)) based on the Equations 6-10 which are presented in Section 5 of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf/ guidance] can be completed.

*Finally, the resulting depth-discharge data can be used in the pit inlet curves. 

The Spacing of Road Gullies Excel file above includes a calculation tab which can be used for the completion of the calculation process. Based on calculations and Equations (11) and (12) of the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf/ guidance] the maximum spacings for gully grating can be calculated.

'''Key assumption''' '''Note:''' This method assumes that the route the flow takes around the trap limits the discharge from the gully pot to 10 l/s. This limit is effective in both directions, so any number of negative head on the gully would create -10 l/s flow back up through the gully and flood onto the road. 

== UK Water Industry Research (UKWIR) Inlet Capture Tool ==
In 2023, the UK Water Industry Research (UKWIR) Limited released the Modelling Sewer Inlet Capacity Restrictions Report [https://ukwir.org/modelling-sewer-inlet-capacity-restrictions/ Modelling Sewer Inlet Capacity Restrictions Report]. The main aim was to develop a sewer modelling methodology to enable the representation of inlet inflow restrictions, focusing on the development of a new 1D model approach to provide more accurate model sewer flooding predictions. The new modelling approach has been devised by combining the findings from a literature review and the development of semi-empirical relationships from academic studies which investigated factors affecting inlet capacity. The new approach allows for 2 types of gully response reflecting 2 flow conditions: Subcritical flow on a shallow road gradient and Supercritical flow on a steep road gradients. A threshold of 0.02 is used to distinguish between shallow and steep road gradients. The reported equations can be used for the production of input inlet curves for TUFLOW 1D pit inlet modelling.

A template for the generation of the UKWIR Inlet Curve can be downloaded from [https://downloads.tuflow.com/Other/Inlet_Spreadsheets/Inlet%20Curve%20Capture%20tool%20v4.xlsx here]. The template determines both Subcritical Head-Discharge and Supercritical Head-Discharge relationships obtained from the Modelling Sewer Inlet Capacity Restrictions Report based on user input values of water depth (in metres). Two sets of curves can be generated, curves based on default parameters, and those based on user-defined parameters.

== How to Translate On-Grade Approach Flow / Pit Capture Flow Curves to Depth / Discharge Curves for use in TUFLOW ==
Manning's equation calculations can be used to convert on-grade approach flow information to a water depth at the pit. After manually calculating the depth to flow relationship the user simply needs to associate these water depth values with the pit capture flow information typically included in on grade pit inlet curve datasets.

=TUFLOW Model Inputs=
The steps required to represent pit inlet information within a TUFLOW model is summarised below:
<ol>
<li> Import an empty 1d_nwk GIS file from the TUFLOW file template folder (model\gis\empty).
<li> Digitise points to represent pit locations. The points should be snapped to the start or end of 1d_nwk line features that define the underground pipe network.
<li> Update the field attributes for each Pit point. Refer to 5.12.2 of the 2016 TUFLOW Manual. The most commonly used attributes are:
* Type = Q (C, R and W are also options if pit inlets based on structure dimension is required instead of using a Pit Inlet Database approach).
* US_Invert = Used to specify the ground elevation of the pit. If Conn_1D_2D is set to “SXL”, US_Invert is used as the amount by which to lower the 2D cell and the pit channel invert is set to this level.
* DS_Invert = The bottom elevation of the pit. This input can also be used to set the upstream and downstream inverts of connected pipes/channels.
* Inlet_Type = For Q pit channels, the name of a pit inlet type in the Pit Inlet Database. Multiple Pits can use the same Inlet_Type ID if they have the same design dimensions.
* Conn_1D_2D = SXL can be specified to connect the 1D pit or node to the 2D domain and lower the 2D cell by the amount of the US_Invert attribute. The invert of the pit channel is set to the lowered 2D cell level. This is useful to help trap the water into the pit as it flows overland in the 2D domain. This feature works well in combination with the new Read GIS SA PITS option.
<li> Update the Estry Control File (*.ecf) to include reference to the new 1d_nwk GIS file. 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\Estry\1d_nwk_****.MIF</tt> 
<li> Create a Pit Inlet Database csv file. This file lists each type of pit (matching the names listed in the 1d_nwk "Inlet_Type" field). It also provides reference to the depth-discharge curve information. 
[[File:M05 pit inlet dbase 01.png]]
<li> Create the Source file referenced in the Pit Inlet Database. The source file defines the depth-discharge information for each pit (determined from the relevant design standards). The column headers must match the entries in the Pit Inlet Database. 
[[File:M05 pit inlet v2.png]]
<li> Update the Estry Control File (*.ecf) to include reference to the Pit Inlet Database. 
<tt>Pit Inlet Database</tt> <tt>==</tt><tt>..\pit_dbase\EG_pit_dbase.csv</tt> 
</ol>

An example model including Pits is available for download: https://wiki.tuflow.com/index.php?title=TUFLOW_Example_Models

==Pit Search Distance==
Some agency pit datasets may not have all pit point features snapped to the associated pipe line features. The *.ecf command "Pit Search Distance" can be useful in this instance. It automatically connects floating nodes to the 1D pipe network where connectors are not snapped to channel ends: 

<tt>Pit Search Distance</tt> <tt>==</tt><tt>xxx</tt> 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\1d_nwke_*****.MIF</tt> 
 
The order of the "Pit Search Distance" command is important as it can be repeated multiple times with different values that are assigned to the 1d_nwke(s) below the ''Pit Search Distance'' command. The pit search command should be included above the the GIS layer containing the pits.

To check if the ''Pit Search Distance'' is working as expected, import the [[Check_Files_1d_nwk_C | *_nwk_C_check]] file to visually see if the pits are automatically connecting to a culvert. The image below is an example of the *_nwk_C_check file and the connections TUFLOW has made to each pit. 

 
[[File:Pit_search_distance_check.JPG|border|500px]]

 
Any further questions please email TUFLOW support: [mailto:support@tuflow.com?Subject=TUFLOW%201D%20pits%20help support@tuflow.com]
 
{{Tips Navigation
|uplink=[[ TUFLOW 1D Channels and Hydraulic Structures | Back to 1D Channels and Hydraulic Structures]]
}}

1D Pits

2024-01-30T10:05:33Z

Angelos Livogiannis:

=Introduction=
There are predominantly two types of stormwater pits (drains/gullies) used as inlets to collect overland runoff and transfer that water to the underlying drainage/culvert/pipe network;
* Grated inlets
* Kerb Inlets (side entry pits / lintel inlets).
This page of the Wiki describes how pit inlet data is incorporated into a TUFLOW model.

= Pit Inlet Types =
{|class="wikitable"
|-
! Inlet Type !! Example !! Description
|-
! Q
| [[File:Q pit inlet.jpg|thumb|none|300px|Depth-Discharge Pit or Channel]]|| width="300pt"|Depth-Discharge Pit or Channel, pit inlet inflow information is defined within TUFLOW via a user defined Pit Inlet Database and associated pit inlet curves. This approach allows for unlimited flexibility. Any pit design or configuration can be incorporated into a TUFLOW model if the inlet depth-discharge relationship is known.
|-
! R
| [[File:Side_Entry_pit.jpg|thumb|none|300px|Kerb Inlet]]|| width="300pt"|Kerb inlets, also know as side entry pits or lintels are common in Australia. The pit chamber can vary depending on overall depth, length and the addition of any haunched riser units.
|-
! C
| [[File:Circular pit inlet.jpg|thumb|none|300px|Circular Pit Inlet]]|| width="300pt"|Circular pit inlet
|-
! W
| [[File:Gully pit.jpg|thumb|none|300px|Grate (London, UK)]] || width="300pt"|Grates, also known as Gully Pits, are common in the United Kingdom and are generally a square grate on top of a circular chamber and a riser outlet. The outlet will then feed into a larger culvert that forms part of the larger urban drainage network.
|}

= Pit Inlet Data Sources =
Pit inlet depth-discharge data can be obtained from a variety of sources. The most common typically being from suppliers or local agencies who enforce consistent design standards within their jurisdiction. For demonstration purposes, examples from Sutherland Shire Council and Brisbane City Council are provided below.

== Sutherland Shire Council ==
The Sutherland Shire Council Urban Drainage Manual (1992) includes summary tables and graphs documenting pit grate and lintel capacity information (derived from Department of Main Roads testing). The guidelines are compatible with the standard pit grate and lintel design shown below: 
[[File: Pit_Inlet_Curves_SSC000.JPG|700px]] 
The capacity of a pit depends on three factors:
* The clear opening area of the grate
* The depth of water ponding over the grate
* The length of kerb inlet (lintel) opening
The following graphs summarise grate and lintel discharge estimates for a range of water depths and blockage factors, derived from the Sutherland Shire Council design standards. 
[[File: Pit_Inlet_Curves_SSC001.JPG|700px]]
[[File: Pit_Inlet_Curves_SSC002.JPG|700px]] 

The above graphs estimate unit length and area flow estimates. These unit values can be multiplied by real pit dimensions to define at site depth-discharge characteristics.

TUFLOW modelling requires the derivation of a unique depth-discharge curve for each pit type within the modelled area. An example is provided below for a single pit location. 

[[File: Pit_Inlet_Curves_SSC003.JPG|700px]]

== Brisbane City Council==
The pit inlet curve examples below originate from Brisbane City Council 8000 series standard drawings: https://www.brisbane.qld.gov.au/planning-building/planning-guidelines-tools/planning-guidelines/standard-drawings 
[[File: BCC_BSD-8077.JPG|border|700px]]
[[File: BCC_BSD-8051.JPG|border|700px]] 
[[File: BCC_BSD-8082.JPG|border|700px]]
[[File: BCC_BSD-8052.JPG|border|700px]] 

== South Australian Road Stormwater Drainage Inlets: Hydraulic Study (University of South Australia)==
The Urban Water Resources Centre (UWRC) at the University of South Australia conducted a comprehensive set of hydraulic studies, examining performance of the most common roads’ stormwater drainage inlets in use in South Australia. The study was carried out using the Centre's unique full-scale road surface drainage test rig. Links to the pipe inlets curves are provided in the following link and sections below: [https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/ Hydraulic Study (University of South Australia)]
=== Transport South Australia ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/transport-sa/ Transport South Australia Pit Inlet Curves]
=== City of Adelaide ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-adelaide/ City of Adelaide Pit Inlet Curves]
=== City of Campbelltown ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-campbeltown/ City of Campbelltown Pit Inlet Curves]
=== City of Charles Sturt ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-charles-sturt/ City of Charles Sturt Pit Inlet Curves]
=== City of Onkaparinga ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-onkaparinga/ City of Onkaparinga Pit Inlet Curves]
=== City of Playford ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-playford/ City of Playford Pit Inlet Curves]
=== City of Port Adelaide / Enfield ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-port-adelaideenfield/ City of Port Adelaide / Enfield Pit Inlet Curves]
=== City of Marion ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-marion/ City of Marion Pit Inlet Curves]
=== City of Mitcham ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-mitcham/ City of Mitcham Pit Inlet Curves]
=== City of Salisbury ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-salisbury/ City of Salisbury Pit Inlet Curves]
=== City of Tea Tree Gully ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-tea-tree-gully/ City of Tea Tree Gully Pit Inlet Curves]
=== City of West Torrens ===
[https://www.unisa.edu.au/research/sustainable-infrastructure-and-resource-management/australian-flow-management-group/stormwater-drainage-hydraulic-study/city-of-west-torrens/ City of West Torrens Pit Inlet Curves]

== UK Water Industry Research (UKWIR) Inlet Capture Tool ==
In 2023, the UK Water Industry Research (UKWIR) Limited released the Modelling Sewer Inlet Capacity Restrictions Report [https://ukwir.org/modelling-sewer-inlet-capacity-restrictions/ Modelling Sewer Inlet Capacity Restrictions Report]. The main aim was to develop a sewer modelling methodology to enable the representation of inlet inflow restrictions, focusing on the development of a new 1D model approach to provide more accurate model sewer flooding predictions. The new modelling approach has been devised by combining the findings from a literature review and the development of semi-empirical relationships from academic studies which investigated factors affecting inlet capacity. The new approach allows for 2 types of gully response reflecting 2 flow conditions: Subcritical flow on a shallow road gradient and Supercritical flow on a steep road gradients. A threshold of 0.02 is used to distinguish between shallow and steep road gradients. The reported equations can be used for the production of input inlet curves for TUFLOW 1D pit inlet modelling.

A template for the generation of the UKWIR Inlet Curve can be downloaded from [https://downloads.tuflow.com/Other/Inlet_Spreadsheets/Inlet%20Curve%20Capture%20tool%20v4.xlsx here]. The template determines both Subcritical Head-Discharge and Supercritical Head-Discharge relationships obtained from the Modelling Sewer Inlet Capacity Restrictions Report based on user input values of water depth (in metres). Two sets of curves can be generated, curves based on default parameters, and those based on user-defined parameters.

== Page Under Construction (Section: Spacing of Road Gullies) ==
== Spacing of Road Gullies (BS EN 124 and BS7903) ==
The following section describes the method to determine the spacing of road gratings, according to the [https://new.sthelens.gov.uk/media/330117/5126_ha-102_00.pdf/ Spacing of Road Gullies] guidance ('''BS EN 124''' and '''BS 7903''').

The method depends on the following '''Hydraulic parameters:'''
* Longitudinal gradient, ''SL'', along the length of the scheme (expressed as fraction).

* Cross-fall, ''Sc'' (also expressed as a fraction).

* Manning’s roughness coefficient, ''n''. Usually ''n'' = 0.017 for a conventional road surface. Other values are given in the following '''Table 1'''. (For more details, please see Section: 4.3; p.g.:4/1; Table 1 of the guidance).

'''Table 1:''' Values of Manning's ''n''
 [[File:Table1.jpg|450px|]] 

* The grating type (P, Q, R, S or T), or the size and angle of kerb inlet.

* The maximum allowable Flow Width (as shown below by ''B'' in m) against the kerb.
 [[File:Figures 1 2.jpg|850px|]] 

'''A) Use of Tables for determining the flow capacity of gullies and maximum spacings for gully gratings''' 
Equations given in Section 5 of the guidance are used for the calculation of the Spacing of Road Gullies. Design Tables have been compiled to present a quick design approach. Tables can be found in Annex C.
Annex C includes Design Tables for the grating types: Types P, Q, R, S and T. The Design Tables C2-C6 in Annex C of the guidance (p.g: C/3-C/12), present the area that can be drained for an intermediate gully and a range of crossfall and gradient of flow widths. For the Design Tables a rainfall intensity of 50mm/h and Manning’s ''n'' = 0.017 are considered.

For ease of access, the Tables C2-C6 (Type P-T) of Annex C, are replicated in the Spacing of Road Gullies file here [Excel File]. Please see, tabs: Type P, Type Q, Type R, Type S and Type T. The Excel file provides tables like the following examples and their corresponding graphs.
 [[File:Tables C2-C6 of Annex C.jpg|950px|]] 

 '''Note:''' a) ''Tables C2 to C6 are for intermediate gullies on a uniform gradient and are not strictly accurate for gradients which vary greatly over short distances.''
b)''The Excel tables also present the flow collection efficiency η of the grating in % (in brackets)''. 

Based on Tables and Equations (2), (3) and (4) of the guidance (p.g: 5/1) the Maximum spacings for gully grating can be calculated.

'''B) Calculation of Gully Spacings based on Equations'''
 Alternatively, the equations given in Sections 5 of the guidance can be used for the Spacing of Road Gullies, directly. The method requires the calculations of the Flow capacity of the kerb channel and Flow collection efficiency of the gully grating.

*As a first step, a gully grate type: P, Q, R, S or T should be selected. The selection of the grating Type will determine the design value ''Gd'' (grating parameter) from '''Table 2'''. (For more details, please see Annex B of the guidance; p.g.: B/1.).

'''Table 2:''' Determination of grating type ''Gd''
 [[File:Determination of grating type.jpg|650px|]] 

'''Note:''' ''According to the manual: The value of Gd should be used to calculate the maximum spacing between gullies.''

*Road (longitudinal) gradient (''SL''), Crossfall (''Sc'') and Manning's (''n'') should then be determined. Parameter values can be obtained from '''Table 3'''.

'''Table 3:''' Determination of ''SL'', ''Sc'' and Manning's ''n''
 [[File:Table SL SC N Range.jpg|750px|]] 

*Further, a Water Depth against the kerb ''H'' (m) range should be provided. (Please note: The depth range can be changed, but the following equations that are used to calculate the flow capacity are only valid up to the kerb height).

*With the above parameters, the calculations of i) The Flow width (''B'' in m), ii) the Cross-sectional area (''Af'' in m2), iii) Hydraulic radius (''R'' in m), iv) Flow rate (''Q'' in m3/s) and v) Flow collection efficiency (''ŋ'' (%)) based on the Equations 6-10 which are presented in Section 5 (p.g.:5/2) of the guidance can be completed.

*Finally, the resulting depth-discharge data can be used in the pit inlet curves. 

The Spacing of Road Gullies Excel file above includes a calculation tab which can be used for the completion of the calculation process. Based on calculations and Equations (11) and (12) of the guidance (p.g: 5/3) the Maximum spacings for gully grating can be calculated.

'''Key assumption''' 
'''Note:''' This method assumes that the route the flow takes around the trap limits the discharge from the gully pot to 10 l/s. This limit is effective in both directions, so any number of negative head on the gully would create -10 l/s flow back up through the gully and flood onto the road. 

== How to Translate On-Grade Approach Flow / Pit Capture Flow Curves to Depth / Discharge Curves for use in TUFLOW ==
Manning's equation calculations can be used to convert on-grade approach flow information to a water depth at the pit. After manually calculating the depth to flow relationship the user simply needs to associate these water depth values with the pit capture flow information typically included in on grade pit inlet curve datasets.

=TUFLOW Model Inputs=
The steps required to represent pit inlet information within a TUFLOW model is summarised below:
<ol>
<li> Import an empty 1d_nwk GIS file from the TUFLOW file template folder (model\gis\empty).
<li> Digitise points to represent pit locations. The points should be snapped to the start or end of 1d_nwk line features that define the underground pipe network.
<li> Update the field attributes for each Pit point. Refer to 5.12.2 of the 2016 TUFLOW Manual. The most commonly used attributes are:
* Type = Q (C, R and W are also options if pit inlets based on structure dimension is required instead of using a Pit Inlet Database approach).
* US_Invert = Used to specify the ground elevation of the pit. If Conn_1D_2D is set to “SXL”, US_Invert is used as the amount by which to lower the 2D cell and the pit channel invert is set to this level.
* DS_Invert = The bottom elevation of the pit. This input can also be used to set the upstream and downstream inverts of connected pipes/channels.
* Inlet_Type = For Q pit channels, the name of a pit inlet type in the Pit Inlet Database. Multiple Pits can use the same Inlet_Type ID if they have the same design dimensions.
* Conn_1D_2D = SXL can be specified to connect the 1D pit or node to the 2D domain and lower the 2D cell by the amount of the US_Invert attribute. The invert of the pit channel is set to the lowered 2D cell level. This is useful to help trap the water into the pit as it flows overland in the 2D domain. This feature works well in combination with the new Read GIS SA PITS option.
<li> Update the Estry Control File (*.ecf) to include reference to the new 1d_nwk GIS file. 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\Estry\1d_nwk_****.MIF</tt> 
<li> Create a Pit Inlet Database csv file. This file lists each type of pit (matching the names listed in the 1d_nwk "Inlet_Type" field). It also provides reference to the depth-discharge curve information. 
[[File:M05 pit inlet dbase 01.png]]
<li> Create the Source file referenced in the Pit Inlet Database. The source file defines the depth-discharge information for each pit (determined from the relevant design standards). The column headers must match the entries in the Pit Inlet Database. 
[[File:M05 pit inlet v2.png]]
<li> Update the Estry Control File (*.ecf) to include reference to the Pit Inlet Database. 
<tt>Pit Inlet Database</tt> <tt>==</tt><tt>..\pit_dbase\EG_pit_dbase.csv</tt> 
</ol>

An example model including Pits is available for download: https://wiki.tuflow.com/index.php?title=TUFLOW_Example_Models

==Pit Search Distance==
Some agency pit datasets may not have all pit point features snapped to the associated pipe line features. The *.ecf command "Pit Search Distance" can be useful in this instance. It automatically connects floating nodes to the 1D pipe network where connectors are not snapped to channel ends: 

<tt>Pit Search Distance</tt> <tt>==</tt><tt>xxx</tt> 
<tt>Read GIS Network</tt> <tt>==</tt><tt>..\model\mi\1d_nwke_*****.MIF</tt> 
 
The order of the "Pit Search Distance" command is important as it can be repeated multiple times with different values that are assigned to the 1d_nwke(s) below the ''Pit Search Distance'' command. The pit search command should be included above the the GIS layer containing the pits.

To check if the ''Pit Search Distance'' is working as expected, import the [[Check_Files_1d_nwk_C | *_nwk_C_check]] file to visually see if the pits are automatically connecting to a culvert. The image below is an example of the *_nwk_C_check file and the connections TUFLOW has made to each pit. 

 
[[File:Pit_search_distance_check.JPG|border|500px]]

 
Any further questions please email TUFLOW support: [mailto:support@tuflow.com?Subject=TUFLOW%201D%20pits%20help support@tuflow.com]
 
{{Tips Navigation
|uplink=[[ TUFLOW 1D Channels and Hydraulic Structures | Back to 1D Channels and Hydraulic Structures]]
}}