MétaCan
Menu
Back to cohort
Record W2811107749 · doi:10.3390/s18072076

Multifunction RF Systems for Naval Platforms

2018· review· en· W2811107749 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

VenueSensors · 2018
Typereview
Languageen
FieldEngineering
TopicSatellite Communication Systems
Canadian institutionsDefence Research and Development Canada
Fundersnot available
KeywordsKey (lock)RadarSystems engineeringElectronic warfareElectronicsRadio frequencyAntenna (radio)EngineeringSystems designComputer scienceTelecommunicationsElectrical engineeringEmbedded systemOperating system

Abstract

fetched live from OpenAlex

The evolving role of modern navies has required increasingly higher levels of capability in the Radio Frequency (RF) shipboard systems that provide radar, communications, Electronic Attack (EA) and Electronic Support (ES) functions. The result has been a proliferation of topside antennas and associated hardware on naval vessels. The notion of MultiFunction RF (MFRF) systems has drawn considerable interest as an approach to reversing this trend. In a MFRF system, RF functions are consolidated within a shared set of electronics and antenna apertures that utilize Active Electronically Scanned Array (AESA) technology. This paper highlights a number of issues to be considered in the design and implementation of a naval MFRF system. Specifically, the key requirements of the RF functions of interest are first reviewed, and MFRF system design trade-offs resulting from costs and/or performance limitations in existing hardware technology are then discussed. It is found that limitations in hardware technology constrain the implementation of practical MFRF systems. MFRF system prototype development programs that have been conducted in other countries are described. MFRF resource allocation management is identified as an important future research topic.

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 categoriesMeta-epidemiology (narrow), Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.977
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.112
GPT teacher head0.325
Teacher spread0.213 · 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