HORRIBLE OPUS results
I rarely use OPUS, I have had too many files that didn’t process over the years. I much prefer to process my own.
I ran a base on Monday and Tuesday of this week. Created three files because the session on Monday ran past UTC midnight, I could have merged the two into one file but left it the way it was. 180 minutes, 177 minutes, and 241 minutes. There are a couple of CORS nearby, the nearest one only had data from last year (stopped on July 18 of 2018) and the other, a PBO, stopped in April of 2019.
Submitted the first file to OPUS, got a 9011 message…
9011 OPUS could not process the data file that was submitted. The data was
9011 either very noisy or it was collected in kinematic mode.Or OPUS software
9011 has issue during this time, please reupload later.
9011Next two files processed, but results were really bad.
REF FRAME: NAD_83(2011)(EPOCH:2010.0000) IGS08 (EPOCH:2019.5372)X: -2366566.975(m) 0.208(m) -2366567.932(m) 0.208(m)
Y: -4221233.722(m) 0.751(m) -4221232.427(m) 0.751(m)
Z: 4142536.328(m) 0.429(m) 4142536.267(m) 0.429(m)LAT: 40 45 14.33588 0.182(m) 40 45 14.34838 0.182(m)
E LON: 240 43 24.70620 0.186(m) 240 43 24.64360 0.186(m)
W LON: 119 16 35.29380 0.186(m) 119 16 35.35640 0.186(m)
EL HGT: 1180.592(m) 0.853(m) 1180.051(m) 0.853(m)
ORTHO HGT: 1202.975(m) 0.854(m) [NAVD88 (Computed using GEOID12B)]and
REF FRAME: NAD_83(2011)(EPOCH:2010.0000) IGS08 (EPOCH:2019.5386)
X: -2366566.799(m) 0.114(m) -2366567.756(m) 0.114(m)
Y: -4221232.974(m) 0.797(m) -4221231.679(m) 0.797(m)
Z: 4142535.949(m) 0.650(m) 4142535.888(m) 0.650(m)LAT: 40 45 14.34218 0.067(m) 40 45 14.35468 0.067(m)
E LON: 240 43 24.69713 0.290(m) 240 43 24.63456 0.290(m)
W LON: 119 16 35.30287 0.290(m) 119 16 35.36544 0.290(m)
EL HGT: 1179.785(m) 0.993(m) 1179.244(m) 0.993(m)
ORTHO HGT: 1202.168(m) 0.994(m) [NAVD88 (Computed using GEOID12B)]Stats weren’t bad, RMS good, %obs used was high, etc.
Submitted all three to Trimble RTX, results were stdev in X of 2 mm, Y of 5 mm, and Z of 2 mm (ECEF)
Is this a fluke or is OPUS “broken”?
Log in to reply.