On 09/08/2020 3:07 p.m., Duncan Murdoch wrote:
On 09/08/2020 3:01 p.m., John Mount wrote:
Doesn't this preclude "y ~ ." style notations?
Yes, but you can use "y ~ . - w".
And as was pointed out to me offline, often one doesn't have a simple
vector w giving the weights, instead one computes
On 09/08/2020 3:01 p.m., John Mount wrote:
Doesn't this preclude "y ~ ." style notations?
Yes, but you can use "y ~ . - w".
Duncan Murdoch
On Aug 9, 2020, at 11:56 AM, Duncan Murdoch wrote:
This is fairly clearly documented in ?lm:
"All of weights, subset and offset are evaluated in th
Doesn't this preclude "y ~ ." style notations?
> On Aug 9, 2020, at 11:56 AM, Duncan Murdoch wrote:
>
> This is fairly clearly documented in ?lm:
>
> "All of weights, subset and offset are evaluated in the same way as variables
> in formula, that is first in data and then in the environment of
This is fairly clearly documented in ?lm:
"All of weights, subset and offset are evaluated in the same way as
variables in formula, that is first in data and then in the environment
of formula."
There are lots of possible places to look for weights, but this seems to
me like a pretty sensibl
I know this programmers can reason this out from R's late parameter evaluation
rules PLUS the explicit match.call()/eval() lm() does to work with the passed
in formula and data frame. But, from a statistical user point of view this
seems to be counter-productive. At best it works as if the user
Dear R-Devel list members
I'm facing as problem already known and linked to the use of
getGraphicsEvent(prompt = "Waiting for input",
onMouseDown = NULL, onMouseMove = NULL,
onMouseUp = NULL, onKeybd = NULL,
onIdle = NULL,
con
