Robert Kern wrote:
> On Thu, Mar 14, 2013 at 11:00 AM, Neal Becker wrote:
>> Robert Kern wrote:
>>
>>> On Wed, Mar 13, 2013 at 12:16 AM, Neal Becker wrote:
I guess I talked to you about 100 years ago about sharing state between
numpy
rng and code I have in c++ that wraps boost::ra
On Thu, Mar 14, 2013 at 11:00 AM, Neal Becker wrote:
> Robert Kern wrote:
>
>> On Wed, Mar 13, 2013 at 12:16 AM, Neal Becker wrote:
>>> I guess I talked to you about 100 years ago about sharing state between
>>> numpy
>>> rng and code I have in c++ that wraps boost::random. So is there a C-api
Robert Kern wrote:
> On Wed, Mar 13, 2013 at 12:16 AM, Neal Becker wrote:
>> I guess I talked to you about 100 years ago about sharing state between numpy
>> rng and code I have in c++ that wraps boost::random. So is there a C-api for
>> this RandomState object I could use to call from c++? May
Robert Kern wrote:
> On Wed, Mar 13, 2013 at 12:16 AM, Neal Becker wrote:
>> I guess I talked to you about 100 years ago about sharing state between numpy
>> rng and code I have in c++ that wraps boost::random. So is there a C-api for
>> this RandomState object I could use to call from c++? May
On Wed, Mar 13, 2013 at 12:16 AM, Neal Becker wrote:
> I guess I talked to you about 100 years ago about sharing state between numpy
> rng and code I have in c++ that wraps boost::random. So is there a C-api for
> this RandomState object I could use to call from c++? Maybe I could do
> something
Neal Becker wrote:
> Neal Becker wrote:
>
>> I guess I talked to you about 100 years ago about sharing state between numpy
>> rng and code I have in c++ that wraps boost::random. So is there a C-api for
>> this RandomState object I could use to call from c++? Maybe I could do
>> something with
On Tue, Mar 12, 2013 at 7:10 PM, Robert Kern wrote:
> On Tue, Mar 12, 2013 at 10:38 PM, Neal Becker wrote:
>> Nathaniel Smith wrote:
>>
>>> On Tue, Mar 12, 2013 at 9:25 PM, Nathaniel Smith wrote:
On Mon, Mar 11, 2013 at 9:46 AM, Robert Kern wrote:
> On Sun, Mar 10, 2013 at 6:12 PM, Siu
Neal Becker wrote:
> I guess I talked to you about 100 years ago about sharing state between numpy
> rng and code I have in c++ that wraps boost::random. So is there a C-api for
> this RandomState object I could use to call from c++? Maybe I could do
> something with that.
>
> The c++ code coul
I guess I talked to you about 100 years ago about sharing state between numpy
rng and code I have in c++ that wraps boost::random. So is there a C-api for
this RandomState object I could use to call from c++? Maybe I could do
something with that.
The c++ code could invoke via the python api,
On Tue, Mar 12, 2013 at 10:38 PM, Neal Becker wrote:
> Nathaniel Smith wrote:
>
>> On Tue, Mar 12, 2013 at 9:25 PM, Nathaniel Smith wrote:
>>> On Mon, Mar 11, 2013 at 9:46 AM, Robert Kern wrote:
On Sun, Mar 10, 2013 at 6:12 PM, Siu Kwan Lam wrote:
> My suggestion to overcome (1) and (2
Nathaniel Smith wrote:
> On Tue, Mar 12, 2013 at 9:25 PM, Nathaniel Smith wrote:
>> On Mon, Mar 11, 2013 at 9:46 AM, Robert Kern wrote:
>>> On Sun, Mar 10, 2013 at 6:12 PM, Siu Kwan Lam wrote:
My suggestion to overcome (1) and (2) is to allow the user to select
between the two impleme
On Tue, Mar 12, 2013 at 5:27 PM, Nathaniel Smith wrote:
> On Tue, Mar 12, 2013 at 9:25 PM, Nathaniel Smith wrote:
>> On Mon, Mar 11, 2013 at 9:46 AM, Robert Kern wrote:
>>> On Sun, Mar 10, 2013 at 6:12 PM, Siu Kwan Lam wrote:
My suggestion to overcome (1) and (2) is to allow the user to se
On Tue, Mar 12, 2013 at 9:25 PM, Nathaniel Smith wrote:
> On Mon, Mar 11, 2013 at 9:46 AM, Robert Kern wrote:
>> On Sun, Mar 10, 2013 at 6:12 PM, Siu Kwan Lam wrote:
>>> My suggestion to overcome (1) and (2) is to allow the user to select between
>>> the two implementations (and possibly differe
On Mon, Mar 11, 2013 at 9:46 AM, Robert Kern wrote:
> On Sun, Mar 10, 2013 at 6:12 PM, Siu Kwan Lam wrote:
>> My suggestion to overcome (1) and (2) is to allow the user to select between
>> the two implementations (and possibly different algorithms in the future).
>> If user does not provide a ch
On Sun, Mar 10, 2013 at 6:12 PM, Siu Kwan Lam wrote:
> Hi all,
>
> I am redirecting a discussion on github issue tracker here. My original
> post (https://github.com/numpy/numpy/issues/3137):
>
> "The current implementation of the RNG seems to be MT19937-32. Since 64-bit
> machines are common now
Hi all,
I am redirecting a discussion on github issue tracker here. My original post
(https://github.com/numpy/numpy/issues/3137):
"The current implementation of the RNG seems to be MT19937-32. Since 64-bit
machines are common nowadays, I am suggesting adding or upgrading to
MT19937-64. Thou
16 matches
Mail list logo
