Reviewers have requested I give confidence intervals on estimates from a common pathway model (I am using the `umx::umxCP`

function to build my common pathway model).

When I try and use Hunter's nice `mxSE(top.es_std[1,1], model = cp3)`

function on to request the SE on the specific-e for variable 1), I get the following error:

```
Model does not have a reasonable Hessian or standard errors.
Model has at least one mxConstraint. This prevented standard error computation.
Try mxCI()
```

Is there any work-around for this (to use `mxSE`

with a constraint in the model)?

Computing profile-based CIs will take a considerable time…

Can the CP model be implemented without constraints? the constraint used is

mxConstraint(diagL == nFac_Unit , name = "fix_CP_variances_to_1"),

Many thanks!

PS: Why do constraints invalidate SEs?

I think so. You could instead just fix the nonshared-environmental variance of the CP to some value (1.0, say). Or, you could fix one of the loadings onto the CP to 1.0, and freely estimate the CP's

A,C, andEvariances.As you know, standard errors are calculated as the square roots of the diagonal elements of the inverted Fisher information matrix (which in OpenMx is typically twice the inverted Hessian). The sampling covariance matrix you get from inverting the information matrix simply doesn't reflect the influence of the constraints on the repeated-sampling distribution of the parameter estimates.

You must have missed my recent email to the OpenMx developer list about valid standard errors in the presence of constraints. It turns out it's possible to calculate an asymptotically valid sampling covariance matrix from the usual Hessian, and a matrix providing a basis for the nullspace of the constraint Jacobian matrix. The current plan is to implement this approach in the backend, as part of the MxComputeNumericDeriv and MxComputeStandardError compute steps. Here's a demonstration script:

Hi Rob,

Did computing the sampling covariance matrix from the usual Hessian and the nullspace of the constraint Jacobian matrix get implemented in the backend?

If so, can mxSE now be allowed to work with constraints? Would be very useful.

Yes to both questions.

Fantastic!

Thanks. The whole standard-errors-with-constraints feature was a few weeks' worth of effort on my part.