OpenMx Developer Forums

At developers meeting on 8/19 we discussed the following:

• The group decided OpenMx version 1.1 is ready to be released. The release will be occurring in the near future. Details on the new features of OpenMx version 1.1 can be found here.

Hi,

I just found that the omxMnor returns a value for an input involving a non p.d. covariance matrix.

Example

omxMnor(array(1,dim=c(2,2)),cbind(0,0),cbind(-Inf,-Inf),cbind(0,0))

returns a value of .375. The limiting value should be .5

S<-diag(1,2);
S[1,2]<-S[2,1]<-2
omxMnor(S,cbind(0,0),cbind(-Inf,-Inf),cbind(0,0))

returns a value of 0.4262082, though S is not p.d.

Hi! I'm really a new beginner but had a lot of help from the Simplified OpenMx manual. In the end of this manual there is a script that I used to explore my own data. However, this script give 95% CIs for the unsquared path estimates but for standardized variance estimates which would be of great interest. Is there a simple way to modify this script to get 95% CIs also for the variance estimates?? Really grateful for any help!

At developers meeting on 8/12 we discussed the following:

At developers meeting on 8/5 we discussed the following:

• Changes in the front and back end to the make RAM Objectives work with ML and FIML. The proposed changes will have RAM populate things like the covariance matrix and latent variables. These changes will make it easier to add LISREL Objective Functions to OpenMx.
• We discussed a parallel strategy for FIML:

So I put together this function to estimate polychoric correlations by ML. It may improve on the polychor() by i) accepting a dataframe with more than two variables; ii) avoiding the threshold-estimates-in-the-wrong-order problem (see http://r.789695.n4.nabble.com/polychor-error-td806416.html).

Question is, how should I dispose of this function? Obviously it needs a bit more tidying up - error checking on input, testing, documentation etc. but it could be quite handy. Comments welcome.

> polychoricMatrix(data[1:2])
Running model
$polychorics
t1neur1 t1mddd4l

At developers meeting on 7/29 we discussed the following:

• The bug in OpenMx 1.1 Beta release where an ordinal non-positive definite covariance matrix goes into an infinite loop has been fixed.
• The 'connect' slot which is replacing the deprecated 'all' slot in MxPath is ready for testing. It will be checked in over the weekend for testing. For more information on this please see the forum post here.

At developers meeting on 7/22 we discussed the following:

• There continues to be a known bug in the OpenMx 1.1 Beta release. When running FIML with an ordinal non-positive definite covariance matrix OpenMx goes into an infinite loop instead of reporting an error to the user. This issue has been moved very high on the OpenMx 1.1 priorities list.

At developers meeting on 7/15 we discussed the following:

• There is a known bug in the OpenMx 1.1 Beta release. When running FIML with an ordinal non-positive definite covariance matrix OpenMx goes into an infinite loop instead of reporting an error to the user.

At developers meeting on 7/8 we discussed the following list of upcoming development changes for OpenMx 1.2. OpenMx 1.1. is currently being beta tested and has been feature frozen.

• Changes to the back-end of the OpenMx to enforce consistency and make the addition of new model types more straight forward.
• The inclusion of multi-level models. Currently we have an interface design that the group is pleased with but we are still soliciting some additional feedback.
• The implementation of weighted least squares to offer performance improvements.