Time-varying Overland Flow Boundary Conditions
The default boundary condition for Overland Flow in MIKE SHE is a constant water level on the outer boundary. The value of this boundary condition is determined by the initial water depth on the boundary. In most models the recommended value is a water depth of zero. In this case, if the water level adjacent to the boundary increases, water will discharge across the boundary and out of the model. If you want to prevent overland outflow then you can use the Separated Flow Areas option to restrict lateral flow out of the model.
If you specify a non-zero value for initial water depth on the boundary, then this value becomes a constant for the entire simulation. If the water level inside the model decreases below this value, the boundary will act as an infinite source of inflow to the model.
However, in many models - especially those with significant wetland areas - the constant water level condition on the boundary is too restrictive.
The following extra parameter options allow you to specify a time varying condition for the outer boundary of the overland flow. If you initialize this option, then you must supply a dfs2 integer grid code file that defines the locations at which you want a time varying boundary. The input requirements have been set up such that you can re-use the model domain dfs2 output file from the pre-processor. In the model domain pre-processed output, the outer cells are defined by a value of 2 and the inner cells are defined by a value of 1.
If the grid code value on the boundary is:
· 2 - the cell is a time varying boundary node, or
· 1 - the cell will have a constant water depth equal to the initial water depth.
The second required file is the actual time-varying water level values. These can be obtained from any MIKE SHE simulation, where the overland water elevation has been stored as a grid series output. There is no requirement that they be stored on the same grid. Internally, the actual boundary condition values will be interpolated from the nearest input values. Thus, the OL boundary conditions can be taken from a coarse regional model and applied to a local scale model.
Finally, each file name must be accompanied by an integer item number that defines which item in the dfs2 file should be used.
Parameter Name |
Type |
Value |
---|---|---|
time varying ol boundary |
Boolean |
On |
ol boundary code file name |
filename |
.dfs2 file |
ol boundary code item number |
integer |
item number in dfs2 file, greater than zero |
ol boundary head file name |
filename |
.dfs2 file |
ol boundary head item number |
integer |
item number in dfs2 file, greater than zero |
The Hot Start function is not impacted by the time varying OL boundary. If the continuing simulation includes the time varying OL function then it will be used. If the continuing simulation does not include the time varying OL function the head from the hot start time point.