Trimble Business Center — Have confidence in your data. Start free trial.

AI Assistant
Notifications
Clear all

OPUS Error

7 Posts
6 Users
0 Reactions
1,207 Views
surveyor85
(@surveyor85)
Posts: 84
Free
Topic starter
Translate ▼
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Anyone ever seen this before? New crew on the job...

1007 The RINEX dataset submitted to OPUS failed to pass an initial
1007 test for one or more of the following reasons.
1007 1. The data only contained values for a single frequency.
1007 2. RINEX file not formatted correctly.
1007 3. One of the lines in the RINEX file is over 80 characters
1007 in length.
1007


 
Posted : February 1, 2016 11:49 am
loyal
(@loyal)
Posts: 3735
Free
Translate ▼
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Yes...

Usually for one of the above stated reasons.

RINEX files are highly formatted, and it doesn't take much to screw them up.

If you would like me to take a look at the file in question, shoot me a copy:

LDOGEO at aol dot com


 
Posted : February 1, 2016 12:25 pm
surveyor85
(@surveyor85)
Posts: 84
Free
Topic starter
Translate ▼
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Loyal, post: 355988, member: 228 wrote: Yes...

Usually for one of the above stated reasons.

RINEX files are highly formatted, and it doesn't take much to screw them up.

If you would like me to take a look at the file in question, shoot me a copy:

LDOGEO at aol dot com

Thanks Loyal, Ill be sending shortly


 
Posted : February 1, 2016 12:54 pm
wgd
 wgd
(@wgd)
Posts: 127
Free
Translate ▼
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I got that same message last week while I was goofing around with Convert to Rinex. I had sent the same file earlier and gotten the message about two MARKERS so I went in and deleted the wrong one and resent. The resend resulted in the error you received above. I undid my edit, deleted the correct marker and resent. This time I got and error saying my file contained less than 7.2 mins of data so I kicked my trashcan and moved on to something else.


 
Posted : February 2, 2016 5:04 am
paul-in-pa
(@paul-in-pa)
Posts: 6034
Free
Translate ▼
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

For the life of me I cannot figure out why OPUS does not give an honest answer such as "The dog ate my homework."

Quite often that error goes away in a few days when all the CORS data is finally settled in.

Most probably your new crew started collecting data too soon after turning the receiver on, removing the first few minutes will usually clear that up.

The most classic error I have ever received was "Your file ends before it begins."

Paul in PA


 
Posted : February 2, 2016 6:51 am

Mapman
(@mapman)
Posts: 651
Free
Translate ▼
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Has anyone ever parsed out the body of an OPUS FS observation? As a network solution, not vector line, it has a very different processing method from commercial packages.

My understanding of the OPUS results is somewhat limited to the top paragraph.
OBS USED:
QUALITY IND.
NORMALIZED RMS:

After that it tends to get like reading a computer manual. The top has a summary of the quality which is good, but it would be nice to know if the results could have been better by editing out any broken observations from the "o" file (of which I have limited knowledge).


 
Posted : February 2, 2016 10:21 am
larry-scott
(@larry-scott)
Posts: 1059
Free
Translate ▼
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Sounds like file might have tabs. If I open a rinex to edit something (station ID) I make sure that "no tabs" is set in my editor.

Reconvert the file.


 
Posted : February 22, 2016 10:47 am