MétaCan
Menu
Back to cohort
Record W4413029491 · doi:10.2514/1.i011629

On the Role of Communications for Space Domain Awareness

2025· article· en· W4413029491 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueJournal of Aerospace Information Systems · 2025
Typearticle
Languageen
FieldEngineering
TopicSatellite Communication Systems
Canadian institutionsPolytechnique Montréal
FundersCanadian Network for Research and Innovation in Machining Technology, Natural Sciences and Engineering Research Council of Canada
KeywordsComputer scienceDomain (mathematical analysis)Space (punctuation)Situation awarenessAeronauticsEngineeringAerospace engineeringMathematicsOperating system

Abstract

fetched live from OpenAlex

Space domain awareness (SDA) has become increasingly important due to the rapid growth of commercial space activities and the expansion of New Space. This paper examines the need for transitioning from centralized to distributed SDA architectures, highlighting the limitations of traditional centralized systems in scaling with increasing satellite nodes. The analysis demonstrates that centralized architectures, which rely on individual downhaul, struggle to maintain efficiency as the number of satellites grows. In contrast, distributed architectures offer enhanced scalability, coverage, and resilience by processing data on orbit. Specifically, a low Earth orbit constellation capable of performing data analysis and response formulation on orbit can reduce routing times from 60 to 9 ms, providing an order-of-magnitude improvement in performance. The study applies this analysis to Starlink, OneWeb, Planet Labs, and Jilin constellations, demonstrating the advantages of distributed approaches across diverse satellite systems. This paper also discusses the tradeoffs between centralized and distributed architectures and provides key considerations for selecting the most appropriate approach for scalable and resilient SDA systems.

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: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.908
Threshold uncertainty score0.325

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.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.017
GPT teacher head0.262
Teacher spread0.245 · 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