"Software error:
Can't call method "logger" on an undefined value at /ngs/projects/opus/www/cgi/cgi-cors/OPUS/Upload/Opusup.prl line 154.
For help, please send mail to the webmaster ([email protected]), giving this error message and the time and date of the error."
Date and time of error = 19-Jun-2017 +/- 23:50 UTC
Data file is from Day 17-093 (03-Apr-2017)
SHG
Shelby H. Griggs PLS, post: 433273, member: 335 wrote: "Software error:
Can't call method "logger" on an undefined value at /ngs/projects/opus/www/cgi/cgi-cors/OPUS/Upload/Opusup.prl line 154.
For help, please send mail to the webmaster ([email protected]), giving this error message and the time and date of the error."Date and time of error = 19-Jun-2017 +/- 23:50 UTC
Data file is from Day 17-093 (03-Apr-2017)
SHG
Is there a space or some other illegal character in your file name?
bobwesterman, post: 433275, member: 7106 wrote: Is there a space or some other illegal character in your file name?
Excellent idea. File names that are legal under Windows may not be under Unix rules.
File is named BAS10930.17o.
Thought maybe the GLONASS was derailing it, wrote a new RINEX with GPS only, same issue.
Wait till morning and see if NGS has a solution.
SHG
OPUS magically works this morning uploading same RINEX files.
SHG
Funny how that works...
:party:
Sometimes it seems like OPUS may have some reason to not work, like not having good CORS data yet, but it throws out a random message having nothing to do with the problem.
Bill93, post: 433345, member: 87 wrote: Sometimes it seems like OPUS may have some reason to not work, like not having good CORS data yet, but it throws out a random message having nothing to do with the problem.
I'm sure the error message has SOMETHING to do with the problem, it's just trying to figure out what that something is.
The way I read the error message is "this is logger, I can't do my job, sorry I can't really say why but this is the error OS is sending me."
Somebody just have the translation for OS.
NGS refuses to add "The dog ate my homework." to the incredible messages lists.
Paul in PA
What really perturbs me is getting an "Abort" message saying my data is not good, yet three days later the unedited file gives a very good solution. I can live with the honest "We did the best we could but did not have three good available CORS, please try later".
Personally though if the fault is their data, why not save my file and send me a solution whenever it gets better. That would save me from clogging up their filters by multiple resends.
Paul in PA
No, the way OPUS error messages work is:
"There is a big fishbowl of possible error messages. There are over 300. Each message is written on a small slip of paper (like in a fortune cookie.)
When a solution aborts, the computer pulls the five best answers from the fishbowl. Then the fishbowl is then aggressively shaken and 3 additional messages are then removed at random. These 3 messages are returned to the user.
The five best answers are replaced in the fishbowl and the error system is ready for the next failure!"
Really, I am pretty sure this is the way it works.
And the reason that it works so well is similar to Fortune cookies. All of the possible answers are just generic enough to work. Kind-of.