[teqc] next official version of teqc on-line (2018 Dec 12)

Lou Estey lou at unavco.org
Wed Dec 12 10:11:32 MST 2018


dear All,

The next official version -- 2018Dec12 -- of teqc is on-line:
https://www.unavco.org/software/data-processing/teqc/teqc.html#executables

As usual, save a copy of your previous teqc executable in case there is some unexpected
problem with the new executable.  Again, 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 Oct 15 are given in detail in reverse chronological
order starting at: https://www.unavco.org/software/data-processing/teqc/log/log.html#2018Dec12 --
but here's a brief summary about the main changes between this release and the last one:

- Doing a qc on a raw data file or stream should now be even easier:
	o a default qc window of 24 hours is assumed for qc of a raw data file
	o a default qc window of 30 seconds is assumed for qc of a stream
   And of course either of these default window lengths can be overridden by using one of
   the '+dX' options, e.g. '+dh 12' for 12 hours, '+ds 120' for 120 seconds, '+dm 15' for
   15 minutes, etc.

- All windowing functionality should now be working when doing a qc on a raw data file or
   stream, including the '-ns' and '-ne' options, e.g. the tip of week 2029,
   https://ls.unavco.org/pipermail/teqc/2018/002579.html.

- GPS CNAV/CNAV2 navigation messages, if present and detected, should be _excluded_
   by default from GPS RINEX nav output. (*)

- QZSS CNAV/CNAV2 navigation messages, if present and detected, should be _excluded_
   by default from QZSS RINEX nav output. (*)

- Galileo F/NAV navigation messages, if present and detected, should be _included_
   by default in Galileo RINEX nav output. (*)

- Galileo F/NAV navigation messages, if present, are internally _excluded_ from being used
   in qc point-position solutions, along with not using any pseudoranges from Galileo E5a,
   E5a+b, or E6.

- A new qc '+eepd' option has been added, which is like the '+eepg' option, except '+eepd'
   outputs the geographic coordinates of the qc point-position solutions in decimal degrees.

- New 'Alert' stderr messages have been added for any detected changes in receiver firmware
   or detected changes in model type or number for a receiver or antenna.

- Reading new u-blox UBX-RXM-RAWX (0x1215) "version 1" message has been expanded for
   multi-frequency observations per constellation, plus correction to eliminate phase or
   pseudorange observables from being used if not set to be "valid".

* There are two new options, '-eph' and '+eph' which can be used to change the new default
   behaviour, which is equivalent to '-eph G:CNAV,G:CNAV2,J:CNAV,J:CNAV2'.  For example, to
   also exclude Galileo F/NAV in Galileo RINEX nav output, use '-eph E:F/NAV'.  But it is
   strongly advised not to use '-eph' or '+eph' unless you are quite certain you know what
   you are going, or just want to experiment.  Also, be advised that detection of GPS LNAV
   vs. CNAV/CNAV2, QZSS LNAV vs. CNAV/CNAV2, or Galileo I/NAV vs. F/NAV can potentially be
   problematic.

Currently 2018 Dec 12 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.

cheers,
--lou

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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