)
TEQC FAQs
Question 1:
Is there a license for using teqc?
Answer:
No, teqc is freeware. UNAVCO makes executables for most common operating systems available. Get it. Use it. Caveat emptor.
Question 2:
Where do I find the teqc executables?
Answer:
See Executables on the teqc homepage.
Question 3:
Is there an install package for teqc?
Answer:
No. You just download the executable (in a .zip file after Dec 2013 for each operating system), uncompress it, and deploy it as you see fit. Your system path to the teqc executable is your responsibility. (You can keep multiple versions around if you want to, which is helpful when testing a new release and you want to compare results with an earlier version.)
Question 4:
I click on teqc and nothing happens. What's wrong?
Answer:
Nothing. You're probably a Windows user, right? See the Note to Micosoft Windows users at the end of Executables.
Question 5:
What documentation exists for teqc?
Answer:
There is an HTML tutorial covering all the original options and a newer Teqc Tutorial [PDF]. Also you can execute
teqc +help
for a quick listing of all available options; the output goes to stdout, so it can be directed to a file, piped to grep, etc.
Question 6:
Is the source code for teqc available?
Answer:
No. Some material is based on non-disclosure agreements with several of the manufacturers, and therefore cannot be released.
Question 7:
What is the teqc command to remove GLONASS data?
Answer:
Use the '-R' option to remove GLONASS while doing translation, qc operations, or even some other filtering of a RINEX file. Similarly use '-S' to remove SBAS, '-G' to remove GPS, '-E' to remove Galileo, '-C' to remove Beidou/Compass, '-J' to remove QZSS, and '-I' to remove IRNSS. These can be used individually or at the same time — just don't use all seven at the same time, i.e. '-G -R -S -E -C -J -I', as this will remove the data from all possible constellations! You can also remove specific SVs, if needed; see the Tutorial.
Question 8:
I have 1-second data and I want to decimate it to 30-second data. What's the teqc command that I need to use?
Answer:
For this case or where the original sampling is > 1 second, you just need use the '-O.dec' option, so for 30-second input data use '-O.dec 30'.
However, if the the original sampling is < 1 second, then you may need to also include the '-O.int' option specifying the original sample interval in seconds, e.g. use '-O.dec 30 -O.int 0.1' if the original data is 10-Hz. You should not need to include the '-O.int' option if reading a RINEX observation file that includes the optional INTERVAL header line with the correct value.
Question 9:
How can I keep apprised of teqc bug fixes, enhancements, or other changes?
Answer:
First, consult the Development & Release Log. Second, consider joining the teqc Email Forum.
Question 10:
Can teqc deal with RINEX 3.xx?
Answer:
No. You would have to convert RINEX 3.xx to RINEX 2.11 in order to, say, qc it. Teqc will allow an extended constellation set in RINEX 2.11 in order to qc Beidou/Compass, QZSS, and L-band IRNSS data, in addition to the normal GPS, GLONASS, Galileo, and SBAS data which is allowed in 2.11. See teqc forum email 2013 Mar 15 and teqc forum email 2017 Jun 19 for more information.
Question 11:
I run teqc on a raw data file with the '+meta' option and get meaningful results, like the antenna position and receiver type. But then I run teqc on the same data file with no options to translate to a RINEX observation file but none (or not all) of the metadata is in the RINEX header. What's wrong?
Answer:
Nothing except your expectations. Teqc is nominally a one-pass filter, in other words, it (mostly) only reads the input once — which, for example, is helpful when using teqc with streamed data. But here the results can mislead you. The '+meta' option does not terminate until the entire input has been read, thus outputting metadata that might occur anywhere in the file. (In fact, for metadata that might be repeated, like the antenna position, it outputs the last found value. When translating to RINEX, the metadata that is output in the header depends on what is supplied by the user or in the file found prior to the first data epoch that is output.
Question 12:
What's going on with all these +'s and -'s on the command line options? Why not just use - like the rest of UNIX? Is there a difference?
Answer:
Many of the options used by teqc have two states: either used to turn something off or on, or used to input or output something. In order to keep the total number of flags (option names) to a minimum, each flag might be proceeded by a - or a +:
- - means you want to turn an option off; or you are inputting something, like a file
- + means you want to turn an option on; or you are outputting something, like a file
Also see 'helpful tip of week 1897' for more explanation.
Examining the results of teqc +help should help clarify the meanings, and will show you the default settings of various options in teqc. If you do not find a - or + differentiation in the help, then either sign should work, like for obtaining help itself.
Last modified: 2019-12-24 02:29:43 America/Denver