public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matti Nykyri <matti.nykyri@iki.fi>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: OT Best way to compress files with digits
Date: Sun, 2 Nov 2014 14:06:09 +0200	[thread overview]
Message-ID: <14914DDC-1E9F-443C-BD65-5673B9CD4426@iki.fi> (raw)
In-Reply-To: <54555725.30108@ntlworld.com>

> On Nov 1, 2014, at 23:56, David W Noon <dwnoon@ntlworld.com> wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Sat, 01 Nov 2014 22:47:15 +0200, Alan Mckinnon
> (alan.mckinnon@gmail.com) wrote about "Re: [gentoo-user] Re: OT Best
> way to compress files with digits" (in <545546D3.3030005@gmail.com>):
> 
>> On 01/11/2014 19:59, meino.cramer@gmx.de wrote:
> [snip]
>>> Ah! By the way...I was astonished to read, that the digits of PI
>>> are called random on the one hand and on the other hand there is
>>> a formula [1] to calculate a certain digit of PI without
>>> calculation of the previous digits... Calculated random? Are
>>> nature constants the purest form of PRNGs ??? ;) (Quantum physics
>>> is everywhere... ;;))
>>> 
>>> [1]:
>>> http://en.wikipedia.org/wiki/Bailey%E2%80%93Borwein%E2%80%93Plouffe_formula
>> 
>> 
>> The sequence of digits that make up pi are a random sequence - you
>> can analyze the order any way you want and you'll find no inherent
>> pattern.
> 
> Actually, the sequence of digits is most definitely *not* random.  If
> the sequence of digits is written any other way then the value is not
> Pi.  Hence the sequence is unique, not random.
> 
> I think what you are grasping for is that the frequency of distinct
> digits tends to be uniform: 0's occur as often as 1's as often ... as
> 9's.  Note that the "as often as" operator is really approximate for
> finite sub-sequences, but is asymptotically accurate.
> 
> Moreover, this is the same in any number base: the binary
> representation has 0's occurring as often as 1's; the ternary
> representation has 0's occurring as often as 1' and as often as 2's;
> etc., etc.
> 
> Such numbers are called "normal".  It was a poor choice of name, but
> we are stuck with it.  I would have called them "digit soup" numbers
> - -- an oblique reference to alphabet soup.

Well all the digit of pi can be compressed to the following:

=pi();

If you have the infinite series that calculates the digits :)

>> However, any given digit in the sequence is 100% predictable, as
>> you just showed :-)
>> 
>> Randomness has got to be the second most mind-boggling thing out
>> there, first being quantumness (that's not a waord, I just made it
>> up. You you should get the meaning OK from context ;-) )
> 
> I would say that probability theory is more mind boggling, as it
> underpins much of quantum theory.  But, as someone who majored in
> probability theory, I might be biased. [Incidentally, there is a small
> statistical joke in that last sentence.]
> 
> Getting back to Meino's original request, one of the optimum
> compression algorithms for this would be custom Huffman encoding.  To
> do this the algorithm requires that all the data (i.e. digits) be read
> and a frequency table built.  The only problem is that to read all the
> digits of Pi could take rather a long time. ... :-)

That would take infinite time :)

> - -- 
> Regards,
> 
> Dave  [RLU #314465]
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> dwnoon@ntlworld.com (David W Noon)
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iEYEARECAAYFAlRVVyQACgkQRQ2Fs59Psv/9qwCeKwuLz/7RGEV06X+RdDQryDe+
> /xwAoK1qMgb9RZXkQByBUMqB8eqs20bG
> =XUPB
> -----END PGP SIGNATURE-----
> 


  reply	other threads:[~2014-11-02 12:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 15:36 [gentoo-user] OT Best way to compress files with digits meino.cramer
2014-10-31 15:45 ` Ralf
2014-10-31 15:59   ` meino.cramer
2014-10-31 16:52     ` Helmut Jarausch
2014-10-31 17:56     ` Rich Freeman
2014-10-31 18:55       ` David Haller
2014-10-31 19:23         ` Rich Freeman
2014-10-31 20:25           ` [gentoo-user] " Grant Edwards
2014-10-31 22:22             ` Rich Freeman
2014-11-01 17:15 ` James
2014-11-01 17:26   ` Alan McKinnon
2014-11-01 20:18     ` Matti Nykyri
2014-11-01 17:59   ` meino.cramer
2014-11-01 20:47     ` Alan McKinnon
2014-11-01 21:56       ` David W Noon
2014-11-02 12:06         ` Matti Nykyri [this message]
2014-11-03 15:48           ` Grant Edwards
2014-11-02 19:55         ` Alan McKinnon
2014-11-02 22:03           ` Peter Humphrey
2014-11-03 19:37             ` Mick
2014-11-04  2:04               ` Peter Humphrey
2014-11-04  6:35                 ` Mick

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=14914DDC-1E9F-443C-BD65-5673B9CD4426@iki.fi \
    --to=matti.nykyri@iki.fi \
    --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