MétaCan
Menu
Back to cohort
Record W2083246289 · doi:10.1109/tpwrs.2011.2177999

Use of Markov Models in Assessing Spare Transformer Requirements for Distribution Stations

2012· article· en· W2083246289 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

VenueIEEE Transactions on Power Systems · 2012
Typearticle
Languageen
FieldEngineering
TopicPower System Reliability and Maintenance
Canadian institutionsHydro One (Canada)
Fundersnot available
KeywordsSpare partReliability engineeringTransformerMarkov chainProbabilistic logicDistribution transformerRedundancy (engineering)EngineeringComputer scienceMathematicsElectrical engineeringStatisticsVoltageOperations management

Abstract

fetched live from OpenAlex

This paper describes a probabilistic method based on Markov models for assessing the number of spare transformers, regular units and mobile units, required for a group of distribution transformers. The proposed method uses two criteria in determining the required number of spare transformers. The first criterion assumes that a pre-determined level of the group availability is given and the number of spare units is determined when the calculated group availability exceeds the pre-determined level of the group availability. The second criterion uses a cost/benefit analysis method in calculating the number of the spare units. In the second criterion, the number of spare units (optimal number) is determined when the total cost (spare unit capital costs and unit outage costs) is minimum. The proposed method is also used to evaluate the impacts of multi-transformer stations (stations with transformer redundancy) and station capabilities for use of mobile unit transformers on the number of spare units. Two distribution transformer groups of the Hydro One's distribution system are used to illustrate the proposed method of assessment and to compare the results obtained using the two criteria.

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: none
Teacher disagreement score0.964
Threshold uncertainty score0.717

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.001
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.055
GPT teacher head0.272
Teacher spread0.217 · 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