Known Problems

  1. The Portland Group f90 compiler, version 3.2-3, can't compile sources that use the == and != operators to compare data with a FillValue object. The workaround is to use the hasValue() and getValue() subroutines instead. To make life a little easier you could for example use the following preprocessor macros definitions:
    2. #if defined(linux86)
# define fill_eq(a,b) (hasValue(a) .AND. getValue(a) == b)
# define fill_ne(a,b) (.NOT._eq(a,b))
#else
# define fill_eq(a,b) (a) == (b)
# define fill_ne(a,b) (a) != (b)
#endif
  2. When creating debugging code with the -g flag of the Portland Group compiler, version 3.2-3, the linker can resolve all symbols. The problem does not occur when compiling with -O1 or -O2 flags which is the default configured by the configuration script.
  3. After writing data to a DataFile object, the object must be finalized before the programs ends. Otherwise, the last part of the data is lost. This is probably the result of data cashing in the NetCDF library.