Backend
When Does Risk-Controlled Throughput Forecasting Actually Control Risk? A Reproduction Study on LEO Satellite Link
arXiv cs.NI0 views
arXiv:2611.06307v1 Announce Type: cross Abstract: Risk-budgeted throughput forecasting converts a point forecast of LEO satellite capacity into a conservative bound whose overestimation rate is held at a user-specified budget, so that admission control can act on it safely. We reproduce the state of the art, BG-CFQS, on the three Starlink traces its authors used and on an independent fourth dataset, and report four findings. First, its risk guarantee is reproducible but conditional on the calibration split: under a random split we recover every published quantity, including risk-pass on 3 of 3 datasets, but under a contiguous temporal split, which is what a deployed terminal faces, it holds on 1 of 3. Second, independent of any split, the method cannot serve a risk budget below 0.15, the low end of its candidate quantile set. On all four datasets the achieved rate is identical at budgets of 0.05, 0.10 and 0.15, overshooting by 1.4x to 3.7x at the tightest. Third, static conformal calibration cannot improve a ranking, only shift an operating point; we confirm this exactly on latency spike detection, where online calibration improves AUPRC by up to 51%. Fourth, group-conditional online recalibration splits into two mechanisms. The online part replicates: it tracks the budget within 1% from 0.05 to 0.35, where static calibration is 16 to 21% off. The group-conditional part does not: on three of four datasets, conditioning on any available covariate, including measured serving-satellite geometry, is worse than not conditioning, and our attempt to predict which datasets benefit failed. What is new here is empirical, not algorithmic: we claim the findings, not the methods.
Source:https://arxiv.org/abs/2611.06307PreviousSpatial Path Superposition: A No-Cloning Perspective on MIMO-Inspired Spatial DiversityNextFrom Network Experience to Subscriber Retention: An Explainable AI Framework for Mobile Operators
Related posts
How to let Claude Code and Codex talk directly across two computers without copy-pasting logs
0dev.to
Why Is There a Delay When I’m Typing? (I Tested the Bottlenecks So You Don’t Have To)
0dev.to

Moving City GIS Into Unreal Engine: Coordinate Systems, LOD, and the Boring Parts
0dev.to
My AI Agent Said 'Done.' It Wasn't. A Field Guide to Trusting Nothing an Agent Tells You
0dev.to
Bridging Context and Execution: An Engineering Assessment of Connected AI Workflows
0dev.to
把 AI CLI 包成 OpenAI 相容 API:從 stdin、JSON 輸出到逾時處理(附可跑範例)
0dev.to