On Wed, Mar 13, 2013 at 12:16 AM, Neal Becker ndbeck...@gmail.com 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
Robert Kern wrote:
On Wed, Mar 13, 2013 at 12:16 AM, Neal Becker ndbeck...@gmail.com 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
Robert Kern wrote:
On Wed, Mar 13, 2013 at 12:16 AM, Neal Becker ndbeck...@gmail.com 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
On Thu, Mar 14, 2013 at 11:00 AM, Neal Becker ndbeck...@gmail.com wrote:
Robert Kern wrote:
On Wed, Mar 13, 2013 at 12:16 AM, Neal Becker ndbeck...@gmail.com 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
Robert Kern wrote:
On Thu, Mar 14, 2013 at 11:00 AM, Neal Becker ndbeck...@gmail.com wrote:
Robert Kern wrote:
On Wed, Mar 13, 2013 at 12:16 AM, Neal Becker ndbeck...@gmail.com wrote:
I guess I talked to you about 100 years ago about sharing state between
numpy
rng and code I have in c++
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 that.
On Mon, Mar 11, 2013 at 9:46 AM, Robert Kern robert.k...@gmail.com wrote:
On Sun, Mar 10, 2013 at 6:12 PM, Siu Kwan Lam s...@continuum.io 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
On Tue, Mar 12, 2013 at 9:25 PM, Nathaniel Smith n...@pobox.com wrote:
On Mon, Mar 11, 2013 at 9:46 AM, Robert Kern robert.k...@gmail.com wrote:
On Sun, Mar 10, 2013 at 6:12 PM, Siu Kwan Lam s...@continuum.io wrote:
My suggestion to overcome (1) and (2) is to allow the user to select between
On Tue, Mar 12, 2013 at 5:27 PM, Nathaniel Smith n...@pobox.com wrote:
On Tue, Mar 12, 2013 at 9:25 PM, Nathaniel Smith n...@pobox.com wrote:
On Mon, Mar 11, 2013 at 9:46 AM, Robert Kern robert.k...@gmail.com wrote:
On Sun, Mar 10, 2013 at 6:12 PM, Siu Kwan Lam s...@continuum.io wrote:
My
Nathaniel Smith wrote:
On Tue, Mar 12, 2013 at 9:25 PM, Nathaniel Smith n...@pobox.com wrote:
On Mon, Mar 11, 2013 at 9:46 AM, Robert Kern robert.k...@gmail.com wrote:
On Sun, Mar 10, 2013 at 6:12 PM, Siu Kwan Lam s...@continuum.io wrote:
My suggestion to overcome (1) and (2) is to allow the
On Tue, Mar 12, 2013 at 10:38 PM, Neal Becker ndbeck...@gmail.com wrote:
Nathaniel Smith wrote:
On Tue, Mar 12, 2013 at 9:25 PM, Nathaniel Smith n...@pobox.com wrote:
On Mon, Mar 11, 2013 at 9:46 AM, Robert Kern robert.k...@gmail.com wrote:
On Sun, Mar 10, 2013 at 6:12 PM, Siu Kwan Lam
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,
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 could
On Tue, Mar 12, 2013 at 7:10 PM, Robert Kern robert.k...@gmail.com wrote:
On Tue, Mar 12, 2013 at 10:38 PM, Neal Becker ndbeck...@gmail.com wrote:
Nathaniel Smith wrote:
On Tue, Mar 12, 2013 at 9:25 PM, Nathaniel Smith n...@pobox.com wrote:
On Mon, Mar 11, 2013 at 9:46 AM, Robert Kern
On Sun, Mar 10, 2013 at 6:12 PM, Siu Kwan Lam s...@continuum.io 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
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.
16 matches
Mail list logo