@@ -10,15 +10,15 @@ although :class:`~randomgen.sfc64.SFC64` and :class:`~randomgen.xoshiro256.Xoshi
10
10
are both excellent alternatives.
11
11
12
12
For very large scale
13
- applications -- requiring 1,000+ streams,
14
- :class: `~randomgen.pcg64.PCG64DXSM `, :class: `~randomgen.sfc64.SFC64 `
15
- using distinct Weyl increments (``k ``), or one of the cryptography-based generators
16
- :class: `~randomgen.aes.AESCounter ` (if you have hardware acceleration),
13
+ applications -- requiring 1,000+ streams --
14
+ :class: `~randomgen.pcg64.PCG64DXSM ` combined with a :class: `~numpy.random.SeedSequence ` and `` spawn ``,
15
+ :class: ` ~randomgen.sfc64.SFC64 ` initialized using distinct Weyl increments (``k ``), or one of
16
+ the cryptography-based generators :class: `~randomgen.aes.AESCounter ` (if you have hardware acceleration),
17
17
:class: `~randomgen.effix64.EFFIC64 `, :class: `~randomgen.speck128.SPECK128 `,
18
18
:class: `~randomgen.philox.Philox `, or :class: `~randomgen.hc128.HC128 ` if you do not)
19
- are all excellent choices.
19
+ initialized with distinct keys are all excellent choices.
20
20
21
- Unless you need backward compatibilyt , there are no longer good reasons to any
21
+ Unless you need backward compatibility , there are no good reasons to use any
22
22
of the Mersenne Twister PRNGS: :class: `~randomgen.mt19937.MT19937 `, :class: `~randomgen.mt64.MT64 `,
23
23
:class: `~randomgen.sfmt.SFMT `, and :class: `~randomgen.dsfmt.DSFMT `.
24
24
0 commit comments