VG 2 VG 4
ProToel VG 6
VG 3
VAkkaert G1
GZ
VG 5
S2
VG SWA
A1
S4
VG 7
S3
S10 S8 S6 S5
S9
S7 SZ
S1
Version v2.0
Z
ZW
Oostendebank n MBN Zeebrugge
Probabilistic accessibility calculation for Port of Zeebrugge
14_078_1 FHR reports
ProToel v2.0 User manual
www.flandershydraulicsresearch.be
ProToel v2.0 User manual
Verwilligen, J.; Defourny, D.; Vos, S.; Peeters, P.; Mostaert, F.
Cover figure © The Government of Flanders, Department of Mobility and Public Works, Flanders Hydraulics Research Legal notice Flanders Hydraulics Research is of the opinion that the information and positions in this report are substantiated by the available data and knowledge at the time of writing. The positions taken in this report are those of Flanders Hydraulics Research and do not reflect necessarily the opinion of the Government of Flanders or any of its institutions. Flanders Hydraulics Research nor any person or company acting on behalf of Flanders Hydraulics Research is responsible for any loss or damage arising from the use of the information in this report. Copyright and citation © The Government of Flanders, Department of Mobility and Public Works, Flanders Hydraulics Research 2020 D/2020/3241/187 This publication should be cited as follows: Verwilligen, J.; Defourny, D.; Vos, S.; Peeters, P.; Mostaert, F. (2020). ProToel v2.0: User manual. Version 2.0. FHR Reports, 14_078_1. Flanders Hydraulics Research & ATOS: Antwerp Reproduction of and reference to this publication is authorised provided the source is acknowledged correctly. Document identification Customer: Keywords (3-5): Knowledge domains: Text (p.): Confidential:
Flanders Hydraulics Research Ref.: WL2020R14_078_1 ProToel, Probabilistic, Tidal Window, User Manual Harbours and Waterways > Safety > Risk analysis > Simulations Harbours and Waterways > Ship motion > Squat > Numerical calculation Harbours and Waterways > Ship motion > Seakeeping > Numerical calculation 40 Appendices (p.): 24 ܈No ܈Available online
Author(s):
Verwilligen, J. (FHR); Defourny, D. (ATOS)
Control Name Reviser(s):
Project leader:
Vos, S.
Verwilligen, J.
Signature Getekend door: Stijn Vos (Signature) Getekend op: 2020-10-22 11:27:01 +00:00 Reden: Ik keur dit document goed
Getekend door: Jeroen Verwilligen Getekend op: 2020-10-19 12:25:02 +00:00 Reden: Ik keur dit document goed
Approval Head of Division:
F-WL-PP10-2 Version 7 Valid as from 3/01/2017
Mostaert, F.
Getekend door: Frank Mostaert (Signature) Getekend op: 2020-10-19 10:59:18 +00:00 Reden: Ik keur dit document goed
ProToel v2.0 - User manual
Abstract In March 2017 Flanders Hydraulics Research released version 2.0 of their probabilistic accessibility tool ProToel, dedicated to the calculation of tidal windows to the port of Zeebrugge. The major new developments in ProToel v2.0 concern: - separation of client module and solver module allowing to perform the calculations both on a local machine (stand alonestandalone mode) or on a remote server (server mode); - implementation of an sql-database; - synchronization functionality with remote server; - licensing mechanism based on different roles (user, power user, administrator); - optimized web service processing; - fall back functionality for environmental data; - independent reduction point (rdp) definition for each datatype; - independent conditions for squat and RAO calculation; - optimized performance; - new GUI-platform.
Final version
WL2020R14_078_1
III
F-WL-PP10-2 Version 7 Valid as from 3/01/2017
ProToel v2.0 - User manual
Contents Abstract ............................................................................................................................................................ III Contents ............................................................................................................................................................ V List of tables..................................................................................................................................................... VII List of figures .................................................................................................................................................. VIII 1
2
Introduction ............................................................................................................................................... 1 1.1
ProToel............................................................................................................................................... 1
1.2
ProToel v2.0 ....................................................................................................................................... 2
1.3
Overview ............................................................................................................................................ 2
ProToel v2 functionalities .......................................................................................................................... 3 2.1
Database ............................................................................................................................................ 3
2.2
Waypoints .......................................................................................................................................... 6
2.2.1
Reduction points........................................................................................................................ 8
2.2.2
Fall-back ..................................................................................................................................... 8
2.2.3
Web services .............................................................................................................................. 9
2.3
3
2.3.1
Local criteria ............................................................................................................................ 10
2.3.2
Global criterion (maxBTP)........................................................................................................ 11
2.3.3
Standard definition .................................................................................................................. 11
2.4
Trajectories ...................................................................................................................................... 12
2.5
Solver ............................................................................................................................................... 12
Installation and Getting Started .............................................................................................................. 13 3.1
MS Windows .................................................................................................................................... 13
3.1.1
Installation ............................................................................................................................... 14
3.1.2
Initialisation local DB ............................................................................................................... 14
3.1.3
Starting GUI ............................................................................................................................. 14
3.2 4
Criteria ............................................................................................................................................. 10
Linux................................................................................................................................................. 14
Graphical User Interface .......................................................................................................................... 15 4.1
Running in GUI Mode ...................................................................................................................... 15
4.2
Menu bar ......................................................................................................................................... 16
4.2.1
File Menu ................................................................................................................................. 16
4.2.2
Settings Menu .......................................................................................................................... 17
4.2.3
Environment Menu .................................................................................................................. 19
Final version
WL2020R14_078_1
V
ProToel v2.0 - User manual
4.2.4
Ship Menu ................................................................................................................................ 21
4.2.5
Visualization Menu .................................................................................................................. 22
4.2.6
Help Menu ............................................................................................................................... 22
4.3
Trajectory Visualization Panel ......................................................................................................... 23
4.4
Ship Data Panel ................................................................................................................................ 23
4.5
Trajectory Data Panel ...................................................................................................................... 24
4.6
Voyage Data Panel ........................................................................................................................... 25
5
Results ..................................................................................................................................................... 26 5.1
Results form ..................................................................................................................................... 27
5.2
Summary pdf file ............................................................................................................................. 29
6
Batch Mode ............................................................................................................................................. 31
7
Adding data to Database ......................................................................................................................... 33
8
Pop-up messages and Problem Handling ................................................................................................ 36
9
Computing requirements and performance ........................................................................................... 39
10
References ........................................................................................................................................... 40
Appendix 1: Database structure ...................................................................................................................... A1 Appendix 2: Bottom Touch Probability ........................................................................................................... A9 1.
Vertical ship motions ........................................................................................................................... A9 1.1
2.
1.1.1
Overview .................................................................................................................................. A9
1.1.2
Squat ...................................................................................................................................... A10
1.1.3
Vertical Ship Response to Waves .......................................................................................... A12
Probabilistic Considerations .............................................................................................................. A15 2.1
3.
Ship database .............................................................................................................................. A9
Calculation scheme for probability of bottom touch (BTP)....................................................... A15
References ......................................................................................................................................... A19
Appendix 3: Log Messages ............................................................................................................................ A20
VI
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
List of tables Table 1 – General rules for changing local database schemas based on role ................................................... 4 Table 2 – Ship database Container vessels ........................................................................................................ 4 Table 3 – Ship database Bulk carriers ................................................................................................................ 5 Table 4 – Ship database LNG carriers ................................................................................................................ 5 Table 5 – Rdp-strategies defined in standard installation ProToel v2............................................................... 9 Table 6 – Criteria defined for a standard installation of ProToel v2 ............................................................... 11 Table 7 – Batch mode key words..................................................................................................................... 31 Table 8 – Database access ............................................................................................................................... 33 Table 9 – XSLX-templates for adding env data to database ............................................................................ 34 Table 10 – XSLX-templates for adding ship data to database ......................................................................... 34 Table 11 – XSLX-templates for adding frontend data to database ................................................................. 34 Table 12 – Pop-up messages and problem handling ....................................................................................... 36 Table 13 – Performance figures ...................................................................................................................... 39 Table 14 – Ship models: main dimensions, [14]. ........................................................................................... A10
Final version
WL2020R14_078_1
VII
ProToel v2.0 - User manual
List of figures Figure 1 – Visualisation ProToel-waypoints in the coastal routes to the port of Zeebrugge ............................ 7 Figure 2 – Visualisation ProToel-waypoints in the port of Zeebrugge .............................................................. 7 Figure 3 – Reduction points for datatype tide defined in ProToel v2.0 ............................................................ 8 Figure 4 – Reduction points for datatypes current and waves defined in ProToel v2.0 ................................... 8 Figure 5 – ProToel GUI ..................................................................................................................................... 15 Figure 6 – Menu bar ........................................................................................................................................ 16 Figure 7 – File menu ........................................................................................................................................ 16 Figure 8 – Load results ..................................................................................................................................... 17 Figure 9 – Settings menu ................................................................................................................................. 17 Figure 10 – Database synchronization recommendation period .................................................................... 18 Figure 11 – Web service refresh time ............................................................................................................. 18 Figure 12 – Database History........................................................................................................................... 19 Figure 13 – Environment menu ....................................................................................................................... 19 Figure 14 – Load rdp strategy .......................................................................................................................... 20 Figure 15 – Edit rdp strategy ........................................................................................................................... 20 Figure 16 – Ship menu ..................................................................................................................................... 21 Figure 17 – Visualization menu ....................................................................................................................... 22 Figure 18 – Help menu .................................................................................................................................... 22 Figure 19 – About ProToel ............................................................................................................................... 22 Figure 20 – Trajectory Visualization panel ...................................................................................................... 23 Figure 21 – Ship data panel ............................................................................................................................. 23 Figure 22 – Voyage data panel (left) and Trajectory data panel (right) .......................................................... 24 Figure 23 – Set all speeds ................................................................................................................................ 24 Figure 24 – Set speed per criteria .................................................................................................................... 24 Figure 25 – Add waypoint ................................................................................................................................ 25 Figure 26 – Results with meta data and tabs with tidal window, tide, current and wave height .................. 27 Figure 27 – Results, tide .................................................................................................................................. 28 Figure 28 – Results, current ............................................................................................................................. 28 Figure 29 – Results, wave height ..................................................................................................................... 29 Figure 30 – Blockage definition for squat calculation ................................................................................... A11 Figure 31 – Ship model D: maximum squat [12] ........................................................................................... A12 Figure 32 – Squat: comparison between ship models [12] ........................................................................... A12 Figure 33 – Panamax container vessel F, condition FA. Heave and pitch motions in head waves ............... A14 Figure 34 – Illustration of critical point positions corresponding to the positions on the hull that are most likely to experience bottom touch, [14]. ....................................................................................................... A18 Figure 35 – Arrival of a 15 m draft container vessel at Zeebrugge ............................................................... A18
VIII
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
1 Introduction This document is an updated version of report [1] and is a user manual for ProToel version 2.0 released in Autumn 2016. ProToel is owned by the Flemish Government and is a common development of Flanders Hydraulics Research and the Maritime Technology Division of Ghent University.
1.1 ProToel ProToel is a decision support tool that can be used in probabilistic admission policy for deep-drafted ships arriving at and departing from a port. Initially ProToel was tailored to the harbour of Zeebrugge. However, the tool is not limited to the port of Zeebrugge and was successfully extended to the ports of Vlissingen (Sloehaven), Terneuzen and Antwerp in several research projects ([2, 3, 4, 5]). The development and application of ProToel was published in a number of international publications regarding probabilistic accessibility [6, 7, 8, 9]. ProToel results into an advisable tidal window, based on a number of criteria that can be both deterministic and probabilistic. In a deterministic mode, the gross under keel clearance, relative to both the nautical bottom and the top of fluid mud layers, and the magnitude of current components are taken into account. In case probabilistic considerations are accounted for, a positive advise will only be given if the probability of bottom touch during the voyage due to squat and response to waves do not exceed a selected maximum value [7] and if the manoeuvring margin does not fall below a selected minimum value. The program predicts the probability of bottom touch and the manoeuvring margin for ships of a specified type and loading condition based on current, predicted sea states and environmental data. The following input data are taken into consideration: ship characteristics, waterway characteristics, trajectory, nautical bottom depth, top mud depth, speed over ground and through the water, tidal elevation, directional wave spectra, current, wind and departure time. ProToel can either be used for supporting short term decisions for a particular ship, or for long term estimations for the maximum allowable draft. Based on a specified trajectory and departure time, ProToel calculates the under keel clearances, the manoeuvring margins and bottom touch probabilities for a specific ship following the trajectory with a chosen speed along the trajectory. The trajectory is defined by a chain of waypoints. In each waypoint, the under keel clearances (and manoeuvring margin) are calculated based on bottom depth, up-to-date current and tide data and the speed dependent squat. The bottom touch probability is calculated from the directional wave spectrum for that time, location and the motion characteristics of the ship. The calculation results are stored and can be displayed after computation.
Final version
WL2020R14_078_1
1
ProToel v2.0 - User manual
1.2 ProToel v2.0 The major new developments in ProToel v2 concern: • separation of client module and solver module allowing to perform the calculations both on a local machine (standalone mode) or on a remote server (server mode); • implementation of an sql-database; • synchronization functionality with remote server; • licensing mechanism based on different roles (user, power user, administrator); • optimized web service processing; • fall back functionality for environmental data; • independent reduction point (rdp) definition for each datatype; • independent conditions for squat and RAO calculation; • optimized performance; • new GUI-platform.
1.3 Overview This manual describes the (new) functionalities of ProToel and the setup for Zeebrugge in Section 2. Section 3 contains an installation manual in which all steps for getting started with ProToel v2 are described. In Section 4 the graphical user interface is presented in detail, while Section 5 explains different ways of visualizing the calculation results. In case of multiple calculations, the calculations can be initiated in batch-mode (Section 6). The user has (depending on his role) the opportunity to add data to the ProToel-database by means of excel-files. Section 7 elaborates on this functionality. A description of the various error messages is given in Section 8. Finally, Section 9 describes the computing requirements and gives indications of the computing time required by ProToel.
2
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
2 ProToel v2 functionalities Chapter 2 contains a general overview of the functionalities in ProToel v2. Also the standard installation and configuration for application to the port of Zeebrugge is presented.
2.1 Database Since v2.0 ProToel is using a sql-database (PostgreSQL) to store the required data. This database consists of four schemas (see also Appendix 1: Database structure): •
o
•
Frontend: database schema containing all data required for the client module in order to define a calculation. The frontend database holds for example tables with waypoints, trajectories, criteria, ships and fall back strategies. For data defined in the frontend schema also the source of the data is defined: o Server: data initially added by an administrator to the server database Local: data added directly to the local database Env: database schema containing environmental data for the five datatypes (tide, current, waves, density and wind). Except for some static tables and for the height reference table, all data are defined by: o Data type: Tide Current Waves Density Wind o Reduction point name (rdp): geographical information. A reduction point is a reference station where environmental data are defined and typically corresponds to a geographical position or area. o Type: information regarding the content of the data: Astronomical: data resulting from long term predictions Predicted: data resulting from short term predictions (app. 36 h) Measured: measured data. o Source: Information regarding the source of the data Server: data initially added by an administrator to the server database Local: data added directly to the local database Web service: data called from web services added directly to the local database Env-data are clustered to the database by means of datasets (unique combination of creation date, validity period of the data and time step).
•
Ship: database schema containing all the data regarding the calculation of vertical ship motions. The ship schema covers the most common dimensions of deep-drafted container ships (Table 2) and bulk carriers (Table 3) that make use of the Scheur and Pas van het Zand channels and also contains a series of LNG carriers (Table 4). The content of the ship schema is based on seakeeping tests carried out with seven ship models in the Towing tank for manoeuvres in shallow water (co-operation Flanders Hydraulics Research – Ghent University) in Antwerp and additional numerical calculations with the 2D strip method Seaway. The database covers a large number of draft – water depth combinations, and also contains data for a variation of metacentric heights.
Final version
WL2020R14_078_1
3
ProToel v2.0 - User manual
•
Calc: database schema containing calculation results. This schema is only accessible by the solver module and is emptied after each calculation.
The rights for adapting data in the different database schemas depend on the role of the ProToel user. The general rules for database access are defined in Table 1.
Role
Table 1 – General rules for changing local database schemas based on role
user power user administrator
Database Schema frontend env ship YES NO NO YES YES NO YES YES YES
In order to separate data defined by an administrator or a (power) user, the source of the data (respectively server and local) is defined for data in the env and frontend schema. A (power) user is not allowed to adapt data with source server. ProToel v2.0 consists of a local database installed on the same computer as the client module and of a remote database located on an external server 1 and can work in standalone mode (calculations are performed by a local solver module) or server mode (calculations are performed on a server solver module). Also a synchronisation functionality is implemented in order to synchronize the local db with the server db. Only the administrator can make changes to the server database. More information regarding adding data to the database is defined in chapter 7.
Table 2 – Ship database Container vessels
Length over all [m] [180:200[ [200:220[ [220:240[ [240:260[ [260:270[ [270:280[ [280:290[ [290:300[ [300:310[ [30:33[
F100
[33:36[
F105
[36:39[ [39:42[
D080 F110 F115
D085 F120
D090 F130
D100
Beam [m]
[42:44[ [44:45[
D095 W075
D105
F140
[45:46[ [46:47[ [47:48[ [48:50[ [50:51[ [51:53[ [53:57[
At present FHR is not hosting a database server. As a result ProToel v2.0 will be used in standalone mode only and synchronization functionality is not enabled.
1
4
WL2020R14_078_1
Final version
ProToel v2.0 - User manual Length over all [m] [310:318[ [318:330[ [330:340[ [340:350[ [350:360[ [360:370[ [370:380[ [380:400[
≥ 400
[30:33[ [33:36[ [36:39[ [39:42[
Beam [m]
[42:44[
W078
[44:45[
D110
[45:46[
W080
[46:47[
D115
[47:48[
W085
D118
[48:50[
D120
[50:51[
W090
D125
[51:53[
W092
[53:57[
W095
W100
Table 3 – Ship database Bulk carriers Length over all [m]
Beam [m]
[180:200[ [200:220[ [220:240[ [240:260[ [260:280[ [280:300[ [300:320[ [320:340[ [30:33[
G100
[33:36[
G105
[36:39[
G110
[39:42[
G115
H115
G120
G125
[42:45[
E080
H125
[45:48[
E085
E090
[48:51[
E095
[51:54[
E100
Table 4 – Ship database LNG carriers Length over all [m]
B [m]
[280:300[ [300:320[ [320:340[
Final version
[42:45[ [45:48[
L075
L078 L080
WL2020R14_078_1
L085
5
ProToel v2.0 - User manual
2.2 Waypoints In ProToel the environment is reproduced by means of waypoints for which bathymetric and environmental data are defined. A waypoint is identified by a name and a source (local or server). The geographical and environmental information for a waypoint are defined by means of the following parameters: • •
Position o Easting o Nothing Reduction points for all datatypes (see §0)
The bottom profile at waypoint-level is defined by means of the following parameters: • • • • • • •
Depth (nautical depth) Top slib depth Reference depth. Channel width to port Channel width to starboard Standard deviation on the survey accuracy Standard deviation due to sedimentation
The waypoints defined for an installation in Zeebrugge are visualized in Figure 1 and Figure 2.
6
WL2020R14_078_1
Final version
ProToel v2.0 - User manual Figure 1 – Visualisation ProToel-waypoints in the coastal routes to the port of Zeebrugge
Figure 2 – Visualisation ProToel-waypoints in the port of Zeebrugge
Final version
WL2020R14_078_1
7
ProToel v2.0 - User manual
2.2.1
Reduction points
The environmental data for different datatypes is defined at geographical reduction points. The reduction points defined for the datatypes tide, current and waves are defined in Figure 3 and Figure 4. A waypoint refers to a reduction point name for each datatype. Figure 3 – Reduction points for datatype tide defined in ProToel v2.0
Figure 4 – Reduction points for datatypes current and waves defined in ProToel v2.0
2.2.2
Fall-back
Depending on the nature of the calculation different types and sources (see §2.1) of environmental data will be applied. For example for a historical calculation the application of measured data (type) might be most relevant, while for forecast calculations the results of long term and short term prediction models will be used. In order to define the most appropriate environmental data for a given calculation, ProToel v2 allows to define a fall back strategy for different combinations of sources and types 2. A standard installation of ProToel comes with three types of fall back mechanisms or rdp-strategies: • •
Astronomical: forecast calculation based on long term predictions for tide, current and waves (based on JONSWAP) Forecast: forecast calculation based on short term prediction for tide and waves (fetched from web services) with a fall back to astronomical data
However the GUI is defined in such a way, the fall back mechanism is not restricted to different sources and types for one rdp. If defined accordingly in the trajectory.xml a fall back can be defined to other rdp’s as well. In fact a fall back mechanism is defined for different combinations of source, type and rdp name of which only source and type (for a fixed rdp name) can be set from the GUI. 2
8
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
•
Hindcast: historical calculation based on measured data for tide, current and waves with fall back to short term predictions and astronomical data.
In the GUI a rdp-strategy can be defined for each data type (see §4.2.3). It is advised to apply astronomical data for data type current. By default the following rdp-strategies are selected in the config-file: • • •
Tide: Current: Waves:
Forecast,SERVER Astronomical,SERVER Forecast,SERVER
Table 5 – Rdp-strategies defined in standard installation ProToel v2
Astronomical rdpstrategy 0 1 2 3 4 5 6 7 2.2.3
source LOCAL SERVER
type
Forecast source
Hindcast type
Source
type
ASTRONOMICAL WEB SERVICE PREDICTED WEB SERVICE MEASURED ASTRONOMICAL LOCAL PREDICTED LOCAL MEASURED SERVER PREDICTED SERVER MEASURED LOCAL ASTRONOMICAL WEB SERVICE PREDICTED SERVER ASTRONOMICAL LOCAL PREDICTED SERVER PREDICTED LOCAL ASTRONOMICAL SERVER ASTRONOMICAL
Web services
For the rdp-strategies Forecast and Hindcast one of the sources defined concerns ‘webservice’. For those waypoints and reduction points for which the source web service is defined in the rdp-strategy, the database will be updated with web service data if required. This requirement depends on the actual status of the db. Web service datasets in the db for which the creation date is older than the wsRefreshTime defined in protoel.config will be neglected. Web services will only be requested for those periods for which there are no valid web service-data defined in the database. By default the wsRefreshTime is set to 360 minutes (6 hours). If for example a first calculation was performed on March 1st 2017 08:00 AM, then (if defined in the rdp-strategy) web service data will be fetched and stored in the database for the requested calculation period. If the same day the calculation is repeated (e.g. for a different draft) at 12:00 AM then no new web service data will be called from the server. The database contains web service data that are added more recently than the wsRefreshTime (4h<6h). When the calculation would have been repeated at 04:00 PM then the web service data will be called a second time because the web service data present in the db are older than the wsRefreshTime (8h>6h). The value of wsRefreshTime can be adapted as described in §4.2.2. If web service data are added to a local database (by a powerUser or Adminstrator) then they will be stored with source Webservice. In case an Administrator performs a calculation with web services in server mode, then the web service data will be stored in the server database with source Server.
Final version
WL2020R14_078_1
9
ProToel v2.0 - User manual
2.3 Criteria The accessibility calculation in ProToel can be based on a number of criteria which can be divided in local and global criteria. A local criterion applies to an individual route point while a global criterion applies to a voyage and depends on the results of all route points corresponding to this voyage. 2.3.1
Local criteria
The local criteria defined in ProToel v2 can be defined for each waypoint individually. The following local criteria can be applied: • • • • • • • •
Min_ukc_brut_abs Min_ukc_brut_rel Min_ukc_topmud_brut_rel Min_ukc_net_abs Min_ukc_net_rel Max_curr_spd Max_transv_curr_spd Max_wind_spd
Min_ukc_brut_abs Min_ukc_brut_abs concerns a minimum absolute value for the gross under keel clearance with respect to the nautical bottom corresponding to a unit of length:
UKC Brut_Abs = h − Tmax
(1)
Min_ukc_brut_rel Min_ukc_brut_rel concerns a minimum relative value for the gross under keel clearance with respect to the nautical bottom corresponding to a fraction of the maximum ship draft:
UKC Brut_Rel = Min_ukc_topmud_brut_rel
h − Tmax Tmax
(2)
Min_ukc_brut_rel concerns a minimum relative value for the gross under keel clearance with respect to the top mud depth corresponding to a fraction of the maximum ship draft:
UKC Top_Mud_Brut_Rel =
h Top_Mud − Tmax
Min_ukc_net_abs
Tmax
(3)
Min_ukc_brut_rel concerns a minimum absolute value for the net under keel clearance with respect to the nautical bottom corresponding to a unit of length:
UKC Net_Abs = h − Tmax − Squat max
(4)
Min_ukc_net_rel Min_ukc_brut_rel concerns a minimum relative value for the net under keel clearance with respect to the nautical bottom corresponding to a fraction of the maximum ship draft:
UKC Net_Rel =
h − Tmax − Squat max Tmax + Squat max
(5)
Min_ukc_net_rel is often referred to as the Manoeuvring Margin (MM)
10
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
Max_curr_spd Max_curr_speed concerns a maximum value for the current magnitude corresponding to a unit of speed. Max_transv_curr_spd Max_transv_curr_speed concerns a maximum value for the current vector perpendicular to the course over ground of the vessel corresponding to a unit of speed. Max_wind_spd Max_wind_speed concerns a maximum value for the wind magnitude corresponding to a unit of speed. 2.3.2
Global criterion (maxBTP)
The maximum bottom touch probability (BTP) is the only global criterion that is taken into account in ProToel. It concerns the probability of the vessel to touch the nautical bottom during a voyage based on the local BTP’s calculated for the individual routepoints. The theoretical calculation of BTP is presented in Appendix 2. If for one of the waypoints the max_btp criterion is defined than this criterion will be evaluated for the complete voyage. 2.3.3
Standard definition
A standard installation of ProToel will come with the combinations of criteria as defined in Table 6. In a trajectory definition (see §2.4) a criterion is assigned to each waypoint.
Table 6 – Criteria defined for a standard installation of ProToel v2 Local criteria
BtpMm200
min ukc brut rel
min ukc brut abs
min ukc topmud brut rel
[%]
[m]
[%]
Global
min ukc min ukc net rel net abs [%]
[m]
Max curr spd
max transv curr spd
max wind spd
max btp
[kn]
[kn]
[Bft]
[-]
20
5
0.0001
BtpMm150
15
5
0.0001
BtpMm125
12.5
5
0.0001
BtpMm100_70
10
-7
5
0.0001
BtpMm150_70
15
-7
5
0.0001
BtpMm150_70_1.5kn
15
-7
5
1.5
0.0001
BtpMm125_70_1.5kn
12.5
-7
5
1.5
0.0001
BtpMm125_70_2kn
12.5
-7
5
2
0.0001
BtpMm100_0.5kn
10
5
0.5
0.0001
Det200
20
Det150
15
Det125
12.5
Det100_70
10
-7
Det150_70
15
-7
Final version
WL2020R14_078_1
11
ProToel v2.0 - User manual Local criteria
min ukc brut rel
min ukc brut abs
min ukc topmud brut rel
[%]
[m]
[%]
Global
min ukc min ukc net rel net abs [%]
[m]
Max curr spd
max transv curr spd
max wind spd
max btp
[kn]
[kn]
[Bft]
[-]
Det150_70_1.5kn
15
-7
1.5
Det125_70_1.5kn
12.5
-7
1.5
Det125_70_2kn
12.5
-7
2
Det100_0.5kn
10
DetMm200
20
5
DetMm150
15
5
DetMm125
12.5
5
DetMm100_70
10
-7
5
DetMm150_70
15
-7
5
DetMm150_70_1.5kn
15
-7
5
1.5
DetMm125_70_1.5kn
12.5
-7
5
1.5
DetMm125_70_2kn
12.5
-7
5
2
DetMm100_0.5kn
10
5
0.5
0.5
2.4 Trajectories A ship trajectory to be calculated is defined as a chain of waypoints for which the following information is defined: • •
Ship speed over ground; criteria to be evaluated.
2.5 Solver The calculation is fully defined by means of a XML-file (the trajectory.xml). When using the GUI or Batch Mode the trajectory.xml will be created automatically. When sending the trajectory.xml to the solver module (using JMS communication) the solver will perform the calculation corresponding to the content of the trajectory.xml and will send the results (XML-format) and log-file (ascii-file) back to the client module. Depending on the mode defined, the trajectory.xml will be send to the local solver or to an application server.
12
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
3 Installation and Getting Started First be sure a Java Runtime Environment (at least version 1.8) is installed on your computer. You can do this by typing the command “java –version” in a command prompt. If java is not installed or the version is too old, please download it from the Internet and install it. ProToel will be delivered as a zip file. Several versions of this zip file will be foreseen, taking into account the available RAM of the user’s PC, in order to optimize the Java and DB parameters. A ProToel zip file contains: • • • • • • • •
•
protoel.jar file, the ProToel executable file protoel.bat (or protoel.sh for Linux) calling protoel.jar with adapted Java parameters protoel_admin.bat calling protoel.jar with adapted Java parameters for an administrator starting ProToel for the first time protoel_batch.bat (or protoel_batch.sh for Linux) calling protoel.jar with adapted Java parameters and a batch file name as parameter a config subfolder containing several configuration files a data subfolder containing several installation files a doc subfolder containing the information about ProToel and a templates subfolder containing examples of Excel files to fill the different database schemas env, ship and frontend, an input subfolder, o with a data subfolder, with three subfolders env, ship and frontend where files to be loaded in ProToel can be put (see Section 7) o and a map subfolder where kml files can be put, that can be optionally displayed in the trajectory panel (see §4.3) an output subfolder that will contain the results of the calculations
This zip file has to be extracted in a folder of your choice, e.g. “C:\ProToel” (in this document referred to as <PROTOEL_HOME>). The next part of the installation is depending on your environment: Windows or Linux.
3.1 MS Windows The steps for installation are summarised here: 1. check java version and if necessary install JRE 2. extract installation zip-file to a folder of your choice 3. run protoel.bat or protoel_admin.bat (see §3.1.1) a. licenceInfo.txt is generated in config folder 4. send licenceInfo.txt to administrator a. Administrator provides protoel.lic file corresponding to the required role 5. store protoel.lic in config folder 6. run protoel_admin.bat and accept installation a. PostgreSQL installation (sql-database) b. database initialisation by data/server.dump c. GUI starts up 7. execute in GUI: File>Fill database>All (see §3.1.2) a. local data added to database 8. generate a shortcut of protoel.bat to your desktop (see §3.1.3).
Final version
WL2020R14_078_1
13
ProToel v2.0 - User manual
3.1.1
Installation
Protoel can be started by means of the “<PROTOEL_HOME>\protoel.bat” command. Since no license file is contained in the installation zip file, by the first start of ProToel, a “licenseInfo.txt” file will be created in the <PROTOEL_HOME>\config folder. This file contains the necessary information to generate a license file. The licenseInfo.txt file should be provided to the administrator who generates a valid license file which has to be saved in the <PROTOEL_HOME>\config folder with the same name as defined in the <PROTOEL_HOME>\config\protoel.config file. Once the license file installed, ProToel has to be started with administrator rights (via the “<PROTOEL_HOME>\protoel_admin.bat” command) in order to allow the automatic installation, tuning and initialization of the ProToel database. Potential errors during this installation are described in section 8. 3.1.2
Initialisation local DB
During the installation the local database is initialized with the data coming from a server dump. In fact at present FHR is not hosting a server, so that the synchronization functionality is not operational. In order to keep his local database up to date (for example to update the depth values of the waypoints) the user will have to actively fill the database. Because a (power) user is not allowed to update the data with source Server, a standard installation of ProToel v2 comes with empty tables for waypoints and trajectories. After installation of ProToel v2 the (power) user has to load the waypoints and trajectories with the fill database functionality for frontend (see §4.2.1). In this way the waypoints and trajectories are defined with source Local, and the (power) user can update them with the same procedure. 3.1.3
Starting GUI
After an installation, the GUI can be started by means of protoel.bat in the PROTOEL_HOME folder. It is advised to define a shortcut on your desktop in order to launch ProToel easily.
3.2 Linux The procedure to get a license file remains valid, but since several versions of Linux exist, with several installers, an automatic installation is not possible. The installation of PostgreSQL should take place as described in the “ProToel_Installation and Exploitation Guide” and the database should be initialized via the File > Restore menu item.
14
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
4 Graphical User Interface 4.1 Running in GUI Mode The graphical user interface (GUI) of ProToel (see Figure 5) can be started by double clicking the batch file protoel.bat (Windows) or protoel.sh (Linux) and consists of a: • • • • •
Menu bar Trajectory visualization panel Ship data panel Trajectory data panel Voyage data panel Figure 5 – ProToel GUI
Final version
WL2020R14_078_1
15
ProToel v2.0 - User manual
4.2 Menu bar The ProToel menu bar (see Figure 6) consists of 6 menus and 2 buttons. The functionality of the buttons is also included in the first menu "File". The role of the logged in user (depending on the license) and the calculation mode are also displayed in this bar. Figure 6 – Menu bar
4.2.1
File Menu
The "File" menu contains the menu entries displayed in Figure 7. Figure 7 – File menu
•
•
•
16
"Run" o “Calculate based on GUI” will perform a calculation based on the input defined in the GUI. This action is also available through the button "Run" on the menu bar. This calculation saves an XML file (trajectory.xml in output folder) that can be adapted and used for other calculations. o “Calculate based on saved XML…” will perform a calculation based on a saved XML file (format of trajectory.xml). When selecting this option, you will be able to browse the file structure to select the input file. Before that the user has to specify whether he wants to perform the calculation based on an updated status of the database or based on the historical status corresponding to the calculation date defined in the XML. In case the user decides to perform the calculation on an updated database then also web services will be updated (if applicable). o “Generate XML based on GUI…” will create a calculation input XML file (format of trajectory.xml) based on the input defined in the GUI. When selecting this option, you will be able to browse the file structure to select the place to store the file. No calculation will be performed. "Results", which can also be called by the button “Results” in the menu bar, is only available if a valid computation has been performed. On click, a table of the calculated results is shown which will be explained in detail in the section 5.1. "Load results…" will ask for a ProToel computation folder and opens the results xml files in a table in the same way newly calculated results are displayed.
WL2020R14_078_1
Final version
ProToel v2.0 - User manual Figure 8 – Load results
•
• • •
4.2.2
“Fill database” permits, according to the user’s role (Administrator, PowerUser or User, see Table 1) to load data from Excel files in the different ProToel schemas in the local or server database (depending on the calculation mode defined, see section 4.2.2). How to add local data to a database is explained in §7. The Excel files are processed in alphabetical order and have to be located: o For “Frontend” in the folder <PROTOEL_HOME>\input\data\frontend o For “Env” in the folder <PROTOEL_HOME>\input\data\env o For “Ship” in the folder <PROTOEL_HOME>\input\data\ship o The “All” item will load all data above, in the order Env, Ship, Frontend. “Backup” saves the contents of your local database in the file <PROTOEL_HOME>\data\protoel_local_<yyyy_mm_dd hhmmss>.dump.zip “Restore” restores a backup stored as <PROTOEL_HOME>\data\protoel.dump.zip to your local database. This dump file can come from your local database or from a database backed up on the server or another client “Exit” exits ProToel. If some changes have been made to the settings, ProToel will propose you to first save them before exiting. Settings Menu
The "Settings" menu contains the menu entries displayed in Figure 9. Figure 9 – Settings menu
Final version
WL2020R14_078_1
17
ProToel v2.0 - User manual
•
• •
“Output Definition” (see §5 for results) o "Full" means that all possible result XML’s have to be returned by the calculation. o "Basic +" means that the basic results (VOYAGE_SUMMARY, CRITERIA_SUMMARY, WAYPOINTS_SUMMARY and LOCAL_BTP_TIME) have to be returned. Additionally the following check boxes can add results to be returned: “Tide” “Current” “Wave height” “Stand Alone Mode” specifies if the GUI is working in stand alone mode (checked) of server mode 3 (unchecked) “Database Synchronization3” contains o A check box “At the start of ProToel” that will enable the synchronization of the local DB with the server DB each time ProToel starts o A item “Now” that forces this synchronization immediately o A check box “Recommendation period (Every n minutes)…” that prompts a popup (see Figure 10) window allowing the user to define this period. If the latest synchronization dates longer than the recommended period, then the user will be asked if he wants to synchronize. By default synchronization is disabled3.
Figure 10 – Database synchronization recommendation period
•
“Web service refresh time…” prompts a popup window allowing the user to define the refresh time for web services (wsRefreshTime). If for a requested calculation the active DB holds web service data that are not older than the refresh time, then no new web service data will be called. By default the wsRefreshTime is set to 360 minutes.
Figure 11 – Web service refresh time
. •
3
“Database History…” prompts a popup allowing the user to define the data retention in days, in function of the user’s role, the source and type of data and the DB location. At start-up of
At present FHR is not hosting a server for synchronization. 18
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
the GUI the Env-schema of the active DB will be checked. Datasets for which the last timestamp (valid_to_date) is older than the retention period and corresponding the other retention parameters will be deleted from the DB. The default settings for Database History are presented in Figure 12. Figure 12 – Database History
• 4.2.3
“Save settings” saves all the changed settings in the ProToel config file, for the next start. Environment Menu
The "Environment" menu contains the menu entries displayed in Figure 13. Figure 13 – Environment menu
•
“Tide” contains the following options: o “Load rdp strategy…” prompts a popup allowing the user to select the rdp strategy name and source, for the given data type. The rdp strategy defines a fallback mechanism for env-data based on source, type and interpolation method 4.
The input XML also allows to use other reductionpoints as fallback. However this is not implemented for the automated XML generation from the GUI. 4
Final version
WL2020R14_078_1
19
ProToel v2.0 - User manual Figure 14 – Load rdp strategy
o
“Edit rdp strategy” prompts a popup allowing the user to edit the rdp strategy, basis rdp and fallbacks based on source and type, for the given data type.
Figure 15 – Edit rdp strategy
•
20
This form contains: The name of the rdp strategy A table with the sequences, names, sources, types and interpolation methods of the rdp’s. The sequence is generated automatically A “+” button to add a rdp A “-“ button to delete the selected rdp Up and down buttons to change the sequence of the selected rdp An “Apply” button to set the rdp strategy as active strategy A “Save“ button to save to the local DB with source LOCAL and name from form, and set this rdp strategy as active strategy An explanation of the way to define a rdp strategy. “Current”, “Waves”, “Density” and “Wind” contain the same options as in the case of tide.
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
4.2.4
Ship Menu
The "Ship" menu contains the menu entries displayed in Figure 16. Figure 16 – Ship menu
•
•
“Squat” contains the following options: o With “FORMULA” the squat will be calculated, based on a formula o With “MODELSCALE” the squat will be interpolated based on draft, under keel clearance and speed for the MODELSCALE conditions defined in the database o “…”. The possible squat options are defined in the frontend.field_possible_values table and can be adapted by the administrator. “RAO Database” contains the following options: o With “SEAWAY” the corresponding RAO database will be used. The response of the ship to waves is calculated by means of a database based on numerical calculations with the 2D strip theory software “Seaway” (integrated into “Octopus”). Although only a two dimensional approach, the motion characteristic is well represented by Seaway o “…”. The possible RAO databases are defined in the frontend.field_possible_values table and can be adapted by the administrator. For a limited number of ships in the database, the ship’s roll response to waves is available for different values of the metacentric height; the program will select the nearest GM value in the database.
•
“container”; “bulk carrier”; “LNG” contains the ships (name and source) of this type, o presented per shipping company. o “…”. If other ship types are added to the frontend database (frontend.ship), they will be automatically added to the menu.
Final version
WL2020R14_078_1
21
ProToel v2.0 - User manual
4.2.5
Visualization Menu
The "Visualization" menu (see Figure 17) offers the possibility to select the textual and graphical elements that will be displayed in the trajectory panel. The possible elements are defined in kml files located in the <PROTOEL_HOME>\input\map folder. The geographical reference system applied is WGS84 UTM31. Figure 17 – Visualization menu
4.2.6
Help Menu
The "Help" menu contains the menu entries displayed in Figure 18. • •
"Help": opens this document "About": shows some legal notes about the program which are also shown on program start up. A mouse click on the notice closes it again. Figure 18 – Help menu
Figure 19 – About ProToel
22
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
4.3 Trajectory Visualization Panel The “Trajectory Visualization” panel (see Figure 20) displays the textual and graphical elements selected in the visualization menu with the trajectory selected in the trajectory data panel. The trajectory itself can be changed in the "trajectory data" panel which is described in Section 4.5. The changes will be reflected immediately in this panel. The following actions can be performed: • • •
Move the mouse on a waypoint displays information about this waypoint Scrolling of mouse wheel allows basic zooming functionality Press right mouse button and move mouse to drag the map Figure 20 – Trajectory Visualization panel
4.4 Ship Data Panel In the “ship data“ panel (see Figure 21), the user can define the ship characteristics and the loading conditions. Figure 21 – Ship data panel
•
The ship characteristics consist of: o The ship’s name o The ship’s shipping company o The ship’s length o The ship’s beam o The ship type (possibilities based on the frontend.ship table). When performing a calculation, ProToel selects the best fitting ship from the selected database (see Table 2, Table 3 and Table 4). The characteristics can also be entered automatically by selecting a ship in the ship menu.
•
The loading conditions consist of: o The draft at the fore perpendicular o The draft at the aft perpendicular o The metacentric height (GM)
Final version
WL2020R14_078_1
23
ProToel v2.0 - User manual
4.5 Trajectory Data Panel In the "trajectory data" panel the trajectory can be loaded and adapted (see Figure 22): •
To load a trajectory the combo box can be used. A trajectory is defined by consecutive waypoints that define the trajectory to be calculated. For each waypoint the following parameters should be defined and can be adapted in the trajectory-table o Waypoint (name & source) o Depth Nautical depth (=depth) Topslib depth o Speed over Ground (= speed) o Criteria (see §2.3) Figure 22 – Voyage data panel (left) and Trajectory data panel (right)
•
The ship’s speed along the trajectory can be adapted directly in the trajectory table. On the other hand there are some buttons to adapt speeds for a combination of waypoints: o “Set all speeds…” allows to set a fixed speed over the complete trajectory Figure 23 – Set all speeds
o
“Set speed per criteria…” Figure 24 – Set speed per criteria
o 24
“Restore default” restores the speed settings to the initial values in the trajectory WL2020R14_078_1
Final version
ProToel v2.0 - User manual
•
Adapt waypoints in trajectory o You can add a waypoint to the row below the selected row in the trajectory table with the “+” button that prompts a popup where you can define the waypoint characteristic (see Figure 25): Waypoint name and source depth (always in meters) topslib depth (always in meters) speed (always in knots) radius (always in meters) criteria name and criteria source Figure 25 – Add waypoint
o o
You can remove the waypoint selected in the trajectory table with the “-” button You can also change the existing waypoint characteristics in the trajectory table
4.6 Voyage Data Panel In the "voyage data" panel (see Figure 22), the following selections have to be made with respect to the planned voyage: • •
The date and time of departure (timezone defined in <PROTOEL_HOME>\config\protoel.config and visualized in GUI); The number of voyages before and after the given time of departure to be calculated and the time span between each voyage in minutes.
Final version
WL2020R14_078_1
25
ProToel v2.0 - User manual
5 Results After a calculation, results are generated in xml format and saved in a subfolder of the <PROTOEL_HOME>\output folder. The possible result files are: •
Summary: o result_voyage_summary.xml: summary xml with the acceptance of the calculated voyages; o result_criteria_summary.xml: summary xml with the acceptance of local and global criteria for the calculated voyages; o result_waypoints_summary.xml: summary xml with values and acceptance of all requested local criterion at waypoint level and the criteria set for all waypoints (local) and voyages (global); o result_btp_data.xml: summary xml with bottom touch probability for all voyages and local bottom touch probability at route point level
•
Environmental data: xml-files with environmental data fetched from the database and metadata regarding the id’s of the data o result_tide_data.xml: tide value [m LAT] o result_globalcurr_data.xml: current magnitude [m/s] and direction [°] o result_heightsigwav_data.xml: significant wave height [m] o result_zeroupcrossperiod_data.xml [s] o result_wind_data.xml: wind magnitude [m/s] and direction [°] o result_density_data.xml: density [kg/m³] Basic calculation: o result_waterdepth_data.xml: bottom depth and tide [m] o result_shipspeed_data.xml: speed over ground and speed through water [m/s] o result_longcurr_data.xml: longitudinal current [m/s] o result_transvcurr_data.xml: lateral current [m/s] Squat calculation: o result_maxsquat_data.xml o result_meansquat_data.xml Dynamic ship motions calculation: o result_shipmotion_data.xml: significant ship motion at most critical point o result_encounterperiod_data.xml o result_criticalpoints_summary.xml: most critical point Local criteria: o result_ukcbrutabs_data.xml o result_ukcbrutrel_data.xml o result_ukcnetabs_data.xml o result_ukcnetrel_data.xml o result_ukctopmudbrutrel_data.xml Performance: o result_calculation_performance.xml: calculation time at different levels: calculation, voyage, route point.
•
• •
•
•
26
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
5.1 Results form Via the menu “File” item “Results” or “Load results…”, you will display a form (see Figure 26) containing the following results of the last calculation or of a selected saved calculation, respectively: • • • • •
trajectory.xml result_voyage_summary.xml result_criteria_summary.xml result_waypoints_summary.xml result_btp_data.xml Figure 26 – Results with meta data and tabs with tidal window, tide, current and wave height
The form contains: •
•
•
Meta data (see Figure 26) o Ship length = trajectory.ship.lengthOverall trajectory.ship.lengthOverall.<unit> o Ship beam = trajectory.ship.beam trajectory.ship.beam.<unit> o Ship maxDraft = maximum of trajectory.ship.draftForward and trajectory.ship.draftAft trajectory.ship.draftForward.<unit> o Ship GM = trajectory.ship.metacentricHeight trajectory.ship. metacentricHeight.<unit> o First departure = minimum of trajectory.travels.startTime o Last departure = maximum of trajectory.travels.startTime o Waves considered = trajectory.maxBottomTouchProbability defined A tab with the tidal window (see Figure 26), containing, at trajectory level first and waypoint level secondly, the criteria, their limits and for each voyage (one per column) the calculated values of the criteria. The colors correspond to the success (green) or failure (red) at trajectory, trajectory criteria and waypoint criteria level. A tab with the tide data, if available in the results (see Figure 27), containing, at waypoint level, for the passing time and the tide, their unit and for each voyage (one per column) their calculated values
Final version
WL2020R14_078_1
27
ProToel v2.0 - User manual Figure 27 – Results, tide
A tab with the current data if available in the results (see Figure 28), containing, at waypoint level, for the passing time and the current speed, their unit and for each voyage (one per column) their calculated values
•
Figure 28 – Results, current
•
28
A tab with the wave data, if available in the results (see Figure 29), containing, at waypoint level, for the passing time and the waves height, their unit and for each voyage (one per column) their calculated values
WL2020R14_078_1
Final version
ProToel v2.0 - User manual Figure 29 – Results, wave height
5.2 Summary pdf file A pdf file with the same name as the ship, saved in the same folder as the xml files, contains similar results. It’s based on the following xml files: • • • • •
trajectory.xml result_voyage_summary.xml result_criteria_summary.xml result_waypoints_summary.xml result_btp_data.xml
and contains the following sections: •
•
•
“Calculation settings“ o description o calculation time (time zone as defined in config file) o deterministic or probabilistic “Ship” o name o type o length (incl. unit) o beam (incl. unit) o draft at aft (incl. unit) o draft at fore (incl. unit) o metacentric height (incl. unit) o motion characteristics database o squat database “Route” o trajectory name o first start time (time zone as defined in config file) o last start time (time zone as defined in config file) o tide data: rdp strategy of first waypoint for which tide is defined o current data: rdp strategy of first waypoint for which current is defined
Final version
WL2020R14_078_1
29
ProToel v2.0 - User manual
wave data: rdp strategy of first waypoint for which wave is defined density data: rdp strategy of first waypoint for which density is defined wind data: rdp strategy of first waypoint for which wind is defined table with: waypoint number waypoint name waypoint depth (incl. unit and height reference) waypoint topslib depth (incl. unit and height reference) waypoint speed (incl. unit and speed type) waypoint radius (incl. unit) “Tidal window” o Calculation of acceptable time slots (= tidal window) displayed under the form of a table containing: starts at duration before: ‘not calculated’ or names of the criteria that are not fulfilled one voyage before the start of tidal window after: ‘not calculated’ or names of the criteria that are not fulfilled one voyage after the end of tidal window o Table containing the same data as the tab “Tidal window” of the Results form described in section 5.1 “Env data” contains the same data as the tabs “Tide”, “Current” and “Wave height” of the Results form described in section 5.1. o o o o
•
•
30
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
6 Batch Mode The batch mode can be used to progressively calculate several configurations. ProToel can be called from the command line with a batch file name as parameter. To do this, execute the following commands from a command prompt: • •
cd <PROTOEL_HOME> protoel_batch.bat <batch file name>
The batch file name is an XLSX-file for which every line corresponds to one calculation. An example of a batch-file is available in <PROTOEL_HOME>\exampleBatch.xlsx. Per calculation, the batch mode will • • •
• • •
define the time zone define the mode create trajectory.xml based on xlsx and store it in output folder <PROTOEL_HOME>\output\<Calculation name>_<YYYYMMDD_HHMMSS> If Calculation.Name ends with ‘.xml’ then copy this xml-file and store it as trajectory.xml in the output folder else create trajectory.xml based on cells in xlsx read data from Excel and perform time conversion save the result xml’s to the output folder start the calculation save the result xml’s to the output folder generate the summary pdf file to the output folder
Each line of the XLSX-file contains the information of Table 7
Table 7 – Batch mode key words
Category Calculation
Final version
Parameter Name
Mapping to trajectory.xml
Comment
trajectory.name
Description
trajectory.description
add "Generated by BATCH to perform “ + stand alone or server mode + ": " before description
Date
trajectory.calculationDate
convert Time zone to UTC
Time zone
see Date
Update DB
used for run
Mode
see description
WL2020R14_078_1
31
ProToel v2.0 - User manual
Category Travels
Parameter Departure date
Mapping to trajectory.xml travels.startTime
Time zone
Ship
Trajectory
Rdp strategy
Output
32
Comment convert Time zone to UTC see Departure date
# Runs before departure
travels.startTime
see GUI
# Runs after departure
travels.startTime
see GUI
Interval
travels.startTime
see GUI
Type
ship.type
LOA
ship.lengthOverall
B
ship.beam
TF
ship.draftForward
TA
ship.draftAft
GM
ship.metacentricHeight
Squat method
ship.squatMethod
RAO Database
ship.raoDatabase
Name
waypoint
see GUI
Source
waypoint
see GUI
Tide name
waypoint.reductionPoint
see GUI
Tide source
waypoint.reductionPoint
see GUI
Current name
waypoint.reductionPoint
see GUI
Current source
waypoint.reductionPoint
see GUI
Waves name
waypoint.reductionPoint
see GUI
Waves source
waypoint.reductionPoint
see GUI
Wind name
waypoint.reductionPoint
see GUI
Wind source
waypoint.reductionPoint
see GUI
Density name
waypoint.reductionPoint
see GUI
Density source
waypoint.reductionPoint
see GUI
outputDefinition.resultType
1 means all files, 0 only VOYAGE_SUMMARY, CRITERIA_SUMMARY, WAYPOINTS_SUMMARY and LOCAL_BTP_TIME
All files
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
7 Adding data to Database The ProToel database contains information about several domains: • • •
Environment data: tide, current, waves, density and wind Ship data: types, RAO’s and squat values Frontend data: trajectories, rdp strategies and criteria
According to his role and to the mode (standalone or server), the user can add information into the database, on the basis of structured Excel files. These rights are summarized in Table 8 and examples of these structured files are referred to in Table 9 to Table 11. Table 8 – Database access
INPUT USER User User User User
OUTPUT
MODE SOURCE stand alone server stand alone server
SCHEMA
DB
SOURCE
Frontend
LOCAL
local DB
LOCAL
Enable
LOCAL
local DB
LOCAL
Enable
SERVER
local DB
LOCAL
Enable
SERVER
local DB
LOCAL
Enable
env height_reference
ship
Disable + WARNING MESSAGE* Disable + WARNING MESSAGE* Disable + WARNING MESSAGE* Disable + WARNING MESSAGE*
PowerUser
stand alone
LOCAL
local DB
LOCAL
Enable
Enable
PowerUser
server
LOCAL
local DB
LOCAL
Enable
Enable
PowerUser
stand alone
SERVER
local DB
LOCAL
Enable
Enable
PowerUser
server
SERVER
local DB
LOCAL
Enable
Enable
LOCAL
local DB
LOCAL
Enable
Enable
LOCAL
ERROR MESSAGE**
SERVER
local DB
SERVER Enable
Enable
Enable
Enable
SERVER
server DB
SERVER Enable
Enable
Enable
Enable
Administrator Administrator Administrator Administrator
stand alone server stand alone server
Enable
* WARNING MESSAGE: Only administrator can make changes to env.height_reference ** ERROR MESSAGE: <xlsx-filename>: source LOCAL cannot be defined on server DB
Final version
WL2020R14_078_1
33
ProToel v2.0 - User manual
The following xlsx templates (see Table 9, Table 10 and Table 11) explain the format of the different files required to load the tables of the ProToel database. Template folder “<PROTOEL_HOME>\doc\templates\env\”, Database schema “env” Table 9 – XSLX-templates for adding env data to database
Template _heightReference.xlsx Tide.xlsx Current.xlsx Wind.xlsx Density.xlsx Waves.xlsx WavesJonswap.xlsx WaveSpectra\ bvhSpectrumInput_20111114_1.xlsx
Target tables height_reference dataset, rdp_tide, tide_data, rdp_dataset dataset, rdp_current, current_data, rdp_dataset dataset, rdp_wind, wind_data, rdp_dataset dataset, rdp_density, density_data, rdp_dataset dataset, rdp_wave, wave_data, rdp_dataset wave_spectra
The tables unit and rdp_measure have to be fed manually by the administrator. Template folder “<PROTOEL_HOME>\doc\templates\ship\”, Database schema “ship” 5 Table 10 – XSLX-templates for adding ship data to database
Template _registeredShips.xlsx shipCriticalPoint.xlsx Seaway_D100_DA8.xlsx
SquatD100.xlsx
Target tables reg_ship_type ship_critical_point condition_rao, roll_ampl, rel_roll_ampl_cond, roll_phase, rel_roll_phase_cond, pitch_ampl, pitch_phase, heave_ampl, heave_phase condition_squat, squat
The table unit has to be fed manually by the administrator. Template folder “<PROTOEL_HOME>\doc\templates\frontend\”, Database schema “frontend” Table 11 – XSLX-templates for adding frontend data to database
Template _criteria.xlsx _waypoint.xlsx trajectory.xlsx ship.xlsx rdp_strategy.xlsx
Target tables criteria waypoint trajectory, trajectory_definition ship rdp_strategy rdp_strategy_sequence
This folder is not defined in a standard installation, as only an administrator is allowed to make changes to the ship-schema.
5
34
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
The tables rdp_strategy_condition, criteria_datatype and rdp_ field_possible_value have to be fed manually by the administrator. In these XLSX-files the field ‘update method’ defines how the data are inserted in the database. The update method can be: • •
UPDATE_OR_INSERT means updating existing rows and inserting unexisting rows CLEAR_AND_INSERT means clearing the table and inserting all rows. In some specific case, like, _registeredShips.xlsx, it means clearing all the tables of the schema and should be used carefully.
Final version
WL2020R14_078_1
35
ProToel v2.0 - User manual
8 Pop-up messages and Problem Handling Table 12 – Pop-up messages and problem handling
Message ProToel could not find a valid license file at <lic-file>. In order to obtain a Protoel license, please supply the administrator with the following file: <inf-file>.
Context
Invalid License File or Incorrect Role
No valid installation of PostGres could be found. A new installation requires to start ProToel as a windows-administrator and might take long. Do you want to continue?
PG standalone installation
Please check the consistency of your <PROTOEL_HOME>\config\hibernate.cfg.local.xml with your PostgreSQL installation or contact your system administrator.
PG standalone installation
Please uninstall current version of PostgreSQL or install another one, by changing postgreSQLInstaller in <PROTOEL_HOME>\config\protoel.config and copying this installer in <PROTOEL_HOME>\data\ or contact your system administrator.
PG standalone installation
Port <port>, defined <PROTOEL_HOME>\config\protoel.config, PostgreSQL port is already in use. Please either select a free port and update - <PROTOEL_HOME>\config\protoel.config, postgreSQLPort, - <PROTOEL_HOME>\config\hibernate.cfg.local.xml, in hibernate.connection.url, - <PROTOEL_HOME>\data\postgresql.windows.conf, port or contact your system administrator. The first free port after the one from the config file is <first free port>.
PG standalone installation
Error while executing the sequences. Please check the log file at: <PROTOEL_HOME>\data\PGLogs\pgCreateSequence.log.
PG standalone installation
Error while taking back up of PostgreSQL database. Please check the log file at: <PROTOEL_HOME>\data\PGLogs\pgBackupProcess.log.
PG standalone installation
Windows has to be restarted in order to finish the PostgreSQL installation process. Would you like to restart now?
PG standalone installation
Unable to connect to Database. Incorrect database configuration file.
Database Connection Error
RDP strategy defined in protoel.config file (<RDP Strategy>) is not present in the database. Please load other RDP strategies before generating a trajectory.xml based on GUI to avoid further issues.
Rdp Not Present in DB
No ship data available in frontend schema.
Ship Data not present in frontend schema
36
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
Message No trajectories available in frontend schema.
Context Trajectory Data not present in frontend schema
RDP Strategy defined for tide data is missing in the database.
Data not present for currently loaded RDP for Tide
RDP Strategy defined for current data is missing in the database.
Data not present for currently loaded RDP for Current
RDP Strategy defined for wave data is missing in the database.
Data not present for currently loaded RDP for Waves
RDP Strategy defined for wind data is missing in the database.
Data not present for currently loaded RDP for Wind
RDP Strategy defined for density data is missing in the database.
Data not present for currently loaded RDP for Density
Error while editing rdp strategy <RDP Name>.
Edit RDP Strategy
Name field can not be blank.
Saving RDP without entering name
RDP Strategy for <RDP Name> has been saved and applied successfully.
Saving RDP
No data to save.
Saving RDP without entering data
Error while saving rdp strategy.
Saving RDP Error message
Please select a row to delete.
Edit RDP Strategy (deleting row without selecting any row)
Error while loading RDP Strategy for <RDP Name>.
Load RDP Strategy error while loading
RDP Strategy for <RDP Name> has been loaded successfully.
Load RDP Strategy success
Last synchronization of the local database was performed on <time> . Do you want to synchronize now?
Calculate based on GUI
File created and saved at path :: <directory path>.
Generation XML based on GUI
Please define a ship.
Generation XML based on GUI (ship type not selected)
Please define at least one waypoint in the trajectory.
Generation XML based on GUI (trajectory not selected)
Please select an xml-file defining the calculation.
Calculate based on saved XML (run clicked without selecting a file)
XmlParsingException: <error>.
Error while parsing trajectory.xml Missing or incorrect tag(s)
XmlValueOutOfRangeException: <error>.
Error while parsing trajectory.xml Invalid value(s)
The unit <unit> could not be found in the unit table of the <schema> schema.
Error while parsing trajectory.xml input file - Missing unit
No web service entries defined for datatype: <dataType>; rdp name: <reductionPoint.name> and type: <reductionPoint.type>.
Web services
Web service did not contain data for datatype: <dataType>; rdp name: <reductionPoint.name> and type: <reductionPoint.type> from <startTime missing data> to <endTime missing data>.
Web services
Final version
WL2020R14_078_1
37
ProToel v2.0 - User manual
Message No valid data was received from web services for id <id> for the requested period: <starttijd> to <eindtijd> (<timezone corresponding to <Web serviceRdp.xml>)
Context Web services
Calculation completed successfully. Output files generated at path: <output result directory path including <PROTOEL_HOME>>.
Calculation Success
The calculation was aborted. No valid env-data / ship-data could be found. Please check the logfile at path: <output result directory path <PROTOEL_HOME>>.
Calculation failure
Calculation performed succesfully, but failed to summarize results from output
Summary PDF
<Schema Name> schema synchronized successfully.
Synchronization Success Message
No data to synchronize. All tables are up to date.
Synchronization (up to date schema)
Error in database cleaning definition: user cannot delete any table in env schema.
DB History Cleaning Error for Role USER
Error in database cleaning definition: server data can never be deleted on the local db.
DB History Cleaning (cleaning server data on local db)
Error in database cleaning definition: server data on the remote db can only be deleted by an administrator.
DB History Cleaning (deleting server data on remote db)
Processing of <filename>.xlsx requires more memory than assigned to ProToel. Please either increase the Java heap size (in <PROTOEL_HOME>\protoel.bat) if sufficient memory is available on your machine, or reduce the size of the xlsx file.
Fill database - Out of memory error
<FileName> ::: Failed to process.
Fill database - Loading env schema
<FileName>; row: <row> ::: Failed to process.
Fill database - Loading env-waves schema
<FileName> ::: Failed to process.
Fill database - Loading ship schema
<FileName> ::: Failed to process.
Fill database - Loading frontend schema
No unit table available in env and ship schema.
Unit table not loaded in ENV and SHIP schema
Database restore completed successfully.
Database Restore
Backup creation Successfull.
Database Restore
Settings saved in the configuration file.
Save Settings
Do you want to save settings for Protoel? Exit Protoel Application
Yes/No/Cancel
38
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
9 Computing requirements and performance ProToel requires important computer resources for normal and especially long term calculations. When running calculations in standalone mode, only the local resources of the local computer will be required. On a quite standard Intel i5 4 cores CPU computer, depending on the available memory, the following calculations could be run: • • •
4 GB: up to 1 day trajectory, with 20 way points and a time span of 10 minutes between voyages 8 GB: up to 1 month trajectory, with 20 way points and a time span of 10 minutes between voyages 16 GB: up to ??? trajectory, with 20 way points and a time span of 10 minutes between voyages
Table 13 gives, for a trajectory with 20 waypoints and voyages every 10 minutes during a given period, the execution times in standalone mode, on several configurations with tuned parameters. These figures are indicative and also depend on others factors, like CPU, disk access,… Table 13 – Performance figures
Execution time Standalone mode - Client RAM 4 GB
8 GB
16 GB
Java Heap Size (defined in <PROTOEL_HOME>\protoel.bat) ? GB
? GB
? GB
Split Factor (defined in <PROTOEL_HOME>\config\protoel.config) ?
?
?
PostgreSQL Shared Buffers (defined in postgresql.conf) Trajectory period 2 hours
? GB
? GB
? GB
6 hours 1 day 1 month 3 months 6 months 1 year
Final version
WL2020R14_078_1
39
ProToel v2.0 - User manual
10 References [1]
Candries, M.; Vos, S.; Peeters, P.; Mostaert, F. (2012). ProToel v13.1 User Manual: Version 1.0. WL Rapporten, 13_067. Flanders Hydraulics Research & Ghent University: Antwerp, Belgium.
[2]
Richter, J.; Vantorre, M.; Laforce, E.; Eloot, K.; Mostaert, F. (2009). Support of a probabilistic access policy for the Flemish harbours: implementation of the software ProToel for the harbour of Zeebrugge. Long-term analysis of the accessibility of the harbour of Antwerp. Nr. 801_03. Flanders Hydraulics Research & Ghent University: Antwerp, Belgium
[3]
Verwilligen, J.; Richter, J.; Eloot, K.; Mostaert, F. (2010). Tijvensters tijdens en na de derde Scheldeverdieping: grafieken. Nr. 807_05. Waterbouwkundig Laboratorium: Antwerpen
[4]
Van Heel, D.J.E.; Verwilligen, J. (2011). Onderzoek nautische toegankelijkheid van Vlissingen Sloehaven en andere Scheldehavens: eindrapport. Rijkswaterstaat. Directie Zeeland: Middelburg
[5]
Vantorre, M.; Candries, M.; Verwilligen, J. (2013) Deterministisch vs. probabilistisch toelatingsbeleid, vergelijkend onderzoek voor Scheldehavens. Versie 2.0. Universiteit Gent/Waterbouwkundig Laboratorium: Gent.
[6]
Vantorre, M.; Laforce, E.; Dumont, G.; Wackenier, W. (2002). Development of a probabilistic admittance policy for the Flemish harbours, in: Cox, R.J. (Ed.) (2002). 30th PIANCAIPCN Congress, 22-26 September 2002, Sydney, Australia: book of abstracts. pp. 1299-1313
[7]
Vantorre, M.; Laforce, E.; Eloot, K.; Richter, J.; Verwilligen, J.; Lataire, E. (2007). Ship motions in shallow water as the base for a probabilistic approach policy, in: (2008). Proceedings of the 27th International Conference on Offschore Mechanics and Arctic Engineering (OMAE 2008), Estoril, Portugal, 15-20 June, 2008 [CD-ROM].
[8]
Eloot, K.; Vantorre, M.; Richter, J.; Verwilligen, J. (2009). Development of decision supporting tools for determining tidal windows for deep-drafted vessels. Marine navigation and safety of sea transportation. Balkema CRC Press. ISBN 9780415804790. 227–234 pp.
[9]
Vantorre, M.; Candries, M.; Verwilligen, J. (2013) Optimization of Tidal Windows for Deep-Drafted Vessels by Means of ProToel. International Workshop on Next Genereation Nautical Traffic Models 2013, Delft, The Netherlands.
[10] Richter J., Vantorre M., Laforce E., Eloot K., Mostaert F. (2008). Support of a probabilistic access policy for the Flemish harbours: Implementation of the software ProToel for the harbour of Zeebrugge: ProToel User Manual. WL Rapporten, Mod 801/3. Flanders Hydraulics Research & Ghent University: Antwerp, Belgium.
40
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
Appendix 1: Database structure The database consists of four schemas: •
The “Env” schema
Final version
WL2020R14_078_1
A1
ProToel v2.0 - User manual
Table unit height_reference
rdp_measure dataset rdp_tide tide_data rdp_current current_data rdp_wave wave_data wave_spectra rdp_density density_data rdp_wind wind_data rdp_dataset
Sync_hist Sync_audit
A2
Content Holds all units and there relation to the SI-unit applied in the calculation Holds the vertical distance between the vertical reference levels LAT, GLLWS, TAW, NAP and MSL for all reduction points for which tide is defined. Adding reduction points for tide requires to add the corresponding information in env.height_reference (this is restricted to an administrator) Holds information about the dimension or measure of different inputs in the env-schema Holds all the datasets that were added to the db Holds the reductionpoints for datatype tide Holds the tide data Holds the reductionpoints for datatype current Holds the current data Holds the reductionpoints for datatype waves Holds the wave data (1D) Holds the wave spectra Holds the reductionpoints for datatype density Holds the tide density Holds the reductionpoints for datatype wind Holds the wind data Summarizes the available data for different combination of datatype, rdp, source, type and dataset. The rdp_dataset is automatically generated from the dataset-table, rdp-tables and data-tables. Holds the latest sync-date and the latest synchronization id (only relevant for client (stand alone) Holds all db-changes made within the schema (only defined for server db) in order to allow synchronization of clients.
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
•
The “Ship” schema
Final version
WL2020R14_078_1
A3
ProToel v2.0 - User manual
Table unit reg_ship_type ship_critical_point condition_rao roll_ampl rel_roll_ampl_cond roll_phase rel_roll_phase_cond pitch_ampl pitch_phase heave_ampl heave_phase condition_squat squat Sync_hist Sync_audit
A4
Content Holds the unit defined for all parameters in ship-schema Holds the main particulars of the vessels in the ship database of ProToel Holds the positions of critical points on the ship keel for all vessels in the ship database of ProToel Holds the available conditions (for each ship combination of draft, water depth and speed over ground) for which RAOdata are available Holds the RAO-data for amplitude of roll motion Holds the relation between GM and roll_ampl Holds the RAO-data for phase of roll motion Holds the relation between GM and roll_phase Holds the RAO-data for amplitude of pitch motion Holds the RAO-data for phase of pitch motion Holds the RAO-data for amplitude of heave motion Holds the RAO-data for phase of heave motion Holds the available conditions (for each ship combination of draft, water depth and speed over ground) for which squatdata are available Holds the squat data (sinkage midship and trim) Holds the latest sync-date and the latest synchronization id (only relevant for client (stand alone) Holds all db-changes made within the schema (only defined for server db) in order to allow synchronization of clients.
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
•
The “Frontend” schema
Final version
WL2020R14_078_1
A5
ProToel v2.0 - User manual
Table criteria waypoint trajectory trajectory_definition ship rdp_strategy rdp_strategy_condition rdp_strategy_sequence criteria_datatype field_possible_value
Sync_hist Sync_audit
A6
Content Holds the available criteria to be selected in GUI Holds all available waypoints, including position and depthinformation Holds the names of the trajectories defined Holds the definition of the trajectories. This involves an ordered list of waypoints to which criteria ad ship speeds are assigned. Holds a list with vessels that can be selected in the GUI Holds the names of different strategies that can be defined as fall back mechanism for env-data Holds all possible combinations of source, type and interpolation method Holds the definition or the rdp-strategies by defining the order of different rdp-strategy-conditions Holds information regarding the required env-data in order to assess a certain criteria Holds information regarding the available options used in the GUI-menus for the parameters: datatype, source, type, interpolation_method, condition_rao_database, condition_squat_database and db. Holds the latest sync-date and the latest synchronization id (only relevant for client (stand alone) Holds all db-changes made within the schema (only defined for server db) in order to allow synchronization of clients.
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
•
The “Calc” schema
Final version
WL2020R14_078_1
A7
ProToel v2.0 - User manual
Table trajectory ship travel output_def waypoint criteria rdp_strategy calculation voyage route_point calcul_result relevant_dataset_tide relevant_dataset_current relevant_dataset_waves relevant_dataset_density relevant_dataset_wind
A8
Content Holds the basic information for the calculation fetched from the trajectory.xml Holds the ship information fetched from the trajectory.xml Holds the start dates for the different voyages to be calculated (fetched from the trajectory.xml) Holds the results-xml’s that have to be generated (fetched from the trajectory.xml) Holds the waypoint data (fetched from the trajectory.xml) Holds the criteria data (fetched from the trajectory.xml) Holds the rdp_strategy for all waypoints and datatypes (fetched from the trajectory.xml) Holds the calculation results at calculation level Holds the calculation results at voyage level Holds the calculation results at routepoint level Holds the calculation and criteria results at routepoint level Holds the datasets for datatype tide that correspond to the rdp_strategy and calculation_date Holds the datasets for datatype current that correspond to the rdp_strategy and calculation_date Holds the datasets for datatype waves that correspond to the rdp_strategy and calculation_date Holds the datasets for datatype density that correspond to the rdp_strategy and calculation_date Holds the datasets for datatype wind that correspond to the rdp_strategy and calculation_date
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
Appendix 2: Bottom Touch Probability ProToel facilitates the probabilistic calculation of bottom touch along a voyage. The determining criterion (max BTP) is the bottom touch probability over the entire voyage. For calculation of BTP the following parameters are taken into account for every routepoint: •
values and standard deviation of tide, bottom depth and draft;
•
directional wave spectrum with standard deviation on significant wave height;
•
density;
•
wind;
•
speed over ground, speed through the water and course over ground;
•
dwell time;
•
vertical ship motions based on §12.1.
The BTP for the trajectory can be calculated from the local BTP at every waypoint. The local BTP however cannot readily be used as a local criterion as it depends on the dwell time a vessel is present in the routepoint. This implies that the local BTP is strongly affected by the number of waypoints that compose the trajectory, while the global BTP is not.
1. Vertical ship motions For calculations of both manoeuvring margin and BTP the vertical ship motions of a vessel should be accounted for. A distinction is made between: •
changes to the static draft as a result of wind and density;
•
stationary vertical sinkage (squat) independent of wind and waves;
•
dynamic vertical ship motions corresponding to the wave climate.
At present ProToel does not take into account the effects of wind and density on the static draft and roll of the vessel. For the BTP calculation both squat and dynamic motions are taken into account. Below the calculation of the vertical motions as a result of squat and waves are presented, based on [14]. 1.1 Ship database 1.1.1 Overview In order to calculate the probability of bottom touch during a particular voyage, the program requires information about the vertical motion of the ships in the database: •
Squat data: average sinkage and trim;
•
Dynamic response characteristics (motion amplitude relative to wave amplitude and phase lag as a function of wave pulsation and angle of incidence of wave) for the vertical motions (heave, pitch, roll) due to waves;
•
Correction factors for response in irregular seaways.
The database is based on results of model experiments and numerical calculations.
Final version
WL2020R14_078_1
A9
ProToel v2.0 - User manual
The model tests were carried out in 1996-2009 in the Towing tank for manoeuvres in shallow water (cooperation Flanders Hydraulics Research – Ghent University) in Antwerp, Belgium, with five ship models: three normative ships (D, E, W) and two critical ships (F, G), see Table 14. The normative ships, two slender ship types (model D and W, container carrier) and a full one (model E, tanker / bulk carrier) were expected to be the largest ones in their category to frequent the harbours of Antwerp, Ghent and Zeebrugge in the near future. Taking into account the wave characteristics in the southern part of the North Sea, it can be expected that these normative ships will not be subject to the largest motions; deep-drafted ships with smaller horizontal dimensions may have a larger probability of bottom touch. For this critical category, two ship models – a slender (model F, panamax container carrier) and a full ship (model G, panamax bulk carrier) – were selected. By adapting the scale factor, a series of ships can be derived from each of the five parent scale models. In this way, the complete range of interest of length-beam combinations is covered by the investigated ship models, see Table 2, Table 3 and Table 4 on p.4 to p.5.
Table 14 – Ship models: main dimensions, [14].
Model Scale Length over all Length between perpendiculars Breadth, moulded Maximum draft Block coefficient at max. draft
1.1.2
(-) (m) (m) (m) (m) (-)
D 1/75 300.0 291.1 40.25 15.00 0.6
E 1/85 343.0 325.0 53.00 21.79 0.85
F 1/50 200.0 190.0 32.00 11.60 0.6
G 1/50 190.0 180.0 33.00 13.00 0.85
W 1/90 398.0 376.0 56.40 16.00
Squat
The actual time-averaged vertical distance between the bottom and the ship’s keel is smaller than the gross under keel clearance due to the squat phenomenon. Due to a ship's forward speed, the pressure and, hence, the water level around the ship is lowered, causing a sinkage and a change of trim. This phenomenon is especially significant in restricted waters, where the influence of squat increases. Initially, the database contained a tabular relationship of mean sinkage and dynamic trim as a function of the speed through the water for each of the combinations ship type – scale factor – water depth – draft. Taking account of the bathymetry of the dredged channels in the North Sea, the effect of the lateral boundaries of the waterways due to blockage could be neglected. In order to be able to extend the calculation tool with trajectories in more confined waters such as rivers and canals, where blockage may be of interest, an alternative calculation method for squat of container vessels has been developed, based on various series of model tests. Principally, the calculation method for squat of container vessels is based on the widely used Tuck parameter Tnh: Tnh =
A10
2 Fnh 2 1 − Fnh
WL2020R14_078_1
(1)
Final version
ProToel v2.0 - User manual
with Fnh =
u g⋅h
•
TNH
Tuck parameter [-];
•
FNH
depth based Froude number [-];
•
u
ship's forward speed component [m/s];
•
g
acceleration of gravity [ms-2];
•
h
water depth [m]
(2)
However, the present method makes use of an alternative Tuck parameter that takes account of the effect induced by the lateral boundaries of the waterway. (1) is replaced by: ′ = Tnh
′2 Fnh ′2 1 − Fnh
(3)
with ′ = Fnh
u kmks g h
(4)
km is a blockage dependent factor: km
Arc sin (1 − m ) = 2 ⋅ sin 3
3
(5)
m denotes an equivalent blockage factor, defined in Figure 30. It should be noted that Schijf’s limiting Froude Number [11] equals km Fnh. ks is a ship dependent factor that increases with the draft. with •
Am
midship section [m2];
•
S
cross section waterway [m²];
•
B
ship’s beam [m];
•
T
ship’s draft [m]. Figure 30 – Blockage definition for squat calculation
Final version
WL2020R14_078_1
A11
ProToel v2.0 - User manual
The importance of squat and its dependence on ship characteristics is illustrated in Figure 31 and Figure 32. In particular, Figure 31 shows that an increase of draft may lead to a decrease of squat, for equal values of the under keel clearance expressed as a fraction of the draft. This can be explained by the fact that, under these circumstances, an increased draft implies an increased water depth and, therefore, a reduced Froude depth number Fnh for the same speed. In addition, a variation of the dynamic trim (bow- or stern-heavy) is noticed during the experiments depending on the load condition or draft. The squat model applied in ProToel was applied for several studies to determine the probabilistic tidal windows to Zeebrugge, Antwerp en Vlissingen. These studies also revealed that the squat has a major impact on the results of a probabilistic calculation combined with a manoeuvring margin.
Figure 32 – Squat: comparison between ship models [12]
2
2
1.5
1,5
sinkage aft (m)
sinkage aft (m)
Figure 31 – Ship model D: maximum squat [12]
1 0.5
1 0,5
0
0 8
10 12 14 Ship's speed (knots) h = 18.0 m h = 17.0 m h = 16.0 m h = 14.0 m h = 13.3 m h = 18.0 m h = 17.0 m
1.1.3
; ; ; ; ; ; ;
T = 15.0 m T = 15.0 m T = 15.0 m T = 11.6 m T = 11.6 m T = 15.0 m T = 15.0 m
; ; ; ; ; ; ;
16
8
TA - TV = 0.0 m TA - TV = 0.0 m TA - TV = 0.0 m TA - TV = 0.0 m TA - TV = 0.0 m TA - TV = 2.0 m TA - TV = 2.0 m
10 Ship's speed (knots)
12
D ; h = 13.3 m; T = 11.6 m (sinkage aft) E ; h = 13.3 m ; T = 11.6 m (sinkage fore) F ; h = 13.6 m ; T = 11.6 m (sinkage aft) G ; h = 13.6 m ; T = 11.6 m (sinkage fore)
Vertical Ship Response to Waves
The vertical ship response to waves is calculated based on: •
Dynamic response characteristics (motion amplitude relative to wave amplitude and phase lag as a function of wave pulsation and angle of incidence of wave) for the vertical motions (heave, pitch, roll) due to waves;
•
Correction factors for response in irregular seaways.
These data for the ships available in the database (ship schema) are a part of the ProToel Back End. Dynamic response characteristics For a number of draft – water depth combinations for each ship from the ProToel Database, the response functions for heave, pitch and roll are stored in the ship database for a range of forward ship speeds; the roll characteristics are defined for a number of metacentric heights. The response functions are formulated under tabular form as a function of wave frequency and wave angle of incidence.
A12
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
The response functions are derived partly from the results of tests in regular waves, partly from numerical calculations. The dimensions of the Towing tank for manoeuvres in shallow water only allows the execution of model tests with angles of incidence in the ranges [-10 deg ; 10 deg] (following waves) and [170 deg ; 190 deg] (head waves). Tests with higher angles of incidence can only be carried out at zero speed. Therefore, computer computations have been used to increase the database by including motions for larger wave angles. Seaway, a strip-theory based seakeeping program developed by JournĂŠe [15], appeared to generate results with acceptable accuracy in comparison with experimental data. As an illustration, Figure 33 compares the frequency characteristics for heave and pitch of ship model F in head waves. Precalculation of the response functions for different ship classes results in a datasets of response functions that were verified and validated based on towing tank tests. During calculation of the response functions the calculation options were optimized for shallow water conditions. This method is considered to be more reliable than an on line calculation of response functions for every vessel separately and applying the results from the numerical codes directly in the BTP calculation. Correction factors for irregular waves The response functions for heave, pitch and roll were partly validated by model tests in regular and irregular waves. Deviations between results in regular and irregular waves can be accounted for by introducing correction factors.
Final version
WL2020R14_078_1
A13
ProToel v2.0 - User manual Figure 33 – Panamax container vessel F, condition FA. Heave and pitch motions in head waves: comparison between model tests (•) and SEAWAY results computed with 2D diffraction method (–––) and classical strip theory (- - -), [13].
2.0
2.0 1.5
1.5
1.5
1.0
1.0
1.0
0.5
0.5
0.5
0
0
0.25
0.50
0.75
1.00
0
0
0.25
0.50
0.75
1.00
0
360
360
360
270
270
270
180
180
180
90
90
90
0
0
0.25
0.50
0.75
1.00
0
0
0.25
0.50
0.75
1.00
0
2.5
2.5
2.5
2.0
2.0
2.0
1.5
1.5
1.5
1.0
1.0
1.0
0.5
0.5
0.5
0
0
0.25
0.50
0.75
1.00
0
0
0.25
0.50
0.75
1.00
0
360
360
360
270
270
270
180
180
180
90
90
90
0
A14
2.0
0
0.25
0.50
0.75
1.00
0
0
0.25
0.50
0.75
WL2020R14_078_1
1.00
0
Diffractie Klassiek Exp.
0
0.25
0.50
0.75
1.00
0
0.25
0.50
0.75
1.00
Diffractie Klassiek Exp.
0
0.25
0.50
0.75
1.00
0
0.25
0.50
0.75
1.00
Final version
ProToel v2.0 - User manual
2. Probabilistic Considerations 2.1 Calculation scheme for probability of bottom touch (BTP) The following steps are executed consecutively to calculate the probability of bottom touch during a particular voyage defined by the Front End. •
Based on the ship definition a ship is selected in the database.
•
Based on the passage time of the consecutive waypoints (j = 1,….,n) the tide and current along the trajectory are time interpolated from the data base. The water depth is calculated based on bottom depth and tide with a standard deviation taking into account: o
standard deviation on the tide prediction;
o
standard deviation on the survey;
o
standard deviation as a result of sedimentation between two surveys.
•
For each waypoint, four combinations water depth – draft – speed are selected in the database which give the best approximations for the actual condition. A weight factor is attributed to each selected combination.
•
Sinkage and trim are calculated for each waypoint, taking into account the ship's speed through the water. This allows computation of the stationary sinkage of a number of so-called critical points on the ship hull. These points are predefined as the positions on the hull that are most likely to experience bottom touch, see Figure 34.
•
For each waypoint, the wave data (spectral density Sζ(ω), average angle of propagation, standard deviation of this angle) for the reference location are introduced and transformed into a table Sζ(ω,μ) of the spectral density of the irregular seaway as a function of angle of incidence and frequency.
•
Based on the motion characteristics for the four selected combinations (Tk, hk, Vk), the spectral density table Sζ(ω,μ) and the experimentally determined correction factors for response in irregular seaways, weighted average amplitude and phase characteristics for heave, pitch and roll are computed. This allows the computation of the amplitude characteristic of the vertical motion of each critical point YZζ (ω; µ ) (ℓ = 1,…,N).
•
The spectral density function of the vertical response of critical point ℓ can be computed as S Z (ω; µ ) = Sζ (ω; µ ) ⋅ YZ2 ζ (ω; µ )
(6)
with •
ω
wave frequency [rad s-1]
•
µ
incident wave angle [deg]
•
ζ
wave elevation [m]
which allows computation of:
m0, Z =
Final version
2π +∞
∫ ∫ S (ω; µ )dωdµ = 16Z 0
0
Z
WL2020R14_078_1
2 s,
(7)
A15
ProToel v2.0 - User manual
m 2, Z =
2 π +∞
2 ∫ ∫ S Z (ω; µ)ω dωdµ 0 0
(8)
with •
m 0, Z
0th moment of response spectrum of vertical motion of critical point ℓ [m2]
•
m 2, Z
2nd moment of response spectrum of vertical motion of critical point ℓ [m2s-2]
Zs,ℓ being the significant value of the vertical wave-induced peak-to-peak motion of critical point ℓ, comparable to the significant wave height. The actual (time-averaged) under keel clearance 6 for critical point ℓ in waypoint j is denoted UKCj,ℓ: UKC j, = h j − T − Z
(9)
with: •
hj
water depth in waypoint j [m]
•
Tℓ
vertical distance between waterline static position critical point ℓ [m]
•
Z
sinkage due to squat (sink and trim) of critical point ℓ [m]
As the peak-to-peak values of the vertical wave-induced motion of critical point ℓ are assumed to follow a Rayleigh distribution:
(
)
p R Z ; Z s , =
16 Z s2,
Z
Z −8 Z e s ,
2
(10)
the probability of bottom touch of critical point ℓ for one oscillatory cycle is given by:
[
]
P j(,1) = P Z > UKC j, = e
−
UKC2j, 2m0, Z
=
UKC j, −8 Zs , e
2
(11)
The probability of bottom touch of critical point ℓ during the passage of the ship in waypoint j with dwell time tj can be expressed by:
Pj , =
1 2π
m2 , Z m0, Z
t j Pj(,1)
(12)
Pj ≡ max (Pj,ℓ) can be considered as the probability of bottom touch in waypoint j. The probability P of bottom touch in full trajectory can be computed as: P = 1−
N
∏ (1 − Pj ) j=1
(13)
In this document the actual under keel clearance is considered the actual time-averaged under keel clearance. It corresponds to the net under keel clearance without taking into account wave response. 6
A16
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
Effect of uncertainty of the actual under keel clearance The calculation above is valid if the actual under keel clearance UKCj,ℓ is exactly known. In reality, this value is subject to uncertainty, due to uncertainty of the bottom level, the still water draft, the tidal level, the squat estimation. If a normal distribution of this actual under keel clearance is assumed with standard deviation σZℓ, than (10) can be calculated as follows:
P1 =
∞
∫ p (z; Z )P (z;UKC R
s ,
G
j ,
0
;σ Z
)
z2
∞
z
− −8 2 16 1 Z dz = ∫ 2 z e S , dz ∫ e Z s , 0 − ∞ 2π σ Z
(x −UKC j , )2 2σ Z2
dx
(14)
The importance of a reliable tide forecast is illustrated in Figure 35. For a container carrier with 15.0 m draft, the window based on a 10-4 probability of bottom touch appears to decrease with 1.5 hours if the standard deviation on the tide prediction increases from 0.01 m to 0.19 m. Effect of uncertainty of wave forecast The calculation scheme described above is valid for a given wave climate. If the wave input is based on forecasts, however, the uncertainty on the prediction should be taken into account. If the significant wave height Hs is predicted with an uncertainty expressed by a standard deviation σHs, it can be assumed that the significant wave-induced motion Zs,ℓ has a normal distribution with standard deviation σZs,ℓ:
σ Zs , =
Z S , ⋅ σ Hs HS
(15)
The peak-to-peak values of the vertical wave-induced motion of a critical point ℓ no longer follows a Rayleigh distribution (10), but a Rayleigh based distribution with a Gaussian distribution of the variance: +∞ +∞
Z2
−8 2 16 pRG (Z ; Z s , ;σ Zs , ) = ∫ pG (Z S ; Z s , ;σ Zs , ) 2 Z e Z S dZ S ≈ ZS −∞
∫ 0
Z2
−8 2 16 pG (Z S ; Z s , ;σ Zs , ) 2 Z e Z S dZ S ZS +∞
∫ p (Z G
0
S
; Z s , ;σ Zs , )dZ S
(16)
taking account of the fact that negative values for the significant value of the vertical motion are physically meaningless. By calculating the probability of bottom touch in this way, not only account can be taken of the quality of the wave forecasts, but also uncertainties of ship characteristics can be dealt with. As a matter of fact, the RAO’s for heave, pitch and roll not only depend on the main dimensions of the ship, but also on parameters that depend on the weight distribution, such as the moments of inertia and the metacentric height. A spreading of 5% appears to be sufficient to take account of variations of the longitudinal moment of inertia, but the effect of GM variations may be 10 to 20%, so that this value should be correctly defined.
Final version
WL2020R14_078_1
A17
ProToel v2.0 - User manual Figure 34 – Illustration of critical point positions corresponding to the positions on the hull that are most likely to experience bottom touch, [14].
Figure 35 – Arrival of a 15 m draft container vessel at Zeebrugge (fictitious example): influence of standard deviation of tide prediction, [14].
A18
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
3. References [11]
Vantorre, M.; Laforce, E.; Dumont, G.; Wackenier, W. (2002). Development of a probabilistic admittance policy for the Flemish harbours, in: Cox, R.J. (Ed.) (2002). 30th PIANCAIPCN Congress, 22-26 September 2002, Sydney, Australia: book of abstracts. pp. 1299-1313
[12]
Vantorre, M. and Dumon, G., 2004, "Model test based requirements for the under keel clearance in the access channels to the Flemish harbours", 2nd Squat Workshop "Aspects of Under Keel Clearance in Analysis and Application", Elsfleth.
[13]
Vantorre, M. and JournĂŠe, J.M.J., 2003, "Validatie van scheepsbewegingenprogramma SEAWAY met behulp van zeegangsproeven in ondiep water". Colloquium "Numerieke oppervlaktewater modellering, mogelijkheden en beperkingen", Antwerp, Belgium.(in Dutch).
[14]
Vantorre, M.; Laforce, E.; Eloot, K.; Richter, J.; Verwilligen, J.; Lataire, E. (2007). Ship motions in shallow water as the base for a probabilistic approach policy, in: (2008). Proceedings of the 27th International Conference on Offshore Mechanics and Arctic Engineering (OMAE 2008), Estoril, Portugal, 15-20 June, 2008 [CD-ROM].
[15]
JournĂŠe, J. and Adegeest, L., 2003. "Theoretical Manual of SEAWAY for Windows". Laboratory of Ship Hydromechanics, Technical University Delft, Report 1370.
Final version
WL2020R14_078_1
A19
ProToel v2.0 - User manual
Appendix 3: Log Messages Message ProToel could not find a valid license file at <lic-file>. In order to obtain a Protoel license, please supply the administrator with the following file: <inf-file>. No valid installation of PostGres could be found. A new installation requires to start ProToel as a windowsadministrator and might take long. Do you want to continue? Please check the consistency of your <PROTOEL_HOME>\config\hibernate. cfg.local.xml with your PostgreSQL installation or contact your system administrator. Please uninstall current version of PostgreSQL or install another one, by changing postgreSQLInstaller in <PROTOEL_HOME>\config\protoel.co nfig and copying this installer in <PROTOEL_HOME>\data\ or contact your system administrator. Port <port>, defined <PROTOEL_HOME>\config\protoel.co nfig, PostgreSQL port is already in use. Please either select a free port and update <PROTOEL_HOME>\config\protoel.co nfig, postgreSQLPort, <PROTOEL_HOME>\config\hibernate. cfg.local.xml, in hibernate.connection.url, <PROTOEL_HOME>\data\postgresql. windows.conf, port or contact your system administrator. The first free port after the one from the config file is <first free port>. Error while executing the sequences. Please check the log file at: <PROTOEL_HOME>\data\PGLogs\pg CreateSequence.log. Error while taking back up of PostgreSQL database. Please check the log file at: <PROTOEL_HOME>\data\PGLogs\pg BackupProcess.log.
A20
Context
Used In
Invalid License File or Incorrect Role
Pop-up
PG standalone installation
Pop-up
PG standalone installation
Pop-up
PG standalone installation
Pop-up
PG standalone installation
Pop-up
PG standalone installation
Pop-up
PG standalone installation
Pop-up
WL2020R14_078_1
Final version
ProToel v2.0 - User manual
Windows has to be restarted in order to finish the PostgreSQL installation process. Would you like to restart now? Unable to connect to Database. Incorrect database configuration file. RDP strategy defined in protoel.config file (<RDP Strategy>) is not present in the database. Please load other RDP strategies before generating a trajectory.xml based on GUI to avoid further issues. No ship data available in frontend schema. No trajectories available in frontend schema. RDP Strategy defined for tide data is missing in the database. RDP Strategy defined for current data is missing in the database. RDP Strategy defined for wave data is missing in the database. RDP Strategy defined for wind data is missing in the database. RDP Strategy defined for density data is missing in the database. Error while editing rdp strategy <RDP Name>. Name field can not be blank. RDP Strategy for <RDP Name> has been saved and applied successfully. No data to save. Error while saving rdp strategy. Please select a row to delete. Error while loading RDP Strategy for <RDP Name>. RDP Strategy for <RDP Name> has been loaded successfully. Last synchronization of the local database was performed on <time> . Do you want to synchronize now? File created and saved at path :: <directory path>. Please define a ship. Please define at least one waypoint in the trajectory. Please select an xml-file defining the calculation. XmlParsingException: <error>. XmlValueOutOfRangeException: <error>. The unit <unit> could not be found in the unit table of the <schema> schema.
Final version
PG standalone installation
Pop-up
Database Connection Error
Pop-up
Rdp Not Present in DB Ship Data not present in frontend schema Trajectory Data not present in frontend schema Data not present for currently loaded RDP for Tide Data not present for currently loaded RDP for Current Data not present for currently loaded RDP for Waves Data not present for currently loaded RDP for Wind Data not present for currently loaded RDP for Density
Pop-up
Edit RDP Strategy Saving RDP without entering name
Pop-up Pop-up
Saving RDP Saving RDP without entering data Saving RDP Error message Edit RDP Strategy (deleting row without selecting any row)
Pop-up Pop-up Pop-up
Load RDP Strategy error while loading
Pop-up
Load RDP Strategy success
Pop-up
Calculate based on GUI
Pop-up
Generation XML based on GUI Generation XML based on GUI (ship type not selected) Generation XML based on GUI (trajectory not selected) Calculate based on saved XML (run clicked without selecting a file) Error while parsing trajectory.xml Missing or incorrect tag(s) Error while parsing trajectory.xml Invalid value(s)
Pop-up
Error while parsing trajectory.xml input file - Missing unit
WL2020R14_078_1
Pop-up Pop-up Pop-up Pop-up Pop-up Pop-up Pop-up
Pop-up
Pop-up Pop-up Pop-up Pop-up Pop-up Pop-up
A21
ProToel v2.0 - User manual
No web service entries defined for datatype: <dataType>; rdp name: <reductionPoint.name> and type: <reductionPoint.type>. Web service did not contain data for datatype: <dataType>; rdp name: <reductionPoint.name> and type: <reductionPoint.type> from <startTime missing data> to <endTime missing data>. No valid data was received from web services for id <id> for the requested period: <starttijd> to <eindtijd> (<timezone corresponding to <Web serviceRdp.xml>) Calculation completed successfully. Output files generated at path: <output result directory path including <PROTOEL_HOME>>. The calculation was aborted.
Web services
Pop-up
Web services
Pop-up
Web services
Pop-Up
Calculation Success
Pop-up
Calculation failure
Pop-up
Summary PDF
Pop-up
Synchronization Success Message
Pop-up
Synchronization (up to date schema)
Pop-up
DB History Cleaning Error for Role USER
Pop-up
DB History Cleaning (cleaning server data on local db)
Pop-up
DB History Cleaning (deleting server data on remote db)
Pop-up
No valid env-data / ship-data could be found. Please check the logfile at path: <output result directory path <PROTOEL_HOME>>. Calculation performed succesfully, but failed to summarize results from output <Schema Name> schema synchronized successfully. No data to synchronize. All tables are up to date. Error in database cleaning definition: user cannot delete any table in env schema. Error in database cleaning definition: server data can never be deleted on the local db. Error in database cleaning definition: server data on the remote db can only be deleted by an administrator. Processing of <filename>.xlsx requires more memory than assigned to ProToel. Please either increase the Java heap size (in <PROTOEL_HOME>\protoel.bat) if sufficient memory is available on your machine, or reduce the size of the xlsx file. <FileName> ::: Failed to process. <FileName>; row: <row> ::: Failed to process. <FileName> ::: Failed to process. <FileName> ::: Failed to process. No unit table available in env and ship schema.
A22
Fill database - Out of memory error Fill database - Loading env schema Fill database - Loading env-waves schema Fill database - Loading ship schema Fill database - Loading frontend schema Unit table not loaded in ENV and SHIP schema
WL2020R14_078_1
Pop-up Pop-up Pop-up Pop-up Pop-up Pop-up
Final version
ProToel v2.0 - User manual
Database restore completed successfully. Backup creation Successfull. Settings saved in the configuration file. Do you want to save settings for Protoel? Yes/No Database cleaning in progress. Please wait. Calculation in progress. Please wait. Web services in progress Please wait. Loading env schema data. Please wait. Loading ship schema data. Please wait. Loading frontend schema data. Please wait. Synchronizing ship schema. Please wait. Synchronizing env schema. Please wait. Synchronizing front end schema. Please wait. Database backup in progress. Please wait. Database restore in progress. Please wait. Data is clearing from database older than the date : <now date> UTC. Computation starts at <now>. Computation ends at <now>. Calculation starts at <now>. Calculation ends at <now>. Retrieve entries from <config.web serviceRdpFile>. No web service entries defined for datatype: <dataType>; rdp name: <reductionPoint.name> and type: <reductionPoint.type>. Connecting to web services at url: <config.wsdlfile> with user: <config.username> . Connection to web services succeeded. Web service did not contain data for datatype: <dataType>; rdp name: <reductionPoint.name> and type: <reductionPoint.type> from <startTime missing data> to <endTime missing data>. Connection to web services closed. Connection to web services failed. Web service data stored in <local/server> database. endtime for sending web service tide inside connection starttime for sending web service tide inside connection
Final version
Database Restore Database Restore Save Settings
Pop-up Pop-up Pop-up
Exit Protoel Application
Pop-up
DB History Start calculation Web services Fill database - Loading env schema
Progress Bar Progress Bar Progress Bar Progress Bar
Fill database - Loading ship schema
Progress Bar
Fill database - Loading frontend schema
Progress Bar
Synchronize Ship Schema
Progress Bar
Synchronize Env Schema
Progress Bar
Synchronize Frontend Schema
Progress Bar
DB backup
Progress Bar
DB restore
Progress Bar
DB cleaning validation Computation start Computation end Calculation start Calculation end
Log file Log file Log file Log file Log file
Web services
Log file
Web services
Log file
Web services
Log file
Web services
Log file
Web services Web services Web services
Log file Log file Log file
Web services
Log file
Web services
Log file
Web services
Log file
WL2020R14_078_1
A23
ProToel v2.0 - User manual
Processing of all access methods starts at <now>. Processing of all access methods ends at <now>. Processing time of all access methods: <time duration>. Fetching <access method> data starts at <now>. Fetching <access method> data ends at <now>. Fetching ConditionSquat data starts at <now>. Fetching ConditionSquat data ends at <now>. Fetching Squat data starts at <now>. Fetching Squat data ends at <now>. No wave spectra were found. Filling calc schema starts at <now>. Filling calc schema ends at <now>. No Env Data found for waypoint <waypointName>, passageTime <passageTime>, datatype <datatype>. Error:GC overhead limit exceeded
A24
Start of processing of all access methods Process completed for all access methods
Log file Log file
Processing time of all access methods
Log file
Fetching of <access method> data start
Log file
Fetching of <access method> data end
Log file
Fetching of condition squat data start
Log file
Fetching of condition squat data end Fetching of squat data start Fetching of squat data end Fetching of spectra data during calculation Update of calculation result in calc schema start Update of calculation result in calc schema end
Log file Log file Log file
Env Data not found OutOfMemory Error
Log file Log file
WL2020R14_078_1
Log file Log file Log file
Final version
DEPARTMENT MOBILITY & PUBLIC WORKS Flanders hydraulics Research Berchemlei 115, 2140 Antwerp T +32 (0)3 224 60 35 F +32 (0)3 224 60 36 waterbouwkundiglabo@vlaanderen.be www.flandershydraulicsresearch.be