Measurement ID and Cluster ID are erroneously reported when "--output-adj-gnss-units 1" is provided to adjust.exe

[nicgowans]

Description When adjust.exe is run with options --output-database-ids and --output-adj-gnss-units 1 erroneous data is reported in the Measurement Id and Cluster Id columns of the *.adj file.

The behaviour is inconsistent, and individual calls to adjust.exe will produce varying results (see screenshots 2 and 3).

Steps to reproduce To reproduce the unexpected behaviour:

1. Import msr file (and associated stn file) with type G measurements and database ids.
2. Execute adjust.exe and provide the following options: --output-adj-msr, --output-database-ids, and --output-adj-gnss-units 1
3. Open the output file *.adj file
4. Review Meas. ID and Clust. ID columns

Expected behaviour Meas. ID and Clust. ID data should be printed similar to when --output-adj-gnss-units 0 is provided, e.g. (see first screenshot below)

Screenshots Correct behaviour when adjust.exe is run with --output-adj-gnss-units 0

Erroneous reporting when adjust.exe is run with --output-adj-gnss-units 1:

Erroneous reporting when adjust.exe is run with --output-adj-gnss-units 1. Second example on the same input data - note inconsistent output in Meas. ID and Clust. ID columns:

Operating system

• Windows 10
  • DynAdjust version 1.2.7, Release (64-bit)
  • DynAdjust build Mar 29 2023, 10:01:09 (MSVC++ 1935)