Hey Guys,
I am attempting to OPUS a point using my Trimble R8. I logged the data for about 2hrs onto the receiver.
I then took the .t02 file and converted it to a rinex file using the Trimble Utility. I then uploaded the rinex file(51441380.14o) to OPUS. OPUS accepted the upload but unfortunately emailed me back aborting the job. Its explanation was..
NOTE: Antenna offsets supplied by the user were zero. Coordinates
returned will be for the antenna reference point (ARP).
After the single baseline analysis, fewer than 3 useable
reference stations remain. Aborting.
Any ideas what I am doing wrong. I have never done this before; I'm sure I am making a stupid mistake. Any suggestions would be greatly appreciated.
Thanks
> Any ideas what I am doing wrong... Any suggestions would be greatly appreciated.
Probably nothing. That is data collected today, and on a Sunday, no less. Wait a few hours for the CORS data to download and try again.
I am having the same error message...
for a file I collected 29 April.
I submitted 29 April and got a solution with the ultra-rapid ephemeris; submitted the same file 30 April and got a solution with the rapid ephemeris; submitted the same file last night and got the exact same message you did.
I believe OPUS is having a hiccup.
Since reading your post, I will now try the SAME file again and will update you.
I submitted some files from JD132 and JD133 just now. The sessions I sent to OPUS-S process normally, but all of the OPUS-RS files failed with the same error message shown above.
I should have been more specific...
As Jim said below, my OPUS file processed, my OPUS-RS file is what generated the error messages.
OPUS-RS Requires Good Clean Data...
...from you and from the CORS that it expects to use. Sometimes the problem is that the data has not even gotten to the NGS and sometimes the data is bad, which might be improved by some cleaning up. It appears from the last part of the message that your file went to OPUS-RS.
The first way to improve your probability of a solution is to record more than 2 hours of clean data. OPUS -RS requires L1, L2, C1 or P1 and C2 or P2. The latter ones require that ambiguities be solved. Data that gives an OPUS-S result may not be suitable for an OPUS-RS solution. It ay be possible to edit your RINEX file and get a solution. It may just be necessary to wait until better or more CORS data is available.
Paul in PA
OPUS-RS Requires Good Clean Data...
> It ay be possible to edit your RINEX file and get a solution. It may just be necessary to wait until better or more CORS data is available.
While the problem may indeed by data availability, I don't think it has anything to do with the CORS themselves, but rather with the OPUS data store or maybe even the processing application (hardware and/or software) itself. One of the files that I sent today as a test and that failed with the "fewer than 3 useable reference stations" message processed fine on May 16 with 94% usable observations.
OPUS-RS Requires Good Clean Data...
I have selected specific CORS and had the "no good data" response when I had seen the CORS files in the NGS folders. Sometimes it may be flagged bad even if sufficient good data is there because OPUS-RS wants better. The filtering when it happens may not do anything noticeable to the CORS data to anyone else except OPUS-RS.
Paul in PA
Thanks for sharing this, NGS sees error messages too.
We just posted this alert and will remove it from the OPUS header when we figure out what's going on:
- - - OPUS-Rapid Static failure alert
- - - OPUS rapid static is failing with error 6029:
- - - fewer than 3 useable reference stations.
- - - We will remove this alert when the failure is corrected.
- - - OPUS static appears unaffected.
I am having the same error message...
I had some Saturday data uploaded Sunday that had some issues. Will be converting to RINEX and trying again later this week.
My data required entrance to the airport (I got to drive over the runway - too cool) and the USCG station. Those in charge were very easy to work with to provide the access, but still a slow down to get to the points.
I am having the same error message...
Still no joy as of a few minutes ago. It looks like something got broken pretty good.
OPUS-RS Is Back!
> Still no joy as of a few minutes ago. It looks like something got broken pretty good.
Never mind -- I sent an OPUS-S file to OPUS-RS by mistake, and didn't check the error message. OPUS-RS is back!
