MétaCan
Menu
Back to cohort
Record W4280566958 · doi:10.3390/en15103774

Choice of the Arch Yielding Support for the Preparatory Roadway Located near the Fault

2022· article· en· W4280566958 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

VenueEnergies · 2022
Typearticle
Languageen
FieldEngineering
TopicTunneling and Rock Mechanics
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsExcavationArchFault (geology)ReinforcementStructural engineeringFinite element methodDeformation (meteorology)Arch damEngineeringGeotechnical engineeringGeologySeismology

Abstract

fetched live from OpenAlex

The article presents a method of selecting an arch yielding support for preparatory workings driven in a hard coal seam. Particular attention was paid to discontinuous deformation in the form of a fault, which significantly contributes to the change of the excavation protection schemes. On the basis of the geometry of the machines and devices in the designed excavation, the support was selected, which was then checked for the ventilation criterion. In the next stage, analytical calculations were carried out using the determined spacing of the steel support in the fault zone and the area outside of it. Additionally, using the RS3 numerical software based on the finite element method, a rock mass model with a fault was built, through which the preparatory excavation passes. The aim of the research was to determine the total displacements occurring in the fault crossing zone for the excavation without support and with the use of steel arch yielding and with additional reinforcement in the form of straight segments. In conclusion, it was found that the variants of the excavation reinforcement can be modeled and selected in advance, which allows for the fastest possible execution of the driving and the maintenance of the minimum movement dimensions while passing through the fault.

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.515
Threshold uncertainty score0.549

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.0010.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.017
GPT teacher head0.234
Teacher spread0.217 · 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