Displaying 20 results from an estimated 5000 matches similar to: "Unexpected email address change - and maybe a missing manual patch"
2018 Nov 30
0
Unexpected argument-matching when some are missing
Argument matching is by name first, then the still missing arguments
are filled positionally. Unnamed missing arguments are thus left
missing. Does that help?
Michael
On Fri, Nov 30, 2018 at 8:18 AM Emil Bode <emil.bode at dans.knaw.nl> wrote:
>
> But the main point is where arguments are mixed together:
>
> > debugonce(plot.default)
> > plot(x=1:10, y=, 'l')
2018 Nov 30
2
Unexpected argument-matching when some are missing
But the main point is where arguments are mixed together:
> debugonce(plot.default)
> plot(x=1:10, y=, 'l')
...
Browse[2]> missing(y)
[1] FALSE
Browse[2]> y
[1] "l"
Browse[2]> type
[1] "p"
I think that's what I fall over mostly: that named, empty arguments behave entirely different from omitting them (", ,")
And I definitely agree we need
2018 Nov 29
0
Unexpected argument-matching when some are missing
> > plot(x=1:10, y=)
> > plot(x=1:10, y=, 10:1)
> >
> > In both cases, 'y=' is ignored. In the first, the plot is for y=NULL (so not
> 'missing' y)
> > In the second case, 10:1 is positionally matched to y despite the intervening
> 'missing' 'y='
> >
> > So it isn't just 'missing'; it's 'not there
2018 Nov 29
2
Unexpected argument-matching when some are missing
On Thu, Nov 29, 2018 at 1:10 PM S Ellison <S.Ellison at lgcgroup.com> wrote:
>
>
> > > plot(x=1:10, y=)
> > > plot(x=1:10, y=, 10:1)
> > >
> > > In both cases, 'y=' is ignored. In the first, the plot is for y=NULL (so not
> > 'missing' y)
> > > In the second case, 10:1 is positionally matched to y despite the
2018 Dec 17
0
Documentation examples for lm and glm
Dear Steve,
Since this relates as well to the message I posted a couple of minutes before yours, I agree that it?s possible to phrase ?best practices? too categorically. In the current case, I believe that it?s reasonable to say that specifying the data argument is ?generally? or ?usually? the best option. That doesn?t rule out exceptions.
Best,
John
2017 Aug 08
1
Latin hypercube sampling from a non-uniform distribution
Thanks for your answer.
I have attached the plot for representing the variable. I think that I need to draw a Hypercube sample for each age class (i.e., for 0, 1, 2, 3, 4, 5, 6, 7) in a given simulation (i.e., N = 1) and the LHS values for all age classes should be like the observed cumulative distribution (see attached figure). Thus, the output of randomLHS should be a matrix with 100 rows (N =
2015 Oct 06
5
authorship and citation
> The former co-author contributed, so he is still author and probably copyright
> holder and has to be listed among the authors, otherwise it would be a CRAN
> policy violation ...
It's a bit of a philosophical question right now, but at some point in a developing package's life - particularly one that starts small but is subsequently refactored in growth - there may be no code
2017 Aug 07
0
Latin hypercube sampling from a non-uniform distribution
> How can I draw a Hypercube sample for the variable mortality_probability so
> that this variable exhibits the same pattern as the observed distribution?
One simple way is to use the uniform random output of randomLHS as input to the quantile function for your desired distribution(s).
For example:
q <- randomLHS(1000, 3)
colnames(q) <- c("A", "B",
2018 Nov 29
0
Unexpected argument-matching when some are missing
> When trying out some variations with `[.data.frame` I noticed some (to me)
> odd behaviour,
Not just in 'myfun' ...
plot(x=1:10, y=)
plot(x=1:10, y=, 10:1)
In both cases, 'y=' is ignored. In the first, the plot is for y=NULL (so not 'missing' y)
In the second case, 10:1 is positionally matched to y despite the intervening 'missing' 'y='
So it
2018 Nov 30
0
Unexpected argument-matching when some are missing
> Yes, I think all of that is correct. But y _is_ missing in this sense:
> > plot(1:10, y=)
> > ...
> Browse[2]> missing(y)
Although I said what I meant by 'missing' vs 'not present', it wasn't exactly what missing() means. My bad.
missing() returns TRUE if an argument is not specified in the call _whether or not_ it has a default, hence the behaviour of
2015 Oct 08
0
authorship and citation
> > I read the CRAN policies twice, and there
> > is no official guideline on how to compile the citation.
The policies are about copyright and IP, not credited authorship. There's overlap but they are not the same thing.
You can see whether someone is a copyright holder by referring to the license you had and whether there is any of their content remaining. But that might not
2018 Oct 17
1
invisible functions
> 2. change cfun[[1]] <- quote(cord.work) to cfun[[1]] <-
> quote(survival:::cord.work). You say this will mess up your test bed.
> That suggests that your test bed is broken. This is a perfectly legal
> and valid solution.
Valid in a package, but forces code to call a loaded library version of a function rather than (say) a 'source'd user-space version that is under
2016 Apr 06
0
Problem with <= (less than or equal): not giving the expected result
> Apparently, abs(1 - 0.95) is not equal to 0.05, which I find however quite
> disturbing.
It's normal.* See R FAQ 7.31 in the html help system.
S Ellison
*... and common to all computers that use binary.
*******************************************************************
This email and any attachments are confidential. Any use, copying or
disclosure other than by the intended
2018 Nov 29
3
Unexpected argument-matching when some are missing
On Thu, Nov 29, 2018 at 10:51 AM S Ellison <S.Ellison at lgcgroup.com> wrote:
>
> > When trying out some variations with `[.data.frame` I noticed some (to me)
> > odd behaviour,
>
> Not just in 'myfun' ...
>
> plot(x=1:10, y=)
> plot(x=1:10, y=, 10:1)
>
> In both cases, 'y=' is ignored. In the first, the plot is for y=NULL (so not
2017 Aug 07
2
Latin hypercube sampling from a non-uniform distribution
Thanks for your answer.
However, my variable is simulated from the cumulative distribution function of the Poisson distribution. So, the pattern obtained from the function "qpois" is not the same as the observed pattern (i.e., obtained from the function "ppois")
set.seed(5)
mortality_probability <- round(ppois(seq(0, 7, by = 1), lambda = 0.9), 2)
2008 Jan 29
1
Fortunes - was Re: [OT] vernacular names for circular diagrams
I did not write that.
On Jan 29, 2008 9:05 AM, S Ellison <S.Ellison at lgc.co.uk> wrote:
> >>> "Gabor Grothendieck" <ggrothendieck at gmail.com> 29/01/2008 12:35:27
> >>>
> > As is common in human affairs, even
> > the illusion of understanding is preferred to a lofty digression
> upon
> > why the audience does not understand.
2006 Sep 21
4
strange matching: maybe a multilanguage collation problem?
Hi,
We''re using Ferret in a slightly unorthodox way: We''re indexing a
large (>100,000) list of names of places all around the world. Mostly
we''re quite happy with it, and have been able to graft on our own
particular required functionality with just a little tweaking.
There''s one strange problem, though: We''ve got a place in Cyprus
called
2017 Sep 05
0
Strange lazy evaluation of default arguments
Mathias,
If it's any comfort, I appreciated the example; 'expected' behaviour maybe, but a very nice example for staff/student training!
S Ellison
> -----Original Message-----
> From: R-help [mailto:r-help-bounces at r-project.org] On Behalf Of Matthias
> Gondan
> Sent: 02 September 2017 18:22
> To: r-help at r-project.org
> Subject: [R] Strange lazy evaluation of
2019 Aug 30
3
?Syntax wrong about `?`'s precedence ?
Precedence is a property of the parser and has nothing to do with the
semantics assigned to various symbols. Using just core R functions you can
see the precedence of '?' is between those of '=' and '<-'.
> # '=' has lower precedence than '?'
> str(as.list(parse(text="a ? b = c")[[1]]))
List of 3
$ : symbol =
$ : language `?`(a, b)
$
2018 Dec 03
1
Unexpected argument-matching when some are missing
>>>>> Michael Lawrence
>>>>> on Fri, 30 Nov 2018 08:24:31 -0800 writes:
> Argument matching is by name first, then the still missing
> arguments are filled positionally. Unnamed missing
> arguments are thus left missing. Does that help?
Thank you, Michael!
Unfortunately, it may not help sufficiently notably once this
thread will be