1D Pumps

Page Under Construction

Introduction

This post provides a modelling example for a 1D pump using a fixed flow rate and pump curve. For this example we will model a pump in two common situations (2D-2D & 1D-2D).

Pump Attributes

A pump needs to first be digitised in a 1d_nwke layer. The direction of the polyline must go from inlet to outlet as a pump is unidirectional (? Is that true). The attributes required for a pump in your 1d_nwke layer can be found within the 2015 TUFLOW manual.
In the 1d_nwk layer, the following attributes are required:

1. ID = ID of the channel
   
2. Type = "P"
   
3. Len_or_ANA = Nominal length in m (only used for calculating nodal storage if UCS is on)
   
4. US_Invert = Upstream invert level of the channel
   
5. DS_Invert = Downstream invert level of the channel
   
6. Inlet_Type = Used to specify the pump curve in the Depth Discharge database.
   

2D-2D Configuration

Because pumps are zero length channels they do not create automatic nodes at the upstream and downstream end. If you ran the model with just a pump polyline you will get ERROR 1353 - No NA data for Node.To remove this error you will need to digitise a node within a separate 1d nwke layer and give a nominal storage amount in the “Len_or_NA” attribute for the 1d nwke ‘Node’, see the example below.
300px
To connect the pump to the 2d domain you will also need to digitise an SX connection. In the figure below I have showed both the 1d node and 2d SX points as being separate from each other for illustrative purposes only – they should both be snapped to the end of the pump polyline. SX connections are required at connections to 2D domains to transfer water from the 1D node to the 2D. Without the SX connection, water will build up within the node and cause an instability.
600px

1D-2D Configuration

Connecting a pump from a 1d network to the 2d domain or vice versa is similar to the configuration above, the only difference is that the connection with a 1d structure does not require a 2d SX connection or 1d nwke ‘Node’. A storage chamber in the 1d network can also be modelled using a 1d_na node with an elevation vs area .csv assigned to the node.
600px

Estry Control File Setup

Within the *.ecf the following commands and files are at a minimum required to run a pump with no logically control:

Read GIS Network ==..\model\mi\1d_nwke_xxxxx.MIF
Depth Discharge Database ==..\bc_dbase\xxxxx.csv

If you do not specify a Depth-Discharge database then you will be faced with ERROR 1118 – Could not find a y-Q curve.

TUFLOW Operating Control File (.TOC)

Rohan - Fill me out

Depth Discharge Database

The depth discharge database is set up in the same way as a pit inlet database, see 4.5.1.2 in the TUFLOW manual (Amend this section link once the manual is finalised).. Each pump ‘Inlet_type’ must reference a name within the depth discharge database, otherwise ERROR 1118 - Could not find pit inlet type ",a," in the pit inlet database will appear because TUFLOW will use the ‘ID’ field instead of the blank ‘Inlet_type’ field to search the database and it will come up with no information (that seemed to be the case during my testing). The ‘Area (m2)’ column is the area of the pump offtake and ‘Width (m)’ is the width of the pump offtake (? Is that true).

Constant Flow Rate

Rohan - fill me out

Pump Curve

Rohan - fill me out

Creating a TUFLOW pump curve

Rohan - fill me out

1D Check File

Although strictly not a check file, the operation of the pump can be confirmed by opening the *_1d_O.csv which is found within the csv folder where the results are written.

Filename prefix / suffix	Brief Description
_1d_O.csv	This csv displays the status of the pump, whether that is closed or fully open, results for any logic parameter specified in the TOC file and the flow through the pump if it is in operation.

Any further questions please email TUFLOW support: support@tuflow.com