I am not a big user of OPUS, but I occasionally use it as a check. I discovered something today that may be useful to others...
Probably more frequent users already know this...
If a session starts with only Glonass in the first epoch, teqc puts in the first line that it is GLONASS only:
2.11 OBSERVATION DATA R (GLONASS) RINEX VERSION / TYPE
This gets rejected by OPUS.
however, if it has both GLONASS and GPS, it says Mixed:
2.11 OBSERVATION DATA M (MIXED) RINEX VERSION / TYPE
this does NOT get rejected.
In the past, I would use the -R switch in TEQC to remove the GLONASS satellites. But, doing that does not change that first line. So today, after I removed the GLONASS satellites, the data was rejected again with the same message.
The solution is to use a text editor and change the "R (GLONASS)" to "M (MIXED)".
Interestingly, I had one session that had "S (SBAS)" in that first header line. OPUS processed that data just fine. So it appears that if it sees an R (GLONASS) in the first header line, it automatically aborts, thinking there are no GPS satellites.
In order not to waste resources, the OPUS site makes a decision on as little data as possible.
That is why I always covert to RINEX and read the file before submitting.
?ÿ
Paul in PA
I always just write a RINEX file without GLONASS for submittal.
SHG
I usually do so as well. In fact, for dealing with .T02 (or .T01) files I have a program that reads a directory and then creates the a batch file (dos...remember that?) with the following lines for each file found...
runpkr00 -g -d 20633100.T01
runpkr00 -d 20633100.T01
teqc.exe -R 20633100.tgd >20633100.17o
That will create a .tgd file with all observables, a .dat file and a rinex file that has Glonass stripped out.
But in this case the rinex files came from someone else...