public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Robert G. Brown" <rgb@phy.duke.edu>
To: Brian Gough <bjg@gnu.org>
Cc: GSL Discussion list <gsl-discuss@sources.redhat.com>
Subject: Re: Three random number generators...
Date: Fri, 07 Jan 2011 20:49:00 -0000	[thread overview]
Message-ID: <alpine.LFD.2.02.1101071533430.5295@lilith> (raw)
In-Reply-To: <43r5cojy1y.wl%bjg@gnu.org>

On Fri, 7 Jan 2011, Brian Gough wrote:

> At Fri, 7 Jan 2011 13:47:41 -0500 (EST),
> Robert G. Brown wrote:
>>
>> I have three random number generators that I think ought to go into the
>> GSL.  One is AES -- which is pretty self explanatory -- fairly fast,
>> cryptographic strength.
>> ...
>> Basically, I'm suggesting that it is time to update the random number
>> generators in the GSL to make them more consistent with state of the art
>> in speed and tested randomness.
>
> Thanks for that, I am happy to add the AES and KISS (or an enhanced
> version of it).  Instead of seeding with mt19937, I think it would be
> preferable to generate the seeds inline and have the generator
> standalone if possible. Maybe the 69069 LCG used elsewhere would
> be sufficient(?), otherwise a strong hash function.

Either one would be fine with me (it was just so EASY to use mt because
the GSL is so EASY to use:-).  I'll get a recent copy of the sources and
see what you use IN the mt generators, which also require some work to
initialize IIRC.

That might take me a few days.  I also need to do some careful
testing...;-)

I'll send them on when done.

    rgb

Robert G. Brown	                       http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567  Fax: 919-660-2525     email:rgb@phy.duke.edu


      reply	other threads:[~2011-01-07 20:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 18:47 Robert G. Brown
2011-01-07 19:48 ` Brian Gough
2011-01-07 20:49   ` Robert G. Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.02.1101071533430.5295@lilith \
    --to=rgb@phy.duke.edu \
    --cc=bjg@gnu.org \
    --cc=gsl-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).