We have a new tool for submitting bug reports, suggestions, and questions.
A complete list of the bugs and their status may be obtained by doing
a query on PAVE. Please submit bugs or requests for enhancement to Bugzilla for any bugs or
requests for enhancements that are needed. If you would like to be notified of any
change of status for bugs that were submitted by another user, please add your e-mail address
to the CC list by clicking on the bug id, and entering your information to the Add CC text box.
- In versions prior to PAVE 2.1, the PAVE formula parser was not smart enough to
determine the difference between plotting TA for dataset n (TAn) and using the tan function.
Similar problems might occur with the combination CO and s. Workaround:
make your dataset use a different letter.
- If the file $EDSS_DIR/$EDSS_ENV/bin/OPTIMIZE/.pave_exe.pave_usage.log
is not writable by the user, versions prior to 1.5 would print out some
information and then crash with a segmentation fault or a memory
fault. PAVE 1.5 gracefully exits and gives a meaningful error message.
- In versions prior to PAVE 2.1 Mesh plots didn't display on some non-8 bit
graphics displays. This problem has been solved by using convert from
ImageMagick. For PAVE 1.7 and below the problem occurred on non-8 bit graphic displays
(e.g. a DEC 5000 X-Server, some SGIs, Linux machines,
some Windows machines). Workaround (for versions prior to PAVE 2.1.0): set your
display to use 8 bit graphics. On Windows machines this can be done by configuring
your display Color Palette to use 256 colors. On Linux, the X-server can be started with
an 8 bit depth using startx -bpp 8.
- Probing in vector plots causes PAVE to crash in version 1.7 and
before. This is fixed in version 1.7.1.
- On Linux, "Close" buttons do not work properly for some windows.
Workaround: close the windows using the window manager decorations.
- Time series plots over a region do not work if all of the data in
the selected region is missing for one of the selected time steps.
- PAVE sometimes prints a message like "Can't allocate ramp color 214"
and runs out of colors to use. Workaround: exit
PAVE, exit out of any other applications running on your X-display that
are using lots of colors (AVS, drawing/painting programs, etc), and then
get back into PAVE. If you were running netscape, try restarting it with
the option -ncols 64 to limit the number of colors it uses.
- Occasionally when saving tile plot images to data files, the
menus "disappear" from the tile plot. They are still active
however they are "invisible". Workaround: iconify the tile
plot, de-iconify it, and you should be able to see the menus
- Printing tile plots may not work reliably on the Sun platform
at this time, for reasons unknown to us. Workaround: save
your images as Gif or RGB, convert them to PostScript
(see the Saving PAVE Plots to PostScript
section for more information on this), then print them.
- The non-default maps in PAVE are a bit slow to generate,
especially the first time you create a plot with a given map projection.
We hope to speed up the map generation process with future
versions of PAVE.
- If you choose "File/Exit" and PAVE does not shut down, there may be
a mesh plot or time series line plot still running that prevents
PAVE from exiting. Workaround: locate any line or mesh plot windows
that you have created, and quit out of them before exiting PAVE.
- Miscellaneous memory leaks. Workaround:
If you run PAVE for a large
number of plots and you notice performance degradation, exit
out of PAVE and then restart it.
- In PAVE 1.4.x, PAVE could export netCDF files, but had trouble
them back in if the exported formula was at all complex. This is corrected
in version 1.5. See New Features in PAVE 1.5
for more details.
- In versions prior to PAVE 1.5, the column numbers in tabbed ASCII files
output from PAVE were sometimes incorrect. This has been corrected in
- In versions prior to PAVE 1.5,
if you use the tile plot Control..Time Series menu item to generate
a time series plot from a tile plot that was generated by first selecting
a subdomain, PAVE may not show the correct data. Workaround:
(1) Download the latest PAVE; (2) Use this menu
item only from plots that are not on a subdomain - zoom in on the subdomain
instead and then generate the plot; (3) select the subdomain for which you
want the time series plot and choose Create Time Series Line Plot from the
Graphics menu to create the plot.
- In versions prior to PAVE 1.5,
creating a time series plot from the Graphics menu when there are
layers of data selected generates a plot for the top data layer only,
instead of for the data averaged over the selected layers. Version 1.5
reports an error message if the user requests a time series plot over
- In versions prior to PAVE 1.5, there was a bug reading UAM-IV wind
files. This has been corrected in PAVE 1.5.
Malloc failure: If PAVE prints or pops up a message of the
form "malloc failure" or "VIS_DATA_Dup() failed" this means that PAVE has
run out of usable memory while trying to perform the requested
operation. To make more memory available, try closing some plots or quit
and restart PAVE.
Can't allocate ramp color xxx: If PAVE prints a message about
not being able to allocate a color that means that all available colors
for the current session on your system have been used up. Applications
like netscape will use as many colors as possible. To keep more colors
available to applications like PAVE, try running netscape with the option
-ncols 64 to prevent it from getting all the colors. This problem may
also occur if you've selected a lot of different color schemes during
your current PAVE session. To get all colors in the desired color scheme
try quitting and restarting PAVE after you've chosen the scheme that you
like. Also, logging out of your current session and logging back in
should make the maximum number of colors available.
Next Chapter: History of new features
Return To Table of Contents