Message-ID: <E2E28790-9767-444B-A4DD-2D75E73E951D@dcn.davis.ca.us>
Date: 2021-03-29T07:31:51Z
From: Jeff Newmiller
Subject: seed problem?
In-Reply-To: <HE1PR0902MB205961BC5D2F17F581F0E1C9E67F9@HE1PR0902MB2059.eurprd09.prod.outlook.com>
Check if you have a .RData file in your R startup directory. It may contain the seed.
.RData files (without anything in front of the period) are dangerous... many R users avoid them because they can easily drag in mistakes from previous sessions to plague you.
On March 28, 2021 9:02:17 AM PDT, Mika Hamari <mika.hamari73 at outlook.com> wrote:
>Hi!
>
>I have Windows 10 on PC and different versions of R. I noticed that
>when I executed simulation with R 4.0.3, it gave exactly the same
>results next time when I re-opened the program. I didn?t set the seed.
>
>I tested this also with simple ?rnorm(10,100,10)?, and the results were
>every time the same, when I re-opened the program. It seems that it
>starts with the same seed. R 4.0.0 and 4.0.3 did it, both with 32- and
>64-bit versions. But with R Studio the results were every time
>different, as they were also different with 3.4.3. This explains, why I
>hadn?t noticed this earlier.
>
>I know the function set.seed(), but I wonder, how in the first place
>seed can be every time same, if you don?t set it to be. What I read
>about seeds, this should be very highly improbable occurence.
>
>Thanks to all developers for what they are doing for common good. I
>love R!
>
>Mika Hamari
>
> [[alternative HTML version deleted]]
--
Sent from my phone. Please excuse my brevity.