search for: 86548915l

...ue, interpreted as an integer, We were confident of R coercing characters to integers correctly. We tested, prior to making this posting that the behaviour remains intact if we change the `seeds` variable from a character vector to the "equivalent" integer vector by hand. > seeds = c(86548915L, 86551615L, 86566163L, 86577411L, 86584144L, 86584272L, + 86620568L, 86724613L, 86756002L, 86768593L, 86772411L, 86781516L, + 86794389L, 86805854L, 86814600L, 86835092L, 86874179L, 86876466L, + 86901193L, 86987847L, 86988080L) > > random_values = sapply(seeds, function(x) { + set.seed...

...their methods by that criterion. There is, however, a large literature on hash functions, which is what you should look at. But if you want a quick fix, perhaps looking not at the first number in the sequence, but rather (say) the 10th, might be preferable. Radford Neal > > seeds = c(86548915L, 86551615L, 86566163L, 86577411L, 86584144L, > 86584272L, > + 86620568L, 86724613L, 86756002L, 86768593L, 86772411L, 86781516L, > + 86794389L, 86805854L, 86814600L, 86835092L, 86874179L, 86876466L, > + 86901193L, 86987847L, 86988080L) > > > > random_values = sapply(see...

This is cross-posted from SO (https://stackoverflow.com/q/47079702/1414455), but I now feel that this needs someone from R-Devel to help understand why this is happening. We are facing a weird situation in our code when using R's [`runif`][1] and setting seed with `set.seed` with the `kind = NULL` option (which resolves, unless I am mistaken, to `kind = "default"`; the default being