[teqc] helpful tip of week 1909

Lou Estey lou at unavco.org
Wed Aug 10 07:45:27 MDT 2016


This week's tip: using paths with file names

Hopefully this week's tip will be obvious to most UNIX/Linux users and maybe
Windows users who have experience with the 'cmd' window or DOS command line.

The tip: you can always include a path, relative or absolute, with any filename
being used with teqc.

Also, it's perfectly allowable to have the path, or part of the path, be an environment
variable (or a shell alias).

An example: Suppose you keep copies of some of CDDIS's combined RINEX navigation
files (the 'brdc' files) in a directory /data/cddis/brdc, where you might have
GPS and GLONASS brdc files for 2016-222 (yesterday) and 2016-223 (today).  (For
Windows users, use '\' instead of '/' to separate the folder levels.  Also, technically,
CDDIS won't have brdc files for 2016-223 until sometime in 2016-224 -- but you get
the idea.)

Then in most UNIX/Linux shells:

<prompt> BRDC=/data/cddis/brdc
<prompt> echo $BRDC
<prompt> /data/cddis/brdc

Also suppose your working data for yesterday and today is under /data/2016/08/09 and
/data/2016/08/10, where you might have a RINEX observation files test2220.16o and
test2230.16o, respectively.  Now change your currently working directory to be the
folder for Aug 2016:

<prompt> cd /data/2016/08

Now you should be able to run the commands:

<prompt> teqc +qc -nav $BRDC/brdc2220.16n,$BRDC/brdc2220.16g ./09/test2220.16o
<prompt> teqc +qc -nav $BRDC/brdc2230.16n,$BRDC/brdc2230.16g ./10/test2230.16o

... (assuming all goes well with the qc) you should end up with the qc report files
/data/2016/08/09/test2220.16S and /data/2016/08/10/test2230.16S.

Behind the curtain: In these commands, the environment variable $BRDC is being
expanded by the shell your using (e.g. sh, ksh, bash, Windows 'cmd'), so that shell is
actually running:

teqc +qc -nav /data/cddis/brdc/brdc2220.16n,/data/cddis/brdc/brdc2220.16g ./09/test2220.16o
and
teqc +qc -nav /data/cddis/brdc/brdc2230.16n,/data/cddis/brdc/brdc2230.16g ./10/test2230.16o

Since your current working directory (cwd) is /data/2016/08, teqc can locate the RINEX
observation files relative to the cwd and then knows to write the qc report files
to the same location as the RINEX observation file.

This example uses both absolute paths (the path names starting with '/') and relative
paths (the path names starting with './').  The './' is actually redundant; you
can safely remove the './' and those path names will mean the same relative path.

If these simplifying concepts are new to you, then with a little experimentation you
will quickly pick up the usage and probably be able to better organize your data
files, improve your workflow, and improve scripts that use teqc.

Happy teqc-ing!

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

Past helpful tips:

week 1894: using teqc config files - http://postal.unavco.org/pipermail/teqc/2016/002067.html
week 1895: qc of high-rate data - http://postal.unavco.org/pipermail/teqc/2016/002071.html
week 1896: UNIX/Linux shells for Windows - http://postal.unavco.org/pipermail/teqc/2016/002072.html
week 1897: '-' vs. '+' teqc options - http://postal.unavco.org/pipermail/teqc/2016/002076.html
week 1898: auto-identification of formats - http://postal.unavco.org/pipermail/teqc/2016/002092.html
week 1899: auto-identification vs. format flags - http://postal.unavco.org/pipermail/teqc/2016/002096.html
week 1900: square brackets in options - http://postal.unavco.org/pipermail/teqc/2016/002105.html
week 1901: using option '+mds' - http://postal.unavco.org/pipermail/teqc/2016/002108.html
week 1902: qc results w/ problematic nav messages - http://postal.unavco.org/pipermail/teqc/2016/002113.html
week 1903: '-no_orb[it]' and '-no_pos[ition]' options - http://postal.unavco.org/pipermail/teqc/2016/002115.html
week 1904: '-week' option - http://postal.unavco.org/pipermail/teqc/2016/002117.html
week 1905: using '+bcf' for XYZ/geodetic conversion - http://postal.unavco.org/pipermail/teqc/2016/002126.html
week 1906: the '+v[erify]' option - http://postal.unavco.org/pipermail/teqc/2016/002128.html
week 1907: '+C2', '+L5', "+L6', '+L7', '+L8', and '+all' options - http://postal.unavco.org/pipermail/teqc/2016/002130.html
week 1908: no doppler shortcut; RINEX L2 - http://postal.unavco.org/pipermail/teqc/2016/002131.html




More information about the teqc mailing list