Thanks Martin, this seems much better. All of the best, Elizabeth
> On Apr 16, 2019, at 10:22 AM, Martin Maechler
> wrote:
>
>> Elizabeth Purdom
>>on Tue, 16 Apr 2019 09:45:45 -0700 writes:
>
>> Hi Bert, Thanks for your response. What you suggest is
>> more or less the fix I sugge
bert
On 4/17/19 6:00 AM, r-help-requ...@r-project.org wrote:
> Date: Tue, 16 Apr 2019 19:22:34 +0200
> From: Martin Maechler
> To: Elizabeth Purdom
> Cc: Bert Gunter, R-help
>
> Subject: Re: [R] Limiting the scope of RNGkind/set.seed
> Message-ID:<23734.3930.10744.1
> Elizabeth Purdom
> on Tue, 16 Apr 2019 09:45:45 -0700 writes:
> Hi Bert, Thanks for your response. What you suggest is
> more or less the fix I suggested in my email (my second
> version of .rcolors). I writing more because I was
> wondering if there was a better way
Hi Bert,
Thanks for your response. What you suggest is more or less the fix I suggested
in my email (my second version of .rcolors). I writing more because I was
wondering if there was a better way to work with RNG that would avoid doing
that. It doesn’t feel very friendly for my package to be m
I think I'm missing something. Why does something like this not do what you
want:
> RNGkind()
[1] "Mersenne-Twister" "Inversion"
> f <- function(){
+cur <- RNGkind(NULL)[1]
+RNGkind("Super-Duper")
+print(RNGkind())
+RNGkind(cur)
+ }
> f()
[1] "Super-Duper" "Inversion"
> RNGkind()
[
Hello,
I have a package, and inside of it I have a small function that selects a
random palette of colors for graphing purposes. It’s a large number of colors,
which is why I don’t manually select them, but I did want them to stay constant
so I set the seed before doing so. So I had a little fu
6 matches
Mail list logo
