MétaCan
Menu
Back to cohort
Record W3089119772 · doi:10.1177/8755293020957374

Probabilistic seismic risk assessment of India

2020· article· en· W3089119772 on OpenAlex
Anirudh Rao, Debashish Dutta, Pratim Kalita, Nick Ackerley, Vítor Silva, Meera Raghunandan, Jayadipta Ghosh, Siddhartha Ghosh, Svetlana Brzev, Kaustubh Dasgupta

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

VenueEarthquake Spectra · 2020
Typearticle
Languageen
FieldEngineering
TopicSeismic Performance and Analysis
Canadian institutionsNatural Resources Canada
Fundersnot available
KeywordsSeismic riskProbabilistic logicEarthquake scenarioVulnerability (computing)HazardSeismic hazardRisk assessmentProbabilistic risk assessmentUrban seismic riskPreparednessRisk analysis (engineering)Computer scienceEngineeringCivil engineeringBusinessComputer securityEconomics

Abstract

fetched live from OpenAlex

This study presents a comprehensive open probabilistic seismic risk model for India. The proposed model comprises a nationwide residential and non‐residential building exposure model, a selection of analytical seismic vulnerability functions tailored for Indian building classes, and the open implementation of an existing probabilistic seismic hazard model for India. The vulnerability of the building exposure is combined with the seismic hazard using the stochastic (Monte Carlo) event‐based calculator of the OpenQuake engine to estimate probabilistic seismic risk metrics such as average annual economic losses and the exceedance probability curves at the national, state, district, and subdistrict levels. The risk model and the underlying datasets, along with the risk metrics calculated at different scales, are intended to be used as tools to quantitatively assess the earthquake risk across India and also compare with other countries to develop risk‐informed building design guidelines, for more careful land‐use planning, to optimize earthquake insurance pricing, and to enhance general earthquake risk awareness and preparedness.

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.169
Threshold uncertainty score0.451

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.008
GPT teacher head0.216
Teacher spread0.208 · 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