MétaCan
Menu
Back to cohort
Record W2104345001 · doi:10.1109/icif.2010.5711858

Measures of effectiveness for high-level fusion

2010· article· en· W2104345001 on OpenAlexaff
Erik Blasch, Pierre Valin, Éloi Bossé

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldDecision Sciences
TopicData Quality and Management
Canadian institutionsDefence Research and Development Canada
Fundersnot available
KeywordsRobustness (evolution)Sensor fusionComputer scienceSituation awarenessWorkloadData collectionReliability engineeringData miningEngineeringArtificial intelligence

Abstract

fetched live from OpenAlex

Current advances in technology, sensor collection, data storage, and data distribution have afforded more complex, distributed, and operational information fusion systems (IFSs). IFSs notionally consist of low-level (data collection, registration, and association in time and space) and high-level fusion (user coordination, situational awareness, and mission control). Low-level IFSs typically rely on standard metrics for evaluation such as timeliness, accuracy, and confidence. Given the broader use of IFSs, it is also important to look at high-level fusion processes and determine a set of metrics to test IFSs, such as workload, throughput, and cost. Three types of measures (measures of performance MOP, measures of effectiveness MOE, and measures of merit MOM) are summarized. In this paper, we seek to describe MOEs for High-Level Fusion (HLF) based on developments in Quality of Service (QOS) and Quality of Information (QOI) that support the user and the machine, respectively. We define a HLF MOE based on (1) information quality, (2) robustness, and (3) information gain. We demonstrate the HLF MOE based for a maritime domain situation awareness example.

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.016
metaresearch head score (Gemma)0.056
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.016
Threshold uncertainty score0.086

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0160.056
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0070.003
Science and technology studies0.0010.002
Scholarly communication0.0030.004
Open science0.0010.002
Research integrity0.0020.001
Insufficient payload (model declined to judge)0.0030.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.363
GPT teacher head0.447
Teacher spread0.084 · 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 designTheoretical or conceptual
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

Citations106
Published2010
Admission routes1
Has abstractyes

Explore more

Same topicData Quality and ManagementFrench-language works237,207