3D/2D modelling suite for integral water solutions Delft3D Hydro-Morphodynamics User Manual Delft3D-FLOW Simulation of multi-dimensional hydrodynamic flows and transport phenomena, including sediments User Manual Hydro-Morphodynamics Version: 3.15.34158 28 May 2014 Delft3D-FLOW, User Manual Published and printed by: Deltares Boussinesqweg 2629 HV Delft P.O Box 177 2600 MH Delft The Netherlands For sales contact: telephone: +31 88 335 81 88 fax: +31 88 335 81 11 e-mail: sales@deltaressystems.nl www: http://www.deltaressystems.nl telephone: fax: e-mail: www: +31 88 335 82 73 +31 88 335 85 82 info@deltares.nl http://www.deltares.nl For support contact: telephone: +31 88 335 81 00 fax: +31 88 335 81 11 e-mail: support@deltaressystems.nl www: http://www.deltaressystems.nl Copyright © 2014 Deltares All rights reserved No part of this document may be reproduced in any form by print, photo print, photo copy, microfilm or any other means, without written permission from the publisher: Deltares Contents Contents A guide to this manual 1.1 Introduction 1.2 Manual version and revisions 1.3 Typographical conventions 1.4 Changes with respect to previous versions 1 2 Introduction to Delft3D-FLOW 2.1 Areas of application 2.2 Standard features 2.3 Special features 2.4 Coupling to other modules 2.5 Utilities 2.6 Installation and computer configuration 7 8 9 Getting started 3.1 Overview of Delft3D 3.2 Starting Delft3D 3.3 Getting into Delft3D-FLOW 3.4 Exploring some menu options 3.5 Exiting the FLOW-GUI 11 11 11 12 15 17 Graphical User Interface 4.1 Introduction 4.2 MDF-file and attribute files 4.3 Filenames and conventions 4.4 Working with the FLOW-GUI 4.4.1 Starting the FLOW-GUI 4.4.2 Visualisation Area window 4.5 Input parameters of MDF-file 4.5.1 Description 4.5.2 Domain 4.5.2.1 Grid parameters 4.5.2.2 Bathymetry 4.5.2.3 Dry points 4.5.2.4 Thin dams 4.5.3 Time frame 4.5.4 Processes 4.5.5 Initial conditions 4.5.6 Boundaries 4.5.6.1 Flow boundary conditions 4.5.6.2 Transport boundary conditions 4.5.7 Physical parameters 4.5.7.1 Constants 4.5.7.2 Viscosity 4.5.7.3 Heat flux model 4.5.7.4 Sediment 4.5.7.5 Morphology 4.5.7.6 Wind 4.5.7.7 Tidal forces 19 19 19 20 21 21 24 26 27 27 27 33 35 37 39 41 44 47 54 62 65 65 70 74 78 82 86 88 Deltares iii Delft3D-FLOW, User Manual 4.5.8 4.5.9 4.6 4.7 Numerical parameters Operations 4.5.9.1 Discharge 4.5.9.2 Dredging and dumping 4.5.10 Monitoring 4.5.10.1 Observations 4.5.10.2 Drogues 4.5.10.3 Cross-sections 4.5.11 Additional parameters 4.5.12 Output 4.5.12.1 Storage 4.5.12.2 Print 4.5.12.3 Details Save the MDF and attribute files and exit Importing, removing and exporting of data Tutorial 5.1 Introduction – MDF-file and attribute files 5.2 Filenames and conventions 5.3 FLOW Graphical User Interface 5.3.1 Introduction 5.3.2 Saving the input data 5.4 Description 5.5 Domain 5.5.1 Grid parameters 5.5.2 Bathymetry 5.5.3 Dry points 5.5.4 Thin dams 5.6 Time frame 5.7 Processes 5.8 Initial conditions 5.9 Boundaries 5.10 Physical parameters 5.10.1 Constants 5.10.2 Roughness 5.10.3 Viscosity 5.10.4 Wind 5.11 Numerical parameters 5.12 Operations 5.13 Monitoring 5.13.1 Observation points 5.13.2 Drogues 5.13.3 Cross-sections 5.14 Additional parameters 5.15 Output 5.16 Save MDF-file 5.17 Additional exercises 5.18 Execute the scenario 5.19 Inspect the results Execute a scenario iv 88 93 93 97 97 98 99 100 102 103 104 108 110 110 112 113 113 114 115 115 117 118 118 118 121 122 125 127 128 130 130 136 137 138 138 139 141 142 144 144 146 147 148 148 151 152 152 153 159 Deltares Contents 6.1 6.2 6.3 6.4 6.5 Running a scenario 6.1.1 Parallel calculations 6.1.1.1 DomainDecomposition 6.1.1.2 MPI-based parallel 6.1.1.3 Fluid mud 6.1.1.4 Mormerge 6.1.2 Running a scenario using Delft3D-MENU 6.1.3 Running a scenario using a batch script Run time Files and file sizes 6.3.1 History file 6.3.2 Map file 6.3.3 Print file 6.3.4 Communication file Command-line arguments Frequently asked questions Visualise results 7.1 Introduction 7.2 Working with GPP 7.2.1 Overview 7.2.2 Launching GPP 7.3 Working with Delft3D-QUICKPLOT 7.4 GISVIEW interface 159 159 159 159 160 160 160 162 162 164 165 165 166 166 167 168 169 169 169 169 171 172 174 Manage projects and files 175 8.1 Introduction 175 8.1.1 Managing projects 176 8.1.2 Managing files 176 Conceptual description 9.1 Introduction 9.2 General background 9.2.1 Range of applications of Delft3D-FLOW 9.2.2 Physical processes 9.2.3 Assumptions underlying Delft3D-FLOW 9.3 Governing equations 9.3.1 Hydrodynamic equations 9.3.2 Transport equation (for σ -grid) 9.3.3 Coupling between intake and outfall 9.3.4 Equation of state 9.4 Boundary conditions 9.4.1 Flow boundary conditions 9.4.1.1 Vertical boundary conditions 9.4.1.2 Open boundary conditions 9.4.1.3 Shear-stresses at closed boundaries 9.4.2 Transport boundary conditions 9.4.2.1 Open boundary conditions for the transport equation 9.4.2.2 Thatcher-Harleman boundary conditions 9.4.2.3 Vertical boundary conditions transport equation 9.5 Turbulence Deltares 177 177 177 177 178 179 180 186 194 197 198 200 201 201 205 212 212 212 213 215 215 v Delft3D-FLOW, User Manual 9.5.1 Algebraic turbulence model (AEM) 9.5.1.1 Algebraic closure model (ALG) 9.5.1.2 Prandtl’s Mixing Length model (PML) 9.5.2 k -L turbulence model 9.5.3 k -ε turbulence model 9.5.4 Low Reynolds effect 9.6 Secondary flow; sigma-model only 9.7 Wave-current interaction 9.7.1 Forcing by radiation stress gradients 9.7.2 Stokes drift and mass flux 9.7.3 Streaming 9.7.4 Wave induced turbulence 9.7.5 Enhancement of the bed shear-stress by waves 9.8 Heat flux models 9.8.1 Heat balance 9.8.2 Solar radiation 9.8.3 Atmospheric radiation (long wave radiation) 9.8.4 Back radiation (long wave radiation) 9.8.5 Effective back radiation 9.8.6 Evaporative heat flux 9.8.7 Convective heat flux 9.8.8 Overview of heat flux models 9.9 Tide generating forces 9.9.1 Tidal potential of Equilibrium tide 9.9.2 Tidal potential of Earth tide 9.10 Hydraulic structures 9.10.1 3D gate 9.10.2 Quadratic friction 9.10.3 Linear friction 9.11 Flow resistance: bedforms and vegetation 9.11.1 Bedform heights 9.11.1.1 Dune height predictor 9.11.1.2 Van Rijn (2007) bedform roughness height predictor 9.11.2 Trachytopes 9.11.2.1 Trachytope classes 9.11.2.2 Averaging and accumulation of trachytopes 9.11.3 (Rigid) 3D Vegetation model 10 Numerical aspects of Delft3D-FLOW 10.1 Staggered grid 10.2 sigma-grid and Z -grid 10.3 Definition of model boundaries 10.4 Time integration of the 3D shallow water equations 10.4.1 ADI time integration method 10.4.2 Accuracy of wave propagation 10.4.3 Iterative procedure continuity equation 10.4.4 Horizontal viscosity terms 10.4.5 Overview time step limitations 10.5 Spatial discretizations of 3D shallow water equations 10.5.1 Horizontal advection terms 10.5.2 Vertical advection term vi 219 219 220 221 223 225 226 230 232 234 235 236 237 242 244 244 247 248 248 249 252 252 255 256 258 259 259 259 260 260 260 261 263 264 265 271 273 275 275 277 277 279 280 282 283 283 284 284 285 289 Deltares Contents 10.5.3 Viscosity terms 10.6 Solution method for the transport equation 10.6.1 Cyclic method 10.6.2 Van Leer-2 scheme 10.6.3 Vertical advection 10.6.4 Forester filter 10.7 Numerical implementation of the turbulence models 10.8 Drying and flooding 10.8.1 Bottom depth at water level points 10.8.2 Total water depth at velocity points 10.8.3 Drying and flooding criteria 10.9 Hydraulic structures 10.9.1 3D Gate 10.9.2 Quadratic friction 10.9.2.1 Barrier 10.9.2.2 Bridge 10.9.2.3 Current Deflection Wall 10.9.2.4 Weir 10.9.2.5 Porous plate 10.9.2.6 Culvert 10.9.3 Linear friction 10.9.4 Floating structure 10.10 Artificial vertical mixing due to σ co-ordinates 10.11 Smoothing parameter boundary conditions 10.12 Assumptions and restrictions 11 Sediment transport and morphology 11.1 General formulations 11.1.1 Introduction 11.1.2 Suspended transport 11.1.3 Effect of sediment on fluid density 11.1.4 Sediment settling velocity 11.1.5 Dispersive transport 11.1.6 Three-dimensional wave effects 11.1.7 Initial and boundary conditions 11.1.7.1 Initial condition 11.1.7.2 Boundary conditions 11.2 Cohesive sediment 11.2.1 Cohesive sediment settling velocity 11.2.2 Cohesive sediment dispersion 11.2.3 Cohesive sediment erosion and deposition 11.2.4 Interaction of sediment fractions 11.2.5 Influence of waves on cohesive sediment transport 11.2.6 Inclusion of a fixed layer 11.2.7 Inflow boundary conditions cohesive sediment 11.3 Non-cohesive sediment 11.3.1 Non-cohesive sediment settling velocity 11.3.2 Non-cohesive sediment dispersion 11.3.2.1 Using the algebraic or k -L turbulence model 11.3.2.2 Using the k -ε turbulence model 11.3.3 Reference concentration Deltares 290 290 291 292 293 293 295 296 297 299 303 304 305 306 307 308 308 309 311 311 314 314 315 319 320 323 323 323 323 324 325 325 326 327 327 327 328 329 329 329 330 331 331 331 331 332 332 332 334 335 vii Delft3D-FLOW, User Manual 11.4 11.5 11.6 11.7 11.8 11.3.4 Non-cohesive sediment erosion and deposition 11.3.5 Inclusion of a fixed layer 11.3.6 Inflow boundary conditions non-cohesive sediment Bedload sediment transport of non-cohesive sediment 11.4.1 Basic formulation 11.4.2 Suspended sediment correction vector 11.4.3 Interaction of sediment fractions 11.4.4 Inclusion of a fixed layer 11.4.5 Calculation of bedload transport at open boundaries 11.4.6 Bedload transport at U and V velocity points 11.4.7 Adjustment of bedload transport for bed-slope effects Transport formulations for non-cohesive sediment 11.5.1 Van Rijn (1993) 11.5.2 Engelund-Hansen (1967) 11.5.3 Meyer-Peter-Muller (1948) 11.5.4 General formula 11.5.5 Bijker (1971) 11.5.5.1 Basic formulation 11.5.5.2 Transport in wave propagation direction (Bailard-approach) 11.5.6 Van Rijn (1984) 11.5.7 Soulsby/Van Rijn 11.5.8 Soulsby 11.5.9 Ashida–Michiue (1974) 11.5.10 Wilcock–Crowe (2003) 11.5.11 Gaeuman et al (2009) laboratory calibration 11.5.12 Gaeuman et al (2009) Trinity River calibration Morphological updating 11.6.1 Bathymetry updating including bedload transport 11.6.2 Erosion of (temporarily) dry points 11.6.3 Dredging and dumping 11.6.4 Bed composition models and sediment availability Specific implementation aspects Validation 12 Fixed layers in Z -model 12.1 Background 12.2 Time integration of the 3D shallow water equations 12.2.1 ADI time integration method 12.2.2 Linearisation of the continuity equation 12.3 Bed stress term 12.4 Horizontal viscosity terms 12.4.1 Overview time step limitations 12.5 Spatial discretisations of 3D shallow water equations 12.5.1 Horizontal advection terms 12.5.2 Vertical advection term 12.5.3 Viscosity terms 12.6 Solution method for the transport equation 12.6.1 Horizontal advection 12.6.1.1 Van Leer-2 scheme 12.6.1.2 Implicit upwind scheme 12.6.2 Vertical advection viii 336 339 340 340 340 341 341 342 343 343 344 347 347 352 352 353 353 354 355 357 359 360 363 364 364 365 366 368 369 370 371 372 373 375 375 378 379 380 380 381 381 381 382 383 383 384 386 386 387 387 Deltares Delft3D-FLOW, User Manual Figure E.4: Location and combination of water level and velocity controlled open boundaries Water level controlled open boundaries: Water level controlled open boundaries are always located just outside the first or last computational control volume The line through these water level points is called the (external) grid enclosure For Figure E.4 water level controlled open boundaries can be located at: lower: (m=2 to Mmax-1, n=1), left: (m=1, n=2 to Nmax-1), upper: (m=2 to Mmax-1, n=Nmax), right: (m=Mmax, n=2 to Nmax-1) Velocity controlled open boundaries: Velocity controlled open boundaries are either located at the (external) grid enclosure (in terms of the grid point (array) number) for the left and lower boundaries, or just inside the grid enclosure (in terms of the grid point (array) number) for the right and upper boundaries However, to make the location of open boundaries irrespective of the open boundary type, also the right and upper boundaries are indicated as being located at the grid enclosure (at implementation level the grid number is decreased by one) For Figure E.4 the velocity controlled open boundaries can be located at: lower: (m=2 to Mmax-1, n=1), left: (m=1, n=2 to Nmax-1), upper: (m=2 to Mmax-1, n=Nmax), internally (m=2 to Mmax-1, Nmax-1), right: (m=Mmax, n=2 to Nmax-1), internally (m=Mmax-1, n=2 to Nmax-1) Remark: The water level points at the corner points (1,1), (1,Mmax), (Mmax, Nmax) and (1, Nmax) are not used in the numerical approximation of the hydrodynamic equations 674 Deltares Computational grid For internal grid enclosures (defining an internal area with either closed or open boundaries) the same rules apply On summarising: The grid generator displays the computational control volumes, i.e the grid cells that are (potentially) used in the computation For the definition of open boundaries the number of (possibly) active grid points in both (horizontal) directions is extended by one grid point These additional grid (array) points are included in the number of grid points as displayed in the FLOW-GUI; Mmax and Nmax The grid file of the grid generator only includes the indices of the computational control volumes, i.e does not include indices of the additional grid (array) points The grid enclosure generated by RGFGRID takes these additional (array) points into account QUICKIN takes the additional grid (array) points into account and automatically assigns them a value of -999 In the Visualisation Area of the FLOW-GUI the numerical grid is displayed as created with RGFGRID The additional points nor the grid enclosure are displayed Example: Suppose you want to define a rectilinear grid in a channel of dimensions 10 000 ∗ 000 m2 with a grid size of 1000 m This will require a grid of 10 ∗ grid cells and thus 11 ∗ grid points When you apply RGFGRID to generate this grid you must set the grid dimensions to 11 ∗ (RGFGRID handles grid points, not grid cells) The grid file will contain blocks of rows with 11 grid point indices, one block for the x-coordinates and the second block for the y -co-ordinates The grid enclosure will include the extra grid (array) points and the default grid enclosure will go through the points (1, 1), (12, 1), (12, 7) and (1, 7) In the Visualisation Area a grid will be displayed of 11 ∗ grid points (with 10 ∗ grid cells) In the FLOW-GUI Mmax = 12 and Nmax = Figure E.5 shows the grid and the grid enclosure for this example The closed (thick) outer line is the grid enclosure, the thinner inner line represents the computational grid The number of computational control volumes inside the area enclosed by thin lines is 10 ∗ 5, as it was meant to be Remarks: The channel only has the required area of · 107 m2 if the left and right open boundaries are velocity controlled The channel area will be 5.5 · 107 m2 when both open boundaries are water level controlled and 5.25 · 107 m2 with a combination of water level and velocity controlled boundaries In (almost) all practical applications this artefact is unimportant and transparent, only in these simple cases you must be aware of these peculiarities You must take into account the type of boundary conditions you are going to apply when Deltares 675 Delft3D-FLOW, User Manual Figure E.5: Straight channel with 10 ∗ computational grid cells you define the computational grid 676 Deltares F Delft3D-NESTHD F.1 Introduction Delft3D-FLOW models require hydrodynamic and transport boundary conditions In case the boundary conditions of a model are generated by a larger (overall) model we speak of a nested model Nesting in Delft3D-FLOW is executed in three steps, using two separate utilities and the Delft3D-FLOW program This manual describes the steps to generate timeseries boundary conditions for a nested Delft3D-FLOW model In principle, the nested boundary conditions are generated by bi-linear interpolation of computational results at monitoring stations of the overall model The procedure to generate nested time-series boundary conditions consists of steps: Using the tool NESTHD1 a list of monitoring stations in the overall model, needed for the interpolation, can be generated In addition to this, the program generates the nesting administration, i.e the link between the boundary support points in the nested model and the monitoring stations in the overall model Run the overall model with the list of monitoring stations generated by NESTHD1 The actual time-series boundary conditions for the nested model are generated by NESTHD2 using the history file of the overall model and the nest administration Restrictions: At present, the nesting programs have the following limitations: Both model grids must be supplied in separate grid files and must be defined in the same co-ordinate system Hydrodynamic time-series boundary conditions for the nested model are of the water level or (perpendicular) velocity type Discharge and Riemann boundary conditions are not implemented yet The boundary definition of the nested model has to be supplied as an attribute file Temporary dry points in the overall model are not taken into account in the nesting programs For a nested 3D model the number and the thickness of the layers must be identical to the overall model The generated time-series boundary conditions are written to a time-series file This implies that the reference date of a simulation with the nested model must be identical to the reference date of the overall model simulation used to generate the boundary conditions Deltares 677 Delft3D-FLOW, User Manual Figure F.1: Hydrodynamics selection window with the Tools option Figure F.2: Additional tools window with the NESTHD1 and NESTHD2 options 678 Deltares Delft3D-NESTHD Figure F.3: Specification of input and output files for NESTHD1 F.2 How to use NESTHD1 NESTHD1 is part of the Delft3D-FLOW tools To access NESTHD1, first set the current directory to the directory where you have stored the required input files Then: Select Tools in the Hydrodynamics selection window, see Figure F.1: Next Figure F.2 is displayed To start NESTHD1: Select Nesting (1) You are asked to supply the following information, see also Figure F.3: The filename of the grid file of the overall model The filename of the enclosure file of the overall model The filename of the grid file of the nested model The filename of the enclosure file of the nested model The filename of the boundary definition file of the nested model This file must fulfil the conventions as specified in the Delft3D-FLOW manual The name of the file which will contain the nest administration An example of this file as used for nesting of the Stonecutters Island model in the Pearl Estuary model is given in section F.4 The name of the file which will contain the position of the monitoring stations in the overall model This file can be used directly in a Delft3D-FLOW simulation with the overall model After running NESTHD1 a simulation with the overall model should be executed using the monitoring stations as generated by NESTHD1 Deltares 679 Delft3D-FLOW, User Manual Figure F.4: Specification of input and output files for NESTHD2 F.3 How to use NESTHD2 NESTHD2 is part of the Delft3D-FLOW tools To access NESTHD2, first set the current directory to the directory where you have stored the required input files Then enter the Tools menu, see Figure F.1 To start NESTHD2, see Figure F.2: Select Nesting (2) You are asked to supply the following information, see also Figure F.4: The boundary definition file of the detailed model The name of the administration file as generated by NESTHD1 The extension (runid) of the history file of the overall model The name of the file which will contain the hydrodynamic boundary conditions This file can be used directly in a simulation with the nested model The name of the file which will contain the transport boundary conditions This file can be used directly in a simulation with the nested model The filename of the diagnostic file You are advised to inspect this file An optional (constant) adjustment of the boundary values at water level boundaries This can be used if both models have a different vertical reference level In case of a 3-dimensional overall model and a nested model with velocity boundaries you are asked if you want to generate depth-averaged or 3-dimensional velocity boundary conditions For each of the constituents in the overall model you are asked: 9.1 9.2 9.3 9.4 If you want to generate boundary conditions for this constituent How much you want to add to the computed overall model value for this constituent The maximum value for this constituent The minimum value for this constituent 10 The type of transport profile You can chose between a uniform profile for depth-averaged computations with the nested model, a linear profile using only the computed boundary values at the surface and the bed and a 3D-profile resulting in boundary values for all computational layers of the nested model 680 Deltares Delft3D-NESTHD Figure F.5: Overview grids overall and nested models F.4 Example This example describes the nesting of the Siu Lam model in the Pearl Estuary model The grid layout of both models is given in Figure F.5: The input and output files of this example are stored in the FLOW Tutorial directory: Using NESTHD1 the monitoring stations file and the administration file are generated The contents of these files are shown below: Part of monitoring stations file : ✭▼✱◆✮ ✭▼✱◆✮ ✭▼✱◆✮ ✭▼✱◆✮ ✭▼✱◆✮ ✭▼✱◆✮ ✳ ✳ ✳ ✳ ✳ ✳ ✭▼✱◆✮ ✭▼✱◆✮ ✭▼✱◆✮ ✭▼✱◆✮ ✭▼✱◆✮ ✭▼✱◆✮ ❂ ❂ ❂ ❂ ❂ ❂ ✳ ✳ ❂ ❂ ❂ ❂ ❂ ❂ ✭ ✭ ✭ ✭ ✭ ✭ ✳ ✳ ✭ ✭ ✭ ✭ ✭ ✭ ✷✼✱ ✷✼✱ ✷✼✱ ✷✼✱ ✷✽✱ ✷✽✱ ✸✺✮ ✸✻✮ ✹✶✮ ✹✷✮ ✸✺✮ ✸✻✮ ✷✼ ✷✼ ✷✼ ✷✼ ✷✽ ✷✽ ✸✺ ✸✻ ✹✶ ✹✷ ✸✺ ✸✻ ✷✾✱ ✷✾✱ ✷✾✱ ✷✾✱ ✸✶✱ ✸✶✱ ✸✺✮ ✸✻✮ ✹✶✮ ✹✷✮ ✸✵✮ ✸✶✮ ✷✾ ✷✾ ✷✾ ✷✾ ✸✶ ✸✶ ✸✺ ✸✻ ✹✶ ✹✷ ✸✵ ✸✶ These monitoring stations have been included (added) to the already existing file of the Pearl model In this tutorial Part of the administration file : Deltares 681 Delft3D-FLOW, User Manual ✯ ✯ ❉❡❧t❛r❡s✱ ◆❊❙❚❍❉✶ ❱❡rs✐♦♥ ✶✳✺✻✳✵✶✳✺✵✻✼✱ ❖❝t ✸✵ ✷✵✵✽✱ ✵✾✿✺✷✿✷✻ ✯ ✯ ❘✉♥ ❞❛t❡✿ ✷✵✵✽✴✶✵✴✸✵ ✵✾✿✺✻✿✺✷ ✯ ✯ ◆❛♠❡ ❣r✐❞ ❢✐❧❡ ♦✈❡r❛❧❧ ♠♦❞❡❧ ✿ ♦✈❡r❛❧❧✳❣r❞ ✯ ◆❛♠❡ ❡♥❝❧♦s✉r❡ ❢✐❧❡ ♦✈❡r❛❧❧ ♠♦❞❡❧ ✿ ♦✈❡r❛❧❧✳❡♥❝ ✯ ✯ ◆❛♠❡ ❣r✐❞ ❢✐❧❡ ❞❡t❛✐❧❡❞ ♠♦❞❡❧ ✿ ♥❡st❡❞✳❣r❞ ✯ ◆❛♠❡ ❡♥❝❧♦s✉r❡ ❢✐❧❡ ❞❡t❛✐❧❡❞ ♠♦❞❡❧ ✿ ♥❡st❡❞✳❡♥❝ ✯ ◆❛♠❡ ❜♥❞✳ ❞❡❢✐♥✐t✐♦♥ ❢✐❧❡ ❞❡t❛✐❧❡❞ ♠♦❞❡❧ ✿ ♥❡st❡❞✳❜♥❞ ✯ ✯ ◆❛♠❡ ♥❡st ❛❞♠✐♥✐str❛t✐♦♥ ❢✐❧❡ ✿ ♥❡st❤❞✶✳❛❞♠ ✯ ◆❛♠❡ ❋▲❖❲ ♦❜s❡r✈❛t✐♦♥ ❢✐❧❡ ✿ ♥❡st❤❞✶✳♦❜s ✯ ◆❡st ❛❞♠✐♥✐str❛t✐♦♥ ❢♦r ✇❛t❡r ❧❡✈❡❧ s✉♣♣♦rt ♣♦✐♥t ✭▼✱◆✮ ❂ ✭ ✹✾✱ ✷✽ ✹✺ ✵✳✺✶✵✼ ✷✾ ✹✺ ✵✳✶✽✷✷ ✷✽ ✹✻ ✵✳✷✷✻✹ ✷✾ ✹✻ ✵✳✵✽✵✽ ◆❡st ❛❞♠✐♥✐str❛t✐♦♥ ❢♦r ✇❛t❡r ❧❡✈❡❧ s✉♣♣♦rt ♣♦✐♥t ✭▼✱◆✮ ❂ ✭ ✺✻✱ ✷✽ ✹✸ ✵✳✶✹✾✻ ✷✾ ✹✸ ✵✳✵✷✼✶ ✷✽ ✹✹ ✵✳✻✾✼✷ ✷✾ ✹✹ ✵✳✶✷✻✶ ✳ ✳ ✳ ✳ ✳ ✳ ✳ ✳ ◆❡st ❛❞♠✐♥✐str❛t✐♦♥ ❢♦r ✇❛t❡r ❧❡✈❡❧ s✉♣♣♦rt ♣♦✐♥t ✭▼✱◆✮ ❂ ✭ ✺✸✱ ✹✼ ✹✺ ✵✳✽✺✻✸ ✹✽ ✹✺ ✵✳✶✹✸✼ ✵ ✵ ✵✳✵✵✵✵ ✵ ✵ ✵✳✵✵✵✵ ◆❡st ❛❞♠✐♥✐str❛t✐♦♥ ❢♦r ✇❛t❡r ❧❡✈❡❧ s✉♣♣♦rt ♣♦✐♥t ✭▼✱◆✮ ❂ ✭ ✺✼✱ ✹✼ ✹✹ ✵✳✸✷✻✽ ✹✽ ✹✹ ✵✳✵✾✻✹ ✹✼ ✹✺ ✵✳✹✹✺✹ ✹✽ ✹✺ ✵✳✶✸✶✹ ◆❡st ❛❞♠✐♥✐str❛t✐♦♥ ❢♦r ✈❡❧♦❝✐t② s✉♣♣♦rt ♣♦✐♥t ✭▼✱◆✮ ❂ ✭ ✹✾✱ ✷✽ ✹✺ ✵✳✸✽✽✽ ✷✾ ✹✺ ✵✳✸✷✶✻ ✷✽ ✹✻ ✵✳✶✺✽✺ ✷✾ ✹✻ ✵✳✶✸✶✶ ◆❡st ❛❞♠✐♥✐str❛t✐♦♥ ❢♦r ✈❡❧♦❝✐t② s✉♣♣♦rt ♣♦✐♥t ✭▼✱◆✮ ❂ ✭ ✺✻✱ ✷✽ ✹✸ ✵✳✶✸✻✽ ✷✾ ✹✸ ✵✳✵✼✼✸ ✷✽ ✹✹ ✵✳✺✵✷✷ ✷✾ ✹✹ ✵✳✷✽✸✽ ✳ ✳ ✳ ✳ ✳ ✳ ✳ ✳ ◆❡st ❛❞♠✐♥✐str❛t✐♦♥ ❢♦r ✈❡❧♦❝✐t② s✉♣♣♦rt ♣♦✐♥t ✭▼✱◆✮ ❂ ✭ ✺✸✱ ✹✼ ✹✺ ✵✳✾✾✼✸ ✹✽ ✹✺ ✵✳✵✵✷✼ ✵ ✵ ✵✳✵✵✵✵ ✵ ✵ ✵✳✵✵✵✵ ◆❡st ❛❞♠✐♥✐str❛t✐♦♥ ❢♦r ✈❡❧♦❝✐t② s✉♣♣♦rt ♣♦✐♥t ✭▼✱◆✮ ❂ ✭ ✺✼✱ ✹✼ ✹✹ ✵✳✹✷✹✼ ✹✽ ✹✹ ✵✳✵✸✺✺ ✹✼ ✹✺ ✵✳✹✾✽✷ ✹✽ ✹✺ ✵✳✵✹✶✻ ✶✮ ✶✮ ✼✹✮ ✼✹✮ ✶✮ ❆♥❣❧❡ ❂ ✷✵✳✹✵✾ ✶✮ ❆♥❣❧❡ ❂ ✷✵✳✹✵✾ ✼✹✮ ❆♥❣❧❡ ❂ ✶✷✷✳✻✸✷ ✼✹✮ ❆♥❣❧❡ ❂ ✶✷✷✳✻✸✷ Remarks: 682 Deltares Delft3D-NESTHD When you run the NESTHD1 tool, the location of the nested boundary should be final The type of data (water level or velocity) need not be final That’s why NESTHD1 generates the administration for both The type of data should also be final NESTHD1 only generates the administration for time-series The first lines, starting with an asterisk, are comment lines These are followed by several blocks of lines containing the information on nesting of water level and transport boundaries The first of these lines gives the indices of the boundary support point This line is followed by lines containing the indices of the surrounding overall model monitoring stations and the relative weights of these stations The information on nesting of water levels and transport is followed by information on nesting of velocities To adjust the nesting, for instance to avoid the use of a monitoring station that dries during the computation, the administration file should be adjusted by hand Before running NESTHD2, first the overall model should be run, using the file Remark: It is a good modelling practice to re-generate the bathymetry in the overall model using the detailed bathymetry of the nested model If you Verify this scenario the following warning will be generated: ✯✯✯ ❲❆❘◆■◆● ❙t❛t✐♦♥ ✭▼✱◆✮ ❂ ✭ ✷✽✱ ✹✻✮ ❧✐❡s ♦✉ts✐❞❡ t❤❡ ❝♦♠♣✉t❛t✐♦♥❛❧ ❞♦♠❛✐♥ This means that this required nesting stations lies on a dry point If you check the administration file, you will see that every boundary support point has at least overall nest stations Ignoring the nest station which lies on a dry point would result in the worst case that the nesting information only comes from overall station (If you check the administration file carefully, you will find out that the mentioned station is always part of a set of 4.) Using the administration file and the history file of the Pearl Estuary model, the boundary conditions for the Siu Lam model have been generated by running NESTHD2 The result files are the hydrodynamic flow boundary conditions and the transport boundary conditions The diagnostic file contains the following warning: ✯✯✯ ❲❛r♥✐♥❣✿ ◆❡st st❛t✐♦♥ ✭ ✷✽✱ ✹✻✮ ♥♦t ♦♥ ❤✐st♦r② ❢✐❧❡✳ ❲❡✐❣❤ts r❡s❡t This station, as noted before, lies on a dry point NESTHD2 then resets weights Deltares 683 Delft3D-FLOW, User Manual 684 Deltares PO Box 177 2600 MH Delft Rotterdamseweg 185 2629 HD Delft The Netherlands +31 (0)88 335 81 88 sales@deltaressystems.nl www.deltaressystems.nl