MétaCan
Menu
Back to cohort

Machine learning in earthquake engineering: A review on recent progress and future trends in seismic performance evaluation and design

2025· review· en· W4411049700 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

VenueEngineering Structures · 2025
Typereview
Languageen
FieldComputer Science
TopicSeismology and Earthquake Studies
Canadian institutionsUniversity of British Columbia, Okanagan CampusUniversity of British Columbia
FundersH2020 Marie Skłodowska-Curie ActionsNational Science Fund for Distinguished Young ScholarsInstituto de Investigación de Recursos Biológicos Alexander von HumboldtAlexander von Humboldt-Stiftung
KeywordsEarthquake engineeringEngineeringSeismic analysisConstruction engineeringForensic engineeringCivil engineeringComputer scienceStructural engineering

Abstract

fetched live from OpenAlex

Applying machine learning (ML) in earthquake engineering has introduced new opportunities for better predicting, evaluating, and mitigating structural damage under seismic hazards . The rapid advancement of ML in earthquake engineering necessitates a thorough understanding of its potential and limitations to guide future research and practical applications effectively. This literature review focuses on the recent advancements of ML in structural seismic performance evaluation and design optimization. This paper comprehensively explores recent trends and innovations for each area, highlights ongoing challenges, and suggests future directions involving emerging technologies. Key findings reveal significant progress in ML methodologies. Still, challenges related to the accurate prediction of nonlinear hysteretic responses, the need for improved generalizability of ML models, the scarcity of high-quality data, effective feature selection techniques, and regional scale investigations remain. Moreover, the future research needs and strategies for addressing these challenges are presented.

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.969
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.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.023
GPT teacher head0.287
Teacher spread0.264 · 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