Real-Time Coseismic Displacement Retrieval Based on Temporal Point Positioning with IGS RTS Correction Products
Bibliographic record
Abstract
With the rapid development of the global navigation satellite system (GNSS), high-rate GNSS has been widely used for high-precision GNSS coseismic displacement retrieval. In recent decades, relative positioning (RP) and precise point positioning (PPP) are mainly adopted to retrieve coseismic displacements. However, RP can only obtain relative coseismic displacements with respect to a reference station, which might be subject to quaking during a large seismic event. While PPP needs a long (re)convergence period of tens of minutes. There is no convergence time needed in the variometric approach for displacements analysis standalone engine (VADASE) but the derived displacements are accompanied by a drift. Temporal point positioning (TPP) method adopts temporal-differenced ionosphere-free phase measurements between a reference epoch and the current epoch, and there is almost no drift in the displacement derived from TPP method. Nevertheless, the precise orbit and clock products should be applied in the TPP method. The studies in recent years are almost based on the postprocessing precise orbits and clocks or simulated real-time products. Since 2013, international GNSS service (IGS) has been providing an open-access real-time service (RTS), which consists of orbit, clock and other corrections. In this contribution, we evaluated the performance of real-time coseismic displacement retrieval based on TPP method with IGS RTS correction products. At first, the real-time precise orbit and clock offsets are derived from the RTS correction products. Then, the temporal-differenced ionosphere-free (IF) combinations are formed and adopted as the TPP measurements. By applying real-time precise orbit and clock offsets, the coseismic displacement can be real-timely retrieved based on TPP measurements. To evaluate the accuracy, two experiments including a stationary experiment and an application to an earthquake event were carried out. The former gives an accuracy of 1.8 cm in the horizontal direction and 4.1 cm in the vertical direction during the whole period of 15-min. The latter gives an accuracy of 1.2 cm and 2.4 cm in the horizontal and vertical components, respectively.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| 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 teacher head, 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".