MétaCan
Menu
Back to cohort
Record W4297828245 · doi:10.1061/9780784484401.032

Eccentricity Coefficient in Berthing Energy Calculations

2022· article· en· W4297828245 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenuePorts 2022 · 2022
Typearticle
Languageen
FieldEngineering
TopicEngineering and Materials Science Studies
Canadian institutionsHatch (Canada)
Fundersnot available
KeywordsEccentricity (behavior)Computer scienceEnergy (signal processing)StatisticsMathematics

Abstract

fetched live from OpenAlex

The purpose of the eccentricity coefficient in berthing energy calculations is to estimate the portion of the ship’s kinetic energy that fenders must absorb in side-berthing scenarios where angular motion of the ship results from the initial fender contact. Analytical derivations of the eccentricity coefficient were initially introduced to the industry in the 1950s and 1960s. Several analytical solutions were proposed at the time, derived by adopting sets of varying assumptions. More notably, solutions formulated by Vasco Costa and Saurin gained popularity and were eventually introduced into marine design guidelines where they remain relatively unchanged to this day. These guidelines also introduced the notion that berthing velocities of ships approaching under tug-assist should be taken as normal to the berth face, and as such, guidance provided to practitioners on velocity selection for side-berthing scenarios apply only to this approach condition. Standard methods for fender performance rating were also developed based on this assumption, with the energy absorption capacity measurements obtained by compressing the fenders in a direction normal to their base. Authors like Vasco Costa did not necessarily adhere to this simplified approach in their derivation and proposed application of the eccentricity coefficient. Consequently, when ship berthing schematics based on Vasco Costa’s work were introduced in the design guidelines, they portrayed a general solution to side-berthing in which the velocity vector contained a notable longitudinal component. These schematics were seldom updated to reflect the simplified normal direction of the berthing velocity assumed in the guidelines. Since the velocity and berthing approach angles depicted in these general solutions are often used as direct input in the eccentricity coefficient formulae, finding diverse interpretations in fender selection calculations is a common occurrence in cases where practitioners believe special consideration of potential longitudinal velocity may exist because of water currents or due to particular berthing practices. It is also common to find poor and contradictory statements in the definition of these and other input variables in codes and standards, leading to further confusion and misuse of these equations, even when applied to simpler berthing scenarios. A re-derivation of the commonly used eccentricity coefficient solutions provides clarity around the basic assumptions, term definitions, and appropriate application in marine guidelines such as PIANC, MOTEMS, and BS 6349, in a manner that is consistent with the velocity vector assumptions and standard fender performance rating procedures. This paper provides recommendations for existing guidelines that include the adoption of new ship berthing schematics that depict clearly the normal-velocity condition assumed by the standards; clarification that, with very few exceptions, the longitudinal component of the kinetic energy in side-berthing scenarios is assumed to be conserved as longitudinal motion and not absorbed by the fenders; and lastly, clarification that given the stated assumptions, the eccentricity coefficient in side-berthing scenarios only modifies the normal component of the total kinetic energy and therefore the input values used in the eccentricity coefficient equations must reflect the condition in which the velocity vector is normal to the fender base.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.186
Threshold uncertainty score0.350

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.004
GPT teacher head0.176
Teacher spread0.171 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it