The desirable behavior is to insert the estimate into the lower and upper bound and continue.

One way would be to make things like this work:


model$intervals = NULL
model$intervals = model$intervals[-3]


An aid to learning would be to add a note to the help about remove = TRUE parameter to mxModel(), which would remove a CI of that name from the model.


newModel = mxModel(oldModel, mxCI("a_r1_c1"), remove = TRUE)


doesn't error, but it does nothing (the interval requests remain)

model@intervals = NULL
fails with an error:
Error in checkAtAssignment("MxModel", "intervals", "NULL") :
assignment of an object of class “NULL” is not valid for @‘intervals’ in an object of class “MxModel”;

It would be nice if the $ operator allowed removing CI requests from models.

I wonder:
1. Why don't we use the cheap SEs from the 2nd derivative matrix to seed the starts for CI computation? What would be wrong with that?
2. Even with variance in how long it takes per CI, something like this would be helpful to the user:


nCI <- length(CIs) # actually want this in cells, so unpack matrices, rows etc into vector of cell addresses)
# create progress bar