Skip to content

Convergence issues running clmm in ordinal package

2 messages · Karen Lamb, Rune Haubo

#
On 20 April 2011 13:41, Karen Lamb <k.lamb at sphsu.mrc.ac.uk> wrote:
Observe that this is a warning and not an error message, also it says
that clmm *may* not have converged: whether the optimizer terminated
close enough to the optimum is essentially op to you. The reason you
get the warning is because 5e-4 is larger that 1e-5, which is the
default maximum absolute gradient criterion (the grtol control option
in the ucminf optimizer), however, 5e-4 should be small enough for
most applications, so I would trust the results in this case.

If you change the optimizer and use, e.g. method = "nlminb" or "optim"
I expect you get essentially the same parameter estimates. You could
also (using the default ucminf optimizer) change the maximum absolute
gradient convergence criterion and append
control=clmm.control(grtol=1e-6) to your clmm call and see if it gets
closer to the optimum.

The main message is that you probably do not need to worry in this
case, but if you do, there are control options you can change.
If you want standard errors, p-values etc. you should add 'Hess =
TRUE' to your clmm call. (I am aware that a more informative warning
message would be nice)
Observe that this is the exact same maximum absolute gradient
indicating that the optimizer took the same path to the optimum and
that maxIter and maxLineIter never came into play.
about with your data. There is no limit to the number of observations
or random effect levels that clmm can cope with - you may run out of
memory at some point or other things can come into play, but that is
not directly related to clmm. So the number of areas in your data does
not seem to be a problem.

I hope I got around to all your questions, but please follow up if I
missed something or you experience additional issues.

Cheers,
Rune