MétaCan
Menu
Back to cohort
Record W4417276718 · doi:10.1520/stp165420240006

Validation of the SDAR Algorithm and ASTM Standard Practice E3076

2025· book-chapter· en· W4417276718 on OpenAlexaff
S. A. Graham, Kimberly Maciejewski

Bibliographic record

Venuenot available
Typebook-chapter
Languageen
FieldEngineering
TopicFatigue and fracture mechanics
Canadian institutionsKensington Health
Fundersnot available
KeywordsChord (peer-to-peer)Test methodWork (physics)Test (biology)TangentTest data

Abstract

fetched live from OpenAlex

Many ASTM standards (for example, ASTM E8, Standard Test Methods for Tension Testing of Metallic Materials; ASTM E9, Standard Test Methods of Compression Testing of Metallic Materials at Room Temperature; and ASTM E111, Standard Test Method for Young's Modulus, Tangent Modulus, and Chord Modulus) require slope determination as part of data analysis but do not specify an objective method for making this determination. This lack of method leads to increased variability, which impacts precision and bias. In 2007, work began to develop an algorithm that would perform an objective determination of slope. That algorithm became known as SDAR (Slope Determination by Analysis of Residuals). In 2011, ASTM Committee E08 on Fatigue and Fracture began developing a draft standard practice based on the SDAR algorithm. Because implementation of the algorithm is computationally intensive, there were concerns about its complexities. The ability of users to code the algorithm in the language or application of their choice was evaluated by way of two analytical round robins. The results of those two round robins are here presented and the conclusions derived from them are discussed.

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 imitation

Not 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.

metaresearch head score (Codex)0.018
metaresearch head score (Gemma)0.036
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.027
Threshold uncertainty score0.097

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0180.036
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0060.005
Science and technology studies0.0020.001
Scholarly communication0.0060.004
Open science0.0030.002
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0270.028

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.006
GPT teacher head0.206
Teacher spread0.200 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreMethods

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".

Quick stats

Citations0
Published2025
Admission routes1
Has abstractyes

Explore more

Same topicFatigue and fracture mechanicsFrench-language works237,207