Dear AllOne more simple trick is to use this pyferret opening command. This command will not open the graphics but instead it will help saving the image.pyferret -nodisplaythe no display command works with png and not with jpeg/jpg (check in the documentation as well).So in one terminal you can use pyferret normally i.e. with the graphic and if you satisfy with the generated plot you can then use pyferret -nodisplay in another terminal to save the image file.Cheers SaurabhOn Thu, Jul 13, 2023, 23:07 Ryo Furue <furue@xxxxxxxxxx> wrote:Dear ZAK,
Thanks for the answer, it seems that the problem comes mainly from the use of python3.9. Working in nodisplay mode works fine, but it doesn't allow to save figures "on the fly"... The best solution for me would be to reinstall pyferret with a lower version of python...Okay, if it's the python version (as opposed to the pyferret version), then the only difference in the installation process isconda create -n FERRET -c conda-forge pyferret ferret_datasets python=3.8 --yesif I remember correctly.Billy's instructions are for lowering the pyferret version.Ryo
I have recovered Billy's threads if needed for other ferret users :
https://www.pmel.noaa.gov/maillists/tmap/ferret_users/fu_2019/msg01017.html
Thanks again for your quick help
ZAKLe 13/07/2023 à 09:11, Ryo Furue a écrit :
Dear ZAK,
I'm having a problem with the graphic output generated by the frame command, which doesn't match the image displayed in the window. Only part of the image is visible in the png file. Using another format (jpg, pdf or ps) gives the same problem. Bellow's a screenshot illustrating my problem...
my linux version (Ubuntu 22.04.2 LTS), upgraded to python3.9
I didn't know that PyFerret has the same problem on Linux! It's been known for Mac for some time now.
For Mac at least, two workarounds have been known:
1. Use the script mode on the command line: pyferret -nodisplay -script yoursript.jnl
2. Use a previous version of pyferret (See Billy Kessler's comprehensive instructions in the Ferret email archive . . . which I haven't been able to locate . . . ).
See, e.g.,
Here is the entry to the email archive:
Ryo--