Discussion of “Shear Lag in Rectangular Hollow Structural Sections Tension Members: Comparison of Design Equations to Test Data” by Bo Dowswell and Stacey Barber
Bibliographic record
Abstract
The discussers argue that the authors (Dowswell and Barber) inappropriately use data for efficiency factor (U) accuracy verification because the data, gleaned from 1999 Zhao et al. and 1995 Zhao and Hancock efforts, has a governing failure mechanism which always correponds to block shear or tear-out (TO). The discussers also argue that the authors, in calculating U, calculate weld return length (l) using a weld portion located in the weld return region which AISC definitions of l say should be neglected in calculating l. Model response validation should be done against experimental data if finite-element modeling (FEM) data is to be used. The discussers argue that the authors' inclusion of 1995 data by Girard et al. is questionable because they could not verify circumferential fracture (CF) failure mechanism reproduction capacity (and corresponding ultimate load). The discussers note, however, the authors' postulation that shear lag-induced fracture is more accurately predicted by reduced eccentricity value is correct. The discussers argue for using reduced eccentricity for connections fabricated with elliptical hollow sections and circular hollow sections for predicted capacity improvements as shown by 2006 Martinez-Saucedo et al. and 2006 Willibald et al. efforts. Shear lag reduction factor (U) influence should be assessed only by tests failing by CF. Hollow section U factor modification should be related to the latest AISC specifications.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.007 | 0.014 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".