[teqc] next official version of teqc on-line (2018 Oct 15)

Lou Estey lou at unavco.org
Mon Oct 15 09:36:03 MDT 2018

dear All,

The next official version -- 2018Oct15 -- of teqc is on-line:

As usual, save a copy of your previous teqc executable in case there is some unexpected
problem with the new executable.  However, I _strongly_ encourage everyone to download
this new version, try it out, and promptly report anything which you think is a bug or
error.  (You may want to review https://postal.unavco.org/pipermail/teqc/2016/002187.html.)

The main changes and fixes since 2018 June 8 are given in detail in reverse chronological
order starting at: http://www.unavco.org/software/data-processing/teqc/log/log.html#2018Oct15 --
but here's a brief summary about the main changes between this release and the last one:

- For all functionality: the upper SV count limit per epoch was increased from 64 to 96.

- Although labeled as "experimental" in the log, you should be able to do a qc full on
any raw data file that teqc can read -- thus avoiding an intermediate translation to
RINEX and doing a qc full on that RINEX.  The only extra command line parameter(s) that
need to be included are one or more options to tell teqc the time window of interest of the
input data for the qc, e.g. see https://postal.unavco.org/pipermail/teqc/2016/002159.html.
Thus, to qc 24 hours of raw data, include you will need to include '+dd 1', or '+dh 24',
or '+dm 1440', etc.  Because of the order of reading ephemerides in the raw data, the
qc results will usually not be 100% identical to a translation to RINEX and qc on that
RINEX, but the results should be very close, probably at the 99.9% level.  Doing a qc
on raw data also automatically sets '+all', so you will see a qc on all constellations
and all signals of those constellations that are in the raw data input being used.  Keep
in mind that when doing a qc on raw data, teqc is also doing a read and internal "translation" --
so it's also a full translation step under the hood and any special translation options
that you were also using will probably be needed as well.  (BTW, Freddy Blume, here at
UNAVCO, came to my office in person and told me that this new functionality is the
best thing since sliced bread. :)

- For qc:  A new SSN summary line shows signal-to-noise means for the various S* observables.

- For qc:  New '-pos_h_min' and '-pos_h_min' options, with default values of -500 meters
and 9000 meters respectively, the values of which are used in find_position() to eliminate
physically unrealistic solutions based on the ellipsoid height of the solution.  (The defaults
are good for point-position solutions on or very near the surface of the solid Earth.
If doing qc of data, say, from high-elevation aircraft or from space observations, these
options with appropriate values will need be used.)

- For qc:  Correction of qc counter dimensions and associated initialization loops, which
fixes problems where nonsensical loss-of-lock counts could show up for one or more SVs
in the qc report.

- For translation:  The separation of GPS L1C/A vs L1P(Y)/L2C vs L2P(Y) from GLONASS
G1SA vs G1HA/G2SA vs G2HAis essentially complete with two new options '±SA_G1' and '±SA_G2',
for GLONASS only, which are analogous to the original '±CA_L1' and '±L2C_L2' options,
the latter options now for GPS only.  (The only formats only partially tackled for this
separation are those use by Ashtech receivers: the B/E/S/D filesets, MBEN/MBN stream format,
R-file format, and U-file format.)

- Using documentation provided by Trimble, the receiver and antenna IDs used by Trimble
formats have been updated in the code to output the IGS standard names in translated
RINEX headers and the '+meta' output through to the latest Trimble receivers and antennae.

- For translation:  Using documentation provided by Trimble and personal communication with
Trimble, an updated parsing of their streamed "RT27" (0x57 records) has been implemented,
which allows a larger number of GNSS SVs (approx > 60) and their observables to be included
in each epoch of streamed data, and additionally provides a more robust 0x57 page grouping
when the RT27 stream is being transmitted in lossy environments.

- For translation:  From personal communication with Trimble, a clarification on the
assignments of the broadcast group delays in the Galileo navigation messages has been
resolved when reading decoded Galileo nav messages in Trimble .tgd record 28 or in
streamed 0x55.

Currently 2018 Oct 15 builds for Allwinner H5 ARM 64-bit processor are not yet available,
but hopefully will be soon.  I'll keep you informed.

As with several past versions, some builds are no longer available with this release:

- any HP-UX builds
- the 32-bit Borland build for Windows; instead, use the Mingw-32 or Mingw-64 bit builds
- the Mac OSX i5 gcc 4.2 64-bit build; instead, use the OSX i5 gcc 4.3 64-bit build
- Solaris Sparc 5.9 builds

If you have any questions, please let me know.


Louis H. Estey, Ph.D.              office:  [+001] 303-381-7456
UNAVCO, 6350 Nautilus Drive           FAX:  [+001] 303-381-7451
Boulder, CO  80301-5554            e-mail:  lou  unavco.org

"If the universe is the answer, what is the question?"
                                                -- Leon Lederman

More information about the teqc mailing list