MétaCan
Menu
Back to cohort
Record W157156586

An Automated Explanation Approach for a Decision Support System based on MCDA.

2005· article· en· W157156586 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueExplanation-aware Computing · 2005
Typearticle
Languageen
FieldComputer Science
TopicAI-based Problem Solving and Planning
Canadian institutionsUniversité Laval
Fundersnot available
KeywordsMultiple-criteria decision analysisDecision support systemRanking (information retrieval)Computer scienceContext (archaeology)Operations researchCompromiseDecision analysisProcess (computing)Action (physics)Management scienceProcess managementRisk analysis (engineering)EngineeringArtificial intelligenceMathematics
DOInot available

Abstract

fetched live from OpenAlex

In a military context, the process of planning operations involves the assessment of the situation, the generation of Courses of Action (COAs), and their evaluation according to significant points of view, in order to select the course of action that represents the best possible compromise. Since several conflicting and quite incommensurable criteria need to be considered and balanced to make wise decisions, MultiCriterion Decision Aid (MCDA) has been used to develop decision support systems. Defence Research and Development Canada – Valcartier (DRDC Valcartier) has developed an advisor tool to assist the Air Operation Centre staff in managing events and their related COAs, as well as prioritizing these COAs according to different evaluation criteria by means of a MCDA procedure. Following this development, an investigation has been conducted to provide this decision support system with explanation facilities. This paper describes the suggested approach for the automated generation of explanations of a ranking proposed by a decision support system based on a MultiCriterion Aggregation Procedure (MCAP).

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.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.628
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.000
Scholarly communication0.0000.001
Open science0.0010.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.020
GPT teacher head0.295
Teacher spread0.274 · 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