Arctic Pipeline Leak Detection using Fiber Optic Cable Distributed Sensing Systems
Bibliographic record
Abstract
Abstract Multiple offshore Arctic fields have been developed over the past three decades and the world demand for oil and gas will continue to drive hydrocarbon development in Arctic and sub-Arctic environments. Arctic pipelines are used for the safe and economic transportation of hydrocarbons. While pipelines are designed not to leak, excessive strains due to the effects of ice gouging, strudel scour, frost heave and permafrost thaw settlement along with other loading and failure mechanisms (i.e. corrosion, third party damage) could result in a leak. Failure to detect leaks in a timely manner could have severe safety, environmental, and economic impacts. Large leaks can easily be detected, but small chronic leaks may go undetected for a period of time, especially when pipelines are buried in remote locations or under seasonal ice cover. First, this paper reviews existing Leak Detection System (LDS) technologies for their potential use on Arctic and sub-Arctic pipelines. The technology evaluation based on regulatory requirements and functional criteria suggests that Fiber Optic Cable (FOC) distributed sensing systems have a high potential to be used on Arctic pipelines. Distributed sensing FOC can be used to detect and locate leakages. Pipeline leakage would generate a local change in temperature. These thermal anomalies can be captured by FOC Distributed Temperature Sensing (DTS) systems with good spatial and temporal resolution. Similarly, the acoustic signature generated by leaking fluid can be detected using FOC Distributed Acoustic Sensing (DAS) systems. Inelastic Brillouin and Raman backscattering principles are used for measuring temperature in DTS, whereas the Rayleigh backscattering principle is used for measuring acoustics in DAS. This paper presents information on applicable regulations, operating principles, optical budgets, system integration, sensor positioning, installation and maintenance assessment, technology status, risk analysis using Failure Mode, Effects and Criticality Analysis (FMECA) and field implementation challenges.
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.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.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.
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".