Overflow may occur if the function attempts to scale the polynomial coefficients.

In rare circumstances overflow may be observed if $\mathbf{scale}=\mathrm{Nag\_TRUE}$.

Non-critical

7

Set argument $\mathbf{scale}=\mathrm{Nag\_FALSE}$.

Heap corruption when $\mathbf{maxpts}$ constraint is unmet.

If function d01wcc is called with argument values that violate documented constraints, the function may terminate in an unfriendly way, such as a segmentation fault.

Critical

6

31.0

The workaround is to make sure that arguments passed do not violate documented constraints by using checks prior to calling d01wcc.

d06acc returns $\mathbf{fail}\mathbf{.}\mathbf{code}=\mathbf{NE\_MESH\_ERROR}$error for some boundary meshes due to an internal scaling issue.

d06acc returns $\mathbf{fail}\mathbf{.}\mathbf{code}=\mathbf{NE\_MESH\_ERROR}$error for some boundary meshes due to an internal scaling issue.

Non-critical

7

28.4

Scale input boundary mesh prior to calling d06acc so that $\mathbf{}\mathbf{}=0$and $\mathbf{}\mathbf{}=1$.

e01shc will occasionally incorrectly identify a point as being outside the region defined by the interpolant.

e01shc will occasionally incorrectly identify a point as being outside the region defined by the interpolant. This leads to the function value being extrapolated rather than interpolated and can lead to incorrect results.

Non-critical

26.0

27.1

None.

In some cases, the solver hangs indefinitely at an iteration.

In some cases, when certain variable lower bounds are not present, the solver might hang indefinitely due to an infinite loop during the line search stage.

Critical

27.1

30.3

None.

and $\mathbf{rinfo}$were not correctly filled by the presolver.

The arrays $\mathbf{stats}$and $\mathbf{rinfo}$were not correctly filled when the problem was entirely solved by the presolver. It now returns the correct values.

Non-critical

26.1

27

Don't rely on $\mathbf{rinfo}\left[0\right],\mathbf{rinfo}\left[1\right]$to hold the primal and dual objective in this case and recompute it as $c^{\prime }x$and $by$, respectively.

e04mtc does not report the correct solution when $3$or more columns are proportional to each other in the constraint matrix.

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.

Non-critical

26.1

27

A workaround is to disable the more complex presolve operations by setting the optional parameter $\mathbf{LP\; Presolve}=\mathrm{BASIC}$. This may slow down the solver depending on the problem.

In some very rare cases, the solution reported presents big violations on a small number of linear constraints.

In some very rare cases, the solution reported presents big violations on a small number of linear constraints.

Non-critical

26.1

27.1

A workaround is to deactivate the more complex presolver operations with the optional parameter $\mathbf{LP\; Presolve}=\mathrm{BASIC}$.

In some very rare cases, e04mtc reports problem infeasibility for a feasible problem.

In some very rare cases, the solver reports problem infeasibility when there are numerical difficulties.

Non-critical

26.1

28.6

Unfortunately there is no convenient workaround.

In some very rare cases, at presolve phase the solver declares unboundedness on a bounded problem.

In some very rare cases, especially when there are a large amount of singleton variables, the solver might report unbounded error message on a bounded problem.

Non-critical

26.1

29.0

A workaround is to deactivate the more complex presolver operations with the optional parameter $\mathbf{LP\; Presolve}=\mathrm{BASIC}$. This may slow down the solver depending on the problem.

In some cases the solver declares dual infeasibility during presolving for feasible and bounded problems.

For a bounded problem, the solver reports dual infeasibility during dominated columns removal at the presolving stage.

Non-critical

26.1

29.1

A workaround is to deactivate the more complex presolver operations with the optional parameter $\mathbf{LP\; Presolve}=\mathrm{BASIC}$. This may slow down the solver depending on the problem.

Infeasible bounds defined by e04rjc of a variable are ignored and infeasibility is not reported.

When infeasible bounds are defined by e04rjc for a variable, instead of reporting problem infeasibility, the bounds are overridden and wrong solution may be reported.

Non-critical

26.1

27.1

A workaround is to deactivate the more complex presolver operations with the optional parameter $\mathbf{LP\; Presolve}=\mathrm{BASIC}$for e04mtc and $\mathbf{SOCP\; Presolve}=\mathrm{BASIC}$for e04ptc.

Optional parameters $\mathbf{List}$and $\mathbf{Nolist}$are not handled correctly.

Functions e04nrc, e04vkc and e04wec do not handle optional parameters $\mathbf{List}$and $\mathbf{Nolist}$correctly. Specifying $\mathbf{List}$does not alter the behaviour of subsequent functions in the suite, and specifying $\mathbf{Nolist}$erroneously reports an error.

Non-critical

8

27.3

Function e04nsc should be used instead to set optional parameters $\mathbf{List}$or $\mathbf{Nolist}$.

Information about the last constraint might not be printed.

If the problem has a nonlinear objective function without a linear part and $\mathbf{objrow}<\mathbf{nf}$, the last constraint is not printed in the final information about the solution (Rows section).

Non-critical

8

26

None.

When $\mathbf{fail}\mathbf{.}\mathbf{code}=\mathbf{NE\_REF\_MATCH}$is returned, the expected value of $\mathbf{nvar}$in the error message may be wrongly reported.

When $\mathbf{fail}\mathbf{.}\mathbf{code}=\mathbf{NE\_REF\_MATCH}$is returned, the expected value of $\mathbf{nvar}$in the error message may be wrongly reported. This incorrect behaviour may occur when the internal solver works with a different number of variables than what is declared during handle initialization, e.g., when some variables are fixed by the user.

Non-critical

28.3

30.2

None.

Multithreaded versions of the functions f11bec, f11bsc, f11gec and f11gsc may produce slightly different results when run on multiple threads.

Multithreaded versions of the functions f11bec, f11bsc, f11gec and f11gsc may produce slightly different results when run on multiple threads, e.g., the number of iterations to solution and the computed matrix norms and termination criteria reported by the associated monitoring functions. A bug affecting f11bec and f11gec has been fixed, and parallel vector dot products have been modified in all functions to improve consistency of results.

Non-critical

26

27.1

None.

f16qec and f16tec reference diagonal elements when unit diagonal entries are assumed.

f16qec and f16tec reference and copy diagonal elements when unit diagonal entries are assumed.

Critical

7

28

Nothing needs to be done unless diagonal entries of the target matrix contain useful data prior to a call of f16qec or f16tec with $\mathbf{diag}=\mathrm{Nag\_UnitDiag}$, in which case the useful data should be saved and copied back to the diagonal of the target matrix after the call to either f16qec or f16tec.

f16qfc, if called with $\mathbf{pdb}$that violates minimum contraints, will produce a segmentation fault.

f16qfc, if called with $\mathbf{pdb}$that violates minimum contraints, will produce a segmentation fault.

Critical

7

28

Call f16qfc with $\mathbf{pdb}$that meets the documented minimum contraint.

Incorrect Frobenius norm returned in some cases.

When calling one of the functions: f16rdc, f16rec, f16udc, f16uec, f16ufc and f16ugc with $\mathbf{order}=\mathrm{Nag\_RowMajor}$and $\mathbf{norm}=\mathrm{Nag\_FrobeniusNorm}$, the returned norm can be incorrect.

Critical

23

28

These functions will return the correct norm if the $\mathbf{order}$argument is set to $\mathrm{Nag\_ColMajor}$and the $\mathbf{uplo}$argument is flipped, i.e., from $\mathrm{Nag\_Upper}$to $\mathrm{Nag\_Lower}$or vice versa.

f16smc returns wrong update of $A$when $\mathbf{a}$is stored in row major order and $\mathbf{y}$is to be conjugated.

When f16smc is called with $\mathbf{order}=\mathrm{Nag\_RowMajor}$and $\mathbf{conj}=\mathrm{Nag\_Conj}$, $A$is updated as though $\mathbf{conj}=\mathrm{Nag\_NoConj}$.

Critical

8

28

Call f16smc with $\mathbf{conj}=\mathrm{Nag\_NoConj}$and conjugate $\mathbf{y}$prior to call.

f16tac stops program execution when called with $\mathbf{pda}<\mathbf{n}$.

f16tac, when called with $\mathbf{pda}<\mathbf{n}$does not return error code $\mathbf{fail}\mathbf{.}\mathbf{code}=\mathbf{NE\_INT\_2}$, but terminates program execution.

Critical

8

28

Call f16tac with $\mathbf{pda}\ge \max \left(1,\mathbf{n}\right)$.

f16tfc returns incorrect results when computing a transposed copy of a matrix.

f16tfc returns incorrect results when computing a transposed copy of a matrix.

Critical

7

28

Call f01cwf with $\mathbf{alpha}=\text{one}$and $\mathbf{beta}=\text{zero}$; for row-ordered matrices, $\mathbf{m}$and $\mathbf{n}$should be switched.

If the first row or column of the weight matrix $\mathbf{h}$consists only of zeros, then the function will fail to find the nearest correlation matrix for that weight matrix.

An error can occur when the first row or column of the weight matrix $\mathbf{h}$consists only of zeros, then the function will fail to find the nearest correlation matrix for that weight matrix.

Critical

25

30.1

The workaround is to apply a small weight (relative to other non-zero weights given in $\mathbf{h}$) to one of the elements in the first row/column.

When $\mathbf{mean}=\mathrm{Nag\_AboutZero}$, output arguments $\mathbf{a}$and $\mathbf{a\_serr}$are not initialized.

When $\mathbf{mean}=\mathrm{Nag\_AboutZero}$, output arguments $\mathbf{a}$and $\mathbf{a\_serr}$are not initialized. These values relate to a regression constant that is only relevant in the $\mathbf{mean}=\mathrm{Nag\_AboutMean}$case. However, the code for $\mathbf{mean}=\mathrm{Nag\_AboutZero}$should initialize them to $0.0$. This was not done, allowing previously set values or random results to be erroneously returned.

Non-critical

7

27.3

The safest solution is to manually set these to $0.0$(but only in the $\mathbf{mean}=\mathrm{Nag\_AboutZero}$case) immediately after calling this function.

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 $\mathbf{Subject}$term.

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 $\mathbf{Subject}$term.

V1 + V2 / SUBJECT = V3
V4 + V5 / SUBJECT = V6

V1 + V2
V4 + V5 / SUBJECT = V6

V1 + V2

Critical

27

27.1

A workaround to this issue is to always supply a $\mathbf{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.

Memory leak reported from CL interface on Windows from checking tools.

A during-execution memory leak can be reported from checking tools on Windows when running a multi-threaded program calling d01xbc.

Critical

5

28

Ignore warnings.

The wrong value for $\mathbf{p}$is returned when $\mathbf{aa2}$is large.

In g08ckc and g08clc the value returned for the upper tail probability $\mathbf{p}$is wrong when the calculated Anderson-Darling test statistic $\mathbf{aa2}$is large. In the case of g08ckc, when $\mathbf{aa2}>153.4677$the returned value of $\mathbf{p}$should be zero; in the case of g08clc, when $\mathbf{aa2}>10.03$the returned value of $\mathbf{p}$should be $\le \exp \left(-14.360135\right)$.

Critical

23

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);

g13fac may return a negative value as the estimate of the last $\beta$parameter (i.e., ${\beta }_p$) for a subset of models.

g13fac can result in a negative value for the estimate of the last $\beta$parameter (i.e., ${\beta }_p$) or, if $p=0$, the last $\alpha$parameter (i.e., ${\alpha }_q$).

Critical

7

27

None

When $\mathbf{what}=\mathrm{Nag\_VarianceComponent}$the information returned in $\mathbf{plab}$and/or $\mathbf{vinfo}$may be incorrect.

The information returned in $\mathbf{plab}$and/or $\mathbf{vinfo}$may be incorrect in cases where $\mathbf{what}=\mathrm{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.

Non-critical

27.0

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.

$\mathbf{rinfo}$ was not correctly filled with the primal objective value and the dual objective bound when fixed variable presents.

Primal objective value and the dual objective bound were not returned correctly in $\mathbf{rinfo}$due to the removal of fixed variables from the model. It now returns the correct values.

Non-critical

29.3

31.0

Recompute primal objective value as $c\prime x$.

In some cases, solver returns inaccurate solution when there are binary variables.

When there are binary variables, the accuracy of the solution will be influenced by the initial values. The solver could return inaccurate solution.

Non-critical

25

29.1

The work around is to use integer variables with $0$and $1$as lower and upper bound, respectively.

Thread Local Storage default limit was exceeded for delay loaded shared library.

A fair amount of thread local storage had been allocated by an auxiliary function which has now been updated to use a very small amount of thread local storage. Prior to the update, this only affected the case where the shared version of the Nag Library was delay loaded, since this assumed a small default maximum amount of thread local storage, which was in fact exceeded.

Non-critical

26.1

28.6

None.