MétaCan
Menu
Back to cohort
Record W2030007150 · doi:10.1115/pvp2007-26124

Technical Basis of Proposed New Acceptance Standards for Class 1, 2 and 3 Piping

2007· article· en· W2030007150 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

VenueVolume 1: Codes and Standards · 2007
Typearticle
Languageen
FieldEngineering
TopicFatigue and fracture mechanics
Canadian institutionsKinectrics (Canada)
Fundersnot available
KeywordsPipingAcceptance testingEngineeringClass (philosophy)Structural engineeringForensic engineeringComputer scienceMechanical engineering

Abstract

fetched live from OpenAlex

Acceptance Standards in Section XI of the ASME Boiler and Pressure Vessel Code have an important role as the first step in the flaw evaluation procedure. When a flaw size is within the allowable flaw size in the Acceptance Standard, the flaw is acceptable and analytical evaluation is not required. Although ASME Section XI has Acceptance Standards for Class 1 piping in IWB-3500, there are no Acceptance Standards for Class 2 and 3 piping. Furthermore, the development of the current Acceptance Standards for Class 1 piping was based on flaw detectability by ultrasonic inspection and consideration of fracture mechanics. In this paper, the development of proposed new Acceptance Standards for Class 2 and 3 piping, as well as for Class 1 piping, is described. The development methodology is based on a fracture mechanics approach. For Class 1 piping with high fracture toughness, the allowable flaw sizes were determined by limit load solution. For Class 1 piping, the intent was to maintain overall consistency with the current Acceptance Standards. Proposed Acceptance Standards for Class 2 and 3 austenitic piping were also developed by the methodology used to develop the proposed new Acceptance Standards for Class 1 piping. Allowable flaw sizes for both surface flaws and subsurface flaws for preservice and inservice examinations were developed.

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.001
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: none
Teacher disagreement score0.937
Threshold uncertainty score0.627

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
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.009
GPT teacher head0.258
Teacher spread0.248 · 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