MétaCan
Menu
Back to cohort
Record W2026069763 · doi:10.1680/stbu.2010.163.6.361

Current static design guidance for hollow-section joints

2010· article· en· W2026069763 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

VenueProceedings of the Institution of Civil Engineers - Structures and Buildings · 2010
Typearticle
Languageen
FieldEngineering
TopicStructural Load-Bearing Analysis
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsStructural engineeringWeldingEngineeringChord (peer-to-peer)Section (typography)Engineering drawingMechanical engineeringComputer science

Abstract

fetched live from OpenAlex

The first edition of the International Institute of Welding (IIW) subcommission XV-E design recommendations on static strength of tubular joints was published in 1981. The second edition was published in 1989, which was the basis for the Cidect (International Committee for the Development and Study of Tubular Structures) design guides on the static strength of tubular joints in the early 1990s. Extensive research on tubular joints has been carried out all over the world in the last 20 years. There has hence been a need to update the current static design rules. This paper summarises the third edition of the IIW static design procedure for welded hollow-section joints. It also briefly describes the major changes made to the previous edition and the relevant research background in terms of validity ranges (yield stress), extension of recommendations (moment resistance and multiplanar joints), formulae harmonisation, chord stress function, overlap joints, and plate to tube joints. Two Cidect design guides were published recently, where the new (2009) IIW static design recommendations were adopted. The previous (1989) IIW static design recommendations still exist in many codes/guides. Explanation is given as to which codes/guides follow the IIW (1989) rules and which follow the IIW (2009) rules, and hence what the major differences are between them.

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.000
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: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.018
Threshold uncertainty score0.646

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.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.010
GPT teacher head0.222
Teacher spread0.212 · 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