MétaCan
Menu
Back to cohort
Record W4366506674 · doi:10.11159/icsect23.146

Investigation of the Separation Distance for Preventing Seismic Effects on Reinforced Concrete Buildings

2023· article· en· W4366506674 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueProceedings of the World Congress on Civil, Structural, and Environmental Engineering · 2023
Typearticle
Languageen
FieldSocial Sciences
TopicEarthquake and Disaster Impact Studies
Canadian institutionsnot available
Fundersnot available
KeywordsSeparation (statistics)Reinforced concreteStructural engineeringComputer scienceEngineering

Abstract

fetched live from OpenAlex

In this paper, the importance of leaving a separation (earthquake joint) distance in the design against structural movements and the damages caused by earthquakes were examined.Possible collision and pounding scenarios between adjacent buildings that can occur through various combinations were presented by the help of figures.The consequences that may arise if necessary precautions are not taken were explained.Two adjacent buildings with different story heights and dynamic characteristics were modelled separately with ETABS software in accordance with Turkish Seismic Code (TBDY-18).In addition, earthquake analysis was performed.The building models consisted of two adjacent blocks.During the design reinforced concrete columns with beam slab system were modelled as structural members.Reinforced concrete columns and beams were implemented to the system as frame elements.It was clearly seen that the results obtained with the empirical formulas specified in the regulations and the results of the detailed analysis are not matching with each other.

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.078
Threshold uncertainty score0.324

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.238
Teacher spread0.228 · 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