Comparison of Provisions for Nonslender Reinforced Concrete Columns: American Concrete Institution, Eurocode, Indian Standard, and Canadian Standards Association
Bibliographic record
Abstract
The basis for the design of any concrete structural element is the concrete building code. Since the requirements for different used codes are dissimilar, a detailed comparative analysis needs to be conducted to compare multiple structural design aspects of various codes used worldwide and find out if there is any significant differences in the design procedures. The main objective of this study is to compare 4 building codes: ACI Standard: Building Code Requirements for Structural Concrete; the European Standard: Eurocode 2: Design of concrete structures—Part 1-1: General Rules and Rules for Buildings; the Indian Standard: Plain and Reinforced Concrete—Code of Practice; and the Canadian Standard: CSA A23.3-19 Design of Concrete Structures to draw conclusions on the differences in the design requirements for general characteristics, flexure, and provisions for nonslender columns. The same column cross section was used to calculate axial capacities based on all four codes and the results were presented in a comparative table. All the codes have some differences in the provisions compared. In general, regarding column axial capacities, it was seen that estimates provided by the Indian code were more conservative compared to the remaining three codes.
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.003 | 0.009 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.007 | 0.009 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 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".