Ginan
Loading...
Searching...
No Matches
preprocessorFreqs.cpp File Reference

Functions

bool satFreqs (E_Sys sys, E_FType &ft1, E_FType &ft2, E_FType &ft3)
 Select up to three configured frequency bands for a satellite system.
 
int obsFreqs (const GObs &obs, E_FType &ft1, E_FType &ft2, E_FType &ft3)
 Select observed frequency bands that are usable for slip detection.
 

Function Documentation

◆ obsFreqs()

int obsFreqs ( const GObs & obs,
E_FType & ft1,
E_FType & ft2,
E_FType & ft3 )

Select observed frequency bands that are usable for slip detection.

This helper is intentionally stricter than satFreqs(): it still honours configured code priorities, but only returns frequency bands that are present in the current observation, have a non-zero representative phase measurement, and have a non-zero wavelength available in the satellite navigation data.

The selector returns the first three distinct usable frequencies only. Extra usable frequencies later in code_priorities are left for future 4+ frequency processing rather than silently changing the current dual/triple frequency slip-detection model.

Here is the caller graph for this function:

◆ satFreqs()

bool satFreqs ( E_Sys sys,
E_FType & ft1,
E_FType & ft2,
E_FType & ft3 )

Select up to three configured frequency bands for a satellite system.

This is the legacy frequency selector used by several modelling paths outside slip detection. It follows acsConfig.code_priorities[sys] and converts the first unique codes into frequency bands, but it does not inspect a particular observation to confirm that measurements are present.

The outputs retain historical defaults (F1, F2, F5) when priorities are incomplete. Do not use this helper when the algorithm must know which frequencies are actually observed at the current epoch; use obsFreqs() for slip detection.

Here is the caller graph for this function: