You are here

Handle row of missing continuous data in joint FIML objective

See https://openmx.ssri.psu.edu/thread/1111

Reporter: 
Created: 
Tue, 10/25/2011 - 12:43
Updated: 
Thu, 12/10/2015 - 17:24

Comments

This still causes an error.

Running ACE
Error: The job for model 'ACE' exited abnormally with the error message: MxComputeGradientDescent: fitfunction ACE.fitfunction evaluated to 1.#INF00 ()
In addition: Warning message:
In model 'ACE' Optimizer returned a non-zero status code 6. The model does not satisfy the first-order optimality conditions to the required accuracy, and no improved point for the merit function could be found during the final linesearch (Mx status RED)

Should be closed now?
The error was just not telling people the starting values were infeasible?

Perhaps a slight bug still. Bates is right that the starting values are infeasible. This is returned correctly now. However, with intervals=TRUE it currently returns the error

Error in runHelper(model, frontendStart, intervals, silent, suppressWarnings,  : 
  MxComputeConfidenceInterval: reference fit is not finite

because it tries to compute confidence intervals even though there's a status 10 and the base fit function value is INF/NaN.

> However, with intervals=TRUE it currently returns the error

Should be fixed with 3e864c52

Fixed.