Skip to content
Prev 13223 / 20628 Next

calculation max|grad value?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 15-04-13 08:41 AM, Ben Pelzer wrote:
As Doug Bates pointed out and explained, we should really be using
solve(chol(Hessian), gradient) instead (I started this e-mail this
morning and have had the compose window sitting open all day).
Heuristically, what this means is that we're estimating the expected
change in the deviance over the scale of one standard error of the
parameter, rather than over the scale of one unit of the parameter (as
Doug points out, the latter can be rather arbitrary).

  We know and have known for a while that the convergence criteria
we're currently using are rather dodgy, but we've been struggling with
what to replace them with.  We know there are lots of false positives
for large (say nobs > 10^5) data sets, and we are trying to come up
with reasonable, simple criteria that will reduce the number of false
positives without completely scrapping the convergence criteria.

  In the meantime, I would say that the gold standard (at this point)
for "is my fit really OK?" is  whether you can refit with several
different optimizers (and possibly different starting points?) and get
practically the same result in each case; see e.g.
https://rstudio-pubs-static.s3.amazonaws.com/33653_57fc7b8e5d484c909b615d8633c01d51.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJVLDQ9AAoJEOCV5YRblxUH4E8IALrcXjAHXP9fmg77LwqYH9II
DaLh3QaQLcp3D2RB74U6zfHgXh9lsrO6ojGIPQDSa6k21L+Yfa4EBmmQs77hkzEz
+yBYJdgWCJl5YL0J3d3Rckbtl2ieYxO046E764r9X4m2w8kIz+wHT51SHma7S9ho
Ghw6GbFTaen9X5x9pPIC1otA3CVXHDtErZwYKi522ACF2hnvd1Z7GjkMAZZ6V868
fvBmXIx3BfgrGhYvbQpNKcxu1iQ2AbfHtq9JgjUA60jmnQIvbHDHOyqiNP0ksiJO
OFIt7x9n7RR0jEOPL4sTJAeUitvagw6eTFy4OqjHTHz4sysX8z9b9OJJ5FeOv88=
=A25k
-----END PGP SIGNATURE-----