Unless I'm missing something, I don't think this would work. The random
numbers are generated in the C library and while I could replace the RNG
I use now with the RNG from SyncRNG, requiring the users to take action
for this seems to place an unnecessary burden on them.
Gertjan
On 04/18/2018 10:01 PM, Iñaki Úcar wrote:
2018-04-18 22:49 GMT+02:00 Gertjan van den Burg <gertjanvandenb...@gmail.com>:
Thanks for your comment. Your suggestion wouldn't solve my original problem
unfortunately, because then I'd have to reverse engineer R's RNG for my
Python package. Besides, the quality of the random numbers doesn't really
matter here, it only matters that they're the same across my packages.
You could instead write a vignette instructing the user on how to
replace the default RNG with your SyncRNG. Wouldn't this solve the
problem?
Iñaki
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
