MétaCan
Menu
Back to cohort
Record W4405360332 · doi:10.1115/ipc2024-133038

Matching of Corrosion Features in Multiset Pipeline In-Line Inspection Data Utilizing Relative Point Positions

2024· article· en· W4405360332 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

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicStructural Integrity and Reliability Analysis
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsMultisetPipeline (software)Matching (statistics)Computer sciencePoint (geometry)Line (geometry)CorrosionPipeline transportData miningArtificial intelligenceMathematicsEngineeringStatisticsMaterials scienceCombinatoricsGeometryProgramming languageMechanical engineeringMetallurgy

Abstract

fetched live from OpenAlex

Abstract Pipeline in-line inspection (ILI) stands out as an effective approach for comprehensively understanding the conditions of pipelines. Matching of corrosion features detected in multiset pipeline ILI is an essential prerequisite to determining corrosion growth. State-of-the-art methods for corrosion defect matching require the iterative process to find the optimal affine transformation or the extraction of individual defect attributes for matching model training. However, not only are these processes labor intensive, but the collection of substantial amounts of data is also challenging. To simplify the matching process, an automated method was proposed to match corrosion features that use the position of the features. This algorithm requires only the positions of detected corrosion points and applies to complex defect scenarios with high corrosion density. Firstly, triangles are constructed based on corrosion features. Secondly, local matching was employed to identify matching triangle pairs within two ILIs. Then, a global matching strategy was applied to refine the initially identified matches, filtering the false matches based on predefined requirements. Finally, the points in the final pairs of matched triangles serve as correspondences to determine the registration transformation. Experiments were conducted to validate the efficacy of the proposed method. The results demonstrate its reliability in accurately matching features within pipelines, which supports the integrity and risk assessment of pipeline systems.

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.218
Threshold uncertainty score0.516

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.001
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.025
GPT teacher head0.292
Teacher spread0.267 · 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