Skip to content

Merge latest changes from main branch - #828

Open
AndreHauschild wants to merge 154 commits into
devfrom
main
Open

Merge latest changes from main branch#828
AndreHauschild wants to merge 154 commits into
devfrom
main

Conversation

@AndreHauschild

Copy link
Copy Markdown
Collaborator

No description provided.

ourairquality and others added 30 commits April 20, 2026 18:58
It was missing implementations for plots 3 and 4.
preceph: fix code_bias_ix system indexing
rtknavi: fix the track plot expand and shrink for plots 3 and 4
Add BDS to the systems in the default process options
rnx2rtkp: default nav sys to include Galileo and BDS
Common product files are using more that the example 4 lines,
so rework the code to handle this without generating error messages.
It uses the 'flag' to indicated that a clock file is expected and to
handle the format changes in clock files from version 3.04, but could
incorrectly parse the type and system if this expectation was not
met. Rework this to use the flag to bias the search but to fallback to
the alternative if not met.
…and 2 for all constellations if freqs="L1+L2", else use L1/L2 for GLONASS and freq slots 1 and 3 for all other constellations
rtknavi_qt: correct freq change in SNR and sky plots
rtkpost_qt, rtknavi_qt: fix for incorrect target install in CMakeLists.txt
code2bias: guard code being zero, and code_ix not found
readsp3: handle arbitrary comment lines
rinex header: fix clock file system parsing
- Fix field length errors
- Derive IODEs per Beidou ICD
- Add reset of rtksvr structure when starting RTKNAVI as a commented out line, uncommenting this line makes RTKNAVI solutions repeatable when postprocessing data from files.
The standard deviations can be supplied at a lower rate than the clock
biases, e.g. 30 sec biases with 5 minute standard deviations seen in
the CODE precise clock bias products.
satposs() was failing when precise clocks were configured and supplied in only
an sp3 file and without broadcast ephemeris. Rework the code to fix this and
a few related issues noted.

pephclk() - rework to search both the precise clocks and the precise ephemeris
data, giving preference to the precise clocks which are typically at a shorter
period and more accurate. It was searching only the precise clocks and failing
to make use of the satellite clock biases in sp3 files in some paths. Return 0
on all failure return paths, so the caller can test the return value for
success or failure, and rework the callers as necessary.

satposs() use the updated pephclk() to work with only satellite clock biases
in sp3 files, and without broadcast ephemeris to give the satellite clock
bias.

pephpos() correct the returned clock variance which was not being scaled by
CLIGHT to return it in units of m^2. It was effectively only applying the
interpolation variance.

Lower the precise clock extrapolation error from 1mm/s to 0.4mm/s. This gives
a midpoint standard deviation of around 6mm for 30s data and 60mm for 5 minute
data which seems more appropriate for current satellite clocks and still
conservative.
satposs: fix to work with precise clocks from sp3 files
readrnxclk: interpolate the standard deviations
… ppp.c to avoid using wrong macro define for state indices
SSR7 types are in common uses, updated from the tentative
allocation. Allows these to be processed with current SSR streams.

Change SSR7 BDS prn offset of 1 to 0 which appears consistent with
current SSR streams, fixing the BDS PRN mapping.

The SSR7 phase bias standard-deviation field do not appear in current
SSR streams, so remove it. Otherwise the phase biases read as garbage.

The RTCM-SSR and IGS-SSR signal mapping has diverged, so split these
into separate tables. Update these tables with current common signal
mappings.

Include the subtype in trace messages in the ssr code paths.
JensReimann and others added 30 commits June 23, 2026 12:54
… as well as between epochs instead of simple mean of drives
The paths were being pruned down to a name. Want the pruned name but
do not want to destroy the path. This was losing details of paths.
After getting the source table for the mount names, it was splitting
at the new-line which left a trailing carriage return which was then
passed along in the stream path causing issues.
Some casters, such as RTKLIB, do not send all the possible line items
and so some of the table elements were not being filled and this in
turn created trouble for updateMap() when it tries to use these items.

casterTableSelectItem: fix incorrect ref to the streams table which
blocked casters being selected depending on the streams table.
rtknavi GetOpt: copy over posopt6
rtkplot_qt: fix the paths passed to stropen
tcpopedlg qt: trim white space from the STR data
srctblbrows_qt: fill the all the table elements with an item
Avoid using an empty result of file selection which occurs when the
selection is cancelled. So that when a file selection is cancelled then
an existing filename setting is retained.
…es/sec for consistency across constellations and frequencies. Use median doppler instead of mean for offset.

Note that this changes the units for the doppler cycle slip threshold in the config file from cycles/sec to meters/sec
The default was 100 which will not give a lock for most uses. The
libary default is 3 so use that.
…han elevation for better compatibility with urban canyon solutions where SNR may be a better indicator of quality than elevation. Also exclude sats with lock count less than zero from first pass search for reference sat.
… of satellites instead of number of double-differences-1 which was only valid for single frequency solutions. Note that this means the config file values should be adjusted appropriately
qt apps: avoid empty file selections
rtknavi_qt: default navsys to also include GLO, GAL, BDS
rtknavi_qt: default threshold AR to lib defaults
These were being loaded but not saved.
Use 3 decimal places for the error-snr, steps size of 0.001, and
default to 0 - a value of 0.002 to 0.02 would be typical. Default the
SNR max to 52, was 1.

Use 3 decimal places for the baseline error and a step size of 0.001.
An error of 0.010m per 10km baseline would be typical.
which were missing from the user interface.
rtknavi win: write err 4,5,6 to the ini file
rtknavi_qt: for error-snr use the library defaults
rtknavi_qt opts: update doc for rejphase
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants