Release date: 2022-10-23


Earlier bug fixes have already been applied in the previous release.

Below is the list of all bug fixes and improvements for this release before the next release was created.

The update file containing all these fixes is available for Unix/Linux and for Windows. You will need a username and a password to access these files. Please use the update procedure to obtain the access information.

Executables for Windows systems are only available for the latest release.

If you run into a problem, please contact us.




B_00: Bug


Date: 15-Dec-2022


Description: CCRNXO in mode 'Concatenate files, any naming convention' did not consider the output file name given by the panel option BSWOUT.


Affected platforms: All platforms




B_01: Bug


Date: 25-Jan-2023


Description: Solve several issues regarding error reporting, reading and writing of antenna azimuth corrections from the station information file into the SINEX result file.


Affected platforms: All platforms




B_02: Improvement


Date: 10-Feb-2023


Description: The deletion file from RESCHK starts with blank characters. They make the deletion in the BPE script more complex than needed. They are not written anymore.


Affected platforms: All platforms




B_03: Bug


Date: 16-Feb-2023


Description: If the measurements on all frequencies have been deleted subsequent GPSEST runs will fail. This happens for instance when executing PPP with enabled options for "Ignore measurements with antenna calib. method" in RXOBV3.


Affected platforms: All platforms




B_04: Bug


Date: 24-Feb-2023


Description: Troposphere SINEX result file, version 2.0, do not report the used "OCEAN TIDE LOADING MODEL" filename.


Affected platforms: All platforms


Remarks: We are grateful to Christina Kempe from Lantmäteriet, Sweden for pointing us to this problem.




B_05: Bug


Date: 01-Mar-2023


Description: ATX2PCV: The "Special Missing Value Handling" request may not be handled correctly for the first receiver antenna if no input PCV file is provided.


Affected platforms: All platforms




B_06: Bug


Date: 15-May-2023


Description: Potential illegal array access when long station IDs are extracted. It depends on the compiler and operating system whether and how this error appears.


Affected platforms: All platforms




B_07: Bug


Date: 12-May-2023


Description: Ambiguity resolution strategy (Sigma) bug: Wrong fixes w.r.t. reference ambiguity may have effects in the decimeter range.


Affected platforms: All platforms


Remarks: We are grateful to Christina Kempe from Lantmäteriet, Sweden for providing example data sets demonstrating this problem.




B_08: Bug


Date: 12-May-2023


Description: If an OSB file does not contain a satellite number the reading was not done in an appropriate way (effect ranges between no correction and segmentation fault, depending on the compiler). Apart from the improvement of the reading, a message is issued if a requested bias type is not provided.


Affected platforms: All platforms




B_09: Improvement


Date: 12-May-2023


Description: Consider a time window when importing Bias SINEX into Bernese OSB format.


Affected platforms: All platforms




B_10: Bug


Date: 12-May-2023


Description: The copy scripts responsible to get product files from the DATAPOOL area into the campaign were not able to handle ION files with long file names. This concerns the PPP.PCF, RNX2SNX.PCF, CLKDET.PCF and the IONDET.PCF.


Affected platforms: All platforms




B_11: Bug


Date: 15-Jun-2023


Description: Receiver antenna azimuth reporting in the SINEX file might change horizontal antenna offsets in the GPS_PHASE_CENTER-block


Affected platforms: All platforms


Remarks: We are grateful to Tomasz Liwosz of the Warsaw University of Technology for providing his detailed analysis of this issue.




B_12: Bug


Date: 15-Jun-2023


Description: Read the receiver antenna misalignment from a SINEX file; allow for lower case site codes.


Affected platforms: All platforms


Remarks: We are grateful to Tomasz Liwosz of the Warsaw University of Technology for providing his detailed analysis of this issue.




B_13: Bug


Date: 15-Jun-2023


Description: The potential output files in the subsequent parallel script are not deleted (residual screening step in RNX2SNX example).


Affected platforms: All platforms


Remarks: We are grateful to Tomasz Liwosz of the Warsaw University of Technology for providing his detailed analysis of this issue.




B_14: Bug


Date: 21-Jun-2023


Description: Some initial values in the panels of CCRNXN and RXN2PRE are missing. The programs crash therefore.


Affected platforms: All platforms




B_15: Bug


Date: 22-Jun-2023


Description: For some ground based stations with empty or non-present RINEX header entry MARKER TYPE, the program CCRNXO was erronously setting MARKER TYPE to LIKELY SPACEBORN.


Affected platforms: All platforms




B_16: Bug


Date: 24-Jul-2023


Description: Ambiguity resolution strategy (Sigma): add STONEX (STO) receiver group. Request from C. Voelksen.


Affected platforms: All platforms




B_17: Bug


Date: 04-Oct-2023


Description: Ambiguity resolution bug (using SIGMA, especially on short baselines). Fixing under difficult observation scenario improved, logic and book keeping for introducing later on L1, L2 ambiguites in L3 improved. Introducing receiver types STO, CHC, SPE.


Affected platforms: All platforms


Remarks: We are grateful to Mike Piraszewski (Natural Resources Canada) and Christina Kempe (Lantmäteriet, Sweden) for providing example data sets demonstrating this problem.




B_018: Improvement


Date: 10-Oct-2023


Description: More flexibility when identifying the 9-chr ID when writing troposphere SINEX file (version 2.00)


Affected platforms: All platforms




B_019: Improvement


Date: 16-Oct-2023


Description: Add a new option to the RINEX tools to limit the data import to dual-frequency GPS and GLONASS measurements when importing data from RINEX2.


Affected platforms: All platforms

 


















Quick Links

Back to support