I just emailed them.
OPUS upload error
- Thread starter Sean Joyce
- Start date
I just emailed them.
Fine!
Here is what Lou from UNAVCO said:
Hi Matt,
Well, I got the same notice and exit using that version of the Mingw32-compiled build
on my Windows machine.
I then compiled the current code (that we're testing for release) with Mingw32
and tried that executable ... and it works just fine for me. That build for
version 2015Jun05 (today) is at ftp://brick.unavco.org/pub/users/lou/johnson/teqc_mingw_32.zip
Generally speaking, if you see a message from teqc that is "cannot allocate memory for ..."
then the code is trying to dynamically allocate memory for something and the
operating system isn't letting the program do that, so teqc aborts. (It has no recourse.)
Now why the new build works (for me, at least) and the 2013Mar15 build doesn't
is a good question, but I'm not going to research it.
cheers,
--lou
It sounds like this should be fixed when OPUS upgrades to the next version of TEQC.Well, I got the same notice and exit using that version of the Mingw32-compiled build
on my Windows machine.
I then compiled the current code (that we're testing for release) with Mingw32
and tried that executable ... and it works just fine for me. That build for
version 2015Jun05 (today) is at ftp://brick.unavco.org/pub/users/lou/johnson/teqc_mingw_32.zip
Generally speaking, if you see a message from teqc that is "cannot allocate memory for ..."
then the code is trying to dynamically allocate memory for something and the
operating system isn't letting the program do that, so teqc aborts. (It has no recourse.)
Now why the new build works (for me, at least) and the 2013Mar15 build doesn't
is a good question, but I'm not going to research it.
cheers,
--lou
Michael Glutting
Member
Hello All,
I followed up with our friends at NGS on June 3rd. They are now aware of the issue and will work to resolve it. I'll advise when they confirm the issue is resolved.
Regards,
Michael Glutting
JAVAD GNSS, Inc. | Sales
M 408.375.9135 | E michael@javad.com
I followed up with our friends at NGS on June 3rd. They are now aware of the issue and will work to resolve it. I'll advise when they confirm the issue is resolved.
Regards,
Michael Glutting
JAVAD GNSS, Inc. | Sales
M 408.375.9135 | E michael@javad.com
Charles Craft
Member
I am having the same problem since my firmware was updated in mid May. I learned how to convert to rinex and got a solution. I am so new to this that I don't have my confidence level up. I only do opus for practice while I am learning.
Charles Craft
Charles Craft
Sean Joyce
Well-Known Member
Experienced a potential new problem with jps files and DPOS today.
I performed an RTK survey about 3.5- 4hours in duration 2 days ago.
The file downloaded from the T2 at the end of the session is 23mb which seems an excessive amount compared to past file sizes. (30 sec sampling rate)
My last 2 hour session was 7mb which also seems to be large. (see previous thread)
Today, Sunday the 7th I cannot upload the 23mb file to DPOS after trying repeatedly all day in case the USA server was down etc.
Anyone else have this problem?
-Suggest A progress indicator on the TLS when uploading a file as there is no way of knowing how the file transfer is going.
I performed an RTK survey about 3.5- 4hours in duration 2 days ago.
The file downloaded from the T2 at the end of the session is 23mb which seems an excessive amount compared to past file sizes. (30 sec sampling rate)
My last 2 hour session was 7mb which also seems to be large. (see previous thread)
Today, Sunday the 7th I cannot upload the 23mb file to DPOS after trying repeatedly all day in case the USA server was down etc.
Anyone else have this problem?
-Suggest A progress indicator on the TLS when uploading a file as there is no way of knowing how the file transfer is going.
Hi Sean. I do not expect 23 mb file causes a problem with DPOS. Did you try web DPOS? We've sent successfully much bigger files to process. Share the 23 mb with us.
I processed the file with TEQC on my Mac. It generated a lot of warning and even one error ("? Error? './219_093813.jps' rejection due to './219_093813.jps': SV count @ 2015 May 25 13:42:00.000 appears wrong: total= 23 max= 22 (use option '-max_rx_SVs 23'?))"
But finally it generated correct Rinex file. With the option -max_rx_SVs 26 there is no errors at all (only warnings remained).
But it would be good to contact with OPUS to use the options for our new files
But finally it generated correct Rinex file. With the option -max_rx_SVs 26 there is no errors at all (only warnings remained).
But it would be good to contact with OPUS to use the options for our new files
Sean Joyce
Well-Known Member
Alexey;
I uploaded through the website and it was processed. I couldn't get the file to upload on the TLS. This might be a problem with my network although my internet connection was fine.
My comment about file size, the static .jps files seem to have become much larger after the last firmware update when compared to a similar data recording sessions using the past firmware version. Could that be possible?
Sean are you sure the recording interval was set to 30 seconds? Could you email the file to me? Thanks
Hi Sean, I received your email:
Here the recording interval is still set to every second. It is controlled by the "Implicit Message Output Period" setting, not "Logging Period". I can see how this could be confusing. Did you you start the recording with Base Rover Setup or with the record button on the T2? If you started the recording with Base Rover Setup this setting in Net View is irrelevant. It applies when recording button is pressed on the T2.
When I inspect your file with JPS2RIN it shows it has an Interval of 1:
Here the recording interval is still set to every second. It is controlled by the "Implicit Message Output Period" setting, not "Logging Period". I can see how this could be confusing. Did you you start the recording with Base Rover Setup or with the record button on the T2? If you started the recording with Base Rover Setup this setting in Net View is irrelevant. It applies when recording button is pressed on the T2.
When I inspect your file with JPS2RIN it shows it has an Interval of 1:
Last edited:
Michael Glutting
Member
Hello All,
NGS advised that they have restored the ability to process the JAVAD GNSS jps file format. I have tested OPUS with a jps file from both the latest firmware release (3.6.3) and the previous firmware release (3.6.2). Both files were processed by OPUS successfully.
NGS advised that they have restored the ability to process the JAVAD GNSS jps file format. I have tested OPUS with a jps file from both the latest firmware release (3.6.3) and the previous firmware release (3.6.2). Both files were processed by OPUS successfully.