OPUS problem TTT

What happens when you submit a rinex file?

I tied exporting one and got the same result

FILE: BASE104m.11O 000001875

9007 ERROR! One of the OPUS baseline solutions terminated abnormally.
9007 OPUS cannot process this dataset.
9007 Aborting...
9007

Send me one of your RINEX files, and let me take a look at it.

LDOGEO AT AOL dot COM

Loyal

Thanks I will send you some

Okay...well this is a little strange, but NOT “unheard of.”

I looked at the RINEX files, and they look fine, but I got the same error message from OPUS. I played with them awhile (decimated, trimmed, edited to C1/L1/L2), and still...same error message.

It occurred to me that MAYBE the problem was with the CORS sites picked by OPUS (which is totally automated), so I selected three IGS site (GODE, MDO1, & DRAO) and gave it a whirl (ALGO is actually [a lot] closer than DRAO, but OPUS won't let me select it).

Well...BINGO...all of the files processed fine!

Now I would NOT use these solutions, DRAO is in British Columbia, and MDO1 is in Texas, BUT it proves that the data (RINEX file) is FINE, and it's the CORS sites selected by OPUS that are the problem.

If I was you, I would SELECT (in OPTIONS) sites nearby your project, and you should be in business. GODE is very near the area of the observations (GODE=Goddard Space Center in Maryland), so it's a winner for sure.

Loyal

Thanks Loyal you are truly awesome!!!

Glad that I could be of assistance.

Out here in the West, I use PBO sites almost exclusively, and even then I will have to "pick-n-chose" from time to time IF I'm in a hurry.

The CORS webpage has the option of checking data availibilty for each CORS, so that is where I would start.

Loyal

We usually get this error within the first couple of days after collecting data. If we wait 2-3 days to process the data through OPUS, it works fine.

Changing the cors stations will sometimes work too.

Pole-lock:

I agree with your above statements.

The surprise with Thoth's files, is that three of the four files were collected on March 17th of this year (40 days ago), and yet STILL WON'T process through OPUS if you let OPUS select the CORS sites (I just tried again this morning).

I don't know if this problem is limited to a specific geographic area or not (I see that Merlin had a similar problem last week). There are several scenarios that can return the error in question, but this might be the first time that I have seen this specific issue. It would be nice if OPUS told you WHICH baseline failed, then you would know where to start.

This is rather troubling, and an Email to Rick Foote at NGS HQ is probably in order.

I NEVER let OPUS chose the CORS sites, so I rarely see this error. When I do, I simply chose another CORS site.

Loyal

Wow that is surprising. That is a long period of time gone by to still get that error. What kind of gps file editing software are you using? Have you looked at the file to see if there are any particular satellites giving you issues? Just like one bad apple can spoil a bunch, one bad satellite can as well. We use some in-house designed software (one of my colleagues is pure genius) that is really slick. If you would like, I could take a look at the file for you.

I have run it through TEQC, and also just "eye-balled" the files based on experience. I would think that any problems with the observations (bad birds, multipath, whatever) would ALSO bomb the solution to British Columbia!

I have assembled an Email explaining my findings, and shot it off to Rick Foote along with one of the “offending” RINEX files.

Loyal

Post his findings or advice if you don't mind. Thanks in advance.