unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
To: guile-devel@gnu.org
Subject: Re: Improve `seed->random-state' in stable-2.0?
Date: Fri, 20 Jan 2012 09:37:21 +0100	[thread overview]
Message-ID: <87zkdin51a.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 87d3afvyr6.fsf@netris.org

Mark H Weaver <mhw@netris.org> writes:

> I know how to make this _much_ better, but here's the question: is it
> okay to change the behavior of the random number generator in 2.0?  Or
> is it important that the same sequence of random numbers are generated
> from a given seed in the entire stable-2.0 series?

As long as the total _sequence_ stays the same (and does not contain
duplicate values), I would not worry.  If the sequence itself becomes
different, then the probability of two random subsequences having at
least one match match grows with the product rather than the sum of
their length.  Of course, if the subsequences _do_ overlap, you tend to
get colliding sequences instead of just single outliers.

-- 
David Kastrup




  reply	other threads:[~2012-01-20  8:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20  3:28 Improve `seed->random-state' in stable-2.0? Mark H Weaver
2012-01-20  8:37 ` David Kastrup [this message]
2012-01-20 14:54 ` Andy Wingo
2012-01-20 18:52   ` Mark H Weaver
2012-01-20 20:35     ` Andy Wingo
2012-01-20 22:45       ` Mark H Weaver
2012-01-21  7:38         ` David Kastrup
2012-01-21  8:20           ` Mark H Weaver
2012-01-23  9:52         ` Andy Wingo
2012-01-20 23:46       ` Mike Gran
2012-01-23  9:55         ` Andy Wingo
2012-01-23 13:06           ` Mike Gran
2012-01-23 14:06             ` Andy Wingo
2012-01-24  6:08               ` Mike Gran
2012-01-24  9:56                 ` Andy Wingo

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=87zkdin51a.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=guile-devel@gnu.org \
    /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).