Super Work Package 2

Application of the Telemac suite

Mr Nicolas Chini Prof Peter Stansby

University of Manchester University of Manchester

Table of Contents
1. 2. Generalities about the TELEMAC suite ..................................................................................... 3 Setting up of a standard simulation............................................................................................. 3 2.1 2.2 2.3 2.4 2.5 3. 4. Mesh generation .................................................................................................................... 4 Steering file generation.......................................................................................................... 4 Modification of FORTRAN routines, if requested ................................................................ 5 Execution ............................................................................................................................... 5 Post processing ...................................................................................................................... 5

Application of the TELEMAC suite within FRMRC2 .............................................................. 6 Data collection ............................................................................................................................... 8 4.1 4.2 4.3 4.4 Bathymetry ............................................................................................................................ 8 Topography ........................................................................................................................... 8 Field measurements ............................................................................................................... 8 Numerical modelling results.................................................................................................. 9

5.

Coastal model .............................................................................................................................. 10 5.1 Mesh generation .................................................................................................................. 10

Work Package 2.1 Appendix 1 Deliverable 2.1

28.09.2011

1

5.2 5.3 6.

Telemac-2d simulation ........................................................................................................ 10 Tomawac simulation ........................................................................................................... 15

NEARSHORE MODELLING ................................................................................................... 19 6.1 6.2 6.3 Mesh generation .................................................................................................................. 19 Tomawac simulations .......................................................................................................... 20 Coupling with the Eurotop Neural Network application ..................................................... 21

7.

Flooding modelling...................................................................................................................... 22 7.1 7.2 Mesh generation .................................................................................................................. 22 Telemac-2d simulation ........................................................................................................ 23

8.

References .................................................................................................................................... 24

Work Package 2.1 Appendix 1 Deliverable 2.1

28.09.2011

2

wetting and drying. module execution and post-precessing. Tomawac This module solves the wave action conservation equation taking into account wind wave generation. earth rotation. The execution of the model is carried out by calling several PERL scripts. tracers.org Within the FRMRC.opentelemac. bathymetric wave breaking and bottom friction (Benoit et al. Alongside with these solvers.0 : Telemac-2d This module solves the non linear depth-averaged shallow-water equations. and especially the website www. Setting up of a standard simulation For any of these two modules belonging to the TELEMAC suite.opentelemac. In July 2010. white capping.. a standard set up is proposed to perform simulations.1 28. sediment transport and morphodynamics. wave-wave interactions. HR WALLINGFORD and BAW since the early 90’s. 2 modules from the TELEMAC suite are used in their open source version V6. 2. ground water flows.09. 1996). steering file creation. the software comes with a pre-processing module used for the generating the input files and a post-processing module to handle the outputs of a simulation. the reader is encouraged to consult the references. FORTRAN file creation. Work Package 2.org for the system installation procedure. A finite elements library Bief. wind wave propagation. including the effects of bottom friction. CETMEF. SOGREAH. For further details. completes the software architecture. It consists into 5 main stages: mesh generation. The software has been developed and validated by EDF R&D/LNHE. the software was released in an open-source version and is freely downloadable from the following website: www. Generalities about the TELEMAC suite The hydro-informatics software TELEMAC is a finite element based solver for shallow water flows. weirs.2011 3 . porosity. tracer transport. wind.1 Appendix 1 Deliverable 2. diffusivity and addition of local sources(Hervouet. 2007).1. commonly used by any module.

the number of elements. The first one is a binary file containing the information about the mesh. The two remaining integers are respectively the point number in the global numbering and the point number in the boundary point numbering. Each line of this file provides the type of boundary conditions for one boundary point. The other constraints are the outer contour of the domain. These KEY-WORDS specify the input files and the output ones. where x and y are coordinates associated with the bed elevation. The user provides as input a bathymetry file in an ASCII format. The first free columns are three integers defining the type of boundary conditions on the free surface elevation and on the two velocity components.e. Each line contains 13 columns. They are all specified by the user. z.2011 4 . the islands boundary within the domain and the criteria for defining the local densification of nodes.1 28. the GEOMETRY FILE and the BOUNDARY CONDITIONS FILE generated by MATISSE are requested. The binary file is called the GEOMETRY FILE and the ASCII file is the BOUNDARY CONDITIONS FILE and they are used in the steering file. They provide respectively the type of boundary condition on the tracer.1 Appendix 1 Deliverable 2. the initial conditions.09. the connectivity table. the number of nodes per elements. here. Work Package 2. the boundary conditions. the number of nodes.2 Steering file generation This file is an ASCII file containing a list of KEY-WORDS and it is used to command the execution of the simulation. The following three columns specify the imposed values for the free surface elevation and the velocity components. Among the input files. and the numerical options. MATISSE can handle xyz file format. the general options of the simulation. its imposed value and the coefficient for the wall friction. It is. This module automatically operates a density map-driven automatic optimal Delaunay triangulation given constraints provided by the user. MATISSE interface is launched by. The following four values are used when a tracer in considered. the boundary points.1 Mesh generation The mesh consists in an unstructured grid composed of triangular elements. The seventh value is the coefficient affected to the wall friction. The KEY-WORDS are extracted from the dictionary contained in the lib directory of each module. generated by the module MATISSE. the coordinates of the points and the bathymetry. i. MATISSE generates two output files. The second file is an ASCII file containing information about boundary conditions. in a Terminal for Linux users or in a command prompt for WS users typing the command: >matisse -a 2.2.

or in a command prompt. If option –n is used. and vectors map. the user is allowed to modify subroutines of the program. Work Package 2. 2. The user can specify when he wants the simulation to start by using option –n and –d. Option –d hh:mm is used for any other time. for WS users. for Linux users. if needed and launch the simulation. This command will automatically create a temporary directory. The temporary directory is used to store all the files and executable requested for the simulation.5 Post processing The post-processing is performed using the application RUBENS whose interface is activated by typing in the command prompt or in a terminal: >rubens –a RUBENS reads the result file and can generates temporal series. In that case only the FORTRAN file is compiled and added to an archive created during the initial system installation. then the KEY-WORD FORTRAN FILE should be added in the Steering file.3 Modification of FORTRAN routines.2011 5 . If a FORTRAN file is created. 2. Option –s allows to print the listing into a separated file.1 28. In that case.1 Appendix 1 Deliverable 2. the users can use different optional commands –opt. the following command: > module_name –opt case_name where module_name is the name of the considered module. It also allows computing some extra variables based on the printed output variables. the user should create a FORTRAN file where the modified subroutines are saved.4 Execution The execution of a simulation is performed by typing in a Terminal. The case_name is the name of the Steering file. either telemac2d. if requested For particular cases. That permits not to recompile the entire system when a subroutine is modied.2. Option –D is used when compilation and execution are performed using a debugger. compile the FORTRAN file. surface colours map. tomawac.09. then the simulation starts at 8pm. During the call of one module. artemis or sisyphe.

2007. Eventually. These 3 TELEMAC system based models are presented successively in the following sections. At that location. Work Package 2. In order to perform these nearshore transformations. these nearshore conditions are extracted in order to compute the water levels and the wave integrated parameters at the toe of the structure. The outputs from the Regional Operational Model (ROM) is imposed along the boundary of a coastal domain where the TELEMAC system is used to transfer water levels and wind waves towards the nearshore at the water depth of about 10m.1 Appendix 1 Deliverable 2.2011 6 . a nearshore model. is set up to use once again the TELEMAC suite.3.van Gent et al. Application of the TELEMAC suite within FRMRC2 The Super Work Package 2 of FRMRC2 was dedicated to wave overtopping and induced coastal flooding modelling. with emphasis on the data exchange procedure between the different models.1 28. The output from this nearshore model are used as input to the Neural Network application of the Eurotop manual (Pullen et al. 2007). These two coastal phenomenons are generated by storm event related to large scale atmospheric conditions.09.. these rates are imposed to another TELEMAC system based model to produce flooding maps. which produces estimations of the overtopping discharge rates. Figure 1 presents the flow chart of the transferred data between the different modelling approaches in order to estimate flooding maps caused by wave overtopping. embedded within the coastal domain.. This multi-scale problem is solved by a downscaling procedure chaining different modelling approaches in order to transfer offshore wind generated wave and surge towards a seawall protecting a low-lying coastal land.

09.Figure 1: Modified chart flow showing the application of TELEMAC (bold blocks) into the downscaling procedure to assess coastal flooding from regional operational modelling.1 28.2011 7 .1 Appendix 1 Deliverable 2. Work Package 2.

ac. Work Package 2.uk/data/dataset_index/?source=data d. 4. a directional wave buoy was deployed off Cromer at the water depth of 30m.rl. and interviewing local residence.1 Bathymetry The bathymetry for the coastal modelling is provided by Seazone Ltd. These measurements are available on the BODC website.1 Appendix 1 Deliverable 2. under licence.ac.3 Field measurements a. Wind data Wind measurements at Gorleston and Weybourne are available from the BADC website: http://www. In 2002.4. The temporal series of these sensors are available on the BODC website: https://www.1 28. 4.2011 8 .2 Topography The topography for the flooding modelling is extracted from LIDAR data provided by the Environment Agency. Observed highest water mark The collection of information about the water marks during the 2007 storm event at Walcott was performed by a visit to the North Norfolk Borough Council. Water level data Two tidal gauges are located in the computational domain of the Coastal Domain one in Cromer and another one in Lowestoft. nearshore wave measurements were performed off Walcott. c. Data collection 4.09. Wave data In 1985-1987. These data are available through BOCD.bodc.uk/data/online_delivery/ntslf/ b. The bathymetry used for the nearshore modelling is extracted from the 1km Strategic bathymetric and beach survey and it is provided by the Environment Agency.badc.

These projections are an ensemble runs simulating the emission scenario SRES A1B with different model parameterisation.1 Appendix 1 Deliverable 2. c. Water level and velocity data Hindcast The hindcast for water levels and depth-averaged velocity components are provided by NOC using the model POLCOMS. These projections are an ensemble runs simulating the emission scenario SRES A1B with different model parameterisation. The model used for the climate projection is WAM developed by NOC. Wind data Hindcast Wind velocity and direction are hindcasted by the Metoffice for the November 2007. lon = 1.2011 9 .ac.1 28. The available hindcast example corresponds to the month of November 2007.09. Climate projections Water levels and depth-averaged velocities from the UKCP09 marine projections are provided by the Hadley Centre.mace.59E) located offshore Walcott.4.html. Data availability These data are made available through the following website:http://www.manchester.uk/research/sigs/coastalprocesses/projects/sw p2/index. Climate projections Waves from the UKCP09 marine projections are provided by NOC. b. The results are provided at a point (lat = 52.4 Numerical modelling results a. Wave data Hindcast The hindcast of waves for the month of November 2007 is provided by NOC using the model WAM. d. The model used for the climate projection is CS3 developed by NOC.950N. Work Package 2.

depending on the criticality of the flow. The coastline is located at the Lowest Astronomical Tide. one needs to impose either the water elevation or the velocity components. Coastal model 5. The file provided by Seazone Ltd. the outputs from ROM are imposed. The access to the bathymetry is subjected to licensing. MATISSE. 1000m over the sandbanks and 700m along the coastline. The bathymetry covers the South-West of North Sea.2 Telemac-2d simulation a. This computational mesh is used both for propagating the surges and the tides along the coastline and for the propagation of wind waves towards the shoreline. meaning that no flux across that boundary is permitted. produces a mesh of 5506 elements (Figure 2). Along the maritime boundary points.09.1 Appendix 1 Deliverable 2. The coordinates of bathymetric points are expressed in Eastings and Northings.). Boundary conditions imposition As previously stated. For tidal flows. The constraint on point density is about the 2400m in deep water. here ROM-POLCOMS. is a xyz file directly imported within MATISSE. Along the coastline. To run Telemac-2d.1 Mesh generation The initial bathymetry is provided from a digitalised chart map (Seazone Ltd. Work Package 2.1 28. Bottom elevations are referenced to the Chart Datum. the boundary conditions are provided by the Regional Operational Model. set up by the National Oceanography Centre. using this set of information.2011 10 . the subroutine BORD is modified to allow the imposition of both water depths and velocities along each nodes of the offshore boundary according to the output provided by the ROM-POLCOMS.5. 5. a solid boundary is assumed. To take into account these modifications. the direction of the flow varies temporally and spatially. The outer boundary of the computational domain of the Coastal model is set to be a rectangle whose dimensions are about 100km by 70km so that deep water conditions are imposed along the maritime boundary points.

Figure 2 : Computational mesh of the Coastal domain.1 Appendix 1 Deliverable 2. a radiation condition is employed (Hervouet. The green points represent the coastline and the red ones are the points from the grid of the operational model. This method adapts the boundary conditions according to the inner domain conditions and therefore requires solving the shallow-water equations with the methods of characteristics. 2007).1 28. The imposition of water levels and velocities over-constrains the model resulting in possible reflexion along the boundary. b. Blue points represent the offshore boundary. In order to avoid this numerical artefact.09.2011 11 . These Work Package 2. Consistency issues ROM-POLCOMS model provides hourly free surface elevation and depth-averaged velocities on a grid whose points are expressed into a latitude longitude system.

the shift of reference level for free surface elevation. a datum shift is then performed to bathymetry of the Coastal model. Each variable is stored for each time step in a table having NGX ⋅ NGY elements.CS3_POLCOMS. The red points on Figure 2 are the ROM points converted into Eastings and Northings. meaning that the output from ROM-POLCOMS are imposed to the Coastal model and that information from the Coastal domain is not send back to ROMPOLCOMS. whereas the bathymetry used for the Coastal domain is referenced to the Lowest Astronomical Tide level. Coordinate system consistency The coordinates of the ROM-POLCOMS points are expressed into Latitudes and Longitudes. In order to be consistent with the geographical system used for the Coastal computational grid. These levels are interpolated on the computational grid of the Coastal domain and the minimum free surface elevation over this period is saved at each points of the grid.htm. For consistency. That means that the zero for the free surface elevation in the Coastal model is the Lowest Astronomical Tide level.e. i.uk//osgbfaq.200711. This reanalyses contains 40 years of tidal level around the UK.09. a spatial interpolation is requested.bangor. allocating a value for the water depth and velocity components at each nodes of the offshore boundary of the Coastal domain. a spatial interpolation and a temporal interpolation. which is not the mean sea level.ac.1 Appendix 1 Deliverable 2. Given that the resolution of the ROM-POLCOMS grid is about 12km. The spatial interpolation Since the ROM-POLCOMS grid spatial resolution is different from the Coastal domain one. the ROM-POLCOMS points are converted into Eastings and Northings using software proposed by Phil Bradley and downloadable from http://pbrady. The value of the shift is estimated by using the ERA40 reanalyses of water level performed by Horsburgh and Wilson (2007) (Horsburgh and Wilson. Reference level consistency The free surface elevation provided by ROM-POLCOMS is referenced to the mean sea level.1 28. Thus this minimum is used as the shift datum to be applied to the bathymetry of the Coastal model so that the reference for its free surface elevation is the mean sea level. 2007). The coupling between ROM-POLCOMS and the Coastal model is a one-way coupling. much smaller than the wavelength of a tide. In order to perform this coupling. four consistency issues must be verified: the changes of the coordinate system.2011 12 . The temporal interpolation Work Package 2. a simple bilinear interpolation is applied to estimate the water level and the velocity components at each point of the maritime boundary of the Coastal model.outputs are saved into a binary file written in simple precision and called zet_UBVB. This minimum represents is assumed to provide with an estimate of the lowest astronomical tide.

latitude to eastings and northings. if T belongs to the segment [T1. The subroutine BORD is called at each time step and performs the temporal interpolation between two outputs of ROM-POLCOMS. The subroutine TEMP computes the time in seconds between the beginning of the simulation and the date of the first ROM-POLCOMS output. Then the test on T is once again performed. Work Package 2. The first two subroutines are modified TELEMAC subroutines and the three remaining ones have been especially created for the coupling with ROM. followed by a spatial interpolation.1 28. TEMP. the coordinates of the ROM-POLCOMS are converted into eastings and northings allowing selecting a mask of points surrounding the Coastal domain.2011 13 . This file contains 5 subroutines: BORD. This information is used to compute the coordinates of the ROM nodes and to select the mask of nodes that are used for the interpolations. READPOL. Then at each Telemac-2d time step. The subroutine BORD is the chief subroutine. A linear interpolation is chosen. Therefore an interpolation is needed to assess the offshore conditions at each time step of the Coastal model.T2]. The subroutine READPOL has been created for two purposes. then the record T1 is set to be the record T2 and a new record of ROM-POLCOMS is read. This mask selection is not necessary but it is implemented in order to reduce the number of iterations for the spatial interpolation. c. then a linear interpolation is performed. At the beginning of the simulation. The spatial and temporal interpolations are performed in the FORTRAN file. An initialisation step is added to find the two ROM-POLCOMS outputs surrounding the date of the beginning of the computation. which converts the coordinates of the ROM-POLCOMS points from longitude. The subroutine READPOL calls two subroutines: LL2XY. Coupling implementation The coupling is implemented in a way allowing the user (i) to specify the PATH and the name of the ROM-POLCOMS output file. It has been modified to take into account dates with 14 digits. LL2XY and INTERP2. The header contains information about ROMPOLCOMS grid. and (ii) the date of the beginning of the simulation. The second purpose is to read a record of the ROM-POLCOMS output file. If T is no longer between T1 and T2. and INTERP2 that performs the bilinear spatial interpolation. instead of 10 digits. calling TEMP and READPOL and generating temporally and spatially varying boundary conditions used by Telemac-2d.The time step of the Coastal model is much smaller than ROM-POLCOMS output period.1 Appendix 1 Deliverable 2. The date and time of the beginning of the simulation are stored respectively in the variables MARDAT and MARTIM. The procedure of the imposition of spatially and temporally boundary conditions is summarised the chart flow in Figure 3. No other information is requested from the user given that a ROMPOLCOMS output file is used. The first one is to read the header of the ROM-POLCOMS output file.09. which is for the present case: 01/11/2007 00:00. the records in the ROM-POLCOMS surrounding time T are located by reading the ROMPOLCOMS output file. The subroutine TEMP is part of the BIEF library.

Figure 3 : Temporal evaluation of the boundary conditions d. It also specifies the binary type of the file. The file is copied in the telemac2d temporary file and opened with the logical unit NBI2.2011 14 .CS3_POLCOMS. One should pay attention that the ROM-POLCOMS file is written with this option.1 28.09.1 Appendix 1 Deliverable 2.200711' Work Package 2. the KEY-WORD BINARY DATA FILE 2 can be: BINARY DATA FILE 2 = 'F:/POLCOMS/new/zet_UBVB. TELEMAC system is compiled with the option BIG ENDIAN. Example of KEY-WORDS in the Steering file Three KEY-WORDS are requested for the coupling with the regional operational model: BINARY DATA FILE 2 This KEY-WORD specifies the PATH and the name of the ROM-POLCOMS output file. As an example.

The first integer is the hours of the time. Boundary conditions imposition For Tomawac simulations.2011 15 . It requires three integers separated by semicolons. The temporal series is stored within an ASCII file. the boundary conditions are extracted and then interpolated along the boundary nodes of the Coastal domain.58 5. It requires three integers separated by semicolons.3. Wind input The wind velocity components are provided by the MetOffice at a location off Walcott. Offshore wave input The offshore wave input is provided by NOC and results from a simulation performed with WAM on the ROM computational grid. Water depths input Work Package 2.3 Tomawac simulation a. the third one are the seconds of the date As an example.8 ORIGINAL HOUR OF TIME This KEY-WORD provides the time of the beginning of the simulation. The wind field is assumed uniform. the subroutine LIMWAC is modified.11. The first integer is the year of the date.ORIGINAL DATE OF TIME This KEY-WORD provides the date of the beginning of the simulation.1 Appendix 1 Deliverable 2. the second one is the minutes of the date. the offshore wave input (either wave integrated parameters or wave directional spectrum) and the water depth. three inputs are requested: the wind. the KEYWORD should be: ORIGINAL DATE OF TIME = 2007. the KEY-WORD should be: ORIGINAL HOUR OF TIME = 15. for starting the simulation on the 8th of November 2007. The subroutine VENUTI is modified in order to read this file.1 28. Similarly to the procedure implemented for Telemac-2d. In order to do this.09. The outputs from ROM-WAM are stored in a file per day and two types of files are provided: the MAP files providing records of wave integrated parameters on the entire ROM grid and the SPE files containing the directional wave spectrum at points located near the Coastal domain boundary. the third one is the day of the date As an example. for starting the simulation on the 15:03:58. the second one is the month of the date.

(ii) the date of the beginning of the simulation.09.1 Appendix 1 Deliverable 2. and a number of subroutines dedicated to read and to interpolate of the wave directional spectrum from ROM-WAM. This perform by the subroutine MODIF_DEPTH called by LIMWAC. calling MODIF_DEPTH and ENRSPE. the coupling between ROM-WAM and Tomawac has been implemented in order to allow users to set up a simulation by only modifying the steering file of Tomawac. This routine calls also LL2XY in order to convert the ROM grid coordinates from longitude and latitude to eastings and northings. MODIF_DEPTH computes the water depth at each Coastal domain node. and generating temporally and spatially varying boundary conditions used by Tomawac. This file contains two TELEMAC subroutines LIMWAC and TEMP. regardless the velocity components. The subroutine LIMWAC is the chief subroutine. An initialisation step is added to find the two ROM-POLCOMS and ROM-WAM outputs surrounding the date of the beginning of the computation. The spatial and temporal interpolations are performed in the FORTRAN file. Eventually. The user has to specify (i) the PATH and the name of the ROM-POLCOMS output file. Although BORD was dedicated to compute the boundary conditions along the Coastal domain boundary nodes. using the subroutine INTERP_TEMP. The subroutine MODIF_DEPTH performs exactly the same statements as BORD used when running Telemac-2d. embedded within subroutine MODIF_DEPTH. A bilinear interpolation is used to assess the water depths at each nodes of the coastal model. the routine LECSPEC is called in order to assess the parameters of the ROM grid and the of the ROM-WAM spectrum grid.1 28. Work Package 2. the FORTRAN file also contains the TELEMAC subroutine VENUTI used for the wind input reading. The date and time of the beginning of the simulation are stored respectively in the variable DDC. b. The subroutine LIMWAC is called at each time step and performs the temporal interpolation between two outputs of ROM-WAM. the subroutines created for the coupling with ROM-POLCOMS.Water depths are provided by ROM-POLCOMS.2011 16 . (iii) the PATH and the name of ROM-WAM output file. The initialisation contains also the computation of the weights for the interpolation in the spectrum space. During this initialisation. Coupling implementation Similarly to the coupling between POLCOMS and Telemac-2d. the offshore boundary points from Tomawac are also assessed and then compared to the ROM grid points in order to compute the weights used for the spatial interpolation. These weights are computed after assessing the frequencies of in the ROM-WAM spectrum grid. During the initialisation procedure.

As an example. the coordinates of the ROM-POLCOMS and ROM-WAM are converted into eastings and northings allowing selecting a mask of points surrounding the Coastal domain.1 28. so that the file containing the record hindcast on the 1st of November at 1am is the one called PREFIX20071102000000 As an example. the KEYWORD should be: BINARY TIDAL WATER LEVEL FILE = 'F:/POLCOMS/new/zet_UBVB. so then a routine ENRSPE is set up to open and close these files as the time passes through. Then at each Telemac-2d time step. It also specifies the binary type of the file.200711' Work Package 2. then the record T1 is set to be the record T2 and a new record of ROM-WAM and ROM-POLCOMS is read. One should pay attention that the ROM-POLCOMS file is written with this option. since they are invariant. the month. The date and time at the end of the ROM-WAM output file is the last record saved in the file. If T is no longer between T1 and T2. the records in the ROM-POLCOMS and ROM-WAM surrounding time T are located by reading the both output file. followed by a spatial interpolation.09. The file is copied in the tomawac temporary file and opened with the logical unit NBI1. the day.CS3_POLCOMS. It also specifies the binary type of the file. the KEY-WORD BINARY DATA FILE 1 should be: BINARY DATA FILE 1 'F:/WAM/new/SPE20071102000000' = BINARY TIDAL WATER LEVEL FILE This KEY-WORD specifies the PATH and the name of the ROM-POLCOMS output file. DD.1 Appendix 1 Deliverable 2. MM. The file is copied in the tomawac temporary file and opened with the logical unit NMAB. HH. The format of the name of this file should be : PREFIXYYYYMMDDHHMNSC. YYYY is the year. At the beginning of the simulation.The computation of these various interpolation weights and their saving are not necessary but it is redundant to compute them at each time. if T belongs to the segment [T1. where PREFIX is either SPE or MAP. for starting the simulation on the 8th of November 2007. the seconds. TELEMAC system is compiled with the option BIG ENDIAN. the minutes and SC.2011 17 . Then the test on T is once again performed. ROM-WAM output file is a daily saving. MN. TELEMAC system is compiled with the option BIG ENDIAN. the hour. The user should give to that KEY-WORD the name of the first ROM-WAM file. c.T2]. Example of KEY-WORDS in the Steering file Four KEY-WORDS are requested for the coupling with the regional operational model: BINARY DATA FILE 1 This KEY-WORD specifies the PATH and the name of the ROM-WAM output file. The procedure of the imposition of spatially and temporally boundary conditions is similar the chart flow in Figure 3. then a linear interpolation is performed. One should pay attention that the ROM-WAM file is written with this option.

the minutes and SC. the hour. The file is copied in the tomawac temporary file and opened with the logical unit NVEN. for starting the simulation on the 8th of November 2007. ABSCISSAE OF SPECTRUM PRINTOUT POINTS ORDINATES OF SPECTRUM PRINTOUT POINTS =636870. Coupling with the Nearshore model The wave spectrum and the water level are saved at a location off Walcott in order to provide with information for the boundary conditions of the Nearshore model. It also specifies the ascii type of the file. where YYYY is the year. As an example. =333861. HH. the KEY-WORD should be: DATE OF COMPUTATION BEGINNING = 20071108150358 d. the day.FORMATTED WINDS FILE This KEY-WORD specifies the PATH and the name of the wind output file. for starting the simulation on the 8th of November 2007 at 15:03:58. Work Package 2. MM.1 28.0m.1 Appendix 1 Deliverable 2. It requires an integer formatted as: YYYYMMDDHHMNSC. MN.2011 18 . the Steering file of Tomawac should contain these two additional keywords providing the location of the point where the wave spectrum should be estimated. the month.0m and Y = 333861.09. the seconds As an example. DD. the KEYWORD should be: FORMATTED WINDS FILE 'F:/METOFFICE/wind_ukmo. In this example the wave directional spectrum is computed at the location X = 636870.txt' = DATE OF COMPUTATION BEGINNING This KEY-WORD provides the date and the time of the beginning of the simulation. In order to do so.

0. produces a mesh of 16032 elements (Figure 4). For this application. NEARSHORE MODELLING 6. Bottom elevations are referenced to the Ordnance Datum. This computational mesh is used both for propagating wind waves towards the toe of the seawall at Walcott. The bathymetry is interpolated a posteriori after the generation of the grid.2011 19 . The constraint on point density is about the 80m offshore.09. assuming that the bathymetry is uniform in the longshore direction. The profile off Walcott called N3C8 in the Environment Agency nomenclature is used as input for the bathymetry for the nearshore model. The black dotted line represents the location of the N3C8 profile. The grey line are the triangular elements of the Coastal computational domain.1 Appendix 1 Deliverable 2. only the details from the seawall are imported within MATISSE.1 Mesh generation The initial bathymetry is extracted from the strategic beach and bathymetry surveys undertaken twice a year by the Environment Agency.1 28. Figure 4: Localisation map (a) and (b) computational mesh of the Nearshore model. using this set of information.6. located off Walcott. MATISSE. Work Package 2.1m over the seawall.

Inner point selection For the treatment of the lateral boundary conditions. The direction of waves is assumed perpendicular to the coastline. Steering file generation For each Coastal modelling output. To set up each run. For each simulation. the wind induced processes on wave propagation are disregarded. Coupling implementation The Nearshore model is run for each boundary condition until a steady state is reached. 6. both the nil wave incident offshore condition and the lateral boundaries are imposed in the FORTRAN file.1 Appendix 1 Deliverable 2. For the Nearshore domain where water depths are relatively shallow.09. Offshore wave input The offshore wave input is provided by the Coastal modelling. Along the offshore boundary points. Integrated wave parameters from the Coastal model are extracted every hour and imposed to the offshore boundary nodes of the Nearshore model. Boundary conditions imposition For Tomawac simulations on the Nearshore domain.2011 20 . the Nearshore model needs to locate for each lateral boundary nodes. a pre-processing is requested. the outputs from the wave spectrum estimated from the Coastal modelling is imposed. INITIAL STILL WATER LEVEL. the inner point from which the directional Work Package 2. The hourly outputs are prescribed to Tomawac by assigning the value of the still water level in the Steering file. a special treatment is operated in order to conserve the independency to the longshore direction. For the lateral boundaries. (ii) select the inner point for the lateral boundaries treatment. The imposed values are prescribed in the Tomawac Steering file.2 Tomawac simulations a. a steering file is generated automatically by a PERL script in order to assign the values of the KEY-WORDS: BOUNDARY SIGNIFICANT WAVE HEIGHT.1 28. a solid boundary is free condition is assumed. b. This step is used to (i) generate the Steering files. the wave spectrum from the nearest inner point is imposed. two inputs are requested the offshore wave input (either wave integrated parameters or wave directional spectrum) and the water depth. BOUNDARY PEAK FREQUENCY. Water depths input Water depths are provided by ROM-POLCOMS. For each of these boundary points.Along the seawall crest.

1 where Tp represents the peak wave period. So then the wave direction is equal to the angle of the normal vector of the boundary with respect to the North.1 Appendix 1 Deliverable 2. These parameters are estimated by firstly extracted the significant wave height.3 Coupling with the Eurotop Neural Network application The Neural Network application requires as hydraulic inputs. The wave set-up is then added to simulated water level at the toe of the structure to estimate the water level which is imposed to Eurotop. 2005): Tm 0.2011 21 . the wave period.. The wave height at the breaker is then used to estimate the wave set-up by using the formulation proposed by (Dean and Dalrymple. the BOUNDARY CONDITION FILE is modified to specify an imposed condition for the lateral boundary nodes. The FORTRAN file of that run contains the subroutine CORFON. Tm0. the significant wave height at the toe of the structure. −1 = Tp 1.spectrum will be used as a boundary condition.1 28. Work Package 2. These apexes will be used afterwards to compute the boundary conditions to be imposed at the lateral boundary node. The wave direction is assumed perpendicular to the offshore boundary. When the simulation is performed this subroutine identifies each boundary node having an imposed boundary condition. For each of these nodes. the peak wave period and the water level along each point of profile N3C8. This extraction includes an interpolation involving the barycentric coordinates of these points according to the triangular to which they belong.-1. The translated point is located inside a triangular element whose apexes are then saved. 2002).8. This subroutine is modified to compute the wave direction at the offshore boundary nodes and to impose the wave conditions along the lateral boundaries. The breaking point is then estimated by considering the point where the ratio between significant wave height and the local water depth is higher than 0. the wave incidence and water level at the toe. 6. The selection of these points is performed by a preliminary Tomawac run.09. Only for this run. The remaining boundary nodes are set to a closed boundary. The wave period for Eurotop is estimated using the formula (Coeveld et al. FORTRAN file The FORTRAN file includes the Tomawac subroutine LIMWAC. the subroutine translates this boundary node inside the computational domain according to the normal vector of the boundary at that node.

1 Appendix 1 Deliverable 2.1 28. are provided by the Environment Agency. Along the coastline. and the seawall is located as the point where the bottom elevation is higher than 6mODN. (i) the bottom elevation containing vegetations and buildings.25m resolution. the frontier is modified to take into account the seawall crest Work Package 2. Figure 5: Computation domain for the flooding model showing the bed elevation of surrounding Walcott community. Flooding modelling 7. a 1m resolution and 0. All the elevations are referenced to the Ordnance Datum.25m resolution. Three spatial resolutions are provided: a 2m resolution. The bottom elevation is measured using light detection and ranging (LIDAR) technique.1 Mesh generation Data. Each column is read from North to South. They consist of a set of three tables containing. The computational grid is set as a rectangle whose dimensions are 1000m by 2750m. The mask table provides with the location of building.2011 22 . used for the generating the mesh.09. on a regular grid. (ii) the filtered bottom elevation to remove vegetations and buildings and (iii) the mask of the filter. The seawall location is estimated by reading each column of the table containing the bottom elevation with a 0.7.

0 is here used for the simulation of the inundation of Walcott. both the water depth and the velocities are prescribing along the seawall.6mODN Buildings inside the domain are considered as island. 7. This version contains a treatment for wetting and drying that checks that the water depth remains constantly positive. one for the time in seconds and one for the linear overtopping discharge in m3/l/m.09.1 28. Boundary condition imposition For the inundation modelling. a. This file contains two columns. Work Package 2.2011 23 . assuming the flow to be critical.location (Figure 5).2 Telemac-2d simulation The version V6.1 Appendix 1 Deliverable 2. Two different temporal series of input are considered: either a wave by wave overtopping discharge rates or a constant overtopping discharge rate corresponding to the mean temporal series. The elevation of any point located along the seawall is set to 6. These conditions are derived from the linear overtopping discharge rate provided by the Shallow Water And Boussinesq (SWAB) model. The PATH and name of this file are specified into Telemac2d Steering file by assigning the KEY-WORD: FORMATTED DATA FILE 1. This temporal series are saved into an ASCII file which are open with the unit NFO1 and read by the routine BORD.

112: C08003 Pullen. J.2011 24 .Assessment Manual. N. and Medina.. J. B. and Dalrymple. van Gent. (1996) Development of a third generation shallow-water wave model with unstructured spatial meshing. and Pozueta. R.. and Becq. F. and Wilson.1 28. A.09. R. P.. E. Bruce. Schüttrumpf. Cambridge University Press Hervouet. WL | Delf Hydraulics Dean. A. (2007) Hydrodynamics of free surface flows modelling with the finite element method. H. A. B. F.-M. R. M. Allsop. M. W. (2005) Neural Network: Manual NN_Overtopping 2. Pozueta. Orlando Coeveld.. 25th lnternational Conference on Coastal Engineering. Kortenhaus.. van Gent. Marcos. (2002) Coastal Processes with Engineering Applications. (2007) Tide-surge interaction and its role in the distribution of surge residuals in the North Sea. T. W. Res.8. van den Boogaard. Wiley Horsburgh. A.. J. H. M. T. G. R..1 Appendix 1 Deliverable 2. J. M.. R. H. References Benoit. J. and van der Meer. C. F. Geophys. K. (2007) Neural network modelling of wave overtopping at coastal structures. Coastal Engineering 54: 586-593 Work Package 2. (2007) EurOtop Wave Overtopping of Sea Defences and Related Structures .

Sign up to vote on this title
UsefulNot useful