They are aware of the problem and are working on it, however Giovanni Sella and several other staffers are not in today.
OPUS-RS works in some areas and not others. Until they resolve the issue it would be prudent to plan 2 hour OPUS observations or post process yourself. They belief the problems may be in some miss-formatting of some incoming CORS data. If so they may have to contact every CORS operator.
Best way to check in your area is to grab 1 hour of recent ufcors data from a nearby CORS and submit it for an OPUS-RS solution.
Paul in PA
> ...They belie(ve) the problems may be in some miss-formatting of some incoming CORS data. If so they may have to contact every CORS operator.....
One wonders how that would happen spontaneously and simultaneously at several CORS sites around the country. If true, there must be a back story.
I've been getting very little through OPUS the last couple days. I'm doing 2.5 hours right now. See if it works.
>If true, there must be a back story.
I Did A Test OPUS-RS, Had Solution In 1 Minute
Took a 1 hour file from a local PennDOT CORS and submitted it, Had solution in under a minute, fastest OPUS-RS I've ever seen. I note that no nearby PennDOT CORS were used. 4 NY, 4 NJ and CHES. I was outside the polygon.
NY and NJ CORS are all Leicas reporting a minimum of observables. CHES is a Trimble 5700 reporting 8 observables, C1, P2, L1, L2, S1, S2, D1 & D2, none of which are the new stuff.
I am pretty certain it is in the new expanded RINEX data but NGS says no?
PAMS the PennDOT CORS had no C2 data, all newer satellites were listed as having P2 data.
Paul in PA
Yeah, James... or someone has been messing with the dingle arm on the retro-encabulator module. However, this morning I swear the carburetor shaft was going out on the skyhook. Could have been the muffler bearings....
Hold on. Nope. Never mind, that was just the cat wanting back in. 😀
I got this error message when doing as you suggest (1 hr of data from ufcors submitted to OPUS-RS):
FILE: arlr0560.14o OP1393958361088
6015 OPUS-RS will not attempt a solution because the submitted data
6015 was collected at a location that is more than 50 km outside of
6015 the area spanned by the set of CORS sites whose GPS data OPUS-RS
6015 would use in processing the submitted data. These CORS sites are:
p777
mobr
moat
zme1
Your station is 105.6 KM outside the polygon enclosing the reference stations
I'm assuming that means I'm in a problem area?
They seem to have resolved the problems I was having. No warnings and all the CORS used are relevant to my location.
Ok. I just tried again, and this time it worked.
Yes, They Fixed It
Dear Paul,
I have noticed that you have submitted to OPUS-RS processor four times today. I found a bug in our processing that kept the rinex files with more than 9 OBS not usable. The OPUS is updated as of 2:00pm today. In the solution report, you'll see the version number updated to OPUS-RS version 1.91. Sorry for any inconvenience caused by NGS during this transition and thank you for notifying us the issues.
Kevin
Kevin K. Choi, Ph.D.
Geodesist
Deputy IGS Analysis Center Coordinator
National Geodetic Survey
NOAA/NOS, SSMC3-8104
1315 East-West Hwy.Silver Spring, MD 20910
Email: kevin.choi@noaa.gov
Office: 301-713-3198 x121
Yes, They Fixed It
I submitted about 5 times and only got one result back. Then they fixed it but I never got a nice letter like you did.
Matt, I Was emailing Them Details
of what I did, what I saw and what I thought was wrong. They still had to find it and fix it. Oh yeh, and a couple of phone calls to NGS might have helped. The email track went through several others before it was over.
I am working on an almost similar problem for someone else. Once I get it figured out as best I can I can again approach them.
Paul in PA
