A 3D Time-Domain Model for Iceberg Impacts with Offshore Platforms and Subsea Equipment
Bibliographic record
Abstract
Abstract When designing oil and gas platforms for offshore arctic and subarctic regions, operators may need to consider the influence of iceberg impacts on optimal structure configuration and ice strengthening requirements. Icebergs have complex and varied shapes, are mostly underwater and are usually moving in currents and waves. Previous iceberg profiles developed from sonar profiles and above water measurements have varying limitations in accuracy, necessitating approximations in modeling both the overall and local shape of the icebergs. A field program was conducted to obtain high resolution full three dimensional (3D) iceberg profiles that allow for detailed modeling of icebergs. Following the field program, a number of studies were conducted to utilize this data to develop improved tools both for calculating design iceberg impact loads for offshore structures and for improving ice management. One of these studies, described here, entails development of a full 3D timedomain simulation model for icebergs impacting fixed and floating platforms in 6 and 12 degrees of freedom (DOF) respectively. A key requirement of the model is that existing scale dependent models for global ice crushing failure pressure can be incorporated. The main objective in developing the model was to provide a tool for evaluating specific iceberg impact scenarios that considers 3D effects and requires fewer assumptions regarding interaction mechanics than previous methods. In this paper, the basic framework of the 3D time-domain model is described, and initial model results are presented for several example applications: icebergs impacting a cylindrical GBS, a stepped cylindrical GBS and a moored spar floating production unit (FPU), the probability of iceberg pinnacles impacting a platform topsides, and subsea interactions. For the cylindrical Gravity Base Structure (GBS), sensitivity analyses are presented for ice strength, friction, drag coefficient, damping coefficients, platform diameter and iceberg velocity.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".