Add BOC-aware lock detection and E1C-aided tracking
This commit is contained in:
@@ -25,4 +25,16 @@ Default YAML files:
|
||||
- `e1_default.yaml`: requested 16.368 MHz nominal defaults.
|
||||
- `acquisition_example.yaml`: faster 4.092 MHz executable search.
|
||||
- `tracking_example.yaml`: 4.092 MHz tracking defaults.
|
||||
- `navigation_collection.yaml`: SignalSim IQ-to-I/NAV regression. Its default
|
||||
`tracking.architecture` is `e1c_pilot_aided_e1b`; the CLI can select
|
||||
`e1b_only` for an A/B replay.
|
||||
|
||||
The BOC lock detector parameters are part of `TrackingConfig`. The defaults use
|
||||
25 noncoherent power epochs, three confirmations, and the configured
|
||||
`loss_of_lock_epochs` for sustained failure. Carrier and BOC central/outer
|
||||
shape thresholds have explicit entry and exit values. `lock_signal_loss_power_ratio`
|
||||
sets the five-tap power loss test. These parameters affect monitoring and
|
||||
reacquisition only; they do not change discriminator or loop-filter coefficients.
|
||||
`boc_side_peak_coherence_enter/exit` calibrate the coherent E/L-to-P tap-sign
|
||||
test needed to distinguish the negative half-chip BOC sidelobe from the main
|
||||
peak using more than magnitude-only information.
|
||||
|
||||
Reference in New Issue
Block a user