Community Forums

Community Forums

OPUS-RS aborting, t...
 
Share:
Notifications
Clear all

OPUS-RS aborting, taken from more than one location  

Page 1 / 3

gaidrafting
Posts: 8
Member
(@gaidrafting)
5+ posts
Joined: 3 months ago

I have received an email from opus/ngs:

FILE: 01322057.20o OP1595620477603

 

 1014   The RINEX data submitted to OPUS contains data taken from more than one

 1014   location.  This can be verified by opening up your RINEX file and

 1014   searching for "MARKER".  OPUS will only process data taken from one

 1014   location.  Try separating the data into individual files and then

 1014   re-submit the data

 1014   Aborting...

 1014

I am certain there is extraneous information in the Rinex file but I cannot narrow it down enough to edit the .20o file to get it to be accepted.

Would anyone be able to help me find what needs to be removed from the file (I need to submit seven for solutions).

Thanks for any help anyone can provide,

Jason

15 Replies
John Hamilton
Posts: 2894
Member
(@john-hamilton)
2,500+ posts
Joined: 10 years ago

use a text editor (not a word processor) to open the file and search for "COMMENT" or "MARKER" (after the end of the header lines). Remove those lines. If you want to send it to me I will do [email protected]m

Reply
John Hamilton
Posts: 2894
Member
(@john-hamilton)
2,500+ posts
Joined: 10 years ago

I had an old file from 2005 that I just submitted this week that was similarly rejected. There was a "MARKER" line as the last line in the file. I really wish they (NGS) would modify OPUS to ignore things like that, especially if it is the last (or first) line in a file.

Reply

xyHt Magazine -- Still absolutely free!

Paul in PA
Posts: 6002
Member
(@paul-in-pa)
5,000+ posts
Joined: 10 years ago

I think "gai" should do it himself or he will never learn. One must start with an understanding of what is a line in computer data. A line is every thing until there is a "line return". A "line return" is unseen in a word processor but it is there, or not. I learned about data lines back in 1980 or so. I had one of the first IBM XTs hooked up as a terminal to the Bethlehem Steel IBM 360 mainframes and there were more than one of them. Data for processing was kept on drums, much bigger than discs. Something as simple as a one week payroll for the 4,000+ employees were kept on tapes. I had written a program to sort out from the weekly payroll, the hours charged to construction, not production, projects to provide weekly work progress/expense reports for new construction done by our in plant service division. The arrangement was that the IT department would run my program immediately after processing the weeks payroll and place the divisions construction data on a drum for me to access. Having successfully done this for a while, one day I decided to get a look at my base data file. So I open the file on my XT and I only see three lines of data so I figure something must be wrong. I start to scroll to the right and there was a character counter to let you know where you were. I was at 27,000+ characters and had not reached the end of line, so a drum had fairly extensive line handling ability.

What is a line in in a RINEX file, well a line can hold all the observations for a single satellite for a single epoch. If you look at a RINEX file in your PC text editor and all 9 (legacy data) possible observations are there you will see it on two separate lines, but it is in fact only one line and the text editor word wrap makes it look like two lines. The "end of line" character is after the last bit of data on the apparent second line. If the minimum of 4 observations is output the end of line character comes after the last reported observation so the computer does not waste time looking at lots of blank space characters. However if a observation was not observed blank space characters are inserted. When the OPUS computers start looking at your RINEX file and sees too many blank spaces where there should be data it bails out and sends you an "OPUS Abort" message.

Also should OPUS tell you there is a problem on line 1130 make sure your text editor has a line counter set up correctly, as line 1130 is somewhere after the 2,000th apparent line in a typical RINEX file. One of the persistent problems I had years ago was that my RINEX creator would sometimes not put an "end of line" character after the last line of observations or I would erase it in editing down a file for OPUS-RS. Each type of observation must start exactly at the same character space in each line and there must be numbers or blanks filling each space. I have not really evaluated a complete three signal GPS file so I do not know the maximum observables output in the latest RINEX version, I just chug along as legacy GPS does the job I require.

Also I note your file name "01322057.20o " which would be the 7th file your receiver created yesterday, it is possible that your receiver hiccupped and actually merged files 7 and 8. Or it could have started recording data for location 7 but used the raw XYZ coordinates of location 6, then realized it had a new location and inserted the raw XYZ position for location 7. One of the first things OPUS does is read your raw XYZ coordinates and chooses the closest available CORS to run your solution. Older receivers are particularly slow in calculating the XYZ coordinates of the current position. On my legacy Z-12s I would watch the position change as it worked it's way from the last position to the new position if I had not cleared the memory. I found out the hard way when 2 simultaneous observations on the same project used totally different CORS for my solutions. I contacted  NGS and they kindly informed me about the XYZ coordinates, I changed the offending RINEX file to the XYZ of the other receiver and got solutions from the same set of CORS. I had been on the other side of Pennsylvania on the prior GPS project and I forgot to start my receiver then restart a new observation file after it had been running a while.

Sometimes the easiest fix is to remove the first few minutes of observations, which is why you never observe for 2 hours and 1 minute when you really need an OPUS solution, 2 hours 15 minutes is usually always enough. The brute force method is to remove a few minutes, submit and repeat removal submit until you get a solution.

Paul in PA

 

 

Reply
1 Reply
Bill93
Member
(@bill93)
Joined: 10 years ago

5,000+ posts
Posts: 6914
Posted by: @paul-in-pa

What is a line in in a RINEX file, well a line can hold all the observations for a single satellite for a single epoch. If you look at a RINEX file in your PC text editor and all 9 (legacy data) possible observations are there you will see it on two separate lines, but it is in fact only one line and the text editor word wrap makes it look like two lines. The "end of line" character is after the last bit of data on the apparent second line. If the minimum of 4 observations is output the end of line character comes after the last reported observation so the computer does not waste time looking at lots of blank space characters. However if a observation was not observed blank space characters are inserted. When the OPUS computers start looking at your RINEX file and sees too many blank spaces where there should be data it bails out and sends you an "OPUS Abort" message.

My RINEX files created by TEQC have newline characters hex 0D 0A after each time the column gets too wide, rather than after all data from one satellite. OPUS doesn't seem to mind.

Also I note your file name "01322057.20o " which would be the 7th file your receiver created yesterday

My Trimble receivers start counting at zero, so xxxxddd7.20o would be the 8th file of day ddd for receiver xxxx or point xxxx.

Reply
gaidrafting
Posts: 8
Member
(@gaidrafting)
5+ posts
Joined: 3 months ago

"I think "gai" should do it himself or he will never learn."

I agree with this, however I am getting multiple reasons for rejection and have multiple ***XXX***.

I could type a book to explain what it looks like, or I could attach it and have someone review it. I spent an entire day yesterday going through the procedure to get the .20o file to submit, and I think I would like to make a little progress with this (getting much appreciated help, of course)

The forum will not let me attach a .20o file so...what would be the best way to have someone take a look at it?

Just for grins, here is the starting portion of it:

2.11 OBSERVATION DATA Mixed(MIXED) RINEX VERSION / TYPE
cnvtToRINEX 3.14.0 convertToRINEX OPR 20200724 175834 UTC PGM / RUN BY / DATE
----------------------------------------------------------- COMMENT
1 MARKER NAME
1 MARKER NUMBER
GNSS Observer Trimble OBSERVER / AGENCY
4808145663 TRIMBLE R8 GNSS 4.44 REC # / TYPE / VERS
TRM60158.00 ANT # / TYPE
-939233.5706 -5230843.4063 3515691.7318 APPROX POSITION XYZ
1.4264 0.0000 0.0000 ANTENNA: DELTA H/E/N
1 1 0 WAVELENGTH FACT L1/2
5 C1 C2 L1 L2 P2 # / TYPES OF OBSERV
2020 7 23 15 3 15.0000000 GPS TIME OF FIRST OBS
2020 7 23 15 34 0.0000000 GPS TIME OF LAST OBS
0 RCV CLOCK OFFS APPL
18 LEAP SECONDS
15 # OF SATELLITES
G02 124 0 124 124 124 PRN / # OF OBS
G03 124 124 124 248 124 PRN / # OF OBS
G06 124 124 124 248 124 PRN / # OF OBS
G12 44 44 44 88 44 PRN / # OF OBS
G17 124 124 124 248 124 PRN / # OF OBS
G19 124 0 124 124 124 PRN / # OF OBS
G24 124 124 124 248 124 PRN / # OF OBS
G28 124 0 124 124 124 PRN / # OF OBS
G30 8 8 8 16 8 PRN / # OF OBS
R09 124 0 124 124 124 PRN / # OF OBS
R10 124 0 124 0 0 PRN / # OF OBS
R16 124 0 124 124 124 PRN / # OF OBS
R18 124 0 124 124 124 PRN / # OF OBS
R19 124 0 124 124 124 PRN / # OF OBS
R20 124 0 124 124 124 PRN / # OF OBS
CARRIER PHASE MEASUREMENTS: PHASE SHIFTS REMOVED COMMENT
END OF HEADER
2 1
*** Start of Kinematic Data *** COMMENT
20 7 23 15 3 15.0000000 0 14G02G03G06G17G19G24G28G30R09R10R16R18
R19R20
22912004.875 5 120403394.361 5 93820834.82447 22912007.27047
24508321.852 4 24508328.945 8 128792074.192 4 100357490.124 8 24508328.57848
20803686.117 7 20803693.066 9 109324060.506 7 85187627.503 9 20803692.61348
21413685.305 6 21413688.363 9 112529672.096 6 87685470.253 9 21413688.41848
20551206.875 6 107997319.568 6 84153758.15548 20551207.61348
22845020.258 5 22845027.418 9 120051314.871 5 93546553.002 9 22845027.44147
21587622.820 6 113443719.981 6 88397715.41447 21587625.98847
24671370.227 4 24671379.586 8 129648976.553 4 101025156.665 8 24671379.23046
20028827.289 7 106952819.099 7 83185521.688 9 20028830.238 9
22972335.930 4 122455483.853 4
20254244.367 6 108194535.756 6 84151301.806 8 20254248.355 8
22443886.352 6 119806988.258 6 93183211.979 8 22443890.969 8
19704563.266 4 105406391.605 4 81982545.340 8 19704565.867 8
21297675.953 3 113888416.865 3 88579766.904 8 21297681.293 8
3 5
*** Start of Occupation *** COMMENT
1 MARKER NAME
1 MARKER NUMBER
-939233.5706 -5230843.4063 3515691.7318 APPROX POSITION XYZ
1.4264 0.0000 0.0000 ANTENNA: DELTA H/E/N
20 7 23 15 3 30.0000000 0 14G02G03G06G17G19G24G28G30R09R10R16R18
R19R20
22902194.219 6 120351834.999 6 93780658.71547 22902195.63347
24507289.461 3 24507296.551 8 128786649.936 3 100353263.430 8 24507296.11348
20797469.398 7 20797475.723 9 109291389.376 7 85162169.485 9 20797475.68848
21415690.336 6 21415693.750 9 112540209.393 6 87693681.124 9 21415693.39148
20550247.547 6 107992277.689 6 84149829.42048 20550248.36748
22839433.297 5 22839440.000 9 120021954.527 5 93523674.805 9 22839440.02747
21589328.711 6 113452684.646 6 88404700.85947 21589331.91447
24680526.555 3 24680534.484 8 129697086.191 3 101062644.631 8 24680533.90646
20020609.656 7 106908937.427 7 83151391.490 9 20020612.750 9
22959557.883 5 122387370.236 5
20259850.711 6 108224482.964 6 84174594.070 8 20259854.387 8
22452351.555 6 119852178.828 6 93218360.188 8 22452356.137 8
19707058.164 4 105419738.560 4 81992926.299 8 19707060.828 8
21289412.008 3 113844224.237 3 88545394.858 8 21289417.172 8
20 7 23 15 3 45.0000000 0 14G02G03G06G17G19G24G28G30R09R10R16R18
R19R20
22892387.492 5 120300302.378 5 93740503.42747 22892389.57847
24506272.641 4 24506279.766 8 128781308.153 4 100349101.007 8 24506279.86347
20791268.063 7 20791274.344 9 109258802.251 7 85136776.922 9 20791274.13748
21417691.656 6 21417694.703 9 112550726.928 6 87701876.600 9 21417694.83648
20549291.938 6 107987258.595 6 84145918.43248 20549293.09048
22833862.461 5 22833867.766 9 119992675.655 5 93500860.092 9 22833868.07047
21591039.719 6 113461672.221 6 88411704.14847 21591042.05947
24689670.789 3 24689679.848 8 129745146.935 3 101100094.534 8 24689679.56346
20012408.602 7 106865144.610 7 83117330.410 8 20012411.738 8
22946778.375 5 122319244.775 5
20265474.102 6 108254528.146 6 84197962.524 8 20265478.355 8
22460810.633 6 119897328.270 6 93253476.412 8 22460814.895 8
19709564.320 4 105433152.769 4 82003359.571 8 19709568.547 8
21281160.336 3 113800100.929 3 88511076.730 8 21281165.809 8
20 7 23 15 4 0.0000000 0 14G02G03G06G17G19G24G28G30R09R10R16R18

everything after that is in the same format and it ends with the last 2 lines of:

2 1
*** Start of Kinematic Data *** COMMENT

Reply
1 Reply
Bill93
Member
(@bill93)
Joined: 10 years ago

5,000+ posts
Posts: 6914
Posted by: @gaidrafting

The forum will not let me attach a .20o file so...what would be the best way to have someone take a look at it?

The best way is to copy it to some place that you can give a URL, such as Dropbox or other sharing service.

Otherwise, make a copy rename it  .txt and tell us that it is a .20o

Reply
Page 1 / 3
Scroll to Top