Changeset 11212 in ntrip for trunk/BNC/CHANGELOG.md
- Timestamp:
- Nov 18, 2026, 12:25:58 PM (3 days ago)
- File:
-
- 1 edited
-
trunk/BNC/CHANGELOG.md (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/CHANGELOG.md
r11206 r11212 1 1 # Changelog 2 ## 2.13.9 (unreleased) 3 - ADDED: **SSR QC: phase bias indicators and Melbourne-Wuebbena check.** Per stream and system the SSR format, the dispersive bias and MW consistency indicators, the integer and wide-lane integer indicators per signal and the satellites with discontinuity counter changes are reported. Every 300 s the MW combination of the phase and code biases of the reference signals (wide-lane cycles) is differenced with that of each other AC; the RMS of the fractional parts about the common offset shows whether the wide-lane biases are consistent (< 0.10 cycles) as required for a PPP-AR combination. 2 Oct 2026: MW consistency indicator 1 only for CNES and NRCan, CNES vs NRCan GPS 0.14 cycles (single satellites up to 0.3), all other pairs ~0.25 cycles (random). New test case ssr_qc_phase_bias 4 - CHANGED: **Combination (Kalman filter): robust clock datum.** Per satellite, the satellite-specific clock difference of each AC referred to the reference signals is compared with the median of the ACs; an offset rejected as outlier for 60 s leaves the zero-sum conditions and absorbs the difference (any number of ACs, as long as another offset of the satellite stays in), with at least 3 ACs also an offset deviating by more than 'Maximal Residuum' (at most 0.5 m) for 60 s (largest deviations first, a majority of the ACs stays in); it rejoins after a deviation below half of the threshold without rejection for 10 min. During a data gap of an AC in the datum of a satellite (or if its correction is rejected), the sum of the present offsets is kept, so that the gap does not shift the combined clock; offsets out of the datum never define it. Before, such a difference either shifted the combined clock or the corrections were rejected in every epoch (outlier lock-in), depending on when the filter was started (e.g. SHA G26 2.4 m). Changes are logged, offsets out of the datum are listed in the hourly outlier report. Start-time test (7 ACs, start 2.5 min later): GPS max. difference 2.4 m -> 0.08 m 5 - CHANGED: Combination: an AC excluded from the clock datum again because of inconsistent code biases needs twice as many passing checks to be used again as the time before (1, 2, 4, ... up to 16 hours); each change of the datum shifts the combined clocks of the system (GMV00 BDS 15 Oct: excluded 08:40, used again 18:00, excluded 18:05) 6 - FIXED: Combination (Kalman filter): the zero-sum conditions of the satellite offsets constrained the increments of the epoch instead of the values: after a change of the offsets in a condition (e.g. a satellite no longer provided by an AC) the sum kept its previous, non-zero value, so that the clock datum depended on the history of the filter 2 7 ## 2.13.8 (2026-11-13) 3 8 - FIXED: RINEX 3/4 observation files: MARKER NAME was cut to 9 characters (A60 in RINEX 3/4); RINEX 2 keeps the 4-character station ID, the marker name derived from the stream name in real-time RINEX files stays 9 characters (e.g. WTZR00DEU)
Note:
See TracChangeset
for help on using the changeset viewer.
