From: Brian Gough <bjg@gnu.org>
To: "Robert G. Brown" <rgb@phy.duke.edu>
Cc: GSL Discussion list <gsl-discuss@sources.redhat.com>
Subject: Re: Three random number generators...
Date: Fri, 07 Jan 2011 19:48:00 -0000 [thread overview]
Message-ID: <43r5cojy1y.wl%bjg@gnu.org> (raw)
In-Reply-To: <alpine.LFD.2.02.1101071303570.5295@lilith>
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.
next prev parent reply other threads:[~2011-01-07 19:48 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 [this message]
2011-01-07 20:49 ` Robert G. Brown
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=43r5cojy1y.wl%bjg@gnu.org \
--to=bjg@gnu.org \
--cc=gsl-discuss@sources.redhat.com \
--cc=rgb@phy.duke.edu \
/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).