Bibliographic record
Abstract
Integer ambiguity resolution of carrier-phase measurements from a single receiver can be implemented by applying additional satellite products to mitigate the unmodeled satellite hardware delay. Interoperability of different PPP-AR products would allow the PPP user to transform independently generated PPP-AR products to obtain multiple fixed solutions of comparable precision and accuracy with limited changes required to the core PPP software. The ability to provide multiple solutions would increase the reliability of the solution for, e.g., real-time processing; if there were an outage in the generation of one set of PPP-AR products, the user could instantly switch streams to a different provider. There are currently three main public providers of real-time products that enable PPP-AR. These included Scripps Institution of Oceanography, Natural Resources Canada and Centre national d'etudes spatiales. The research presented examines the PPP-AR products generated from the FCB (Fractional Cycle Bias) and IRC (Integer Receover Clock) model that have been transformed into the DC (Decoupled Clock) format and applied within the PPP user solution. The novelty of the research is the solution analysis using the transformed product. The convergence time (time to first fix and time to a pre-defined performance level), position precision (repeatability), position accuracy and solution outliers are examined. The temporal and spatial behaviour of these estimated terms are examined for the different products applied to understand the unmodeled effects that introduce incorrect solution fixes. Unlike the fixed solution using the DC products, instantaneous convergence was not attained in the horizontal and vertical component when the transformed IRC and FCB products were utilized. In the horizontal component, the transformed IRC product took 10 minutes to attain the predefined threshold while the FCB product took 31 minutes in the horizontal component. A steady state was never attained, as jumps in the solution occurred at frequent intervals. The transformed IRC product had solution jumps every 15 minutes and the transformed FCB products had jumps in the solution every 30 to 45 minutes. The unstable solution from both transformed products are attributed to the magnitude of transformed products, as they were sub-nanoseconds in magnitude, whereas the DC products were few nanoseconds in magnitude.
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.008 | 0.033 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.002 | 0.003 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
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".