Roland Schulz wrote:
> Hi,
>
> I think the best way to solve this issue to not use a state at all. It is
> fast, reproducible even in parallel (if wanted), and doesn't suffer from
> the shared issue. Would be nice if numpy provided such a stateless RNG as
> implemented in Random123: www.deshawres
Hi,
I think the best way to solve this issue to not use a state at all. It is
fast, reproducible even in parallel (if wanted), and doesn't suffer from
the shared issue. Would be nice if numpy provided such a stateless RNG as
implemented in Random123: www.deshawresearch.com/resources_random123.html
In order to make sure all my random number generators have good
independence, it is a good practice to use a single shared instance (because
it is already known to have good properties). A less-desirable alternative
is to used rng's seeded with different starting states - in this case the
inde
