You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am running into an issue while running a latent growth mixture model (2 classes, and four slopes: linear, quadratic, ...). Using mx_growth_mixture, with run = FALSE, and then later run_mx.
Proposed solution
Either of these solve the problem (I like B best):
A. Would it be an option to specify DWLS as an argument to mixture_starts (and therefore, to mx_growth_mixture) so I can use DWLS?
B. Line 580 should not only check for errors, but also check for status code ( != 0) of strts_vals at line 579 of mx_mixture.R and run mxTryHard() if necessary.
I wondered what the starting values were of this model so I did a little debugging of mixture_starts.
Line 567 (see end of message for the snippet) returns a model with crazy intercept and slope values for the two classes.
The intercept value for class 1 is -25.21408 while my data is on the 1 to 5 scale.
For class 2, the linear slope has value -73.41519.
I think these values lead to issues down the line.
After line 579, the model gives a warning (which is silenced by the code):
I guess this result that does not satisfy optimality contraints (stuck in a local optimum I guess)
Comparing those results with the simple_starts values, they don't differ a lot (I subtracted the M matrices for the intercept and slopes) 0.0001419474 0.0004197741 0.001446449 0.004306184 0.002721691
So, the final starting values are improbable values. Leading to the error message I got.
I tried line 569 strts_vals <- simple_starts(strts, type = "DWLS") and that does lead to sensible starting values at line 579.
Would it be an option to specify DWLS as an argument to mixture_starts (and therefore, to mx_growth_mixture) so I can use DWLS?
Line 585, the mxTryHard, also leads to sensible starting values. Perhaps Line 580 should not only check for errors, but also check for status code ( != 0) of strts_vals at line 579 and run mxTryHard().
Hi, I am running into an issue while running a latent growth mixture model (2 classes, and four slopes: linear, quadratic, ...). Using
mx_growth_mixture
, withrun = FALSE
, and then laterrun_mx
.Proposed solution
Either of these solve the problem (I like B best):
A. Would it be an option to specify DWLS as an argument to mixture_starts (and therefore, to mx_growth_mixture) so I can use DWLS?
B. Line 580 should not only check for errors, but also check for status code ( != 0) of
strts_vals
at line 579 ofmx_mixture.R
and run mxTryHard() if necessary.Problem description
OpenMx returns this error:
I wondered what the starting values were of this model so I did a little debugging of
mixture_starts
.Line 567 (see end of message for the snippet) returns a model with crazy intercept and slope values for the two classes.
The intercept value for class 1 is
-25.21408
while my data is on the 1 to 5 scale.For class 2, the linear slope has value
-73.41519
.I think these values lead to issues down the line.
After line 579, the model gives a warning (which is silenced by the code):
I guess this result that does not satisfy optimality contraints (stuck in a local optimum I guess)
Comparing those results with the simple_starts values, they don't differ a lot (I subtracted the M matrices for the intercept and slopes)
0.0001419474 0.0004197741 0.001446449 0.004306184 0.002721691
So, the final starting values are improbable values. Leading to the error message I got.
I tried line 569
strts_vals <- simple_starts(strts, type = "DWLS")
and that does lead to sensible starting values at line 579.Would it be an option to specify DWLS as an argument to mixture_starts (and therefore, to mx_growth_mixture) so I can use DWLS?
Line 585, the
mxTryHard
, also leads to sensible starting values. Perhaps Line 580 should not only check for errors, but also check for status code ( != 0) ofstrts_vals
at line 579 and run mxTryHard().tidySEM/R/mx_mixture.R
Lines 567 to 590 in 7ab1d4c
The text was updated successfully, but these errors were encountered: