jitter starts if optimization can't get started

I see CIs now jitter if they can't get started. That's nice.

Often multivariate scripts won't get started when start values are specified with one value (because matrix is not invertable). I wrote a helper that jiggles starts to avoid this, but it would be nice if mx did this itself, if it can't get started.

This would also take away a lot of frustration from users whose scripts won't run, when the only problem is that the start values are identical across one or more matrices.

OpenMx 0.4.1

This time was have a twofer for you. We were getting prepared to release version 0.4.0, and we detected a few bugs before the release of 0.4.0. So below is the change log for OpenMx 0.4.0 and 0.4.1. This is mostly a bug fixing release. So we recommend upgrading to this version. There are a few performance improvements. Most notably there should be an improvement to our users running FIML models with ordinal data. Expect to see more performance improvements as we get closer to the 1.0 release.

mxCompare(oneModelOnly)

the old gen_epi helper tableFitStatistics(fit) would accept just one parameter, and describe that model's fit:
> tableFitStatistics(fit)
Name ep -2LL df AIC
Model 1 : top 7 2964.37 468 2028.37

The built-in replacement throws an error when the comparison list is omitted:
> mxCompare(fit)
Error in mxCompare(fit) :
'comparison' argument be a MxModel object or list of MxModel objects
It would be nice if it defaulted to simply give the base model data when no comparison models are provided...