Use of Inertial Measurement Unit In-Line Inspection Data to Support Code Stress Compliance and Integrity Evaluations
Bibliographic record
Abstract
Abstract Pipelines are an essential segment of infrastructure required to transport a variety of products to markets in our economies. The integrity and safe operation of those pipeline necessitates that pipeline operators have a thorough understanding of their pipeline systems, their configuration, and the changing operating condition within their pipeline networks. Inertial measurement unit (IMU), a technology that can measure the angular rate and acceleration and when combined with global positioning and navigation equipment such as pipeline above ground markers, can calculate position and orientation with 6 degrees of freedom: x, y, z, and pitch, roll, and yaw. IMU launched within the pipeline via in-line inspection tool trains, can be used to develop accurate three-dimensional geometry of the pipelines they inspect. This information can be used to confirm the geometry of the pipeline (i.e. degree of roping, bend angle, bend radius, and other abnormalities observed within the generated centerline from the inspection based on conventional construction practices). Therefore, the application of IMU technology within pipeline design and integrity work can be a useful tool in providing the necessary input information which can support ongoing studies such as verification of maximum operating thermal differentials which can be imposed on a pipeline to remain compliant with governing pipeline codes, and/or the information can be used to perform gap analysis studies with other integrity records (alignment sheets, as-built pipe tallies), or to support other pipeline integrity evaluations. When IMU data is processed with mathematical techniques essential information from IMU data can be obtained such as bend angle, bend radius, and degree of installed curvature. A case study showing the results of the application of processed IMU data for as-built evaluation is presented and its use to help support a variety of decision making is discussed. The IMU data is a key data input when constructing detailed finite element models for on-going stress analysis studies.
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.001 | 0.008 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.004 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.002 |
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".