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
- Follow-Ups:
- Re: [ferret_users] MEMORY/SIZE= changes the result of SAVE
- From: Ansley C. Manke
- References:
- [ferret_users] MEMORY/SIZE= changes the result of SAVE
- From: Ryo Furue
- Re: [ferret_users] MEMORY/SIZE= changes the result of SAVE
- From: Martin Schmidt
- Re: [ferret_users] MEMORY/SIZE= changes the result of SAVE
- From: Ryo Furue
- Re: [ferret_users] MEMORY/SIZE= changes the result of SAVE
- From: Ryo Furue
- Previous by thread: Re: [ferret_users] MEMORY/SIZE= changes the result of SAVE
- Next by thread: Re: [ferret_users] MEMORY/SIZE= changes the result of SAVE
[Thread Prev][Thread Next][Index]