Mike Neale pointed this out in response to a user post.

http://openmx.psyc.virginia.edu/thread/3883#comment-5602

The saturated/independence models for binary data need to be modified a little be smartly depending on the number of categories in ordinal factors.

Sometimes error messages for NaN get garbled in Windows. See the thread below.

http://openmx.psyc.virginia.edu/thread/3881#comment-5574

exited abnormally with the error message: MxComputeGradientDescent: fitfunction Sat.fitfunction evaluated to 1.#QNAN0 ()

We need a script that generates this error. Rob alluded to there being one. And then we can try to fix the printing of the error message.

Add documentation in man page for mxOption for "Number of Threads".

The following algebras would be nice to have. They are currently scheduled for completion after the 2.0 release:

ceiling, floor, trunk, round
dim
rowMeans, colMeans
qnorm, pnorm
qr

mxEval looks in the parent environments to find objects. This can be handy, allowing reference to such objects in algebra. However, when used in the context of getting things out of models (quite a common use-case), it can be dangerous: mxEval might return an object with the same name from the environment, rather than from inside the model you have set as the target.

Example. Say you have a matrix


m1$submodels$top$matrices$nVar$values
[,1]
[1,] 1


We quite often read and type things like


mxObject(…, dimnames = list(NULL, c("a", "b","c")))
# and
mxExpectationNormal(dimnames = list(c("a", "b","c"), c("a", "b","c")))


Add rownames and colnames parameters to allow:

mxObject(..., colnames = c("a", "b", 'c'))


in place of the harder to read

mxObject(…, dimnames = list(NULL, c("a", "b")))


Would be handy also to interpret a single vector input to dimnames as a list with both entries the same, i.e.:


mxObject(..., dimnames = c('a','b', 'c') )
# would function like: