Known bugs in PyNGL and PyNIO

• Possible disparity in labelbar colors
• Annoying tickmarks warning

• Some people with color PostScript printers have reported a disparity between colors in a filled contour plot, and the corresponding labelbar. The problem only shows up if you are doing a raster contour plot. We believe the problem is not with PyNGL, but with how the color printer is interpreting the color instructions in the PS file.

  Status: we did some initial research to try to force the labelbar to be drawn as a raster image as well, but this didn't seem to make a difference. This is on the back burner for now, since it appears to be a PS printer bug.

• When you run the pynglex example "streamline.py, you get a warning message:

  warning:tmEqualizeXYSizes is not a valid resource in streamline.PlotManager at this time
  

  Status: you can safely ignore this warning. This resource is set to True internally by PyNGL in order to make tickmarks the same length on both the X and Y axes. There's an odd situation with tickmarks in which if you use 2-dimensional latitude/longitude arrays to define your grid, the tickmarks go into a limited mode where you can't make many changes to them. We will eventually fix the code so this annoying warning goes away.

How to report a PyNGL/PyNIO bug

If you think you've found a bug in PyNGL or PyNIO and would like to report it, you can either do it via the pyngl-talk email list, or if you are shy about posting to the whole list, you can just email it directly to Mary Haley. Please be aware that if you just email it to Mary and she happens to be out of the office, then it won't get dealt with in a timely manner.

As a minimum, please email the following information along with your bug report:

• The version of PyNGL/PyNIO you are running.

• The type of system you are on, and what operating system you are running (if you don't know, then the output from "uname -a" can be sent instead).

• The exact error message you are getting. If there is no error message, then a detailed description of the problem or an actual picture (like a PostScript or PDF or NCGM file) is useful.

• What is really useful (but not required unless we can't reproduce the bug) is a simplified version of your script and any necessary data files so we can run it at our end.