I have been unable to get some recent OPUS-RS solutions using actual CORS data. The data appears clean without cycle slips for the submitted as well as nearby CORS.
I believe that RSGPS (OPUS-RS engine) is misinterpreting the fact that some P2 data is missing because the C2 observable is provided as a cycle slip.
I would like to see some recent RINEX files that gave OPUS-RS solutions.
I have been unable to contact NGS as the contact button on the OPUS page is not working. In addition it appears many Federal offices are closed due to anticipated snow.
Paul in PA
It's not a solution
but a rehash from the post from 28 Feb.
I had a 45 minute file collected on 22 Feb that would not process.
I had the message from NGS stating no stations within 250 km of my position.
I manually picked the 3 closest CORS (TxDOT) stations and received the message that one station TXSM did not have data available for that day.
Yesterday, I picked 9 CORS stations, most TxDOT and 2 locals.
Received reply that SAM2 did not have data available for that day.
Process aborted. (there were plenty of stations left, process anyway).
I downloaded the CORS data for that day and processed it myself.
My whole purpose of doing this was for a check on my RTN data.
RINEX 2.10, What Receiver, What Observables ?
I sent a RINEX 2.11 file and NGS said it could not be converted to RINEX format.
Very frustrating.
Paul in PA
RINEX 2.10, What Receiver, What Observables ?
I use an ancient Trimble 5800 that has limited firmware in it for OPUS work. Usually collect about 20 minutes and convert my .t20 file to Rinex using Trimble's utility. Convert to 2.10 RINEX. Seems to be the most stable. Send in the .o file. It usually takes about an hour to get results - maybe longer - sometimes shorter. Use the extended results option to see more than the basics output. That is a typical workflow for me.
Geez, I thought it was just me
Here Is The OPUS-RS Abort Message
FILE: intc058a.14o OP1393868921376
1008 NOTE: Antenna offsets supplied by the user were zero. Coordinates
1008 returned will be for the antenna reference point (ARP).
1008
6014 OPUS-RS cannot find three reference stations within 250 km of
6014 your position and with suitable data for use with your dataset.
6014 OPUS-RS requires at least three reference stations and is
6014 currently limited to a maximum distance of 250 km. If you wish
6014 to use reference stations more than 250 km from your rover station,
6014 you may use the User Selected Base Station feature on the OPUS
6014 Options page.
6014
6014 If your data set is recent, it is likely that data from the nearby
6014 CORS stations have not yet been uploaded to the CORS archive. You
6014 may want to try again later.
Note the name of the file INTC is a CORS station that had 11 RINEX observables. I ran it through teqc to reduce it to 4 observables C/A L1 L2 and P2. the problem I believe is that the surrounding CORS still have the expanded RINEX files. All surrounding CORS are fully populated.
What CORS were used in your successful OPUS-RS solution as I will check out their RINEX format?
Paul in PA
I was getting the same messages last week on a job. I had 3 hours of observation time. I split it up into several different length files to submit to OPUS-RS to confirm my static solution. I finally got one of the files to process. I'm an OPUS rookie, so, I can't offer any suggestions...just letting you know you're not alone.
Lately, I have been having NUMEROUS rejections of my latest RINEX 2.11 files from OPUS-RS where I had *zero* issues before. It seems to throw out my entire file if even one hiccup is present.
I thought at first it was our ancient antenna/controller firmware combination circling the drain, so I re-installed the firmware and also tried using RINEX 2.11 data via observations from our newer GPS equipment... same issues.
It sounds like perhaps the OPUS-RS engine needs a tune-up...???
The only superior evidence is that which you haven't yet found.