Energy Filament Theory · EFT Full KB
Day–Night Difference Test for Multi-Frequency Link Path Redshift in Near-Earth Spacecraft
V33-33.44 · F 证据节 / 显影节 ·
33.44 turns near-Earth spacecraft links into a retainable day–night path-redshift audit: after a shared time and frequency reference, a shared bandpass kernel, explicit 1/f² dispersion removal, troposphere / multipath / thermal stripping, and one-way versus two-way endpoint separation, residuals must recover the same-sign constant offset or slow slope between day-side and night-side windows across S-band, X-band, and Ka-band links, co-occur at effectively zero lag across stations and pipelines, keep frequency-to-frequency ratios stable while absolute baselines shift, and be hit feed-forward by geometry and environment cards; under V08/V09-compatible retain, this stays one near-Earth propagation-path repair ledger inside the TPR / PER redshift lane rather than a replacement redshift first cause.
Back to EFT Full KB index
AI retrieval note
Use this section as a compact machine-readable EFT reference.
Keywords: day–night path redshift, one-way versus two-way, S-band, X-band, Ka-band, 1/f² dispersion, TEC, PWV, zero-lag co-occurrence, solar zenith angle, Kp, Dst, shared time–frequency aperture
Section knowledge units
thesis
33.44 begins by refusing the easy mistake of confusing a familiar day–night engineering contrast with the specific object it wants to audit. Raw carrier phase, group delay, and Doppler all mix geometric, atmospheric, dispersive, multipath, and thermal effects. The chapter therefore asks a narrower question: after multi-frequency and one-way versus two-way constraints strip those known accounts as far as practical, does one nearly non-dispersive day–night common term remain? If it exists, it should appear not as a random anomaly but as one engineering fingerprint: an overall baseline shift between day-side and night-side windows while frequency-to-frequency ratios stay stable. Under compat adjudication, that fingerprint is retainable only as a near-Earth propagation-path repair ledger inside the TPR / PER lane, not as a substitute for the whole redshift case.
mechanism
The measurement court is six-fold. It extracts a constant offset and a slow slope from residual frequency offset, group delay, and phase; compares day-side and night-side arcs by orbit class, band, station, pipeline, and solar-zenith window; demands cross-frequency non-dispersive stability rather than 1/f² leakage; searches for zero-lag same-direction jumps or plateaus across bands and stations; grades geometry and environment structure against solar zenith angle, pierce-point coordinates, TEC, PWV, Kp, and Dst; and finally checks the signature 'overall shift with ratios unchanged.' One-way versus two-way combinations are part of the measurement itself, because they decide whether the residual belongs mainly to the propagation path or to endpoint oscillators and thermal-state ledgers.
mechanism
Execution is intentionally heavy. The chapter wants LEO, MEO, GEO, and related orbit classes, multiple stations with different latitudes and altitudes, and at least two effectively orthogonal pipelines. Each arc must cover long day–night transitions across seasons and geomagnetic regimes. Frequency standards, time standards, and timestamp ledgers are unified and published; ionosphere, troposphere, multipath, and thermal-state models are frozen with explicit holdouts; day-side, night-side, twilight, high-elevation, low-elevation, ocean, inland, summer, and winter windows are preregistered; and a feed-forward team, a blinded measurement team, and an arbitration team are separated. The point is to make any surviving day–night common term walk through the whole engineering gauntlet rather than slip through one favorite pipeline.
evidence
The positive case requires same-direction, similar-magnitude, non-dispersive day–night structure across multiple bands, stations, and pipelines, plus near-orthogonality to endpoint oscillator drift and feed-forward hits from geometry and environment cards. The negative case is equally explicit: if residuals scale like dispersion, track TEC or wet-delay template residuals, appear only in one band or one station, or survive label permutation, time reversal, method swapping, or parameter scrambling, the court must treat the effect as selection bias or method artifact. Low-elevation cuts, stronger ionospheric and tropospheric constraints, and thermal regressions are not optional cosmetics. They are destructive tests designed to force false day–night terms back into atmosphere, scene, or device ledgers.
boundary
The pass line is demanding: at least two pipelines, two stations, two frequency bands, multiple orbit classes, and multiple seasons must reproduce a non-dispersive day–night difference with zero-lag co-occurrence, geometry/environment morphology, and arbitration hit rates above randomized baselines. The result must stay robust to bandpass, alignment, window, detrending, template-family, elevation, and thermal-regression variants. Failure is declared as soon as dispersive leakage, wet-delay uncertainty, multipath, or thermal coupling can explain the residual as well as or better than a path-redshift common term. The systematics ledger is named, not hidden: rapid ionospheric disturbances, low-elevation wet-delay plus ground-scene multipath, and coupling between thermal state and oscillator drift are the three big routes that must absorb the signal first.
interface
So 33.44 closes one specific court and nothing more. If the same-sign day–night common term survives cross-band, cross-station, cross-pipeline, and holdout pressure, then V33 keeps one near-Earth propagation-path repair ledger inside the redshift audit chain. That ledger sharpens the path-side grammar handed to later timing chapters because it proves that a near-field engineering scene can preserve a non-dispersive common term after explicit one-way versus two-way separation. But if the effect follows dispersion, wet delay, multipath, thermal drift, or processing choices, the chapter sends the case back to engineering ledgers and publishes only an upper bound before 33.45 takes over the multi-baseline timing court.