MétaCan
Menu
Back to cohort
Record W2113956231 · doi:10.1109/tpwrs.2011.2130850

Investigation of the 2.5 Beta Methodology

2011· article· en· W2113956231 on OpenAlex
Norm Hann, Caitlin Daly

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

VenueIEEE Transactions on Power Systems · 2011
Typearticle
Languageen
FieldEngineering
TopicPower System Reliability and Maintenance
Canadian institutionsHydro One (Canada)
Fundersnot available
KeywordsReliability (semiconductor)Reliability engineeringBETA (programming language)Beta distributionEconometricsEvent (particle physics)Value (mathematics)StatisticsComputer scienceMathematicsEngineeringPower (physics)

Abstract

fetched live from OpenAlex

The IEEE Standard 1366-2003-2.5 Beta Methodology was developed with the intent of providing a reasonable way to define a major event day with respect to distribution reliability performance. According to this methodology, it is valid only if a utility's reliability data completely follows the log-normal distribution, particularly with respect to the tails. This letter's desire is to show that this is not the case for data sets provided by 12 utilities and may not be the case with other utilities. Problems arise when the right tail of utility data sets do not fit the log-normal distribution. The threshold defined by the IEEE 1366-2003-2.5 Beta Methodology will vary since it is dependent on a utility's reliability data from the previous five years. As a result, catastrophic events, reflected by a large daily SAIDI value, will cause an unsuitable increase in the threshold for future years.

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: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.949
Threshold uncertainty score0.377

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.067
GPT teacher head0.224
Teacher spread0.157 · 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