[teqc] -tbin option coming

Lou Estey lou at unavco.org
Fri Jul 18 10:11:01 MDT 2008


All,

Not only is it coming, but it's ready for beta-testing by anyone who
wants to try it: just send me (not the teqc list, please) the results
of your current `teqc +id` so I know which build to send to you.  This
has a lot of promise as an extremely powerful option for those of you
who have been wanting a easy way to create batches of hourly files,
30-minutes files, 15-minute files, 5-minute files, ..., from one or more
input files (raw or RINEX, though as usual, the input files all have
to be of the same type).

Overview: Currently the most complete writeup is in the latter part of
http://ls.unavco.org/pipermail/teqc/2007/000549.html -- dealing with
the -tbin and -ast options.  (Later, I'll get a complete writeup in the
teqc tutorial.)  Some differences in realization from the hypothetical
in last summer's email:

* the tbin "delta" (first arg of -tbin) will not have a default of
seconds; in other words, you _must_ use a 'd', 'h', 'm', or 's' at the
end (to specify days, hours, minutes, or seconds).  I found it just
to easy to make the mistake of meaning "1d" or "1h" but typing "1" and
ending up with a boatload of one-epoch files (with names to the 1-second
granularity).

* the sub-second case was added: if sub-seconds are indicated, either
by the -tbin delta value or by -ast, then resulting filenames will
expand to include an additional ".ddd" after the seconds value showing
the time down to milliseconds

* in my testing so far, it works for all these cases:

n raw or BINEX files -> m RINEX filesets
n RINEX files of same type -> m RINEX files of same type as input
n raw or BINEX files -> m BINEX files
n RINEX filesets -> m BINEX files

* for creating RINEX with time-binning, you have pretty good control
over which files end up being created with time-binned names; e.g.:

`+nav temp.gps,temp.glo +obs + -tbin 1h temp` == all GPS nav messages go
into RINEX file temp.gps and all GLONASS nav messages go into RINEX
file temp.glo (in other words, neither are time-binned), but all
RINEX obs files _are_ time-binned (to 1-hour in this case)

`+nav +,temp.glo +obs + -tbin 60m temp` == all GLONASS nav messages go
into RINEX file temp.glo, but all RINEX GPS nav files and all RINEX obs
files are time-binned (again, to 1-hour)

`+nav +,+ +obs + +met + -tbin 3600s temp` == all RINEX (GPS and GLONASS nav,
obs, and met) files are time-binned (and again, to 1-hour)

`+tbin 1h temp` == a short-hand for the above (notice the '+tbin' instead
of '-tbin'), i.e. all RINEX files are time-binned (this might turn out
to be the most used form of tbin)

* the only difference to create time-binned BINEX is to use the '+binex'
option (which takes its usual argument), and the resulting BINEX files
will be named (differently from time-binned RINEX):

   <root> = prefix + GPS week + '_' + day_of_week (Sun=0,...,Sat=6)

   daily  = <root>.bnx
   hourly = <root>[a-x].bnx
   minute = <root>[a-x]00.bnx - <root>[a-x]59.bnx
   second = <root>[a-x][00-59]00.bnx - <root>[a-x][00-59]59.bnx
   subsec = <root>[a-x][00-59]00.ddd.bnx - <root>[a-x][00-59]59.ddd.bnx

e.g.:
[4310] teqc +mds input.obs
2008-07-14 00:00:00  2008-07-14 00:59:59   2442349  input.obs

[4311] teqc +binex 0x7f-03 +tbin 15m tmp input.obs; ll tmp*
! Notice ! using RINEX OBS default observable list
! Notice ! using RINEX MET default observable list
teqc: creating file tmp1488_1a00.bnx ...
teqc: creating file tmp1488_1a15.bnx ...
teqc: creating file tmp1488_1a30.bnx ...
teqc: creating file tmp1488_1a45.bnx ...
-rw-r--r-- 1 lou dmg 199980 Jul 18 16:04 tmp1488_1a00.bnx
-rw-r--r-- 1 lou dmg 175824 Jul 18 16:04 tmp1488_1a15.bnx
-rw-r--r-- 1 lou dmg 160074 Jul 18 16:04 tmp1488_1a30.bnx
-rw-r--r-- 1 lou dmg 143100 Jul 18 16:04 tmp1488_1a45.bnx

[4312] teqc +mds tmp1488_1a00.bnx
2008-07-14 00:00:00  2008-07-14 00:14:59    199980  tmp1488_1a00.bnx

* time alignment:

   no -ast specified: time-binning uses a default alignment starting at
   00:00:00 on the first data (obs, nav, or met)

   `-ast -` or `-ast _`: start alignment to the first epoch that is
   output

   `-ast  [[[[[[YY]YY]MM]DD]hh]mm]ss[.sssss]`: start alignment at
   at specified time

This might look daunting, but it isn't.  It's wild crazy fun --
and it just might work, too!

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

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


More information about the teqc mailing list