Known Issues for the NAG Library for .NET
This document reflects all reported and resolved issues that affect recent releases of the NAG Library for .NET.
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 method a00aa( ).
For issues that affect releases of other interfaces, please also see
Order the issues by
Synopsis | Internal buffer overflow in e04fc. |
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 e04fc, 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 marks. (Note: the grade can be observed by setting and using E04FDZ).
How the problem manifests:
Optimization terminates prematurely, usually with . Note: an exit with does not on its own indicate that an optimization is affected by the bug.
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 e04fc significantly.
|
Severity | Non-critical |
Issue Since Mark | 1 |
Fixed at Mark | 2 |
Workaround | There is no practical workaround. |
Synopsis | In very rare cases, the algorithm used by e04lb may become trapped in an infinite loop. |
Description | The method might lock itself in an infinite loop 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 | 1 |
Workaround | Unfortunately there is no convenient workaround. |
Synopsis | Actual array size required is underestimated. |
Description | Sometimes the suggested array size returned in parameter is underestimated. |
Severity | Critical |
Issue Since Mark | 1 |
Fixed at Mark | 2 |
Workaround | Increase the size of array and the value of accordingly. |
Synopsis | Insufficient space in array might lead to a crash. |
Description | Insufficient space in array might lead to a crash, this is particularly likely if . |
Severity | Non-critical |
Issue Since Mark | 1 |
Workaround | Provide sufficient size as recommended in the documentation. |
Synopsis | When the objective function has no separated linear part, using user-defined names for variables and constraints might lead to a crash. |
Description | When the objective function only has the nonlinear part defined without a separated linear part, the solver might crash when trying to read user-defined names for variables and constraints. |
Severity | Critical |
Issue Since Mark | 1 |
Workaround | Unfortunately there is no convenient workaround. The only way to avoid this crash is to not specify names for variables and constraints. |
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 | 1 |
Workaround | None. |
Synopsis | g13fa may return a negative value as the estimate of the last parameter (i.e., ) for a subset of models. |
Description | g13fa can result in a negative value for the estimate of the last parameter (i.e., ) or, if , the last parameter (i.e., ).
This issue only affects a subset of models that have normally distributed errors and do not include an asymmetry term.
If the method did not return a negative value as the estimate of the last parameter (or, if , the last parameter), then that particular model was not affected by the issue.
|
Severity | Critical |
Issue Since Mark | 1 |
Workaround | None |
Synopsis | Misleading error associated with an undocumented error exit can be produced. |
Description | A puzzling error message may be produced with an undocumented error exit if workspace sizes are not sufficiently large to accommodate an internal partition of the workspace that meets the requirements of the problem. |
Severity | Non-critical |
Issue Since Mark | 1 |
Fixed at Mark | 2 |
Workaround | Increase the size of workspace arrays and and their dimensions and . |