|
I am so sorry. For sure I wanted to write ".. similarly to yours
...". Please excuse this typo!
Am 16.12.2019 um 07:54 schrieb Martin
Schmidt:
Ryo,
I propose to produce a file similarly to your with a few
commands. Generate the axes and than the data like
let myvar = 0*(x[gx=xax] + y[gy=yax} ......) + 1
save /file= ... myvar
This data set should reproduce your error. If it does so,
others could also do the checks without sending the huge file
around.
Best,
Martin
Am 16.12.2019 um 05:31 schrieb Ryo
Furue:
Hi,
with early versions of pyferret memory usage
was newly designed. There should be an old
mail-thread on this. Having not enough memory,
ferret just stopped computing and claimed to be
ready. This became visible from sometimes
obviously wrong results. This error was
corrected. I suggest to check this with a recent
version of ferret.
Unfortunately, I've just reproduced exactly the
same problem on Ferret 7.5.0 on Linux. So far, we
haven't got Pyferret on our Linux server.
So, the same problem is reproduced with PyFerret 7.5 on
the same Linux machine: The presence or absence of a SET
MEMORY command changes the result of SAVE without any
diagnostics.
I'll try to further reduce my data file.
Regards,
Ryo
-----------
NOAA/PMEL TMAP
PyFerret v7.5 (optimized)
Linux 4.15.0-1061-azure - 11/14/19
16-Dec-19 13:21
====================
NOAA/PMEL TMAP
FERRET v7.5 (optimized)
Linux 2.6.32-754.11.1.el6.x86_64 64-bit - 04/25/19
16-Dec-19 00:02
!=== my script to reproduce the bug ===
! Delete the SET MEMORY command and the two
output variables become identical.
!
set data tmp-usss0500m-L600.nc ! Contains var
"usss" .
set memory/size=300 ! <- Delete this line
let u = usss[d=1]
save/clobber/file= tmp-u.nc
u[m=1:10@AVE]
save/clobber/file= tmp-usss.nc
usss[m=1:10@AVE]
!--- plot to see if they are identical ---
cancel var/all
cancel data/all
set data tmp-u.nc
set data tmp-usss.nc
plot/x=101W/y=4S:4N u[d=1], usss[d=2]
|