public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Robert G. Brown" <rgb@phy.duke.edu>
To: GSL Discussion list <gsl-discuss@sources.redhat.com>
Cc: David Bauer <astgtciv2009@gatech.edu>
Subject: New rngs...
Date: Thu, 08 Oct 2009 13:46:00 -0000	[thread overview]
Message-ID: <alpine.LFD.2.00.0910080934250.3130@lilith> (raw)

Dear Brian et. al.

As we're discussing the roadmap for a new GSL, I'd like to offer up at
least two, maybe three more random number generators for inclusion in
the GSL list that have been contributed and integrated into dieharder.
One that I think should absolutely be there is rng_aes -- basically an
implementation of AES as a random number generator.  AES is
cryptographic grade random and is arguably very close to a "gold
standard" that can be used to test random number generator testers, as
there is always an unstated addition to the null hypothesis "Assuming
that this is a perfect random number generator AND that this is a valid
test...", and failure of the latter is very difficult to discriminate
from failure of the former without at least a few generators for which
failure of the former is arguably less likely than failure of the
latter.  rng_threefish does the same thing on top of many rounds of
skein.  I was using aespipe to feed dieharder in a pipe until these were
contributed, but having them integrated is worthwhile, especially given
that rng_aes is respectably fast, around 1/5 the speed of mt19937.

    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:[~2009-10-08 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 13:46 Robert G. Brown [this message]
2009-10-14 16:12 ` Jonathan Leto
2009-10-14 16:59   ` Robert G. Brown
2009-10-23 21:28   ` Brian Gough

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.00.0910080934250.3130@lilith \
    --to=rgb@phy.duke.edu \
    --cc=astgtciv2009@gatech.edu \
    --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).