On 02/16/2015 07:35 AM, Duncan Murdoch wrote:
If you are depending on nlme, you don't also need to import it. But it
is generally a good practice to avoid either modifying or relying on the
search list: as people get more packages there, there are more chances
for clashes.
I would suggest adding
On 16.02.2015 14:35, Duncan Murdoch wrote:
On 16/02/2015 8:20 AM, Therneau, Terry M., Ph.D. wrote:
> I'm testing out a new version of coxme and R CMD check fails with "could
not find function
> ranef" (or random.effects or fixef, or anything from nlme). The
NAMESPACE file has t
On 16/02/2015 8:20 AM, Therneau, Terry M., Ph.D. wrote:
>
>> > I'm testing out a new version of coxme and R CMD check fails with
>> "could not find function
>> > ranef" (or random.effects or fixef, or anything from nlme). The
>> NAMESPACE file has the
>> > line below
>>
>> >
> I'm testing out a new version of coxme and R CMD check fails with "could
not find function
> ranef" (or random.effects or fixef, or anything from nlme). The
NAMESPACE file has the
> line below
> importFrom(nlme, ranef, random.effects, fixef, fixed.effects, VarCorr)
On 16/02/2015 4:32 AM, Martin Maechler wrote:
>> Therneau, Terry M , Ph D
>> on Sun, 15 Feb 2015 17:31:00 -0600 writes:
>
> > I'm testing out a new version of coxme and R CMD check fails with
> "could not find function
> > ranef" (or random.effects or fixef, or anything from
> Therneau, Terry M , Ph D
> on Sun, 15 Feb 2015 17:31:00 -0600 writes:
> I'm testing out a new version of coxme and R CMD check fails with "could
not find function
> ranef" (or random.effects or fixef, or anything from nlme). The
NAMESPACE file has the
> line below
