On Mon, May 23, 2016 at 5:41 PM, Chris Barker wrote:
>
> On Sun, May 22, 2016 at 2:35 AM, Robert Kern
wrote:
>>
>> Well, I mean, engineers want lots of things. I suspect that most
engineers *really* just want to call `numpy.random.seed(8675309)` at the
start and never explicitly pass around separ
On Sun, May 22, 2016 at 2:35 AM, Robert Kern wrote:
>
> Well, I mean, engineers want lots of things. I suspect that most engineers
> *really* just want to call `numpy.random.seed(8675309)` at the start and
> never explicitly pass around separate streams. There's an upside to that in
> terms of cod
On Wed, May 18, 2016 at 7:56 PM, Nathaniel Smith wrote:
>
> On Wed, May 18, 2016 at 5:07 AM, Robert Kern
wrote:
> > On Wed, May 18, 2016 at 1:14 AM, Nathaniel Smith wrote:
> >> ...anyway, the real reason I'm a bit grumpy is because there are solid
> >> engineering reasons why users *want* this
On Wed, May 18, 2016 at 5:07 AM, Robert Kern wrote:
> On Wed, May 18, 2016 at 1:14 AM, Nathaniel Smith wrote:
>>
>> On Tue, May 17, 2016 at 10:41 AM, Robert Kern
>> wrote:
>> > On Tue, May 17, 2016 at 6:24 PM, Nathaniel Smith wrote:
>> >>
>> >> On May 17, 2016 1:50 AM, "Robert Kern" wrote:
>>
On Wed, May 18, 2016 at 6:20 PM, wrote:
>
> On Wed, May 18, 2016 at 12:01 PM, Robert Kern
wrote:
>>
>> On Wed, May 18, 2016 at 4:50 PM, Chris Barker
wrote:
>> >>
>> >> > ...anyway, the real reason I'm a bit grumpy is because there are
solid
>> >> > engineering reasons why users *want* this API,
On Wed, May 18, 2016 at 12:01 PM, Robert Kern wrote:
> On Wed, May 18, 2016 at 4:50 PM, Chris Barker
> wrote:
> >>
> >> > ...anyway, the real reason I'm a bit grumpy is because there are solid
> >> > engineering reasons why users *want* this API,
> >
> > Honestly, I am lost in the math -- but li
On Wed, May 18, 2016 at 4:50 PM, Chris Barker wrote:
>>
>> > ...anyway, the real reason I'm a bit grumpy is because there are solid
>> > engineering reasons why users *want* this API,
>
> Honestly, I am lost in the math -- but like any good engineer, I want to
accomplish something anyway :-) I tru
>
> > ...anyway, the real reason I'm a bit grumpy is because there are solid
> > engineering reasons why users *want* this API,
>
Honestly, I am lost in the math -- but like any good engineer, I want to
accomplish something anyway :-) I trust you guys to get this right -- or at
least document what
On Wed, May 18, 2016 at 1:14 AM, Nathaniel Smith wrote:
>
> On Tue, May 17, 2016 at 10:41 AM, Robert Kern
wrote:
> > On Tue, May 17, 2016 at 6:24 PM, Nathaniel Smith wrote:
> >>
> >> On May 17, 2016 1:50 AM, "Robert Kern" wrote:
> >> >
> >> [...]
> >> > What you want is a function that returns
On Tue, May 17, 2016 at 10:41 AM, Robert Kern wrote:
> On Tue, May 17, 2016 at 6:24 PM, Nathaniel Smith wrote:
>>
>> On May 17, 2016 1:50 AM, "Robert Kern" wrote:
>> >
>> [...]
>> > What you want is a function that returns many RandomState objects that
>> > are hopefully spread around the MT1993
On Tue, May 17, 2016 at 6:24 PM, Nathaniel Smith wrote:
>
> On May 17, 2016 1:50 AM, "Robert Kern" wrote:
> >
> [...]
> > What you want is a function that returns many RandomState objects that
are hopefully spread around the MT19937 space enough that they are
essentially independent (in the absen
On May 17, 2016 1:50 AM, "Robert Kern" wrote:
>
[...]
> What you want is a function that returns many RandomState objects that
are hopefully spread around the MT19937 space enough that they are
essentially independent (in the absence of true jumpahead). The better
implementation of such a function
On Tue, May 17, 2016 at 9:40 AM, Sturla Molden
wrote:
> Stephan Hoyer wrote:
> > I have recently encountered several use cases for randomly generate
> random
> > number seeds:
> >
> > 1. When writing a library of stochastic functions that take a seed as an
> > input argument, and some of these f
On Tue, May 17, 2016 at 2:40 PM, Sturla Molden
wrote:
>
> Stephan Hoyer wrote:
> > I have recently encountered several use cases for randomly generate
random
> > number seeds:
> >
> > 1. When writing a library of stochastic functions that take a seed as an
> > input argument, and some of these fu
Stephan Hoyer wrote:
> I have recently encountered several use cases for randomly generate random
> number seeds:
>
> 1. When writing a library of stochastic functions that take a seed as an
> input argument, and some of these functions call multiple other such
> stochastic functions. Dask is one
On Tue, May 17, 2016 at 4:49 AM, Robert Kern wrote:
> On Tue, May 17, 2016 at 9:09 AM, Stephan Hoyer wrote:
> >
> > On Tue, May 17, 2016 at 12:18 AM, Robert Kern
> wrote:
> >>
> >> On Tue, May 17, 2016 at 4:54 AM, Stephan Hoyer
> wrote:
> >> > 1. When writing a library of stochastic functions
On Tue, May 17, 2016 at 9:09 AM, Stephan Hoyer wrote:
>
> On Tue, May 17, 2016 at 12:18 AM, Robert Kern
wrote:
>>
>> On Tue, May 17, 2016 at 4:54 AM, Stephan Hoyer wrote:
>> > 1. When writing a library of stochastic functions that take a seed as
an input argument, and some of these functions cal
On Tue, May 17, 2016 at 12:18 AM, Robert Kern wrote:
> On Tue, May 17, 2016 at 4:54 AM, Stephan Hoyer wrote:
> > 1. When writing a library of stochastic functions that take a seed as an
> input argument, and some of these functions call multiple other such
> stochastic functions. Dask is one suc
On Tue, May 17, 2016 at 4:54 AM, Stephan Hoyer wrote:
>
> I have recently encountered several use cases for randomly generate
random number seeds:
>
> 1. When writing a library of stochastic functions that take a seed as an
input argument, and some of these functions call multiple other such
stoch
Looking at the dask helper function again reminds me of an important cavaet
to this approach, which was pointed out to me by Clark Fitzgerald.
If you generate a moderately large number of random seeds in this fashion,
you are quite likely to have collisions due to the Birthday Paradox. For
example
20 matches
Mail list logo
