MétaCan
Menu
Back to cohort
Record W4235659490 · doi:10.1109/tdc.1991.169579

An intelligent front end for secondary power distribution system design

2002· article· en· W4235659490 on OpenAlex
N.D. Rao, Y. Zhang

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

VenueProceedings of the 1991 IEEE Power Engineering Society Transmission and Distribution Conference · 2002
Typearticle
Languageen
FieldEngineering
TopicPower Systems and Technologies
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsBackward chainingDialog boxChainingComputer scienceFront and back endsExpert systemUser interfaceOverhead (engineering)TransformerDatabaseEngineeringElectrical engineeringOperating systemInference engineArtificial intelligenceVoltage

Abstract

fetched live from OpenAlex

The development and use of an expert-system (ES)-based intelligent front end (IFE) for radial-type electric power secondary distribution system (single-phase/three-phase, overhead/underground) design is described. The design is based on minimizing the total annual cost (TAC) of owning and operating the system, subject to specified voltage drop and dip criteria. A rule-based, goal-driven, backward chaining ES shell, VP-Expert, is used to create the IFE and interface it with relational database (dBASE) files on transformer data and transmission line data. The IFE has a very friendly user interface and makes use of a dialog method to communicate with the user. Menus are used to ask for user inputs. The IFE approach is illustrated by means of an example problem involving secondary distribution system design in an urban area. A sample dialog generated during a typical consultation session is presented. The advantages of using an expert system shell as an IFE to existing database files maintained by electric utility companies for secondary distribution system design are discussed.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

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

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.015
GPT teacher head0.197
Teacher spread0.182 · 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