The revisions let you track differences between multiple versions of a post.
Each of the output codes should report an appropriate error message at the end of evaluation of the mxRun() statement.
This status element is returned from the optimizer (NPSOL).
A value of 0 means a successful optimization--no error returned.
A value of 1 means that an optimal solution was found, but that the sequence of iterates did not converge. There are several reasons this can happen, including starting at the correct values. It generally does not indicate a problem. These estimates can generally be considered correct solutions, so this code is labeled (Mx status GREEN).
A value of −1 means that the optimizer found itself stuck in a location where the objective function could not be calculated, and could not find a way out. This most often happens if the starting values make the calculation impossible.
A value of 2 or 3 means that the bounds or constraints, respectively, could not be satisfied.
A value of 4 means that the iteration limit was reached, with no solution found. You can use mxOptions() to set a higher iteration limit, or just run mxRun() using the output –it will restart from the most recent set of estimates, and make another run of the same number of iterations.
A value of 6 means that optimality conditions could not be reached, and the optimizer could find no way to improve the estimate. It often implies either a mistake in the model specification or starting values in an intractable range. The estimates resulting from this run are NOT optimal estimates, and should not be treated as solutions, so this code is labeled (Mx status RED).
Any other status codes should be reported.
output$status[] returns the error code from OpenMx, which is usually −1. This indicates that some aspect of the objective calculation could not be completed at the current location.
The third element of status provides detailed information on why the objective function could not be calculated. Examples are:
Note, while R coders often use the period character inside variable names, this is not legal in OpenMx, which uses this character to specify the container model for variables.
mxMatrix("Name", nrow=3,ncol=3,free=TRUE, values=.5,)
mxMatrix(type = "Full", nrow = 1, ncol = 1, free = FALSE, values = "l1", labels = "aa", lbound = 0, ubound = 2, name = "la"),
We try and convert the character "l1" to a numeric value, can't, return an NA... hence the error: NAs induced by coercion.
Warning messages: 1: In convertVFN(values, free, labels, lbound, ubound, nrow, ncol) : NAs introduced by coercion...