Notifications
Clear all

OPUS & the Multi-Year Solution

8 Posts
4 Users
0 Reactions
5 Views
(@loyal)
Posts: 3735
Registered
Topic starter
 

Man I sure like this new OPUS_NAD83(2011) Epoch 2010.0000 using the Multi-Year (MYCS1) Solution!

I just submitted four(4) RINEX files on a New Control Point this morning, (got two of them back before the last one was even sent).

Here are the “RAW” (unadjusted) OPUS positions in UTM Zone 12:


Northing Easting Height Date Duration
4,490,888.620(m) 385,596.078(m) 1,393.979(m) 11/30/2011 7h 35m
4,490,888.625(m) 385,596.080(m) 1,393.980(m) 12/07/2011 4h 35m
4,490,888.622(m) 385,596.080(m) 1,393.974(m) 12/14/2011 7h 30m
4,490,888.624(m) 385,596.082(m) 1,393.978(m) 12/28/2011 7h 29m

Even the 4 Hour 35 minute [quicky] observation looks sweet!

Equipment used: Trimble 5700 with Zephyr Geodetic (TRM41249.00 NONE) on 1.5 meter “fixed” height SECO Rod. All occupation were processed to the same three(3) Plate Boundary Observatory (PBO) Stations (ranging from 134 to 231 Km distant), using the Precise Ephemeris.

I reckon that I can put a fork in this baby.

Loyal

 
Posted : January 17, 2012 6:36 am
(@scott-zelenak)
Posts: 600
Registered
 

I always read your posts, though I don't always get the GPS stuff.

One neat thing, when I previewed this post, was the slide bar that let me look at your data.

Was that your doing or a new board feature?

 
Posted : January 17, 2012 2:43 pm
(@loyal)
Posts: 3735
Registered
Topic starter
 

Scott

Not me bro!

I never noticed it before you pointed it out just now...

Maybe Wendell will clue us in?

Loyal

 
Posted : January 17, 2012 4:04 pm
(@jim-frame)
Posts: 7277
 

I don't understand the significance of the multi-year solution. Using the same CORS, the same site equipment, and long (>4 hour) sessions, wouldn't you expect OPUS to deliver similarly clustered results from prior CORS epochs?

 
Posted : January 17, 2012 8:29 pm
(@loyal)
Posts: 3735
Registered
Topic starter
 

Jim

Maybe in some places, but NOT around these parts. The ONLY way I could get those kind of results using OPUS before the Multi-Year Solution, was to either use the 60 Day Times Series (which ONLY works on very recent data), OR to use the SOPAC SECTOR modeled estimates. In BOTH cases, the G-File data had to be extracted from the Extended Output Report, and then applied to the 60 Day or SECTOR esitmates.

Your milage may vary though...

Loyal

Edit: The REAL difference is not so much in the "cluster," as it is in the Peak-Peak Variances (which I did not post). I have to get up at 04:00 in the morning, but I will try and post a post sometime tomorrow that INCLUDES those.

 
Posted : January 17, 2012 9:02 pm
(@loyal)
Posts: 3735
Registered
Topic starter
 

Jim

Here are the OPUS Peak-Peak Variances of the four observations:


IGS08 (EPOCH:2011.9147) -1845716.332 0.006 -4488852.944 0.011 4126403.689 0.014
IGS08 (EPOCH:2011.9340) -1845716.330 0.014 -4488852.942 0.015 4126403.693 0.005
IGS08 (EPOCH:2011.9530) -1845716.330 0.002 -4488852.940 0.010 4126403.687 0.007
IGS08 (EPOCH:2011.9914) -1845716.329 0.004 -4488852.942 0.009 4126403.691 0.011

Here are the same observation using the same PDO sites in the “old” OPUS:


ITRF00 (EPOCH:2011.9147) -1845716.339 0.017 -4488852.960 0.011 4126403.665 0.009
ITRF00 (EPOCH:2011.9340) -1845716.338 0.017 -4488852.960 0.003 4126403.670 0.001
ITRF00 (EPOCH:2011.9530) -1845716.337 0.017 -4488852.957 0.006 4126403.662 0.004
ITRF00 (EPOCH:2011.9914) -1845716.336 0.015 -4488852.959 0.009 4126403.667 0.010

NOT much difference... BUT these are “hand picked” PBO sites that have a long history of stability, and which I have “watched” closely over the years (AND...the NGS had fairly recent ITRF2000 coordinate & velocity estimates on).

Now when I select sites that are NOT so well behaved (or current in the old realization), things change a little.


IGS08 (EPOCH:2011.9914) -1845716.328 0.004 -4488852.936 0.025 4126403.688 0.024
ITRF00 (EPOCH:2011.9914) -1845716.327 0.032 -4488852.941 0.083 4126403.648 0.043

Now even the Multi-Year Solution has kicks out a bit with this combination, BUT look at the “old” OPUS Peak-Peak Variances! Obviously the Multi-Year Solution has a significantly better “handle” on these sites.

Now granted...this is NOT really a fair comparison, in that I KNOW which sites work well, and which work...mmmm... not so well in this area. Not only that, there are OTHER factors that contribute “behind the curtain.”

In fact, IMHO, the Peak-Peak Variances tell you as much (or MORE) about the CORS sites used, as they do about your observation per se.

My point in the opening post was simply that the Multi-Year Solution is a significant improvement in my neck of the woods (especially on the STINKERS).

Your mileage may vary.

Loyal

 
Posted : January 18, 2012 7:42 am
(@jim-frame)
Posts: 7277
 

Jim

I haven't used OPUS much lately, so I've not played around with the MYCS in my area. I'll give it a go next time, though!

 
Posted : January 18, 2012 7:57 am
(@mapman)
Posts: 651
Registered
 

Fast Static OPUS pretty good too

Hello to all. First post here. Just ran a check on a recently acquired 5800 using fast-static and OPUS for the first time. I was amazed at the tight solution it produced on a high velocity mark. Studied the results for some time and it appears to be a rigorous adjustment routine. Just wish I knew what weighing it was applying to each CORS stations used. Base-lines were in the 50k to 120k length, so I would hope that the nearest CORS were weighted properly. It had the option of picking and dropping stations. But wanted to see what the system would pick first. Great thread here.

 
Posted : January 20, 2012 9:43 pm