MétaCan
Menu
Back to cohort
Record W4312533594 · doi:10.1115/pvp2022-86188

A Review of Constraint Effects on Fracture Toughness for Structural Integrity Assessment in Fitness-for-Service Codes

2022· review· en· W4312533594 on OpenAlex
Steven X. Xu, Kim Wallin

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 · 2022
Typereview
Languageen
FieldEngineering
TopicFatigue and fracture mechanics
Canadian institutionsKinectrics (Canada)
Fundersnot available
KeywordsConstraint (computer-aided design)Structural integrityFracture toughnessStructural engineeringComponent (thermodynamics)Reliability engineeringFracture (geology)BrittlenessService (business)ToughnessMatching (statistics)Computer scienceEngineeringForensic engineeringMaterials scienceMechanical engineeringComposite materialMathematics

Abstract

fetched live from OpenAlex

Abstract It is well known that direct application of fracture toughness values measured from standard laboratory specimens to structural components without matching constraint conditions may lead to over-conservative results for structural integrity assessment. In some cases, this may lead to unnecessary repairs or even to an early retirement of the structural component. This is particularly true for structural components operating at late life. For this reason, inclusion of constraint effects on fracture toughness in structural integrity assessment is of great importance. Research on the constraint effects has been very fruitful and is generating standardized methods and procedures that are suitable for engineering applications. This paper provides a review of constraint effects on fracture toughness for structural integrity assessment in fitness-for-service codes. Several fitness-for-service codes (API 579-1/ASME FFS-1, BS 7910, R6, SINTAP/FITNET) have code provisions for including the constraint effects on fracture in ductile-brittle transition region. This paper reviews the two fracture toughness adjustment methods as implemented in the 2019 Edition of BS 7910 and the 2021 Edition of API 579-1/ASME FFS-1. We present the results from a comparative study of the two adjustment methods using four sets of test data recently published in the literature.

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 categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.925
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0020.000
Bibliometrics0.0000.000
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.031
GPT teacher head0.344
Teacher spread0.313 · 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