I??m getting an error when trying to process my rinex file and can??t figure out why.
?ÿ
FILE: 921629_21_122_A1.21O OP1620090545961
6012 ?ÿ?ÿOPUS-RS is not able to find a solution for your data set.
6012 ?ÿ?ÿOPUS-RS has stopped with the following message(s) in RSGPS
6012 ?ÿ?ÿnetwork solution:
STOP(rdrnx): error reading rinex file: /var/tmp/opus_local/RS74/21122/pool/njmt1220.21o
I'm dealing with the same thing. I'll try again later in the week.?ÿ
?ÿFILE: 65421161.21o OP1620085966227
"
?ÿ6015?ÿ?ÿ OPUS-RS will not attempt a solution because the submitted data
?ÿ6015?ÿ?ÿ was collected at a location that is more than?ÿ 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:
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ ac70
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ ab28
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ ac37
?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ Your station is?ÿ?ÿ?ÿ?ÿ?ÿ 81.5 KM outside the polygon enclosing the reference stations
"
?ÿ
That's totally bunk.
error reading rinex file: /var/tmp/opus_local/RS74/21122/pool/njmt1220.21o
Looks to me like there is a problem with your RINEX file.
OPUS-RS requires quality observations, not only in your RINEX file but also in the CORS RINEX files it is trying to use. Very often it can take extra time for the CORS folders to get populated with enough good information.
It appears OPUS-RS stopped while it was reading the Morristown, NJ CORS file. That is not your fault. If you have not gotten a solution yet, exclude NJMT from consideration.
Williwaw, check the raw XYZ position at the beginning of your RINEX file. That is the location OPUS uses to select your CORS. Just because you know where you had your receiver setup, does not mean your receiver sat there long enough to actually update it's position for the record. Have had that problem in the past, used 2 receivers one day and set them up hundreds of miles away the next day. Got a good solution for one but not the other. Replaced the raw XYZ from the first receiver and VOILA!
Paul in PA
It processed eventually. They must have removed the bad data from the solution
