MétaCan
Menu
Back to cohort
Record W2064344480 · doi:10.5430/air.v1n2p75

A Bayesian Network approach to diagnosing the root cause of failure from Trouble Tickets

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

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueArtificial Intelligence Research · 2012
Typearticle
Languageen
FieldComputer Science
TopicSoftware System Performance and Reliability
Canadian institutionsnot available
Fundersnot available
KeywordsBayesian networkScope (computer science)HierarchyComputer scienceRoot causeContext (archaeology)Root cause analysisElement (criminal law)Root (linguistics)Network elementNetwork monitoringDistributed computingComputer securityComputer networkArtificial intelligenceReliability engineeringEngineering

Abstract

fetched live from OpenAlex

Telecommunications networks comprise elements of very different types that work together to provide services. Quite often, hardware failures are interrelated and it is hard for technicians specialized in specific hardware to find out these relationships. In this context, Bayesian Networks (BN) provide a good and flexible solution because they allow us to model the causal relationships between element failures and infer information from existing evidence. The goal is that network technicians can be informed of the real scope of failures and the probable existence of root problems, thus optimizing resources and reducing recovery time. Besides, with this approach a real element hierarchy can be built, allowing the discovery of hidden dependencies between elements. The outcome of this work has been the development of a rooting module attached to an incident management system (trouble ticketing system, TT).

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.005
metaresearch head score (Gemma)0.001
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: none
Teacher disagreement score0.769
Threshold uncertainty score0.462

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0050.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0020.001
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.147
GPT teacher head0.379
Teacher spread0.232 · 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