public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: »Q« <boxcars@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: OT: Mapping random numbers (PRNG)
Date: Sat, 28 Jun 2014 20:46:15 -0500	[thread overview]
Message-ID: <20140628204615.424f3b89@sepulchrave.remarqs> (raw)
In-Reply-To: CADPrc83NbuNwAog_QQZWJoGArqTZDUsDwVAbiXSNDJ+3by3_xw@mail.gmail.com

On Sat, 28 Jun 2014 19:53:08 -0500
Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Sat, Jun 28, 2014 at 7:37 PM,  <gottlieb@nyu.edu> wrote:
> > On Sat, Jun 28 2014, Canek Peláez Valdés wrote:
> >
> >> That doesn't matter. Take a non-negative integer N; if you flip a
> >> coin an infinite number of times, then the probability of the coin
> >> landing on the same face N times in a row is 1.
> >
> > This is certainly true.
> >
> >> This means that it is *guaranteed* to happen
> >
> > That is not as clear.
> 
> Let me be more precise (and please correct me if I'm wrong): It is
> guaranteed to happen at some point in the infinite sequence of random
> flip coins, but we cannot know when it will happen, only that it will
> happen.
> 
> That's the way I got it when I took my probability courses, admittedly
> many years ago.

The probability is 1 in the sense that the as the number of flips M
increases, so does the probability of getting N heads (or tails) in a
row also increases, and the upper bound for the sequence of
probabilities is 1.  It's not a probability about something which
actually happens;  no one so far has been able to flip a coin an
infinite number of times, not even a computer.

> In any way, even if I'm wrong and it is not guaranteed, the main point
> remains true: the probability of getting a large sequence of the same
> number from a RNG is 1 for every true random RNG, and therefore seeing
> a large sequence of the same number form a RNG doesn't (technically)
> means that it is broken.

It's true that that wouldn't *prove* the generator is broken.  But it
might be a good reason to take another look at the algorithm.
> 
> Regards.





  reply	other threads:[~2014-06-29  1:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  2:56 [gentoo-user] OT: Mapping random numbers (PRNG) meino.cramer
2014-06-06  3:58 ` Canek Peláez Valdés
2014-06-06 18:39   ` meino.cramer
2014-06-06 19:37     ` null_ptr
2014-06-06 19:55     ` Canek Peláez Valdés
2014-06-06 21:05     ` Matti Nykyri
2014-06-06 21:03   ` Matti Nykyri
2014-06-07  9:19     ` Matti Nykyri
2014-06-07 12:13       ` Marc Joliet
2014-06-26 21:00     ` [gentoo-user] " Kai Krakow
2014-06-26 22:07       ` Kai Krakow
2014-06-27  8:55         ` thegeezer
2014-06-27 17:49           ` Matti Nykyri
2014-06-27 17:50           ` [gentoo-user] " Kai Krakow
2014-06-27 20:59             ` Neil Bothwick
2014-06-27 21:13       ` [gentoo-user] " Matti Nykyri
2014-06-28 13:08         ` Matti Nykyri
2014-06-28 21:28         ` [gentoo-user] " Kai Krakow
2014-06-28 22:06           ` Canek Peláez Valdés
2014-06-29  0:37             ` gottlieb
2014-06-29  0:53               ` Canek Peláez Valdés
2014-06-29  1:46                 ` »Q« [this message]
2014-06-29  2:57                   ` [gentoo-user] " Canek Peláez Valdés
2014-06-29  6:24           ` [gentoo-user] " Matti Nykyri
2014-06-29 12:38             ` [gentoo-user] " Kai Krakow
2014-06-30 23:47               ` Matti Nykyri

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=20140628204615.424f3b89@sepulchrave.remarqs \
    --to=boxcars@gmx.net \
    --cc=gentoo-user@lists.gentoo.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