MétaCan
Menu
Back to cohort
Record W2612889333 · doi:10.1109/taes.2017.2702259

Track-Before-Detect Strategies for Radar Detection in G0-Distributed Clutter

2017· article· en· W2612889333 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.

Bibliographic record

VenueIEEE Transactions on Aerospace and Electronic Systems · 2017
Typearticle
Languageen
FieldEngineering
TopicRadar Systems and Signal Processing
Canadian institutionsMcMaster University
FundersChina Postdoctoral Science Foundation
KeywordsClutterTrack-before-detectRadarComputer scienceRadar trackerAlgorithmSecondary surveillance radarStationary target indicationRadar cross-sectionMoving target indicationConstant false alarm rateRadar horizonOutlierRadar engineering detailsContinuous-wave radarRadar imagingArtificial intelligenceTelecommunications

Abstract

fetched live from OpenAlex

This paper considers target detection via dynamic-programming based track-before-detect (DP-TBD) for radar systems. The clutter is modeled usingenlr G0 distribution, which is usually used to model clutter received from high-resolution radars and radars working at small grazing angles. Two target models, namely, Swerling 0 and 1 models, are considered to capture the radar cross section changes over time. DP-TBD techniques that integrate amplitude suffer from significant performance loss in this case due to the high likelihood of target-like outliers. In this paper, the log-likelihood ratio (LLR) is used in the integration process of DP-TBD, taking the place of amplitude, to enhance radar detection performance. The expressions for the LLR for the above target models are derived first. However, neither of them has a closed-form solution. In order to reduce the complexity of evaluating the LLR, efficient but accurate approximation methods are proposed. Then the approximated LLR is used in the integration process of DP-TBD. Simulations are used to examine the efficiency of the approximation methods as well as the performances of different DP-TBD strategies.

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.000
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: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.693
Threshold uncertainty score0.935

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0000.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.009
GPT teacher head0.227
Teacher spread0.217 · 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