MétaCan
Menu
Back to cohort
Record W2131894460

An assessment of hierarchical data fusion using SEABAR'07 data

2009· article· en· W2131894460 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

VenueInternational Conference on Information Fusion · 2009
Typearticle
Languageen
FieldComputer Science
TopicTarget Tracking and Data Fusion in Sensor Networks
Canadian institutionsDefence Research and Development CanadaGeneral Dynamics (Canada)
Fundersnot available
KeywordsSonarSensor fusionComputer scienceTracking (education)Artificial intelligenceFusionMultistatic radarSonar signal processingData miningRadarBistatic radarSignal processingRadar imagingTelecommunications
DOInot available

Abstract

fetched live from OpenAlex

The results of processing selected runs from the SEABAR'07 multistatic sonar trials dataset through General Dynamics Canada's Multiple Target Tracker (MTT) hierarchical data fusion system are reported. The purpose of this exercise was to ascertain the performance potential of the MTT and, by inference, of hierarchical data fusion based tracking generally, against a real multistatic sonar scenario. Selected runs of the original SEABAR'07 dataset have proven themselves well suited to this purpose. Tracking results on these runs are quite positive. To compensate for the lack of a real target in these runs, the SEABAR'07 dataset also includes a modified version, in which the strong echo repeater returns have been replaced by much weaker returns computed using the BASIS bistatic target aspect model. Tracking results with this modified dataset proved less encouraging. These results suggest that the viability of multistatic sonar tracking using a hierarchical data fusion system like the MTT appears promising, but remains unproven; a calibrated trials dataset containing a real target is required to provide a definitive answer.

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.001
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: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.978
Threshold uncertainty score0.962

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.007
Open science0.0050.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.118
GPT teacher head0.401
Teacher spread0.284 · 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