OPUS Baseline Processing

I am NOT an expert. Definitley wait for a better answer, but I have seen folks suggest waiting 24 hours before processing. Might be other options to save you from a trip back out.

Most likely it means the CORS station data has not been downloaded to NGS. Especially on weekends when maintenance occurs this happens.

Wait a few days before you re-observe. If it is OPUS data pick a few CORS farther away. You my not get as good a solution as you want but you will find out your data is OK. If it is OPUS-RS your pretty much have to wait until the local CORS data shows up. Because OPUS-RS uses only good clean data it is sometimes necessary for the CORS data to be cleaned and filtered.

If a quick solution is a must you should go with a 3 hour minimum observation in case you have to do filtering and editing on your end. At times in the past I have had to use CORS I have never used before and I have used a lot.

Other times I download CORS data that NGS does not seem to like and process it myself. My post processing software seems to be very forgiving.

Paul in PA

Thanks Paul, I believe that might be my issue. I collected 2 hours on Friday, but when I went to process it thru OPUS I received a message that "the data was too noisy or was collected in kinematic mode" (which it wasn't). So I ran back out this morning and collected 30 minutes to run thru RS and received (and expected) to get the message about the precise orbits not being available yet, but then also had the message previously mentioned about the baselines.

I will wait a day or two and try processing thru RS again.

Thank you!

Stand fast sailor!

Try this very familiar sounding problem with a link:
from Mark Silver

He may have been talking about OPUS-Projects but I'd bet something VERY similar is happening if not the very same thing.
E.

Minor edit and a PS: He is talking about OPUS-RS.
I recently wrote a program regarding OPUS XML data and have kept links about these type of things in my own project for references and future needs... much like this.

Split Your Friday OPUS Into 2 OPUS-RS Files And Submit

There is a probable chance that the Friday CORS Data is in.

Take a look at your data and see if it is too noisy. Do not submit (edit out) any data in which the C1/P1 & P2/C2 data is absent. To check that out open your RINEX files using WordPad. Also you may want to use teqc to reduce to the 4 basic observations.

Paul in PA

I've got a similar error before and if I removed the glonass satellites it would process.
I've got batch files to do it with topocon utility.

Any news?
Did you get it figured out?

I waited until late this morning and ran my Sunday morning session thru RS and did get a result--but the precise and rapid orbits weren't available yet, so I'll just wait until later to run it again.

With my longer session on Friday giving me the "data is too noisy" error, how do I look at the data and tell if it's noisy or where the noise is? And is there a way to edit the noise out?

Thanks for all the help everyone!!

-Jason

FIRST...

Look at the RINEX file for the Friday observation, and see if it crosses GPS "Midnight" (into Saturday).

If it does...then resubmit today, and it should process.

IF NOT, then you will (probably) need some help!

Loyal

Call Mark. He's very amiable guy.
He knows all about this stuff.

If you are using Trimble gear and using their DAT->Rinex converter make sure you are not including "kinematic" data in the conversion.

Just a WAG, but I have seen kinematic data included on accident when that option is selected in converter inadvertently.

Good Luck!

Send Me The File

First send me an email, I will reply and then you can attach your file. Send me "O" and "N" RINEX files.

Paul in PA

I ran the Friday 2 hour session through OPUS again last night and this time it processed it, and the results appear to have good (small) residuals.

Thanks again everyone for your help!