MétaCan
Menu
Back to cohort
Record W2317773672 · doi:10.4043/23790-ms

PIRAM: Pipeline Response to Ice Gouging

2012· article· en· W2317773672 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

VenueOTC Arctic Technology Conference · 2012
Typearticle
Languageen
FieldEngineering
TopicGeotechnical Engineering and Underground Structures
Canadian institutionsCentre For Cold Ocean Resources Engineering
Fundersnot available
KeywordsPipeline (software)KeelFinite element methodMarine engineeringSeabedEngineeringComputer scienceStructural engineeringGeologyMechanical engineering

Abstract

fetched live from OpenAlex

Abstract The Pipeline Ice Risk Assessment & Mitigation JIP (PIRAM) developed aset of engineering models and design procedures for implementation intoindustry best practices for risk mitigation and protection of pipelineinfrastructure from ice keel loading. The models established the pipelinemechanical behaviour in response to ice keel load events, and assessedengineering concepts for protection and risk mitigation strategies. Improvedmethodologies for contact frequency and ice keel loads determination formedpart of the integrated model. Pipeline protection against ice gouging is overviewed. A review of subgougeresponse and physical model tests provided a basis for refinement of threedimensional continuum finite element analyses of steady state gouging includingthe implementation of an effective stress based soil plasticity constitutiveroutine. A fully coupled ice, seabed and pipeline interaction model is used tocalibrate a simpler pipeline design approach for design purposes. Thestructural model, improved by considering 3D interaction effects, comparesstrains within the pipeline to those from continuum analyses and from physicalmodel tests. The PIRAM pipeline model provides the engine for the probabilisticassessment of pipeline cover depth using a GIS-based decision-support-systemfor route planning.

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: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.678
Threshold uncertainty score0.893

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.001
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.010
GPT teacher head0.222
Teacher spread0.212 · 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