Known Issues for the NAG C Library www.nag.com

This document reflects all reported and resolved issues that affect various releases of the NAG C Library up to Mark 26.1.

Some of these issues 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 issue is provided wherever possible.

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

c02agc

Synopsis	Overflow may occur if the function attempts to scale the polynomial coefficients.
Description	In rare circumstances overflow may be observed if $scale = Nag_TRUE$ .
Severity	Non-critical
Issue Since Mark	7
Workaround	Set argument $scale = Nag_FALSE$ .

c09aac, c09ccc and c09cdc

Synopsis	Multi-level wavelets cannot handle periodic end extension.
Description	When $mode = Nag_Periodic$ and $wtrans = Nag_MultiLevel$ the multi-level wavelet transform functions do not work properly if $n$ is not a power of 2.
Severity	Non-critical
Issue Since Mark	9
Fixed at Mark	23
Workaround	The option combination of a multi-level wavelet transform using a periodic end extension is currently disallowed; a call to the initialization function c09aac 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).

d01esc

Synopsis	Initialization and option setting does not work when using the long name.
Description	Initialization and option setting for the sparse grid function nag_quad_md_sgq_multi_vec (d01esc) using nag_quad_opt_set (d01zkc) does not work when using the long name nag_quad_md_sgq_multi_vec in the option string. It does work when using the short name d01esc in the option string.
Severity	Non-critical
Issue Since Mark	25
Fixed at Mark	25.1
Workaround	Initializing and setting options for nag_quad_md_sgq_multi_vec (d01esc) via calls to nag_quad_opt_set (d01zkc) should use option strings containing the short name d01esc rather than the long name.

d01esc

Synopsis	Segmentation faults when optional parameter $Index Level$ is set to a value greater than $m_{q}$ .
Description	Segmentation faults or other array bound violation problems may occur if the value of $Index Level$ (set via a call to d01zkc) is greater than $m_{q}$ , the maximum level of the underlying quadrature rule.
Severity	Critical
Issue Since Mark	25
Fixed at Mark	25.4
Workaround	Do not set $Index Level$ to more than 9 when using Gauss–Patterson or more than 12 when using Clenshaw–Curtis.

d01esc

Synopsis	$Quadrature Rule = GP$ is not accepted as a valid option.
Description	When setting the quadrature rule for d01esc using the d01zkc option setting function, the documented choice $Quadrature Rule = GP$ is not recognised as a valid option and an error is reported.
Severity	Non-critical
Issue Since Mark	25
Fixed at Mark	25.4
Workaround	The alternatives $Quadrature Rule = Gauss-Patterson or GPATT$ may be used instead. Note: Gauss-Patterson is the default choice for the quadrature rule in d01esc, so in general it will not be necessary to specify this option.

d06aac, d06abc and d06acc

Synopsis	Stack size or thread safety problems may be observed with some d06 functions.
Description	d06aac, d06abc and d06acc contain large local arrays that may cause stack size and/or thread safety problems.
Severity	Critical
Issue Since Mark	7
Fixed at Mark	23.3
Workaround	Do not use these functions in a multithreaded environment. For serial execution, set stack size limit to 10MB or greater.

d06abc

Synopsis	Although the documented constraint on $nvmax$ is $nvmax \geq nvb + nvint$ , the actual required minimum for $nvmax$ is $nvb + nvint + 12$ . For some small scale problems, setting $nvmax = nvb + nvint$ will give unpredictable results and could produce a segmentation fault.
Description	Although the documented constraint on $nvmax$ is $nvmax \geq nvb + nvint$ , the actual required minimum for $nvmax$ is $nvb + nvint + 12$ . For some small scale problems, setting $nvmax = nvb + nvint$ will give unpredictable results and could produce a segmentation fault. The problem is remedied by setting $nvmax = nvb + nvint + 12$ and ensuring that the arrays $coor$ and $conn$ are correspondingly large enough.
Severity	Critical
Issue Since Mark	7
Fixed at Mark	26
Workaround	Set $nvmax \geq nvb + nvint + 12$ ; allocate the arrays $coor$ and $conn$ using this value of $nvmax$ .

e01sgc, e01shc, e01tgc and e01thc

Synopsis	The algorithm underlying interpolation functions e01sgc, e01shc, e01tgc and e01thc was modified at Mark 26 and Mark 26.1; different results will be obtained when using these functions than previously.
Description	The algorithm underlying interpolation functions e01sgc, e01shc, e01tgc and e01thc was modified at Mark 26 to improve perceived deficiencies. In particular, at earlier library Marks the evaluation functions would not attempt to return any useful result if an evaluation point was not close enough to any of the original data points, and this issue was addressed at Mark 26. At Mark 26.1 further work was done on the functions because they had been found not to work well on gridded data sets (as opposed to the random data sets that they are primarily intended for). It should be noted that because of the various underlying changes to the functions, the precise results returned from Mark 26 onwards will not usually be identical to those before Mark 26.
Severity	Non-critical
Issue Since Mark	26
Fixed at Mark	26.1
Workaround	Not applicable.

e02gac

Synopsis	Ill-conditioned data sets may cause e02gac to get stuck in an infinite loop.
Description	Certain ill-conditioned data sets could cause e02gac to get stuck in an infinite loop.
Severity	Critical
Issue Since Mark	7
Fixed at Mark	26
Workaround	As a workaround, it may be possible to avoid the infinite loop by reordering the points in the input data.

e04dgc

Synopsis	e04dgc returns wrong gradient values in $g$ .
Description	e04dgc prints gradient values correctly, but returns the wrong values in argument $g$ .
Severity	Non-critical
Issue Since Mark	7
Fixed at Mark	25
Workaround	In $objfun$ , when $g$ is set, push these values into the $user$ structure. Following the call to e04dgc the correct values for $g$ can then be obtained from $user$ .

e04fcc

Synopsis	Internal buffer overflow in e04fcc.
Description	When the grade of the optimization problem drops to zero, an internal buffer overflow occurs. This destroys some of the internal state of the optimizer, typically causing it to stop prematurely. Scope of the problem: If the grade of the optimization problem is non-zero on exit from e04fcc, then the bug is not triggered and that particular optimization is unaffected. If the grade is zero on exit, then the optimization is affected in all supported CL marks. How the problem manifests: Optimization terminates prematurely, usually with warning $fail . code = NW_COND_MIN$ . Note: an exit with $fail . code = NW_COND_MIN$ does not on its own indicate that an optimization is affected by the bug. If $m$ is sufficiently larger than $n$ , the gradient vector $g$ becomes partly or wholly zero in the iteration following the grade dropping to zero. (The gradient vector can be monitored through a user-installed print function). Severity: Since the solver is typically close to convergence when the grade drops to zero, the returned solution is usually pretty good. The bug fix is unlikely to improve the results of e04fcc significantly.
Severity	Non-critical
Issue Since Mark	8
Fixed at Mark	24.2
Workaround	There is no practical workaround.

e04lbc

Synopsis	In very rare cases, the algorithm used by e04lbc may become trapped in an infinite loop.
Description	The function might loop unnecessarily and finish with $fail . code = NW_TOO_MANY_ITER$ when a variable lying on the boundary is cyclically added and removed to/from free variables. This can happen only at points with indefinite Hessian and very small projected gradients when one variable is lying on the boundary and another one is very close to it.
Severity	Critical
Issue Since Mark	7
Fixed at Mark	25
Workaround	Unfortunately there is no convenient workaround.

e04mtc

Synopsis	$stats$ and $rinfo$ were not correctly filled by the presolver.
Description	The arrays $stats$ and $rinfo$ were not correctly filled when the problem was entirely solved by the presolver. It now returns the correct values. The optional parameter $Print Solution$ now correctly writes the linear constraints dual variables when no bounds are defined on the variables.
Severity	Non-critical
Issue Since Mark	26.1
Fixed at Mark	27
Workaround	Don't rely on $rinfo [0], rinfo [1]$ to hold the primal and dual objective in this case and recompute it as $c^{'} x$ and $b y$ , respectively.

e04mtc

Synopsis	e04mtc does not report the correct solution when $3$ or more columns are proportional to each other in the constraint matrix.
Description	e04mtc does not report the correct solution when $3$ or more columns are proportional to each other in the constraint matrix. In such a case, the solution reported may be infeasible.
Severity	Non-critical
Issue Since Mark	26.1
Fixed at Mark	27
Workaround	A workaround is to disable the more complex presolve operations by setting the optional parameter $LP Presolve = BASIC$ . This may slow down the solver depending on the problem.

e04nqc, e04vhc and e04wdc

Synopsis	Internal file overflow.
Description	If you set a $New Basis File$ in e04nqc, e04vhc and e04wdc and your total problem size ( $n + m$ , $n + nf$ or $n + nclin + ncnln$ , respectively) is greater than 80 you will experience an internal buffer overflow and possible program crash.
Severity	Critical
Issue Since Mark	9.4
Fixed at Mark	23
Workaround	Unfortunately there is no convenient workaround. The only way to avoid this crash is to not specify a $New Basis File$ or to have a small enough problem.

e04stc

Synopsis	e04stc returns Lagrangian multipliers in the wrong order.
Description	The Lagrangian multipliers returned in $u$ are in the wrong order: multipliers for lower bound and upper bound of non-box constraints are swapped; nonlinear constraints multipliers are stored before the linear ones.
Severity	Non-critical
Issue Since Mark	26
Fixed at Mark	26.1
Workaround	The order described in the documentation is now used.

e04unc

Synopsis	An inner optimization step might be unnecessarily resolved in certain cases.
Description	If the solver is run in the mode when some (or all) derivatives might be missing ( $options . obj_deriv = Nag_FALSE$ or $options . con_deriv = Nag_FALSE$ ), however, all derivatives are provided, the solver might trigger an extra resolve of the inner optimization step if it detects numerical difficulties. This extra step normally switches derivative approximations to central differences and thus is aimed to improve stability of the problem, however, in this case it doesn't change anything (all derivatives are provided by the user and no derivative approximation takes place) and thus is unnecessary.
Severity	Non-critical
Issue Since Mark	7
Fixed at Mark	26.1
Workaround	You might want to set $options . obj_deriv = Nag_TRUE$ and $options . con_deriv = Nag_TRUE$ if all derivatives are provided.

e04unc

Synopsis	A possible buffer overflow in the printing of the derivative checker of e04unc.
Description	If $options . verify_grad$ is set to a full check of the objective function and/or the constraints ( $options . verify_grad = Nag_CheckObj, Nag_CheckObjCon, Nag_CheckCon$ , ...) and $options . print_deriv = Nag_D_Full$ and the checked function has zero elements in the derivatives, internal buffer might overflow which might lead to a crash.
Severity	Critical
Issue Since Mark	7
Fixed at Mark	26
Workaround	To avoid the problem, use $options . print_deriv = Nag_D_Sum or Nag_D_NoPrint$ .

e04vhc

Synopsis	Information about the last constraint might not be printed.
Description	If the problem has a nonlinear objective function without a linear part and $objrow < nf$ , the last constraint is not printed in the final information about the solution (Rows section).
Severity	Non-critical
Issue Since Mark	8
Fixed at Mark	26
Workaround	None.

e04vhc and others

Synopsis	User-supplied character strings containing spaces may cause garbled error messages.
Description	Some functions produce error messages containing character data that has been supplied through the argument $List$ by the user. An example is e04vhc, 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 function may be garbled.
Severity	Non-critical
Issue Since Mark	9
Fixed at Mark	23
Workaround	Make sure user-provided character data is without spaces

e05ucc

Synopsis	An unhelpful error exit is returned if e05ucc is called with incorrectly initialized optional parameter arrays $iopts$ and $opts$ .
Description	Function e05ucc returns $fail . code = NE_INTERNAL_ERROR$ if e05ucc is called without previously having called e05zkc with argument ‘Initialize = e05ucc’.
Severity	Non-critical
Issue Since Mark	23
Fixed at Mark	24
Workaround	Call e05zkc with argument ‘Initialize = e05ucc’ before calling e05ucc.

f02wec

Synopsis	Function f02wec may fail to compute any results, but with no error flag set.
Description	Certain combinations of arguments $wantp$ and $wantq$ together with their associated output arrays $q$ and $pt$ can cause f02wec to fail to compute any results, but with no error flag set. Specifically, the function documentation states that in some circumstances array argument $q$ may be a NULL pointer (in which case the left hand singular vectors, if required, are stored in array $a$ ). However, an auxiliary function called by f02wec checks whether $q$ is NULL, and if so f02wec silently fails.
Severity	Critical
Issue Since Mark	25
Fixed at Mark	26
Workaround	Always supply a non-NULL array argument $q$ even if the documentation for f02wec states that a NULL pointer is allowed. Alternatively, since f02wec is scheduled for withdrawal at Mark 26, modify your code to use the recommended replacement function f08kbc.

f02xec

Synopsis	Function f02xec may fail to compute any results, but with no error flag set.
Description	Certain combinations of arguments $wantp$ and $wantq$ together with their associated output arrays $q$ and $ph$ can cause f02xec to fail to compute any results, but with no error flag set. Specifically, the function documentation states that in some circumstances array argument $q$ may be a NULL pointer (in which case the left hand singular vectors, if required, are stored in array $a$ ). However, an auxiliary function called by f02xec checks whether $q$ is NULL, and if so f02xec silently fails.
Severity	Critical
Issue Since Mark	25
Fixed at Mark	26
Workaround	Always supply a non-NULL array argument $q$ even if the documentation for f02xec states that a NULL pointer is allowed. Alternatively, since f02xec is scheduled for withdrawal at Mark 26, modify your code to use the recommended replacement function f08kpc.

f16rbc and f16ubc

Synopsis	f16rbc and f16ubc return 0 if $kl$ or $ku$ is 0, instead of the correct norm. $pdab$ is incorrectly forced to be at least $m$ when $m = n$ .
Description	f16rbc and f16ubc mistakenly make a quick return if $kl$ or $ku$ is 0, instead of computing the correct value for the requested norm. Also, $pdab$ is incorrectly forced to be at least $m$ when $m = n$ .
Severity	Critical
Issue Since Mark	9.1
Fixed at Mark	23
Workaround	If $kl$ or $ku$ is 0, use the general matrix-norm functions f16rac or f16uac, with the input matrix in full storage. If $m = n$ , make sure that $pdab \geq m$ .

g02anc

Synopsis	The returned matrix is not a valid correlation matrix.
Description	The algorithm computes an incorrect value for $alpha$ . Thus the returned matrix is not positive definite as stated, and is not a valid correlation matrix.
Severity	Critical
Issue Since Mark	25
Fixed at Mark	25.3
Workaround	Unfortunately there is no convenient workaround.

g02hfc

Synopsis	Incorrect results are returned when performing a Mallows type regression.
Description	Incorrect results are returned when performing a Mallows type regression, averaging over residuals.
Severity	Non-critical
Issue Since Mark	7
Fixed at Mark	26.1
Workaround	None.

g02jcc

Synopsis	Segmentation fault caused by access past the end of an array.
Description	An error can occur when there are multiple blocks of random variables, at least one with a subject variable and at least one without. The error can only occur when the block with the subject variable occurs first in $rndm$ .
Severity	Critical
Issue Since Mark	23
Fixed at Mark	25
Workaround	Ensure that blocks without subject variables appear in $rndm$ before those with subject variables.

g02jdc

Synopsis	In very rare cases, the function may become trapped in an infinite loop.
Description	The function was affected by a bug in the underlying solver e04lbc (modified Newton method). In very rare cases the solver might get into an infinite loop.
Severity	Critical
Issue Since Mark	9
Fixed at Mark	25
Workaround	The bug can be avoided by switching to the other optimizer (SQP method e04ucc, $iopt [4] = 1$ ).

g02jfc

Synopsis	A segmentation fault is likely to occur if a model with multiple random statements is supplied to the function, where at least one of those statements does not have a $Subject$ term.
Description	A segmentation fault is likely to occur if a model with multiple random statements is supplied to the function, where at least one of those statements does not have a $Subject$ term. For example, a model specified using: V1 + V2 / SUBJECT = V3 V4 + V5 / SUBJECT = V6 would not trigger the error, but one specified using: V1 + V2 V4 + V5 / SUBJECT = V6 would. The error is not triggered when there is only a single random statement, so a model specified using just V1 + V2 will not trigger the error.
Severity	Critical
Issue Since Mark	27
Fixed at Mark	27.1
Workaround	A workaround to this issue is to always supply a $Subject$ term. If the required model is of the form: V1 + V2 V4 + V5 / SUBJECT = V6 then you can specify an equivalent model by using: V1 + V2 / SUBJECT = DUMMY V4 + V5 / SUBJECT = V6 where the variable DUMMY has a single level, and always takes a value of one. This will require adding the variable DUMMY to your dataset.

g02qgc

Synopsis	Returns incorrect results when $ntau > 1$ and user supplied initial values for $b$ are being used.
Description	If $ntau > 1$ , the optional parameter $Calculate Initial Values = NO$ is set, and the rows of array $B$ are not all identical, then the results returned by g02qgc are incorrect.
Severity	Critical
Issue Since Mark	23
Fixed at Mark	24
Workaround	Rather than call the function once with $ntau > 1$ , call the function multiple times with $ntau = 1$ , analysing a different value of $tau$ on each call.

g02zkc

Synopsis	Unexpected $fail . code = NE_INTERNAL_ERROR$ s in g02zkc.
Description	g02zkc may report a $fail . code = NE_INTERNAL_ERROR$ error for some valid minimum abbreviations of option names supplied in the input argument $optstr$ , e.g., when using ‘DEF’ instead of ‘Defaults’.
Severity	Non-critical
Issue Since Mark	23
Fixed at Mark	26
Workaround	Use the full options name, e.g., specify ‘Defaults’ rather than ‘Def’.

g08ckc and g08clc

Synopsis	The wrong value for $p$ is returned when $aa2$ is large.
Description	In g08ckc and g08clc the value returned for the upper tail probability $p$ is wrong when the calculated Anderson-Darling test statistic $aa2$ is large. In the case of g08ckc, when $aa2 > 153.4677$ the returned value of $p$ should be zero; in the case of g08clc, when $aa2 > 10.03$ the returned value of $p$ should be $\leq \exp (- 14.360135)$ .
Severity	Critical
Issue Since Mark	23
Workaround	Workaround for g08ckc: Call g08ckc(...); If (aa2 > 153.4677) p = 0.0; Workaround for g08clc: Call g08clc(...); If (aa2 > 10.03) p = exp(-14.360135);

g10cac

Synopsis	The methods $smoother = Nag_3RSSH and Nag_4253H$ were implemented in reverse.
Description	g10cac implements two methods of smoothing, $smoother = Nag_3RSSH and Nag_4253H$ . Unfortunately they were implemented in reverse, so if you ask for $smoother = Nag_3RSSH$ you get $smoother = Nag_4253H$ and vice versa.
Severity	Critical
Issue Since Mark	7
Fixed at Mark	25
Workaround	Use $smoother = Nag_3RSSH$ if you want results for $smoother = Nag_4253H$ , and vice versa.

g13fac

Synopsis	g13fac may return a negative value as the estimate of the last $β$ parameter (i.e., $β_{p}$ ) for a subset of models.
Description	g13fac can result in a negative value for the estimate of the last $β$ parameter (i.e., $β_{p}$ ) or, if $p = 0$ , the last $α$ parameter (i.e., $α_{q}$ ). This issue only affects a subset of models that have normally distributed errors and do not include an asymmetry term. If the function did not return a negative value as the estimate of the last $β$ parameter (or, if $p = 0$ , the last $α$ parameter), then that particular model was not affected by the issue.
Severity	Critical
Issue Since Mark	7
Fixed at Mark	27
Workaround	None

g22ydc

Synopsis	When $what = Nag_VarianceComponent$ the information returned in $plab$ and/or $vinfo$ may be incorrect.
Description	The information returned in $plab$ and/or $vinfo$ may be incorrect in cases where $what = Nag_VarianceComponent$ and the underlying linear mixed effects regression model has a random variable, with a single level (so either binary or continuous), that only takes the value zero.
Severity	Non-critical
Issue Since Mark	27.0
Workaround	The work around is to drop the term from the model, as it does not contribute. For example, if the random part of your model was specified as: V1 + V2 / SUBJECT=V3 and the variable V2 was a continuous variable, that only takes a value of zero in the data, then this is equivalent to re-specifying the model using: V1 / SUBJECT=V3.

Known Issues for the NAG C Library

Known Issues

About

Support

Resources

Purchase

Search form

Known Issues for the NAG C Library

Known Issues