[teqc] -tbin option intermittently removing comments from second and subsequent obs files

Lou Estey lou at unavco.org
Thu Jul 14 08:54:17 MDT 2016


All indications are that both of the problems that Neville Palmer (GNS, New Zealand) was
seeing when creating RINEX using the '-tbin' option:

1) depending on input dataset, disappearance of specified header comments in the second and
subsequent RINEX observation files when '+nav +[,+]' was being used and GPS and/or GLONASS
RINEX navigation files were being created

2) without '-O.int' or '-O.dec' options being used, an INTERVAL header line would be put in
the second RINEX observation file that was created

are fixed and will function correctly in the next version that is released (or any interim
version that I happen to hand out before then).


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
      WWW:  http://www.unavco.org   http://jules.unavco.org

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

On 07-Jul-16 10:53 PM, Neville Palmer wrote:
> I am using the teqc -tbin option to generate daily RINEX files from Trimble NetR9 tgd files. The tgd files are 24 hour files with 15 second
> epochs with occupations spanning 2 to 5 days.
> The problem I encounter seems to happen with the data sets from some occupations but not others. All receivers are NetR9 running firmware 4.62.
> I am running teqc version 2016Apr1 and have had the same result with both Linux and Windows versions.
> As an example if I use the following command
> teqc -config 1144_2016-02-04.cfg -tbin 1d 1144 +obs + +nav +,+ 1144/*.tgd
> The first (24 hour) RINEX obs file is produced correctly but the second and all subsequent files have all the comment lines removed. This
> applies to the comments that I have explicitly added in the config file as well as those automatically inserted by teqc.
> If I run an almost identical command with another set of tgd data from a different occupation/receiver it will sometimes work correctly with
> all obs files containing the comment lines as expected. There doesn't seem to be any reason why it works sometimes but not others.
> If I exclude the "+nav +,+" option or explicitly name the nav file names, as per the following two examples, the obs files are generated
> correctly as expected for all cases.
> teqc -config 1144_2016-02-04.cfg -tbin 1d 1144 +obs + 1144/*.tgd
> teqc -config 1144_2016-02-04.cfg -tbin 1d 1144 +obs + +nav gps.nav,glonass.nav 1144/*.tgd
> I can provide examples of the *.tgd files along with a listing of the commands I am using that give both the correct and incorrect outputs
> if that is of use.
> As another less important aside. In all cases when I am generating RINEX as above, the second obs file generated for each teqc -tbin command
> has an "INTERVAL" header line inserted. I have not specified and -int option in any cases. All subsequent as well as the first obs file do
> not have this additional header line. This doesn't cause me any problems but does seem a little odd.
> Regards
> Neville
> Notice: This email and any attachments are confidential. If received in error please destroy and immediately notify us. Do not copy or
> disclose the contents.

More information about the teqc mailing list