Comments (13)
There is a math stack exchange post that says basically, that this project is a joke (see accepted answer)
http://math.stackexchange.com/questions/1771771/how-to-find-sequence-of-digits-in-pi/1771809#1771809
because for practical reasons, the compression value itself would be larger than the file you are trying to compress because the start index would be so big, also for other reasons described there.
Would you agree with that post?
from pifs.
Best response
from pifs.
Also very instructive
http://math.stackexchange.com/questions/216343/does-pi-contain-all-possible-number-combinations
from pifs.
So if its not proven and we just think that it's the case, there's no guarantee that what you want to compress will even work. Also, even if the finite sequence were to exist, how does this program even find the starting index without trial and error brute force? How does it do this http://www.angio.net/pi/piquery basically?
from pifs.
Basically, it inferred that because it is an endless and randomly distributed sequence, there is a probability of finding a finite sequence within this, given the existence of enough time and computational factor to integrate up to the point to locate this finite sequence, as we can not prove its non-existence because it would be necessary forever integrate this number.
In particular, if we generate a number from an infinite stream of digits selected uniformly at random, then there is a probability of 100% that such a number contains each and every finite sequences of digits. Your statement remains true, we can't prove it unless we run all of the pi number. The only true statement is that a normal number cannot contain another normal number as a subset, but I can't present this proof by now.
https://en.wikipedia.org/wiki/Normal_number
from pifs.
About the query, it simply does an integral math on the number and extract the sequence by brute force. When he located the sequence, the contained information it's more easily calculated with the position and offset of the sequence.
This, if we use a easily mathematically calculated normal number, like pi, sqrt(2) or e, for example. Since we don't know the problem extension, we can't even assure how is the Big-O notation for this, or for any other number, and even if we can find the related sequence on the normal number.
So, essentially this is a logic statement that we can't directly verify, but we can play with the idea.
from pifs.
Yes, it is a joke, on the fact that we can't even prove if it coalesces into something palpable...
from pifs.
In the fact, it doesn't compress anything, it simply stores it by provide a index and offset of the finite sequence we are searching, into the infinite normal set. The "compression" factor exists in the only need to store the index and the offset (and the integration formula) outside.
from pifs.
In some (in fact, many) cases, the index number could be greater than the "encoded" itself. So, the fact remains that we can't consider it as "compression" but "store".
from pifs.
So on the home page it says like They said 100% compression was impossible? You're looking at it!
, but really its more like almost all of the time, increasing the size needed to store the new data...lol
from pifs.
I think this can be used in a sort of encryption, since if we hide the normal number / integration formula, we can easilly create a good crypto system, based on the indexes and offsets. This virtually cannot be targeted by frequency analysis in a traditional way, IMHO.
from pifs.
I think it becomes a good practical idea in the sense that it's not meant for compression but more for something like encryption.
from pifs.
@isapol what do you reckon?
from pifs.
Related Issues (20)
- Performance: get_byte() lookup table
- Security : Everybody has my files HOT 5
- Get to 314 issues HOT 1
- π is a false constant, you should store data in τ instead HOT 11
- Unit test that proves pi is normal HOT 7
- Inception- No saftey net
- Expander? HOT 1
- GDPR Compliance HOT 7
- Misleading/Incorrect claim regarding compression. HOT 15
- Use pifs to store metadata HOT 4
- Viewing the output MetaData file HOT 1
- Maybe have a compression setting?
- ./configure: line 4310: syntax error near unexpected token `FUSE,` HOT 3
- Is there an automated tool to decrypt the metadata? HOT 2
- Copyright HOT 4
- Stop development HOT 3
- Metadata error
- Shorthand encoding for positions
- How does the metadata work, and how can I retrieve my data?
- Support for √2? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pifs.