This message is from OPUS after submitting a hour long observation to OPUS-RS.
2005 NOTE: The IGS precise and IGS rapid orbits were not available
2005 at processing time. The IGS ultra-rapid orbit was/will be used to
2005 process the data.
2005
6029 After the single baseline analysis, fewer than 3 useable
6029 reference stations remain. Aborting.
6029
Should I try a 2+ hour observation and use regular OPUS?
Will the IGS precise and IGS rapid orbits be available at some time so as I can use this observation and get a good solution?
The observation took place today at 11am. I sent it to OPUS at 6:30pm
The sit is far away so a return trip is to be avoided if possible.
Any suggestions?
Thanks!
VRMTSRVY, post: 341408, member: 7295 wrote: Will the IGS precise and IGS rapid orbits be available at some time
The rapid -- which I prefer -- has a nominal latency of 17 hours, and OPUS seems to add about an hour to that. So if you submit to OPUS at UTC end-of-day +18 hours it'll generally use the rapid orbit.
VRMTSRVY, post: 341408, member: 7295 wrote: Will the IGS precise and IGS rapid orbits be available at some time
The rapid -- which I prefer -- has a nominal latency of 17 hours, and OPUS seems to add about an hour to that. So if you submit to OPUS at UTC end-of-day +18 hours it'll generally use the rapid orbit.
Thank you!
Have you seen the situation where the ultra rapid did not give a good solution but waiting and using the others did?
I wouldn't use the ultra rapid orbit. I don't remember how much it makes a difference but I believe it can be tenths to feet different.
I always thought that you had to wait 24 hours before processing (and not use the ultra rapid orbit). It's good to know I can get by with less.
Did some serious editing of Vern's RINEX file and sent him a very good solution and the edited "O" file.
Paul in PA
I then sent Vern's original unedited file and got the same solution. It appears OPUS-RS used the exact same number of observations I had by editing. This makes sense because OPUS-RS runs the RINEX through teqc before processing.
Bottom line, sometimes you just have to wait for OPUS-RS to get all their CORS data in order.
Do not think I wasted my time as I proved to myself the soundness of the OPUS-RS methodology.
Below are the CORS used, note that the last three are near the limit that OPUS-RS uses.
BASE STATIONS USED
PID DESIGNATION LATITUDE LONGITUDE DISTANCE(m)
DG7426 P037 FREEMONTAPCO2004 CORS ARP N382518.293 W1050616.819 95703.5
DJ3037 PUB5 PUEBLO 5 CORS ARP N381712.592 W1042043.812 112765.8
DG7423 P036 ANGELFIRE_NM2004 CORS ARP N362512.969 W1051737.109 127445.1
AI7401 AMC2 ALTERNATE MASTER CORS ARP N384811.226 W1043128.496 151227.8
DK7583 P070 WAGONMOUNDNM2007 CORS ARP N360241.189 W1044152.758 176115.1
DH3852 P039 CLAYTONARP_NM2005 CORS ARP N362653.187 W1030914.194 224258.1
DO2634 CTI4 COMPASSTOOLS4CRNR CORS ARP N370910.489 W1074521.876 226735.1
DH3855 P040 LAMARARPT_CO2004 CORS ARP N380417.375 W1024113.084 232615.2
Paul in PA
VRMTSRVY, post: 341408, member: 7295 wrote: This message is from OPUS after submitting a hour long observation to OPUS-RS.
2005 NOTE: The IGS precise and IGS rapid orbits were not available
2005 at processing time. The IGS ultra-rapid orbit was/will be used to
2005 process the data.
2005
6029 After the single baseline analysis, fewer than 3 useable
6029 reference stations remain. Aborting.
6029Should I try a 2+ hour observation and use regular OPUS?
Will the IGS precise and IGS rapid orbits be available at some time so as I can use this observation and get a good solution?
The observation took place today at 11am. I sent it to OPUS at 6:30pm
The sit is far away so a return trip is to be avoided if possible.
Any suggestions?
Thanks!
It took me two days to get an answer back last week...just one of those things....
I've seen a lot of issues with OPUS-RS over the past two weeks.
Two hour OPUS Static occupations seem to be processing fine on the other hand. I never recommend OPUS-RS as I've never been happy with the results.
I observed two, 40 minute +/- files on Thursday just fine.
I have it on good authority that there are some occasional glitches w/ OPUS-RS lately that are in fact being addressed. Apparently headers are causing the issue.
Manually processing baselines is the suggested interim solution.
FWIW,
The IGS-CB site shows the accuracies and latencies of their orbit products here:
https://igscb.jpl.nasa.gov/components/prods.html
Note that the traditional rule of thumb is that SVpositionError/distance2SV = baselineError/baselineLength
Should be that almost all regular GPS users can meet their accuracy needs with the Ultra-Rapid orbits. That said, waiting until the Rapid is available is good policy in my view.
Cheers,
DMM
