Thank you for your message.
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.
The only difference I saw is that the new version is more sensitive to irregularity in grid spacing:
*** NOTE: Axis "LATV" is irregular. Ignoring erroneous point_spacing=even attribute.
Regards,
Ryo
====================
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.ncset data
tmp-usss.ncplot/x=101W/y=4S:4N u[d=1], usss[d=2]