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.

rxexp(rate, n = 1L, ncores = 1L)

Arguments

rate

vector of rates.

n

number of observations. If length(n) > 1, the length is taken to be the number required.

ncores

Number of cores for the simulation

rxnorm simulates using the threefry sitmo generator; rxnormV uses the vandercorput generator

Value

exponential random deviates

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 RxODE 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 RxODE engine with rxSetSeed()

Also care should be made that the computer you will be running on can run the same number of cores as you are running so they can reproduce your results.

Examples

# \donttest{

## Use threefry engine

rxexp(0.5, n = 10) # with rxexp you have to explicitly state n
#>  [1] 0.7911182 0.1320259 1.9459855 1.6859092 3.0038971 0.6588802 5.1950923
#>  [8] 0.4717652 2.4560537 4.3125862
rxexp(5, n = 10, ncores = 2) # You can parallelize the simulation using openMP
#>  [1] 0.16551084 0.20794066 0.40177014 0.56948888 0.00607623 0.15346835
#>  [7] 0.13083510 0.11834021 0.07913545 0.45465964

rxexp(1)
#> [1] 2.68157


## This example uses `rxexp` directly in the model

rx <- RxODE({
  a <- rxexp(2)
})
#>  

et <- et(1, id = 1:2)

s <- rxSolve(rx, et)
# }