MétaCan
Menu
Back to cohort
Record W7023869293

Probabilistic Methods in Engineering: Quantifying Uncertainty and Implementing Performance-Based Design

2010· other· en· W7023869293 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueMecánica Computacional (Asociación Argentina de Mecánica Computacional) · 2010
Typeother
Languageen
Field
Topic
Canadian institutionsnot available
Fundersnot available
KeywordsProbabilistic logicReliability (semiconductor)Context (archaeology)Probabilistic relevance modelProbabilistic analysis of algorithmsStatistical modelProbabilistic design
DOInot available

Abstract

fetched live from OpenAlex

The last decades have seen great advances in computational models and in the ability to tackle previously intractable problems in mechanics. Yet, these models normally incorporate many variables which are not deterministic, introducing uncertainty in the calculated output. The problem of estimating the probability distribution of the output, given the probabilistic description of the input, has als o received much at tenti on since the 1 9 6 0 ’s and many computational techniques have now been developed to account for the probabilistic nature of the problem. This paper discusses the integration of analysis and reliability assessment, including examples of large Canadian projects and design codification. Current objectives in probabilistic methods include the development of performance-based design. This paper discusses this topic in the context of earthquake engineering, with an application to the performance-based design of a steel pile under seismic excitation.

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.010
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Research integrity, Insufficient payload (model declined to judge)
Consensus categoriesMeta-epidemiology (narrow), Research integrity
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.156
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0100.001
Meta-epidemiology (narrow)0.0030.003
Meta-epidemiology (broad)0.0030.001
Bibliometrics0.0030.003
Science and technology studies0.0010.001
Scholarly communication0.0010.000
Open science0.0020.002
Research integrity0.0020.004
Insufficient payload (model declined to judge)0.0030.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.055
GPT teacher head0.341
Teacher spread0.286 · 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