OpenMx Error Messages

Hello,

I got several code 6 when running simulations. Some of those cases have a near singular estimated hessian, though the calculated hessian is fine. Is this the source of non-convergence? Would it work to re- run the data with the parameter estimates as initial values? Is it possible to have the optimizer use the calculated hessian all the time?

Thanks

- Hao

Question from a user: What is code blue, what should one do, and where is it documented?

In model 'common_path_constraint_ACE' NPSOL returned a non-zero status code 4. The major iteration limit was reached (Mx status BLUE).

Dear all,

Hi,

As I am doing simulations, I can see many warning messages from NPSOL. It seems that @output$status is the place to look for those different convergence types. I can see (from a successful run) that "status" has three empty slots. May I know what the "status" will be for an unsuccessful/non-conventional convergence? Is there any reference or documentation on this topic? Thanks.

- Hao

I'm trying to use a couple of nifty functions that I cribbed from a script from the Twin Workshop. When I try to use
formatOutputMatrices or tableFitStatistics I get an error message saying R "could not find function".

Suggestions?

Thanks,
Carol

Hi again,

I'm trying to run an ordinal model with age and sex as covariates. The ACE model seems to run Ok, but then I receive the following error with an AE model:

> univAEOrdFit <- mxRun(univAEOrdModel, intervals=T)
Running univAEOrd
Error: The job for model 'univAEOrd' exited abnormally with the error message: Objective function returned an infinite value.
In addition: Warning message:
In runHelper(model, frontendStart, intervals, silent, suppressWarnings, :
Not calculating confidence intervals because of error status.

The attached code generates the following error message:


> first <- mxRun(model)
Running Alg