MétaCan
Menu
Back to cohort
Record W4320485914 · doi:10.1080/23249935.2023.2174356

Incorporating design consistency into risk-based geometric design of horizontal curves: a reliability-based optimization framework

2023· article· en· W4320485914 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueTransportmetrica A Transport Science · 2023
Typearticle
Languageen
FieldDecision Sciences
TopicProbabilistic and Robust Engineering Design
Canadian institutionsUniversity Canada WestUniversity of British Columbia
Fundersnot available
KeywordsConsistency (knowledge bases)Reliability (semiconductor)Geometric designComputer scienceCrashMathematical optimizationReliability engineeringEngineeringTransport engineeringMathematics

Abstract

fetched live from OpenAlex

Reliability theory has recently been utilized to consider the uncertainty in highway geometric design and optimize highway cross-section design safety by reducing crash risk. However, despite the importance of design consistency among successive highway segments and its impact on safety, most previous studies optimized road segments individually. This approach could limit the applicability and transferability of the optimization frameworks in practice. Thus, a system reliability-based optimization framework is proposed in this study to design successive highway cross-section elements while achieving overall design consistency and safety. A sequential search procedure with the basin-hopping stochastic algorithm is adopted to optimize the successive horizontal curve segments. A case study of a 12 km segment with 94 horizontal curves in the Sea-to-Sky Highway, Canada, is considered. The results show that the proposed optimization framework provided higher consistency successive cross-section elements design while minimizing the number of expected crashes and providing consistent crash risk levels.

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.025
metaresearch head score (Gemma)0.017
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Meta-epidemiology (narrow), Bibliometrics
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.578
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0250.017
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0060.070
Science and technology studies0.0010.002
Scholarly communication0.0000.001
Open science0.0030.000
Research integrity0.0000.001
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.083
GPT teacher head0.319
Teacher spread0.236 · 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