MétaCan
Menu
Back to cohort
Record W1989553357 · doi:10.1115/imece2005-80592

Risk-Informed Load and Resistance Factor Design (LRFD) Methods for Piping

2005· article· en· W1989553357 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
FieldDecision Sciences
TopicProbabilistic and Robust Engineering Design
Canadian institutionsGolder Associates (Canada)
Fundersnot available
KeywordsPipingReliability (semiconductor)Reliability engineeringSafety factorEngineeringFirst-order reliability methodStructural engineeringLoad factorStructural reliabilityComputer scienceMechanical engineeringProbabilistic logic

Abstract

fetched live from OpenAlex

The main objective of structural design is to insure safety, functional, and performance requirements of a structural system for selected target reliability levels, for specified period of time and for a specified environment. As this must be accomplished under conditions of uncertainty, risk and reliability analyses are deemed necessary in the development of such methods as risk-informed load and resistance factor design for piping. This paper provides a summary of the methodology and technical basis for reliability-based, load and resistance factor design suitable for the ASME Section III, Class 2/3 piping for primary loading, i.e., pressure, deadweight and seismic. The methodology includes analytical procedures, such as the First-Order Reliability Method (FORM) for calculating the LRFD-based partial safety factors for piping. These factors were developed in this paper for demonstration purposes, and they can be used ultimately in LRFD design formats to account for the uncertainties in strength and in the load effects. The technical basis provided in the paper is suitable for a proof-of-concept in that LRFD can be used in the design of piping with consistent reliability levels. Also, the results from additional projects in this area, including future research for piping secondary loads, will form the basis for future code cases.

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.005
metaresearch head score (Gemma)0.018
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.884
Threshold uncertainty score0.991

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0050.018
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.174
GPT teacher head0.432
Teacher spread0.258 · 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