MétaCan
Menu
Back to cohort
Record W4389427253 · doi:10.1139/cjce-2023-0161

Bracing requirements and design for a single column considering semi-rigid connections and initial curvature

2023· article· en· W4389427253 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.
fundA Canadian funder is recorded on the work.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueCanadian Journal of Civil Engineering · 2023
Typearticle
Languageen
FieldEngineering
TopicStructural Analysis and Optimization
Canadian institutionsUniversity of Waterloo
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsBracingColumn (typography)CurvatureStructural engineeringEngineeringComputer scienceConnection (principal bundle)MathematicsBraceGeometry

Abstract

fetched live from OpenAlex

The use of bracing has been widely recognized as an effective technique to increase the strength of columns by reducing their effective length. This paper presents an assessment of the bracing requirements for a semi-rigidly connected column, which is laterally braced at the mid-height. By utilizing the proposed half-length column model, the effects of column stiffness and initial curvature on the brace strength and stiffness requirements are investigated. The results indicate that the column’s initial curvature coefficient increases with a higher applied load, but decreases with increased column end connection stiffness. The required brace stiffness requirement stipulated in AISC 360-22 should be increased when considering the effect of column’s initial curvature. Following the design concepts of AISC 360-22 and CSA S16-19, equations for assessing the bracing requirements for a semi-rigidly connected column are proposed. These equations are validated against the finite element analysis results, demonstrating their ability to accurately assess the bracing requirements for semi-rigidly connected columns. These equations can be adopted in current engineering practice.

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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.472
Threshold uncertainty score0.486

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.028
GPT teacher head0.220
Teacher spread0.192 · 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