MétaCan
Menu
Back to cohort
Record W2128013735 · doi:10.1029/2006wr005636

Estimating resilience for water resources systems

2007· article· en· W2128013735 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

VenueWater Resources Research · 2007
Typearticle
Languageen
FieldEngineering
TopicWater resources management and optimization
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsBivariate analysisResilience (materials science)Probabilistic logicComputer scienceReliability (semiconductor)Range (aeronautics)Autoregressive modelMathematical optimizationImportance samplingDomain (mathematical analysis)LagTime domainReliability engineeringEconometricsMathematicsStatisticsEngineeringArtificial intelligenceMachine learningMonte Carlo method

Abstract

fetched live from OpenAlex

Resilience characterizes the recovery capacity of repairable systems from the failure state to the safe state. Resilience has been recognized as a meaningful probabilistic indicator for evaluating risk‐cost trade‐offs in water resources systems. Traditionally, the resilience in the discrete time domain is estimated by sampling methods, which have a high computational expense. No single approximation approach has been well developed for estimating resilience, even under stationary conditions. This paper proposes two practical approximation methods for estimating the lag‐1 resilience in the discrete time domain. Both methods are theoretical developments, one based on a bivariate normal distribution, and the other based on a stochastic linear prediction of the performance function using the mean point of the failure domain. The foundations of both methods are the first‐order reliability method and the periodic vector autoregressive moving‐average time series model. The methods are robust for a wide range of problem characteristics and are applicable for systems facing stationary or nonstationary input conditions.

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.004
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: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.486
Threshold uncertainty score0.778

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0010.000
Scholarly communication0.0010.000
Open science0.0010.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.033
GPT teacher head0.294
Teacher spread0.261 · 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