search for: testlme4

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15-03-23 12:55 PM, Thierry Onkelinx wrote: > Dear Ben, > > Last week I was struggling with incorporating lme4 into a package. > I traced the problem and made a reproducible example ( > https://github.com/ThierryO/testlme4). It looks very simular to > the problem you describe. > > The 'tests' directory contains the reproducible examples. confint() > of a model as returned by a function fails. It even fails when I > try to calculate the confint() inside the same function as the > glmer() ca...

...ker On 15-03-24 07:55 PM, Ben Bolker wrote: > On 15-03-23 12:55 PM, Thierry Onkelinx wrote: >> Dear Ben, > >> Last week I was struggling with incorporating lme4 into a >> package. I traced the problem and made a reproducible example ( >> https://github.com/ThierryO/testlme4). It looks very simular to >> the problem you describe. > >> The 'tests' directory contains the reproducible examples. >> confint() of a model as returned by a function fails. It even >> fails when I try to calculate the confint() inside the same >> funct...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 WARNING: this is long. Sorry I couldn't find a way to compress it. Is there a reasonable way to design an update method so that it's robust to a variety of reasonable use cases of generating calls or data inside or outside a function? Is it even possible? Should I just tell users "don't do that"? * `update.default()` uses

Dear Ben, Last week I was struggling with incorporating lme4 into a package. I traced the problem and made a reproducible example ( https://github.com/ThierryO/testlme4). It looks very simular to the problem you describe. The 'tests' directory contains the reproducible examples. confint() of a model as returned by a function fails. It even fails when I try to calculate the confint() inside the same function as the glmer() call (see the fit_model_ci funct...