MétaCan
Menu
Back to cohort
Record W1965380876 · doi:10.1109/joe.2013.2239812

Robust Spatial Reuse Scheduling in Underwater Acoustic Communication Networks

2013· article· en· W1965380876 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 Journal of Oceanic Engineering · 2013
Typearticle
Languageen
FieldEngineering
TopicUnderwater Vehicles and Communication Systems
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsNetwork topologyComputer scienceReuseRobustness (evolution)Distributed computingComputer networkScheduling (production processes)Underwater acoustic communicationUnderwaterPropagation delayNetwork packetTopology (electrical circuits)Engineering

Abstract

fetched live from OpenAlex

Resource assignment in underwater acoustic communication (UWAC) networks has recently drawn much attention in the research community. Although in most applications the number of nodes in the UWAC network is relatively small, the long propagation delay of acoustic signals underwater motivates the application of spatial reuse in channel access protocols for throughput enhancement. In this paper, we address the problem of spatial-reuse scheduling in UWAC networks that support frequent transmission of broadcast packets and require robustness to inaccurate topology information. Taking the possibility of outdated network topology information into account is of great importance for UWAC applications due to time-varying topologies in the underwater environment. Our main contribution is the derivation of a broadcast scheduling algorithm that combines topology-transparent and topology-dependent spatial-reuse scheduling methodologies to achieve high throughput in static and dynamic topology scenarios. Simulation results demonstrate that our protocol provides a favorable tradeoff between network throughput and robustness to outdated topology information due to topology changes, and that it also achieves fairness in terms of per-node throughput.

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: Empirical
Teacher disagreement score0.474
Threshold uncertainty score0.665

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.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.001
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.195
Teacher spread0.178 · 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