Determination and analysis of front-end and correlator-spacing-induced biases for code and carrier phase observations
Bibliographic record
Abstract
Abstract Global navigation satellite system (GNSS) biases preclude integer ambiguity resolution and degrade positioning accuracy if they are not corrected in GNSS precise applications. Biases in GNSS positioning applications occur because of imperfections and physical limitations in satellite and receiver hardware. Consequently, these biases will affect the accuracy of positioning solutions, particularly for precise applications due to the existence of biases in the code and carrier phase observations. Various types of biases between systems, frequencies, and satellites have been defined and analyzed. In addition, receiver biases are often assumed to be eliminated by differencing observations between satellites, although this is not always true. This paper investigates the determination of the receiver front-end and correlator-spacing-induced biases in code and carrier phase observations with a focus on how receiver front-end and correlator spacing affect the code and carrier phase measurements, and how such biases vary with respect to the use of different correlator spacings and frontends. Firstly, oscillator, front-end chip, and ADC-induced biases, as well as their observability, will be discussed. Several groups of datasets with different frontends have been collected and used to determine the inter-front-end (including oscillator, chip, and ADC) pseudorange and carrier phase biases. Then, a software receiver that allows the tracking of a satellite with a series of different correlator spacings has been developed to assess measurement biases with different datasets. The results show that the inter-front-end biases and correlator-spacing-induced biases are significantly different among satellites, which can not be ignored during the GNSS positioning. This is because the single-difference of measurements between satellites can not eliminate all these biases. The results with the software receiver connected to different frontends and different correlator spacings indicate that the satellite-dependent biases depend on the configuration of the in-receiver hardware and software.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".