better error when running model?

I think users (and me :-) ) will often struggle with mxRun-time errors - they have that "oh its somewhere in the whole-thing" feel that makes it hard to start pinning them down).

So any clues (such as the name of the algebra causing an error, and or the sizes of the two matrices that were being cbind()ed ) would be gratefully received:

# generated by the rev 871 version of trunk/models/failing/NTF_design.R
fit <- mxRun(model)
# Error in mxRun(model) :
# Non-conformable matrices in horizontal concatenation.

traceback()
# 2: .Call("callNPSOL", objective, startVals, constraints, matrices,
# parameters, algebras, data, options, state, PACKAGE = "OpenMx")
# 1: mxRun(model)

A couple of overlapping things are happening in this example. Any kind of error thrown by .Call("callNPSOL) should not be happening, strictly speaking, and we are doing our best to catch these errors in the front-end. Now that being said, it would be nice to have more debugging information available so that we can figure out where and why this error is occurring in the back-end. That's easier said than done, because a lot of human-readable information is thrown away by the back-end as it processes machine-readable reverse polish notation to compute the algebras, with a bunch of pointers to locations in memory. I've checked in a patch that at least stores the name of the algebra in the back-end, which is a start.

This particular error I've tracked down to computing MZNTF.expCovMz, where for some reason NTF.CvMz is evaluating to something with 0 rows.

Algebras are populated in the back-end with their initial values from the front-end computation.

Automatically closed -- issue fixed for 2 weeks with no activity.