nag logo Error Bulletin for Mark 22 of the NAG Fortran Library

This document contains a list of errors found or reported since the release of Mark 22 of the NAG Fortran Library.

Some of these errors may have been fixed at intermediate "point" releases of the Library, while other fixes are scheduled for incorporation at future releases. For library Marks where those fixes are not yet incorporated, a workaround for the known problem is provided wherever possible.

To find the Mark and point release number of your library, call NAG routine A00AAF( ).

  1. Routine: C05ADF
    Synopsis:   Routine C05ADF exhibits unpredictable (and incorrect) behaviour
    Description:   Certain smooth and continuous test functions can cause the routine to behave in an unpredictable manner, including homing in to a zero outside the specified interval or wildly oscillating and generate NaNs.
    Severity:   critical
    Problem since Mark:   FL22.0
    Fixed in Mark:   FL22.2
    Workaround:   No workaround. A fixed Library is required.

  2. Routines: C09AAF C09CCF C09CDF
    Synopsis:   C09CCF and C09CDF multi-level wavelets cannot handle periodic end-extension
    Description:   When MODE = 'P' and WTRANS = 'M' the multi-level wavelet transform routines do not work properly if N is not a power of 2.
    This combination of options has been temporarily disallowed until a fix is made. An error bulletin will advise when the option combination becomes available.
    Severity:   non-critical
    Problem since Mark:   FL22.0
    Fixed in Mark:   FL23.0
    Workaround:   The option combination of a multilevel wavelet transform using a periodic end-condition is currently disallowed; a call to the initialization routine C09AAF with this combination will return with an error code.
    For multilevel analysis of periodic data, you are advised to experiment with the alternative end conditions; the periodic property of the data can also be used to extend the data set in both directions to points that better suit the alternative end condition (e.g. extend the data to next maximum or minimum).

  3. Routines: D06ABF D06ACF
    Synopsis:   D06ABF D06ACF array bound violation
    Description:   Calls to D06ABF and D06ACF could, potentially, perform memory overwrites leading to unpredictable behaviour. This is due to the possibility of writes to the array argument COOR of D06ABF and D06ACF outside of its declared bounds; this could occur when the argument NVMAX is set to a value less than NVB+NVINT+12 for calls to D06ABF or to a value less than NVB+NVINT+13 for calls to D06ACF.
    Severity:   critical
    Problem since Mark:   FL20.0
    Fixed in Mark:   FL22.1
    Workaround:   Increase the value of NVMAX to be at least NVB+NVINT+12 when calling D06ABF and to be at least NVB+NVINT+13 when calling D06ACF. This will ensure that no array bound violations for COOR are possible.

  4. Routines: D06ABF D06ACF D06BAF
    Synopsis:   D06ABF, D06ACF, D06BAF crash if itrace > 1
    Description:   Setting argument ITRACE > 1 in calls of any of D06ABF, D06ACF, D06BAF causes failure with a run-time error due to record overflow - values are written into a string which is not big enough.
    Severity:   serious
    Problem since Mark:   FL20.0
    Fixed in Mark:   FL22.2
    Workaround:   Argument ITRACE is used to get printed information about a generated grid. The only workaround is to use values of ITRACE <= 1.

  5. Routines: E04VHF and others
    Synopsis:   User-supplied character strings containing spaces may cause garbled error messages
    Description:   Some routines produce error messages containing CHARACTER data that has been supplied through the argument list by the user. An example is E04VHF, where the XNAMES or FNAMES can be referred to in error messages. Having spaces in these strings confuses the internal error-message splitter, which splits on spaces. Thus, error messages returned by the routine may be garbled.
    Severity:   non-critical
    Problem since Mark:   Various (routine-dependent)
    Fixed in Mark:   FL23.0
    Workaround:   Make sure user-provided CHARACTER data is without spaces.

  6. Routines: E04XAA E04XAF
    Synopsis:   Attempt to write too many chars to a record in a routine called by E04XAF
    Description:   Call E04XAF or E04XAA with MSGLVL = 2 and some flavour of compiler runtime error will occur.
    Severity:   critical
    Problem since Mark:   FL20.0
    Fixed in Mark:   FL22.2
    Workaround:   Don't call E04XAF or E04XAA with MSGLVL = 2.

  7. Routine: E05JBF
    Synopsis:   Array-out-of-bounds error in routine called by E05JBF
    Description:   When using initialization method IINIT = 4 with infinite bounds BL and BU, and when the number of randomly-generated initialization points (which will always be between 3 and SDLIST) is greater than N, NaNs may be created in the initialization data, which makes the initializer enter into an infinite loop.
    Severity:   serious
    Problem since Mark:   FL22.0
    Fixed in Mark:   FL22.1
    Workaround:   Use finite bounds when IINIT = 4.

  8. Routines: G05YLF and G05YNF
    Synopsis:   Suspect quality of the direction numbers currently being used in the NAG Sobol generator with 8300 dimensions
    Description:   Doubt has been raised on the quality of the Joe and Kuo direction numbers currently being used in the NAG Sobol generator with 8300 dimensions (GENID=1)
    Severity:   critical
    Problem since Mark:   Unknown
    Fixed in Mark:   FL23.0
    Workaround:   It is recommended that you switch to the older set of direction numbers, designated Sobol A659 in the NAG documentation, and accessed using GENID = 2.

  9. Routine: H02CBF
    Synopsis:   Minimum lengths of real workspace displayed in error messages from H02CBF are incorrect
    Description:   If you provide too little real workspace to H02CBF the minimum value required will be displayed in the error message (if messaging is enabled). The value is too small by 4*MDEPTH + N. The documented values are correct.
    Severity:   non-critical
    Problem since Mark:   19.0
    Fixed in Mark:   FL22.4
    Workaround:   Add 4*MDEPTH + N to the minimum LWRK described in error messages, or use the values from the documentation.

  10. Routine: S30NAF
    Synopsis:   The constraint on argument S is incorrectly checked
    Description:   The documented constraint on argument S is correct, but the constraint was incorrectly checked. This made it impossible to use a value of S less than 1.0.
    Severity:   serious
    Problem since Mark:   FL22.0
    Fixed in Mark:   FL22.2
    Workaround:   None

Page generated on 11-May-2011 16:58:23
The Nag Fortran Library
NAG Technical Support
NAG Home Page