[R] seed problem?
w||||@mwdun|@p @end|ng |rom gm@||@com
Mon Mar 29 17:56:04 CEST 2021
Does this happen if you start R with the --vanilla flag? If so it may
be that you have a startup file, .\.Rprofile or %HOME%\.Rprofile that
is calling set.seed(n) for a fixed n.
On Mon, Mar 29, 2021 at 12:16 AM Mika Hamari <mika.hamari73 using outlook.com> wrote:
> 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]]
> R-help using r-project.org mailing list -- To UNSUBSCRIBE and more, see
> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
More information about the R-help