@ Breakwat Readme

BREAKWAT 3.1.1 June 2005 June, 2005 Readme

WL | Delft Hydraulics 1

1 Readme

Please read this file carefully, before installing BREAKWAT 3. To be able to view, use and print the digital manual, Adobe or Acrobat Reader (Version 5 and higher) has to be installed on the PC on which BREAKWAT is going to be installed. If this is not the case, this software can be downloaded for free from URL: • http://www.adobe.com/products/acrobat/readermain.html.

1.1 Installation procedure

After inserting the BREAKWAT 3 installation disk in the CD-ROM the setup Install_Shield.EXE starts. The dialog shown in

Figure 1.1 will pop up.

Figure 1.1

The program Install-Shield gives the user the ability to do the following: • View readme file (View Readme File). • Install

− Breakwat 3 (Install the software package BREAKWAT 3 on your PC, install the License and the software for the FlexLM Hardware key (Dongle); if BREAKWAT 3 is licensed with a hardware key provided by WL | Delft Hydraulics.)

• Browse the CD (Browse the CD) • Exit the Install-Shield program (Exit)



To start one of these options move the cursor over an item, which will turn red, and click on it. After clicking the item "-Breakwat 3" the BREAKWAT 3 setup will start. One of the dialogs the user will come across is shown in Figure 1.2. In this dialog the user must select the items to be installed. By default three items are selected, see Figure 1.2. These items are all needed if the installation is done for the first time.

Figure 1.2

The meaning of these items is: • Install BREAKWAT 3.1: By selecting this option the user installs the BREAKWAT 3 on

his/her PC. Without a license the program will not work. To install a license see item "Install License". (To run BREAKWAT 3 correctly the regional settings must be set to English UK/US, i.e. numbers and fractions should be separated by a dot (.))

• Install License: By selecting this option the user is able to set the license file correctly. If the license file is attached to a Dongle or Hardware Key, the user must also select "Install Software for recognizing FlexLM Hardware Key (Black Dongle)" to install the hardware key recognition software.

• Install Software for recognizing FlexLM Hardware Key (Black Dongle): By selecting this option the user installs the software for dongle/hardware key recognition. The Dongle/Hardware Key will be provided by WL| Delft Hydraulics if the client asks for a license to be attached to a Hardware Key.

• Install License Manager (Floating/Server License): By selecting this option the user can install the License Manager at a user defined location. This option must be selected if



the user received a floating/server license and there is no FLexLM license manager running.

If after installation BREAKWAT 3 does not work, please select the item "FAQ": • Frequently Asked Questions (FAQ) The list of modifications can be found by clicking the item: • Modifications The list of new features can be found by clicking the item: • New Features If there are any problems please contact. Ed Ehrlich phone +31 15 2858841 email [email protected]



2 BREAKWAT 3

BREAKWAT 3 will be useful for everyone who, even if occasional, is involved in the conceptual design of breakwater structures. This includes for example teaching (universities), design (consultants), testing (research institutes) or construction (contractors) environments. BREAKWAT 3 is an ideal tool for those people who wish to apply the results of the latest research and development and wish to do this quickly and efficiently. For more than 10 years earlier versions of BREAKWAT have been widely used as a tool to guide and assist in the design of many types of breakwaters. In these 10 years new developments in the technical aspects of breakwater design as well as developments in the user-friendliness of computer programs in general have taken place. The development of BREAKWAT 3 incorporates many of those new improvements. With BREAKWAT 3 a conceptual design can be made for statically stable structures, like rubble mound breakwaters with an armour layer of rock or concrete units, as well as for dynamically stable structures, like berm breakwaters, reef type structures and near-bed structures. It is also possible to make calculations for vertical (caisson) structures. BREAKWAT 3 uses modern design formulae to perform calculations to the hydraulic response: • wave height distribution, • wave run-up, • wave overtopping, and • wave transmission or to the structural response: • rock stability of armour layer and toe berm • stability of concrete armour units (Cube, Tetrapod, Dolosse, Accropode, Core-LocTM) of several types of structures: • statically stable structures (rubble mound breakwaters), • dynamically stable structures (berm breakwaters, reef-type structures, near-bed

structures), and • vertical (caisson) breakwaters. BREAKWAT 3 is a windows-based product and runs Microsoft Windows 95-98-ME-2000-NT-XP. It is programmed in the Visual Basic 6.0 program language. The main general features of BREAKWAT 3 are: • flexible set-up, • easy to implement new modules and formulae, • report-ready graphical presentation of results,



• ability to work with input and output files, • possibility to calculate and compare more than one scenario at one time (sensitivity

analysis), • ability to copy data to and from clipboard, to be used for instance in Microsoft Excel , • ‘hard’ and ‘soft’ limits to validity of formulae (‘hard’: no answer outside range of

validity, ‘soft’: answer with warning if outside range of validity), and • extensive digital help function.

2.1 Demo animations

To get an impression of the general program layout and the structure of BREAKWAT 3, watch the following animations via QuickTime Movie or Aawin (Autodesk Animation Player): • in CreateCase.flc a calculation is carried out to determine the stability of the top-layer of

rock armour of a rubble mound breakwater • in CreateGraph.flc a graph is created with the generated output of the stability

calculation • in CompareCasesInGraph.flc the output of two cases is compared in a graph • in CompareCasesInSpreadsheet.flc the output of two cases is compared in a spreadsheet • in VerticalCaissonBreakwater.flc the possibility of copying data from other software to a

specific case in BREAKWAT 3 is shown in a computation with a vertical (caisson) breakwater.

For more information see PDF brochure BREAKWAT 3 (To view this PDF brochure the user must have a PDF reader installed on his/her system)



3 License

3.1 License Information

The license file contains the features which are enabled in the software package. It also contains the expiration date, number of users (SERVER License only) and some other information. Delft-Chess software uses the DS_Flex installation setup to install/update licenses. This section gives a short description of the choices the user has to make during the installation of DS_Flex. For more detailed information see the manual “LicensingEndUserGuide.pdf” which can be found in the installation directory of DS_Flex. If no DS_Flex is installed on your machine the user will be asked to select a type of license (Figure 3.1). Once this type has been selected, all other licenses which uses DS_Flex must be of the same type. E.g. if the user selects the option “Stand Alone” in Figure 3.1 all other Delft-Chess packages must also use Stand Alone. The only way to change this, uninstall DS_Flex and reinstall DS_Flex.

Figure 3.1



The user can select three license types. • Stand-Alone License File (Ethernet card/dongle) Selecting Stand-Alone, the installation of DS_Flex is done an arbitrary PC with a Windows operating system on it. Stand-Alone license equals a Node Locked license and it is valid for one PC, only. There are two different stand-alone license files:

• License file attached to an Ethernet card. This license is locked to one PC. • License file attached to a hardware key. This license is valid for the PC on which the

software is installed and the hardware key is connected to. The license file is sent to the user by floppy disk or email. During the installation the user selects the license file (Figure 3.7) on floppy disk or hard disk. The setup will copy the license file to the installation directory of DS_FLex (default C:\Program Files\DS_Flex ). • Server License File Selecting Server license, the installation of DS_Flex is done on a server. After the installation DS_Flex is able to start the License Service on the Server (Figure 3.3). To check/alter/restart/stop the License Service see section Server. If there is already a FlexLM license file on the server, the user can add the contents of the license file received to the one on the server. How to do these things correctly is described in section Server. • Client License File Selecting Client license, the installation of DS_Flex is done on a PC, connected to a Server. By selecting this option, the user must locate (Figure 3.7) the license file on the server. After selecting a license type the user will/can come across the following windows.

Figure 3.2 WINDOW: Upgrade/Uninstall/Install



Figure 3.2 shows the window which gives the user the ability to upgrade or repair a license file. This option can be used if a user receives a new license file of a certain software package. The option “Uninstall previous version before continuing the installation” must be selected if the user wants a reinstallation of the previously installed DS_Flex. The last option “Install a new license file” must be used if the user installs a new Delft-Chess software package. The option “Upgrade /Repair. And install license file is the default. To find out which license type has been selected previously, go to Start|Programs|Delft Software Flexlm ([License File Type]).

Figure 3.3 WINDOW: Install FLEXlm as an OS service

Figure 3.3 shows the window which gives the user the ability to start a License Service on a Server. This window will be shown if option “Server” in Figure 3.1 is selected.



Figure 3.4 WINDOW: Backup

Figure 3.4 shows the window which gives the user the ability to let DS_Flex backup all the files replaced during installation. A backup directory is created as a subdirectory of DS_Flex installation directory.


WL | Delft Hydraulics 1 0

Figure 3.5 WINDOW: Destination folder

Figure 3.5 shows the window which gives the user the ability to select the destination folder of DS_Flex program. Default the installation is done in directory “C:\Program Files\DS_Flex”.

Figure 3.6 WINDOW: Install license file

Figure 3.6 shows the window which gives the user the ability to install the license file or to postpone this selection.



Figure 3.7 WINDOW: Specify licens file location

Figure 3.7 shows the window which gives the user the ability to select the license file. Depending on the options selected in Figure 3.1, the license file will be copied to the installation directory of DS_Flex or will be left at the selected location.



Figure 3.8 WINDOW: Program manager group

Figure 3.8 shows the window which gives the user the ability change the default of the DS_Flex used by the Program Manager Group Name. The default value is “DelftSoftware FlexLM”.

3.2 Client Information

The client information is stored in the license file sent to the user by email or floppy. This information will be shown in the startup screen and/or the about screen of the application.



4 Server

In this section the procedure is described, how to make use of a Server License file. If a Server License (Floating License) is used there are two possibilities: 1. No FlexLM License Manager is running yet. 2. FlexLM License Manager is already running.

4.1 No FlexLM License Manager is running yet

The FlexLM License Manager has to be activated. This is done in five steps: First Step: Create a directory or directories on the SERVER where to put/install the programs: • lmgrd.exe • lmtools.exe • dwldelft.exe (Use for BREAKWAT 3.01.0000 or lower) • dhsdelft.exe (Use for BREAKWAT 3.01.0001 or higher) • lmdown.exe and the server license file. After the license file has been copied to the correct directory, the license file must be adjusted. A general layout of a typical license file is: If BREAKWAT 3.01.0000 or lower is used: # Begin PACKAGE NAME VERSIONNUMBER License SERVER sunray 80bbf5d7 TCP:8345 DAEMON dwldelft \\eland\app\flexlm\v7.2-wl\wl\dwldelft.exe INCREMENT FEATURE1 dwldelft VERSIONNUMBER DATE NBRUSERS DD21BF2C47F7 \VENDOR_STRING="USERNAME='WL User';FIRMNAME='WL | Delft \ Hydraulics';PLACE='Rotterdamseweg 185,2629HD Delft';" \ OVERDRAFT=0 INCREMENT FEATURE2 dwldelft VERSIONNUMBER DATE NBRUSERS A1955E2C4DF4 \ VENDOR_STRING="WL | Delft Hydraulics" etc. #End PACKAGE NAME License



If BREAKWAT 3.01.0001 or higher is used # Begin PACKAGE NAME VERSIONNUMBER License SERVER sunray 80bbf5d7 TCP:8345 DAEMON dhsdelft \\eland\app\flexlm\v7.2-wl\wl\dhsdelft.exe INCREMENT FEATURE1 dhsdelft VERSIONNUMBER DATE NBRUSERS \VENDOR_STRING="USERNAME='WL User';FIRMNAME='WL | Delft \ Hydraulics';PLACE='Rotterdamseweg 185,2629HD Delft';" \ OVERDRAFT=0 SIGN= “DD21BF2C47F7 ……” INCREMENT FEATURE2 dhsdelft VERSIONNUMBER DATE NBRUSERS VENDOR_STRING="WL | Delft Hydraulics" SIGN= “A1955E2C4DF4 …….” etc. #End PACKAGE NAME License IMPORTANT FOR USER! The user must adjust the following items: • sunray, the user must change this name into the name of his/her server. • The value of TCP:8555, the user should consult the System Administrator. • \\eland\app\flexlm\v7.2-wl\wl\dwldelft.exe, the user must enter the correct path here,

which means the location of the program dwldelft.exe or dhsdelft.exe on his/her server. ---------------------------------------------------- The programs mentioned above can be found in the installation directory of DS_Flex . Second Step: Run LMTOOLS.EXE from the created directory. The window, according to Figure 4.1, will pop up.



Figure 4.1

The user can select one of two options in the window (Figure 4.1). The possible selections are: • Configuration using License File • Configuration using Services To run a Server License select the option "Configuration using Services". After selecting this option the window (Figure 4.1) will change to the window shown in Figure 4.2.

Figure 4.2

The window in Figure 4.1 differs from the window in Figure 4.2, because one extra tab ("Config Services") has been added, tab "Switch report log" has been removed and the name of one tab changed and the name of the tab "Stop/Reread" has changed to "Start/Stop/Reread". Third Step: The next step in starting up a Server License is to select the tab "Config Services". After selection of this tab the window, according to Figure 4.3, can be seen on screen. On this window (Figure 4.3) the user must enter the following options: • Path to the "lmgrd.exe" file. Use Browse to locate the file. • Path to the license file. Use Browse to locate the file. • Path to the debug log file. The user must enter a name here (e.g. logfile). • Select checkbox Use Services. After selection the checkbox "Start Server at PowerUp"

will be able to select. The user must also select this option. This option means that if the server restarts the License Manager will start up automatically.



• Press button "Save Service" to store the information.

Figure 4.3

An example of how the window looks after all the information has been entered, is shown in Figure 4.4.

Figure 4.4

Fourth Step:



The next step in starting up a Server License is to select the tab "Start/Stop/Reread". After selection of this tab the window, according to Figure 4.5, can be seen on screen.

Figure 4.5

In the list "Flexlm license Services installed on this computer" the user can find the service saved in step 3 (see Figure 4, field "Service Name"). In this step the user must select the correct service and press the button "Start Server". This action will start the License Manager. Fifth Step: To check if the License Manager is running the server license correctly, select tab "Server Status". After selection the window according to Figure 4.6 will be shown on screen.



Figure 4.6

The user must press the button "Perform Status Enquiry". If in the window below an error is shown, the user can inspect the debug log file defined in step 3 to see what the problem is. If no problems occur the user can select the menu option File|Exit to quit the application.

4.2 FlexLM Licence Manager is already running

The contents of the Server license file sent by WL | Delft Hydraulics has to be merged with the existing/active Server license file. To activate the new license file there are two different ways (it is strongly recommended to make a copy of the existing/active Server license file): • Deactivate the license manager. Copy the necessary (Server and Deamon/Vendor is not

necessary, if it is already in the existing/active license file) received license information into the Server license file and restart the License manager according the procedure mentioned in section No FlexLM License Manager is running yet.

• Make a copy of the existing/active license file. Copy the necessary (Server and Deamon/Vendor is not necessary, if it is already in the existing/active license file) license information into the existing license file. After updating the existing license file the FlexLM License Manager should be "notified". Officially a simple re-read of the license file should be sufficient. This can be done in the following way:

• Start "lmtools.exe". Go to the "Stop/Reread"-tab. • Select the server in the "Remote Server List" defined as

8555@"computer/hostname" • Click "Reread License File" • The following output should be written to the "diagnostic window":

Rereading LicenseFile



------------------------ -Reread Server License File Completed! ------------------------ -Finding License Server In case you doubt it working correctly, you can also re-boot after updating the license file. For back-up and safety, we strongly recommend to make a copy of the old Server License file, as well as the new Server License file.

4.3 Delft3D users

For those who use the Delft3D software of WL | Delft Hydraulics, the updating and activating procedure can also be found in the Delft3D Installation Manual.



5 Modifications

5.1 List with new versions

• Modifications VERSION 3.00.0023 VERSUS VERSION 3.00.0022 • Modifications VERSION 3.00.0024 VERSUS VERSION 3.00.0023 • Modifications VERSION 3.01 VERSUS VERSION 3.00.0024 • Modifications VERSION 3.01.001 VERSUS VERSION 3.01 Despite these modifications there are still some unsolved problems.

5.2 Modifications VERSION 3.00.0023 VERSUS 3.00.0022

The following bugs/imperfections have been solved: • The WL | Delft Hydraulics mail address has been added to the About-box. • If File|Save As|Case was used the contents was first written to the file followed by

renaming the file name to the new file name. This caused an inconsistency in the name displayed in the GUI and the name saved. This is solved now by first renaming the file to the file name entered in Dialog Box, then saving the Case to file.

• If File|Save As|Case was selected and the user wanted to overwrite an existing CASE with a new name, the CASE name did not change within the BREAKWAT 3.0 user interface. This is now solved.

• Selecting table for parameter Dn50, caused a division by zero error. This is solved now • The Information Box at the bottom of the property window is shown if an error occurs

during calculation and is not show if there are no errors. The message was not removed from the box, so if the button "I" in property window was pushed the error could still be seen. This could cause confusion. To avoid the confusion the contents of the information box is also cleared if there are no errors.

• Some Textual changes: • (P) Porosity factor has been changed To (P) Notional Permeability factor. • (Vol) Volume of overtopping volume per wave per m TO (Vol) Overtopping volume per

wave per m • For Reef type breakwaters the Stability parameter was defined as (Hs/Delta*Dn) this

changed to (Hs/Delta*Dn50) • For Berm Breakwater Rock Armour the name for wave angle "phi" has been changed to

"Beta", this according to the manual. • Default values have been adapted. At startup no errors occur during the default

calculation • Pictures in the main window are modified and improved. The pictures are also better

shown in the main window of BREAKWAT 3.0.



• An error occurred in the Profile case. If the depth (h) was adjusted and an error occurred the change of other parameters had no influence on the result. This was caused by the Fortran DLL "DFORRT.DLL" which was newer than the one the BREAKWAT DLL's were compiled with. Now the right DFORRT.DLL is installed in BREAKWAT 3.0 installation directory.

• Another problem occurred in Profile Case when updating the output profiles. If an error code was generated the output profiles were not always updated again correctly because, after the error was generated the loop was not.

• An extra check has been implemented to see if there are any error messages in the "Profile.Log" file. (This file is generated if the Profile Case is selected). It could happen that an error was generated in Profile.Log but there was no message in the BREAKWAT 3.0 graphical user interface. This problem is solved now. After creation and closing of Profile.Log the LOG file is read again and check for string "error". If this string occurs a message is displayed in BREAKWAT 3.0.

• The restriction rule 1.5< (At/(h'c)^2)<3.0 has been changed to 1.5< (At/(h'c)^2)<3.5. • The property window for Pressure Forces & Safety Factors (sometimes also other

property windows) caused a crash when create TABLE was selected for a parameter. The focus was removed from creating the table while it was not finished yet. This problem is solved now.

• The contents of the file changed if it was open. If a case was created by BREAKWAT 3.0 and saved the contents contained parameter names like [alpha], etc. After opening the case again the parameter names [alpha], etc were converted to Greek symbols. However, if the text editor does not support these symbols, different symbols were used. This problem is solved now.

• If a Graph was created for “1 Rubble Mound Structures 1.1 Conventional breakwater |2. Structural Response 2.1 Rock armour |Van der Meer Cumulative Storms” and saved, an error occurred when opening the same case again. The reason for this problem was the Zparameter was set to "NONE" which caused the program to select another routine to create the graph. Changing "NONE" to "" within BREAKWAT 3.0 solved the problem.

• The box containing CASE icons and PROJECT icons is now not visible if nothing has been created. After creation of a CASE or PROJECT the box becomes visible.

• If pause button was pushed, while an edit field in Property Editor was selected BREAKWAT 3.0 crashed. This is solved now.

• The Breaker Parameter is added as output parameter in Berm Breakwater|Transmission and Conventional Breakwater|Transmission

• The calculation of Hst in Berm Breakwater|Transmission was not done correctly. This has been adjusted.

• Now in both cases Berm Breakwater|Transmission and Conventional Breakwater|Transmission the conditions for wave steepness and breaker parameter are checked.

5.3 Modifications VERSION 3.00.0024 VERSUS 3.00.0023

The following bugs/imperfections have been solved: • The user is able to put only one value in the input table and generate output tables with

only one input value. This make it possible to put a single value in a graph.



• A warning (‘Depth limitation error’) appears when determining the profile development of a Berm Breakwater under wave attack when Hs/h is smaller than 0.6, while this warning should appear when Hs/h is larger than 0.6.

• The ratio H2%/H1/3 in the ‘wave height distribution’ is not equal to the ratio H(P)/H1/3, when P has a value of 2 %.

• The installation procedure could be confusing, because of the use of both a lic-file and a key-file. BREAKWAT 3.00.0024 does not use the key file any more. Instead all the information is put in the license file.

• If 2 cases are active at the same time with the same name, problems could arise, now case names are check and the user is informed if two cases/projects have the same names.

• By entering the value 0 for some parameters, BREAKWAT generated a run-time error. Especially the significant wave height Hs is sensitive for this error.

• When calculating overtopping volumes, the output parameter ‘percentage overtopping waves’ POV has to be multiplied by 100.

• The wave height factor αHs was not correctly implemented in the Hudson-formula. This is the case for conventional rubble mound breakwaters, as well as for breakwaters with a top-layer of concrete armour units. This is now corrected.

• When closing BREAKWAT 3.0, the user was not always informed correctly about if a file needed to be saved or not. This problem is solved now. Files are stored in an object array. Before quitting this array will be walk through sequentially to see if a file needs to be saved or not.

• A few textual improvements have been made to the GUI as well as the manual. • New icon has been made for BREAKWAT 3.0 • The undo-button has been removed from the property editor. • At startup time the Regional Settings of the system are checked. If the regional settings

are not correctly set for BREAKWAT 3.0 the program BREAKWAT 3.0 shows a warning.

5.4 Modifications VERSION 3.01 VERSUS 3.00.0024

The following bugs/imperfections have been solved: • For Overtopping (formula TAW-formula) the unit of the parameters Vmax (Max.

overtopping volume per wave, per m) and Vol (Overtopping volume per wave, per m) has been changed to m3/m1.

• For Concrete armour the unit of the parameter nv (Volumatric porosity) has been changed to (%).

• For Overtopping (formula TAW-formula) and Runup (formula TAW) the parameter γtot is set to 0.4 if the calculated value is lower than 0.4 else the calculated value is used.

• For Concrete armour the input parameters N (number of incident waves) and sm (wave steepness) are disabled for all formula, except for formula Cubes and Tretrapodes because they are not used by these formula.

• The uninstall button in the start menu of ‘Delft-Chess > Breakwat 3.1’ is not pointing to the correct location. Therefore, the unwise.exe and the uninstall procedure can only be activated from the installation directory. This has been improved.



• There is a conflict between the NN_Overtopping.dll and a previous version of the Dforrt.dll. This previous version has been replaced by a newer version of the Dforrt.dll (version 6.6.910.101).

• The Proba2.dll and the Profile_Shallow.dll have been re-compiled. The compilation has been carried out with Microsoft Visual C++, Compaq Visual Fortran Edition 6.6.b.

• All icons have been removed from the property editor, except the input, output and message icon.

• For Accropodes a message “Failure occurs if Nod > 0.5” is generated, if the criteria Hs/∆Dn≥2.5 is met. The value of Nod is set to 1000.

• The manual has been adjusted/updated/extended for: • wave overtopping • stability formulae rock armour • stability formula Cubes • stability formula Accropodes • toe berm stability of vertical(caisson) breakwater • wave transmission over berm breakwaters

• The manual has also been converted to a document in PDF format. The links throughout the document have been preserved. Users can quite easily make hardcopies of this document themselves. The design formulae are displayed more clearly in the document.

• The parameter sm-1,0 has been added as a new output parameter for the formula (TAW ,2002) for runup on conventional RMB’s.

• The roughness reduction factor γf has been changed for the formula (TAW ,2002) for runup on conventional RMB’s. The factor has been made linearly dependent of the surf similarity parameter ξ0 on the interval 1.8 < ξ0 < 10.

• The stability formula for Accropodes has been changed: the threshold for failure has been set to Hs/∆Dn = 2.5 is used in the formula, instead of 3.7 and 4.1. The confidence bands have been disabled.

• For several cases the default values have been changed. • The wave transmission over vertical (caisson) breakwaters is also calculated for wave

heights around Hs = 3m. • The calculations of wave overtopping of RMB’s does not lead to crashes of

BREAKWAT, also for unrealistically small values of Tm-1,0. • The hard/soft limits of the parameters γf and γf-C used in the formulae for determining

the rear side stability of RMB’s: • γf =0.47 (default); lower bound= 0.45; upper bound = 0.45 • γf-C =0.47(default); lower bound= 0.45; upper bound = 0.45

• Some texts of the error messages and warnings have been changed. • The possibility to work with Projects and/or Cases with the same name (by using the

“Save as” button), which ultimately results in a crash of BREAKWAT, has been disabled.

• The possibility to use the same name for different projects by using the “Rename” button has been disabled.

• The possibility to select a file with any arbitrarily extension as the editor has been disabled. It is only possible to select files with the extension exe.

• The Rayleigh distribution option in the Graph start window can only be selected if the active case has a formula with an “Exceedance probability” parameter.



• The initial profile for the calculation of the profile development of berm breakwaters has to be specified with positive x- and y-values. The default values for the initial profile have been changed slightly.

5.5 Modifications VERSION 3.01.0001 VERSUS 3.01

The following bugs/imperfections have been solved: • If a value outside the valid range has been entered for the parameter Dn50-core/Dn50 in

formula Rock Armour, Van Gent et. al., the error message is displayed correctly now. • Switching between Neural Network formula and Toe Berm Stability of RMB formula

leads to comment-free results. • The file “breakwat.ini” has been updated. Due to this update changing between Neural

Network and Toe Berm Stability of RMD formula will not result in an invalid range messages.

• File “for.10” is not generated anymore due to the possibility of opening a Neural Network case/project from an other directory then the installation directory.

• The valid range for cot(alphau), Neural Network, has been changed. Values between -1 and 10 are allowed now.

• A dimension parameter has been added to the header of the input x values for Profile Development.

• Loading Neural Network cases/projects from directories other than the installation directory is possible now. Before an error was generated because the file “nn_overtopping.ntd” could not be found.

• During the setup the error message “The procedure entry point for_read_dir_i8 could not be located in the dynamic library Dfortt.dll” could pop up. This problem is solved now, by installing the file Dforrt.dll in the “c:\windows\system32” directory instead of the installation directory.

• After pressing the menu option “Save” or “Save All” the files will be saved at the locations where the have been save before. In previous versions this was not the case. After pressing these menu options the files were always saved to the directory “_Workingfolder” located in the installation directory.

5.6 Unsolved problems

• Once a Project/Case that has been saved already, is saved again to another directory, the message appears that a Project/Case already exists with that name. Eventually the Project/Case is not saved in that directory. Another name should be given.

• The digital Technical Manual does not describe all cases sufficiently. • Selecting the parameter db in case ‘Vertical (caisson) breakwater – Pressures, forces and

safety factors’, causes BREAKWAT to shutdown automatically sometimes.



6 New Features

6.1 List with new versions

• New features VERSION 3.01 VERSUS VERSION 3.00.0024

6.2 New features VERSION 3.01 VERSUS 3.00.0024

The following features are added to this version: • The user is able to use (if licensed) a new design tool to predict the mean wave

overtopping discharge at coastal structures. The output of this tool includes the Neural Network prediction of the mean wave overtopping discharge and several other parameters indicating the uncertainty of the prediction. The tool was developed by WL | Delft Hydraulics co-sponsored by the Commission of the European Communities within the framework of the CLASH project (‘Crest Level Assessment of Coastal Structures by full scale monitoring, neural network prediction and Hazard analysis on permissible wave overtopping’). Details of the methodology followed for the development of the prediction tool are described in Pozueta et al. (2004) and Van Gent et al. (2004).

• The user is able to use (if licensed) a new design formula to determine the stability of the rock armour at the rear side of rubble mound breakwaters developed by Van Gent & Pozueta (2004). Based on physical model tests Van Gent & Pozueta (2004) proposed a formula to estimate the stone diameter for a given damage level for a wide range of conditions.

• The user is able to use (if licensed) a new set of design formulae to determine the stability of rock armour on the front slope of rubble mound breakwaters developed by Van Gent et al. (2003). Based on new physical model tests Van Gent et al. (2003) proposed to apply modifications to the formulae by Van der Meer (1988) to include situations in which wave breaking occurs on the foreshore. With these modifications the formulae are suitable for both shallow and deep water conditions at the toe of the structure.

• The user is able to use (if licensed) a new design formula to determine the stability of rock armour on the front slope of rubble mound breakwaters developed by Van Gent et al. (2003). Based on new physical model tests Van Gent et al. (2003) proposed a new, relatively simple design formula. There is an influence of the wave period, but this influence is considered small compared to the amount of scatter in the data due to other reasons. Therefore, the wave period is not used in this formula and there is no separation between ‘plunging’ and ‘surging’ conditions. The influence of the permeability of the structure is incorporated by using the ratio between the diameter of the core and the diameter of the main armour material. The formula is suitable for both shallow and deep water conditions at the toe of the structure.



7 Frequently Asked Questions

7.1 Known problems

This section contains solutions to known problems concerned with running or installing BREAKWAT 3. FlexLM License Manager -"No such feature exists": This error indicates that the user does not have a valid license file for the selected feature. New features implemented in BREAKWAT 3 can be viewed by all users, but are only accessible for those users with a valid license file. To be entitled to use new features, the user has to have a maintenance contract or has to purchase the new features. To purchase new features or to receive more information on maintenance contracts, please contact Ed Ehrlich. FlexLM error messages: These errors indicate that the user has a corrupt license file. Copy the original file, received from WL | Delft Hydraulics, to the subdirectory "_License\" in the installation directory. If the message remains, check the string "licensefile=" in the file "settings.ini". This variable should point to the correct license file. If this does not solve the problem, please contact Ed Ehrlich. Message -"No valid key file, cannot run Breakwat 3!": This error indicates that a corrupt key file or that no key file is present in the installation directory. Check if there is a "*.key" file in the installation directory. Save this file in the installation directory, using the setup or copy the key file manually. Rename the file to "Breakwat3.key" and try to startup BREAKWAT 3 again. If there is a "*.key" file present in the directory, overwrite this one with the one received from WL | Delft Hydraulics (manually) and then try running BREAKWAT 3 again. If this does not solve the problem, please contact Ed Ehrlich. Message -"Error in parsing vendor information from license file, closing application": This error indicates that the VENDOR information in the license file is not correct. To solve this, please contact Ed Ehrlich. Crash after selecting specific case: Structure Type: Rubble mound 1.1 Conventional breakwat Response factor: Structural response 1.1.2.1 Rock armour Formula: Probability of damage to armour layer. If after selecting this configuration BREAKWAT 3 crashes, please check the regional settings. It should be set to English UK/US, i.e. numbers and fractions should be separated by a dot (.). If the crash still occurs, please contact Ed Ehrlich. The message "BAD TABLE":



This message occurs if one or more cells in an output table are empty. This does not mean that the calculation is not correct, but that certain values are not within the valid range of that parameter. BREAKWAT 3 crashes when creating a TABLE": This happens if the version of the TeeChart.ocx (located in C:\Windows\System32) is different than the one BREAKWAT uses.

7.2 Report errors/suggestions

If any other errors occur, please let us know by sending the information to Ed Ehrlich. In this way the software package can be improved. Other suggestions with respect to improvements or user-friendliness of BREAKWAT 3 (or its setup) are off course very welcome. Please send the complete version number of BREAKWAT 3 with the error/suggestion-report.

7.3 Getting complete version number

The installation version is BREAKWAT 3. To see the full version number, go to installation directory, select "Breakwat.exe" and press ALT+ENTER. The property window is activated. Under the "Version"-tab the complete version number can be found.

Date post:	10-Apr-2015
Category:	Documents
Upload:	api-3709579
View:	455 times
Download:	3 times

@ Breakwat Readme

Documents