The 2D Job Control settings dialog has a tree control in the left panel. Use this control to display the desired section in the right panel. To load the 2D Job Control settings dialog from the Configuration menu, click Job Control > 2D Model Settings. Alternatively, you can access this dialog using the 2D Job Control icon  in the toolbar.

General Settings

To calculate 2D hydraulics in XPSWMM/XPStorm:

  1. Select the 2D Model Active. 
  2. Specify the Initial timestep and the 1D/2D Sync timestep

    The Initial timestep is the first timestep HPC will use for adaptive timestepping. The 1D/2D Sync timestep applies to all grids when multiple domains are used. Different time steps can be used by overriding the 1D/2D Sync timeste in each 2D Grid Extent. A normal starting value is the cell size divided by two for metric and divided by six for US Customary units.
  3. Select whether to use XP2D Classic or XP2D Extreme

    By default, the XP2D Classic is selected. This setting will follow the export logic using the classic method. When XP2D Extreme is selected, the solution scheme will be changed to HPC.

    The Adaptive timestepping option is always activated when XP2D Extreme is selected. This allows for adaptive time-stepping for 2D only models. These models only work when there are no 1D elements in the model. The Adaptive timestepping option is always disabled when XP2D Classic is selected.

  4. If you have selected XP2D Extreme, select whether to use CPU or GPU for the Hardware.

    1. If you have selected CPU, you have to select the corresponding CPU Threads. By default, the CPU Threads field is set to two. Select a number from the drop-down list based on the number of physical cores of your computer. 

      The CPU Thread option allows the application to solve a 1D-2D model against multiple threads, which also works with Solve Manager, allowing the number of active simulation x threads not exceed the physical cores available for a model simulation.

    2. The GPU option will only be available if you have GPU enabled license and an NVidia/CUDA-capable graphics card. Otherwise, the GPU option will be disabled.

      The GPU option enables the Graphics Processing Unit (GPU) solver in your computer, which takes advantage of the parallel computing power of a GPU for faster processing of your model. Instead of computing values one cell at a time, this option allows you to compute the values of cells simultaneously, which leads to substantial increase in speed, especially for large models.
  5. In the Control Number Factor field, set a value between 0.001 and 1.199.  Default is 1.0. Typical range from 0.5 to 1.0.

    The Control Number Factor is activated when XP2D Extreme is selected. This is not applicable for XP2D Classic.
  6. Select the Default Landuse Category from the drop-down menu. For the list of available landuses, refer to Global Database
  7. For the Default Area Type, select where to use Active Area or Inactive Area, when not specified by a polygon. By default, this is set to Active Area starting XPSWMM/XPStorm 2011. Existing models keep their original setting. Cells outside of the polygon defining the grid extents are always inactive and cells inside the polygon are either active or inactive depending on this setting.

    2D models containing multiple domains are no longer permitted to solve with Inactive Area as the Default Area Type. Multiple 2D domain models should always use Active Area as the Default Area Type, and use appropriate grid extent polygons to define the domain extents, instead of large active area polygons.
  8. For the Wet/Dry Depth, set the minimum cell depth for a cell to be considered as wet in the 2D calculation.

  9. Select the option to Always use double-precision solver. This is the default solver when 2D Rain polygons are used.

  10. Activate the Additional mass balance iteration by selecting the check box.

  11. If the Produce Check Files is selected, then the 2D engine check files will be produced upon completion of the simulation. Setting this option off may be desired if you are performing the same simulation run several times with minor updates and do not wish to review the check files for all model runs.

    When the Produce Check Files is selected, you have the option to write X1D check files to the map output by selecting the Write X1D Check Files button.
  12. You have the option to produce the map output to GIS ASC format by selecting the Produce ASC Map Output option.

  13. Select 2D Inflow Capture accordingly, and provide the necessary values to be used in the analysis. When the 2D Inflow Capture is not selected, the application will use the Pre-2009 Method. Refer to 2D Inflow Capture for more details.

  14. Select from the following options for the Viscosity Formulation:

    1. Constant - It is not recommended that a value other than 1 m²/s or 10.76 ft²/s be used for the constant viscosity formulations.

    2. Smagorinsky - The Smagorinsky coefficient is typically between 0.06 and 1.0.

2D Inflow Capture

Use this option to specify the default method for simulating inflow from a 2D cell to a 1D linked node. If this option is selected, a user-defined power curve will be used. This is defined by the formula:

Q (cfs, cms) = coefficient × 2D cell depth (ft, m) ^ exponent

If this option is not selected, the application uses the Pre-2009 Method, which is defined by the formula:

Q = Area of Manhole × (2D water depth – Node Spill Crest)/2D time stepb

  • Coefficient > 1
  • The inlet capacity setting at individual nodes may be defined with the 2D Inflow Capture setting in the Hydraulics Node dialog.

Model Output


The Map Results Output Interval specifies the time interval used for animation of 2D results.

The Time Series Output Interval specifies the time interval used for Time Series Output Head/Velocity Point or Flow Line timeseries.

Check the box next to Enable Mass Balance Output to specify that the cumulative mass error calculations are saved. A file XXX__MB.CSV (where XXX = project file name) is created in the results folder. The file contains information at each display time step. The time, inflows, outflows, volume, predicted volume error and the mass and cumulative mass errors as a percentage for all 2D domains and each individual 2D domain are tabulated. This output will be saved at the interval specified in the Mass Balance Output Interval field (Seconds).


When the Enable Time-to-Inundation Map check box is checked/selected 2D Times output maps of the Time to Inundation and Time of Inundation will be generated based on the supplied depth levels.

Map Result Types

Any of the following 2D results output types can be selected within the 2D Job Control > Map Result Types list by selecting the check box for the given output type. Note: units listed (U.S Customary; Metric)

  • Flow (ft3/sec; m3/sec)

  • Velocity (ft2/sec; m2/sec)

  • Water Depth (ft, m)

  • Water Elevation (ft, m)

  • Hazard (V*D)

  • Hazard (UK Formula)

  • Hazard Category (Australian NSW Floodplain Management Manual)

  • Hazard Category (Herbert River Flood Study)

  • Hazard Category (Tweed River Flood Study)

  • Hazard Category (Australian Guidelines)

  • Hazard Category (Melbourne Water - Property Safety Risk)

  • Hazard Category (Melbourne Water - Safety Risk in Roads)

  • Hazard Category (UK)

  • Bed Shear Stress (lb/ft2; N/m2) Detailed Bed Shear Equations

  • Courant Number

  • Energy

  • Froude Number

  • Mass Balance (Per Output Interval)

  • Mass Balance (Cumulative)

  • Manning's n

  • Flow Regime

  • Stream Power (lb/ft-sec; N/m-sec) Detailed Stream Power Equations

  • Sink/Source Inflow

  • Viscosity Coefficient

  • Bathymetry

  • Time to/Duration of Inundation (hours)

  • Minimum DT

Hazard maps (depth x velocity relationships) are calculated at each time step, similarly to the other 2D map results sets. This is important to note when reviewing the maximum hazard map values, these values are the true maximum hazard values which occur during the simulation, and not simply the maximum velocity which occurs multiplied by the maximum depth. Typically the maximum depth does not occur at the same time as the maximum velocity value and vice versa so a hazard value taken from these two unrelated values would be inappropriate and unrealistic. 


Water Levels

Initial Water Levels. The initial water level for all cells is set to the elevation specified.

Override Instability Levels. The default value water level used to detect instabilities is 1 m (3.28 ft) higher than the highest cell elevation of all cells (whether wet, dry or permanently dry). If the box is checked, the user specified value is used to detect instabilities – i.e. if this option is checked, when the depth of flow in any cell in the model reaches the specified level, the simulation will terminate and report instability at the location(s) where this depth occurred. This option is only to be used if you specifically wish to terminate a simulation if a given depth occurs, if this is not desired the Override Instability option should NOT BE USED.

2D Cell Checks

If 2D cells along the 1D/2D interface are lower than the Channel Bed:


Do nothing and allow the model to run with inappropriate levels where 1D and 2D are connected, erroneous results may be produced.

Report Only

Model will not run if this situation happens and errors will be produced which can be displayed using the diagnostics layer. These messages are also contained in the [model name]_messages.mif file.

Adjust (Raise if required)

Cell center elevation (Zc) will be raised up to the interpolated Channel bed level. This fixes the model from having the floodplain elevations below the lowest river cross section elevation.

If 2D cell at 1D node connection is above 1D Node Spill Crest the 1D node:


Do nothing and allow the model to run with inappropriate levels where 1D and 2D are connected, erroneous results may be produced.

Report Only

Model will not run if this situation happens and errors will be produced which can be displayed using the diagnostics layer. These messages are also contained in the [model name]_messages.mif file.

Adjust (Lower if required)

Cell center elevation (Zc) will be raised up to the node spill level. This fixes the model from having the manhole rim below the idealized ground elevation from the 2D grid.

Units are m (metric) and ft (US Customary). Node spillcrest levels can be set equal to the elevation of the DTM by using the generate ground elevations from TIN command on the Tools Menu.

Elevation Export Files

If the Include Additional mid/mif Elevation files is checked/selected, then upon solving the simulation the Cell Center elevations (Zpts) will be exported to *.mid/*.mif files for inspection external to the software interface. This is one way in which the Zpts can be expected to ensure that the 2D Grid Cells are appropriately representing the topographic surface. These files could also be used to create a DTM representing exactly how the 2D engine “sees” the data.

Folder Options

This dialog allows the user to specify where 2D data and results are stored. If unchecked, the results are written to the same folder as the .xp file.

Advanced Settings

The Advanced User Settings allows you to incorporate specific additional configuration commands to the 2D engine.

The Control File section allows configuration commands to be added to the Tuflow Control file (*.tcf). In order for commands to be applied to the engine the associated Flag will need to be selected.

PRE-2013 and earlier are no longer supported in XPSWMM/XPStorm 2018.2.1 and later.
Only one *.tgc file per 2D domain is specified within the *.tcf file.

The Geometry Control File section allows specific commands to be added to the Tuflow Geometry Control file (*.tgc). The top or bottom ordering option allows for the sequential application of commands. These commands in the *.tgc file are applied in sequential order, therefore, it is possible to override previous information with new data to modify the model in selected areas. This is very useful where a base data set exists, over which areas need to be modified to represent other scenarios such as a proposed development. This eliminates or minimizes data duplication.

This option is not typically recommended as the Scenario Manager is a robust tool which can allow numerous model designs or scenarios to be simulated, for both the 1D and 2D portions of the model.

Using Geometry Control File Feature to Add 2D Landuse Reference File

This functionality allows the defined 2D landuse polygon to be externally referenced by the numerical engine. By externally referencing a large model, as opposed to directly importing it into the application, the save and analysis times will be significantly faster. This option is recommended when your model contains more than 50,000 vertices.

To externally reference a 2D landuse polygon:

  1. Go to Configuration > Job Control > 2D Model Settings.
  2. Click the Advanced Settings tab.
  3. In the Geometry Control File section, click Insert.
  4. Select the checkbox under the Flag column.
  5. In the Parameter column, type READ GIS MAT.

    The READ GIS MAT command should be written as is.
  6. In the Value column, enter the location and the filename of the GIS file.

    The GIS file should be located in the root folder as there is a limit in the number of characters for this column.
  7. In the Position, select from the drop-down list. The available positions are:
    • Top
    • After Surface
    • Bottom

  8. Click OK
  9. In the Layers Control Panel, verify that the added 2D landuse file is under 2D Landuse Reference


This dialog is used to define the geographic projects for all GIS input and output.

Header Delimiter specifies the field delimiter for the Header Projections input string

Header Charset specifies the character set for the Header Projections input string

Click the Load from Mapinfo MIF file to upload this information.


By default, the Use DTM option is selected for this option. The DTM surface that will be used during the 2D simulation will be the *.xptin file that have been specified in the DTM Layer.

If it is cumbersome to create an *.xptin from a DTM grid file (such as in the case of very large grid files), a grid file can be specified by selecting the User grid file for topography option and browsing to the desired file. In this case no *.xptin is required to be loaded into the software interface in order to solve the 2D model.