OpenMx Developer Forums

Now that the closed beta is released we can get back to the categorical outcomes estimation. What is the status and expected completion date on the backend? Are there front end issues that need to be dealt with?

Currently one of the least polished functions, and at the same time most visible to end users is the summary() function applied to the results of a model optimization.

We need suggestions about what this output should look like.

When specifying mxData() with both covariances and means, should the means vector be a row matrix or a column matrix?

1. Suppose a model has two free parameters.

2. You equate the two parameters by giving them the same name.

3. Now, you fix one of the parameters.

What should happen? One parameter is free and the other is fixed and they both are equated.

Currently OpenMx throws an error. Is there a more sensible thing to do?

OK. So that's a mouthful. This forum is primarily for the OpenMx developers. We will be talking with each other about the R functions that create the command line user interface for OpenMx. There are still a number of unresolved issues in how the user interface handles exceptions and conflicts, in how the function arguments are named, and in how output is structured.

Formerly, these questions were dealt with on a private mailing list. Now, we are making our developer discussions visible to the community.

This is the forum for posting what you would like to see added to OpenMx. We expect that this forum will be used by OpenMx users who are thinking about new and different things they would like to do with OpenMx. But also, since OpenMx is an open source project, we expect that graduate students, post-docs, and early career quantitative psychologists and statisticians might use this forum as a source of ideas for dissertation projects or grant proposals. With many people contributing ideas and programming talents, all parts of the community can benefit.