OpenMx Wishlist

matrix redimensioning
Maybe mxRedim(mat, row, col)
? Conformance would require that the total number of elements remain constant. That is, mat->rows * mat->cols == row * col
.
Semantics would probably fill in by columns.
- Read more about matrix redimensioning
- 3 comments
- Log in or register to post comments

LRtest for model comparison
I'm rather new to the field of SEM, but I am very happy about OpenMx - the learning curve really was really steep (... in the sense of quick successes). Congratulations!
In some post there are already some hints about a "mxCompare" function. I tried to implement a likelihood ratio / chi square test myself:
- Read more about LRtest for model comparison
- 3 comments
- Log in or register to post comments

More example scripts for twin models
It would have been very helpful to have all the scripts in this library converted to OpenMx.
- Read more about More example scripts for twin models
- 2 comments
- Log in or register to post comments

Path diagrams
- Read more about Path diagrams
- 8 comments
- Log in or register to post comments

Square bracket substitution implemented
require(OpenMx) A <- mxMatrix('Full', 1, 1, values = 1, name = 'A')
- Read more about Square bracket substitution implemented
- 5 comments
- Log in or register to post comments

Capability to offer a vector to value and free slots in MXMatrix objects
Chol = mxMatrix(type="Full", 2,2, free=c(TRUE,TRUE,FALSE,TRUE), values=c(1,.2,0,1))
But this fails
Chol@free=c(TRUE,FALSE,FALSE,TRUE) Chol@values=c(1,0,0,1)
It would be nice, given that we can create the free and values slots with vectors, if we could also update them iwth vectors, using the pre-existing nrow and ncol of the MxMatrix to do this:
vec2MatFormxMatrix <- function(oldMat, newVec) { newMat = matrix(data=newVec, nrow=nrow(oldMat), ncol=ncol(oldMat) ) return(newMat) } newVec =c(TRUE,FALSE,FALSE,TRUE)

"saving" the score/information functions
- Read more about "saving" the score/information functions
- 1 comment
- Log in or register to post comments

Save the state of the optimiser for input to a new run (granted)
The cleanest way to implement it for the user would be as a parameter to mxRun, where you pass in the last fit, and this has in it the state of the optimiser which mxRun pushes into the current optimiser run as a set of start values.
fit = mxRun(model)
mxRun(model, fit)
#--> returns almost instantly having been started at the optimal location

Confidence intervals (granted)
maybe something like
mxInterval(..., percent=95, type="ML") where ... consists of matrix addresses
mxInterval(z.A) would mean all cells of A
mxInterval(z.A[1:2,], type="SE") first two rows of A, standard-error based method
- Read more about Confidence intervals (granted)
- 31 comments
- Log in or register to post comments

Welcome to the OpenMx Wishlist forum
- Read more about Welcome to the OpenMx Wishlist forum
- Log in or register to post comments
Pagination
- Previous page
- Page 2