1/ RFC: I just released a rough cut of pytest-caprng. It captures the state of your random number generator before each test; saves it on failure; and, replays it *exactly* on the next run. If you write randomized algos or simulations, you'll like this.https://github.com/jbn/pytest-caprng …
Yea, like you expressed in the intro -- it's valuable to many, but passing around the instantiated PRNG is more robust. That said, it's often expensive in smaller codebases or codebases which rely upon packages that don't allow passing.
-
-
My use case is normally small-ish ABM/DES models whose scheduling patterns don't permit simultaneous computation. In which case, I'm restricted to multiprocessing anyway. (Although, I sometimes use an RNG param as a cheap "stochastic" annotation that also permits robustness.)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.