Backend
Placing the Beamspace Window on a Hopping Carrier: Bin Drift, Exact Capture and the Cost of Rounding
arXiv eess.SP0 views
arXiv:2610.37067v1 Announce Type: new Abstract: A frequency-agile radar with a large digital array moves the spatial frequency of its look direction across the beams of a spatial FFT every time it changes carrier, so a beamspace adaptive processor must decide where to put its window at each hop. Because the beamspace transform is orthonormal, the output of the processor depends only on the span of the window, and a hop changes nothing but where the window sits. Centring the window exactly on the fractional bin of the look direction keeps the look vector fully inside it at every carrier, for the price of one phase ramp before the FFT. On a 32 by 32 array over 4 to 8 GHz the look bin drifts by 1.6 to 6.9 bins for look directions from u=0.2 to 60 degrees. Rounding to the nearest bin costs up to 1.34, 0.74 and 0.50 dB of look-direction capture for 3 by 3, 5 by 5 and 7 by 7 windows. In a three-jammer scenario with 41 carriers, a window frozen at the lowest carrier loses 39 to 60 dB at the worst carrier for a look direction of u=0.55, the exact window beats nearest-bin placement by 0.31 to 0.65 dB there, and the advantage reverses for a nine-beam window near broadside, where nearest-bin was 0.61 dB better.
Source:https://arxiv.org/abs/2610.37067PreviousA Wearable Sensor Array on Conductive Textiles for Body Surface Temperature MappingNextOrthogonal Zadoff-Chu Based Pilot Design For Fractional Channel Estimation in MIMO-OTFS
Related posts
FiveM Script Database Migrations: What to Check Before You Install
0dev.to
The insurance edge case that breaks event-driven policy pipelines
0dev.to
The fix for an empty state isn't filling it
0dev.to UX
Five Things That Make Dependabot Painful for Terraform
0dev.to GitHub
Tracking Roblox player counts: what the public data actually gives you
0dev.to Data
Telegram gold signals this week: results to Oct 30
0dev.to Data