Last modified: Mon, 12/04/2017 - 17:10
What's new in Ferret v6.96
Ferret v6.96 is a minor update to v6.95. It contains all of the same features as the release of PyFerret 1.2
*** NOTES ***
- There's an unresolved graphics issue: When displaying Ferret graphics on a RHEL6 machine, and using the RHEL6 XWindows display (updated since summer of 2015), using a mouse to drag the corners of the window and resize it does not work. This appears to be due to an interaction between the graphics calls in GKS, and the XWindows version under RHEL6. Resizing windows using the SET WINDOW /SIZE= works correctly. Displaying on other systems works fine, even when running Ferret on RHEL6. None of this applies to PyFerret.
New Features/Enhancements:
- The Ferret command-language syntax which is specific to PyFerret is now included in the main Ferret documentation. It is also summarized in this document.
- The images in the on-line Ferret introductory tutorial are drawn with PyFerret, as are the images in the FAQ on publication-quality plots. The process of updating the documentation to include PyFerret discussion and examples will continue.
- When Ferret and PyFerret start, there is a pre-defined symbol "program_name".
yes? show symbol program_name PROGRAM_NAME = "Ferret"
or
yes? show symbol program_name PROGRAM_NAME = "PyFerret"
- New @BIN and @NBIN regridding transformations. (Beta feature): Regridding by unweighted averaging. In @BIN regridding, the result is an unweighted mean of all source points in each destination grid cell. The result of @NBIN regridding reports the number of source data points in each destination cell. This is a beta feature only because it has not yet been heavily used.
Bug Fixes:
- If the SHOW DATA command is given and the requested dataset is not open, the error message did not report what dataset was requested. This is fixed. (Previously the noexist) was not included in the error message.)
yes? show dat noexist **ERROR: unknown data set: noexist
- Grave-accent evaluations lost precision when requesting high precision. When asking for full precision, a LIST/PRECISION= command gave full precision but for instance, `num,prec=16` did not return all expected digits on evaluation. This is fixed.
- A bug has been fixed in initializing some datasets where the coordinate location coincides with the upper- or lower-limit of the grid-cell bounds.