MétaCan
Menu
Back to cohort
Record W2171758753 · doi:10.1109/caia.1995.378780

Using paths to detect redundancy in rule bases

2002· article· en· W2171758753 on OpenAlexaff
P.G. Chandler, T. Radhakrishnan, R. Shinghal

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsConcordia University
Fundersnot available
KeywordsRedundancy (engineering)Computer scienceData miningInefficiencyRule-based systemTheoretical computer scienceAlgorithmArtificial intelligence

Abstract

fetched live from OpenAlex

One of the major causes of inefficiency in rule-based systems is rule base redundancy; hence, its detection is an actively pursued research topic. Most of the existing methods consider rule base redundancy at two levels: at the rule level and at the level of rule sequences or rule chains. The computational complexity and the extent of redundancy that can be detected are two measures of performance that can be used to compare different methods of redundancy detection. We propose the use of "paths" for redundancy detection. Starting from a specification mechanism to abstract the problem solving knowledge of the domain, called goal specification, we have developed software tools for efficient extraction of paths. Based on such paths, we identify rule situations called "rule aberrations" which form the core of the algorithm proposed for redundancy detection. For illustration, the algorithm is applied to an example rule base, and redundant rules and atoms are detected. Our method of redundancy detection is also compared with the existing approaches.>

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.004
metaresearch head score (Gemma)0.032
Version: metacan-v3-hybrid-931329e0061cValidation 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: Methods · Consensus signal: Methods
Teacher disagreement score0.004
Threshold uncertainty score0.021

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0040.032
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0040.002
Science and technology studies0.0010.001
Scholarly communication0.0020.004
Open science0.0020.002
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0020.001

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.059
GPT teacher head0.294
Teacher spread0.236 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations2
Published2002
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering ResearchFrench-language works237,207