Activity Feed › Discussion Forums › Strictly Surveying › One of those mornings, Love hate OpUs
-
One of those mornings, Love hate OpUs
Posted by Williwaw on December 31, 2013 at 6:41 pmArggg.
Did some static work yesterday to get going on a new mapping project, tying together several older surveys in local systems to bring them into real worl coordinates. Collected 2:01 hours of data on the R8_GNSS base to use for post processing fast static. Trying to get OPUS to process base data to get some good seed coordinates to get going, only OPUS isn’t cooperating, giving me an abort message data either to noisy or collected in kinematic mode. Not. Looked data over and it doesn’t look bad with minimal cycle slips.
Can anyone out there give me a clue as to what’s going on? I really, really don’t want to have to go do this over, some of the points tied were bitch to get to. Multipath was minimal and setup was stable. Maybe I can trying parsing into smaller files and try that?
Thanks all. ~Willy
paul-in-pa replied 10 years, 8 months ago 4 Members · 13 Replies -
13 Replies
-
Willy;
Shoot me the RINEX file, and I’ll take a look at it.
LDO-at-aol-dot-com
Loyal
-
>… giving me an abort message data either to noisy or collected in kinematic mode. Not. Looked data over and it doesn’t look bad with minimal cycle slips.
>Pretty sure in the options there is a check box in the converter to ignore kinematic data. Which may be throwing out your raw data. Just did some recent FS and had that problem. Seemed to work.
-
Bad Boy For Shortcutting Your Observation
2:01 hours leaves you no leeway for starting data collection too soon, probably the cause of your cycle slips.
You really do not want to submit to OPUS with any cycle slips in the first few minutes, so you want be able to delete the bad data. I usually drop the first few minutes, but since you have no minutes to play with you want to removing the first few minutes of the slipping satellites.
An alternative is to submit to OPUS-RS but beware that requires even cleaner data, not just L1 & L2, but C1/P1 & P2 as well.
After you stand in the corner for ten minutes, send me your RINEX file. I might be able to invent enough data to get you a solution.
Paul in PA
-
Bad Boy For Shortcutting Your Observation
I know, I know, your right Paul. Fading daylight and finding elusive old PK nails under 2′ of snow that have lost their ring and an hour drive back to the office led me to take a short cut or two and cut it too close. Now I’m paying for it.
I was bad. I’ll go take my place in the corner now. ):
I’ll do better next time, I promise! (:
Willy -
Send Me The File When You Get Out Of The Corner
I love a challenge.
Paul in PA
-
I Am Not Sure OPUS Was Ready For Your File
In several ways.
1/ Your file went past UTC midnight, so OPUS may have ignored the last 35 minutes of your file. If so resubmit.
2/ You file says RINEX Version 2.11 but inludes C2 data. I have never dealt with C2 data before so I am not sure if it belongs in 2.11 RINEX and if NGS is ready to process. Is there a choice in your RINEX converter to not include C2, or to report C2 as P2 data? OPUS-RS would look for C1/P1 & P2 data but do not know if it recognizes C2 data or would consider the lack of P2 data as a data problem. I submitted to OPUS-RS so I may soon find out.
Send OPUS your file in Trimble format and see if you get a different response.
Other than that the data does not look bad.
Paul in PA
PS: OPUS-RS says it was “too long” and did not mention any other problem. I trimmed it to under 2 hours ans am resubmitting.
-
GPS Midnight
The observation does (as Paul pointed out) cross GPS Midnight.
This is ONLY a problem when the file is submitted BEFORE the Rapid Ephemeris is available for BOTH days (it is not in this case, because the observation wraps into TODAY).
OPUS will NOT combine a RAPID & Ultra-RAPID Ephemeris together (at least that has been my experience).
The file should process fine around Noon tomorrow.
Loyal
-
GPS Midnight
Thanks a bunch guys. Learn something new every day. I’ll try resubmitting on Thursday.
Guess patience isn’t my strongest attribute.
Y’all have a great New Year!
Cheers! ~Willy out.
Willy -
OPUS-RS Cannot Find 3 Reference Stations Within 250Km
But again, no other complaint.
“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.”I checked and found that RINEX 2.11 includes C2 as well as all L5 observations.
Most likely you will have to wait until next year.
Paul in PA
-
Got A Decent OPUS Position This PM, OPUS-RS Even Better
Despite the observation being 14.2 Km outside the polygon. I tried to get it inside the polygon but as of today TLKA and AC51 had no or poor quality data. Give them a shot tomorrow.
I was pleased to learn that OPUS-RS is accepting and using L2C observations.
Paul in PA
-
Got A Decent OPUS Position This PM, OPUS-RS Even Better
Post processed my data in TBC Tuesday using a RS-OPUS solution on a 17 minute observation for seed crds. Finally got the 2:01 observation on my base to process in OPUS using precise emphemeris this morning. Missed my TBC values by .04′. Taking that to the bank.
Back in love with OPUS.
Willy -
1 Hour 59 Minute 30 Second OPUS-RS Even Better
I trimmed your file to just under 2 hours.
I’ll forward you my OPUS-RS position.
Paul in PA
-
My email to you has been delayed
out there in cyberspace somewhere.
I received an email back that they will try again later.
Paul in PA
Log in to reply.