Release date: 2013-07-18
Earlier bug fixes have already been applied in the previous release.
Below is the list of all available bug fixes and improvements for this
release.
If you run into a problem, please
contact us.
B_026: Compilerbug
Date: 31-Jul-2013
Description: Users with ifort version 12.0 could not compile the program ATX2PCV.
Affected platforms: Unix/Linux
B_027: Bug
Date: 06-Sep-2013
Description: Coordinates from a clock RINEX file cannot be read if a coordinate component is below 1 meter.
Affected platforms: All platforms
B_028: Bug
Date: 16-Sep-2013
Description: Resolved ambiguities are not correctly displayed in the pseudo graphics.
Affected platforms: All platforms
B_029: Bug
Date: 18-Sep-2013
Description: There were missing line-break characters in the source code of ROCKMD.f.
Affected platforms: All platforms
Remark: This bug has been reported by Johannes M. Fritzer (University of Graz) using the NAG Fortran Compiler 5.3 on a Linux computer.
B_030: Bug
Date: 13-Oct-2014
Description: "Coordinate summary" provided by GPSXTR is incorrect with respect to "DHT" results.
Affected platforms: All platforms
B_031: Bug
Date: 14-Oct-2014
Description: Biased degree of freedom for GPSEST computations with stochastic ionosphere parameters without elimination of reference ionosphere parameters (commonly for QIF ambiguity resolution). The direct consequence is a biased a posteriori rms of unit weight (and proportionately biased rms information for all involved parameters).
Affected platforms: All platforms
B_032: Bug
Date: 27-Oct-2014
Description: RINEX3.02 header label "GLONASS COD/PHS/BIS " unknown.
Affected platforms: All platforms
B_33: Bug
Date: 11-Nov-2014
Description: Wrong format in the warning message if huge numbers are reported for the "big O-C values" by MAUPRP.
Affected platforms: All platforms
B_034: Bug
Date: 19-Nov-2014
Description: If the formal errors for a specific satellite are too small, the resported accuracy code is set to zero (what means suspicious satellite).
Affected platforms: All platforms
B_035: Bug
Date: 24-Nov-2014
Description: GPSEST failure indicated by SR QITPOL: ARGUMENT OUT OF RANGE.
Affected platforms: All platforms
B_036: Bug
Date: 25-Nov-2014
Description: Apply paramter renaming in ADDNEQ2 consistently to the parameter removal for piece-wise linear parameter (consider left and right boundary).
Affected platforms: All platforms
B_037: Improvement
Date: 25-Nov-2014
Description: If satellites are excluded from the processing in CODSPP due to missing orbits or satellite clock or due to an entry in the satellite problem file, they are not counted as "bad satellites" anymore in the statistics provided by the program output (and analysed by CODXTR).
Affected platforms: All platforms
B_038: Improvement
Date: 25-Nov-2014
Description: Check consistency regarding zero- and double-difference processing in RESCHK with respect to the introduced residual summary table.
Affected platforms: All platforms
B_039: Bug
Date: 01-Dec-2014
Description: The verification of available GNSS in the zero-difference observation files in the program SNGDIF only depends on the availability of the last satellite per system.
Affected platforms: All platforms
Remark: We are grateful to Yuki Hatanaka from Geospatial Information Authority of Japan (GSI) for pointing us to this problem and for providing his solution.
B_040: Improvement
Date: 03-Dec-2014
Description: Dimension of all RINEX2 file types are handled in one place.
Affected platforms: All platforms
B_041: Improvement
Date: 04-Dec-2014
Description: The criteria to select RINEX observation files in RNXGRA may now be autmatically adjusted according to the length of the data to be processed. The same input values may now be used for daily and hourly processing schemes because they may now automatically be adjusted.
Affected platforms: All platforms
Remark: If you have already adjusted your RINEX file selection criteria for an hourly processing scheme you must disable the new option "Normalize limits for non-daily session processing" in panel RNXGRA 3 (per default it is set for adjusting the values in the input field).
B_042: Bug
Date: 05-Dec-2014
Description: If an ORBGEN is asking for an entry in the radiation pressure section of the satellite information file that is not available (what should of course not happen) some illegal memory access happen (with unpredictable consequences).
Affected platforms: All platforms
B_043: Bug
Date: 12-Dec-2014
Description: Deactivate the GNSS satellite clock field if baseline observation files are processed.
Affected platforms: All platforms
B_044: Bug
Date: 27-Dec-2014
Description: Strong relative constraints specified in the station information file (TYPE 004) are reported as zero in the ADDNEQ2 program output.
Affected platforms: All platforms
B_045: Improvement
Date: 27-Dec-2014
Description: Consequently allow for four digits to identify a normal equation input file in ADDNEQ2.
Affected platforms: All platforms
B_046: Improvement
Date: 27-Dec-2014
Description: Increase several arrays.
Affected platforms: All platforms
B_047: Improvement
Date: 27-Dec-2014
Description: Add calibration method "FIXED"
Affected platforms: All platforms
B_048: Bug
Date: 27-Dec-2014
Description: Init new antenna number consistently with ATX2PCV
Affected platforms: All platforms
B_049: Improvement
Date: 09-Jan-2015
Description: New Empirical CODE Orbit Model (ECOM) has been implemented and used by CODE for operational IGS products since January 2015. Affected program: ORBGEN.
Affected platforms: All platforms
Remarks:
- After updating the software you may choose the new model by selecting "dynamical orbit parameters" as "D2X" (instead of "DYX") in panel ORBGEN 3.1: Options.
- The new orbit model (activated with "D2X") can even be used to fit precise files generated with the traditional ECOM.
- Please have a look into the BSW mail No. 334 for more details on this model and software change.
Quick Links