Care should be taken with this method not to encounter the
birthday problem, described
https://www.johndcook.com/blog/2016/01/29/random-number-generator-seed-mistakes/.
Since the `sitmo`

`threefry`

, this currently generates
one random deviate from the uniform distribution to seed the
engine `threefry`

and then run the code.

## Arguments

- lambda
vector of (non-negative) means.

- n
number of random values to return.

- ncores
Number of cores for the simulation

`rxnorm`

simulates using the threefry sitmo generator.`rxnormV`

used to simulate with the vandercorput simulator, but since it didn't satisfy the normal properties it was changed to simple be an alias of`rxnorm`

. It is no longer supported in`rxode2({})`

blocks

## Details

Therefore, a simple call to the random number generated followed by a second call to random number generated may have identical seeds. As the number of random number generator calls are increased the probability that the birthday problem will increase.

The key to avoid this problem is to either run all simulations in the
`rxode2`

environment once (therefore one seed or series of seeds
for the whole simulation), pre-generate all random variables
used for the simulation, or seed the rxode2 engine with `rxSetSeed()`

Internally each ID is seeded with a unique number so that the results do not depend on the number of cores used.

## Examples

```
# \donttest{
## Use threefry engine
rxpois(lambda = 3, n = 10) # with rxpois you have to explicitly state n
#> [1] 3 2 3 3 5 3 3 4 1 1
rxpois(lambda = 3, n = 10, ncores = 2) # You can parallelize the simulation using openMP
#> [1] 4 5 4 7 1 3 4 3 3 6
rxpois(4) ## The first arguments are the lambda parameter
#> [1] 2
## This example uses `rxpois` directly in the model
rx <- function() {
model({
a <- rxpois(3)
})
}
et <- et(1, id = 1:2)
s <- rxSolve(rx, et)
#>
#>
#>
#>
#> using C compiler: ‘gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0’
# }
```