Big Data Vs Bible Code
While I upgrade myself on BigData I landed on one writeup on Bible Code Vs Machine Learning Vs Big Data which is really a amazing one. So just wanted to share to my friends
The Bible Code is much more complex than this simple pattern searching, however. Variable skip letter values are employed, and the entire Torah is searched with each value. But then each of these results are overlayed with the results of other skip letter value results (see the red and blue highlighted letters in the above figure), in order to see if "relevant" terms overlap at some "significant" intersection, and so on, and so on, layering these ELS results one on top of another. Given this complexity, ELS and its application to the Bible Code is a problem that can be reduced to the cross product of an incredible number of parameters and, as such, result permutations become astronomical in size, and eventually something "significant" arises.
Similar results of significant findings have been replicated in a variety of other works of non-trivial length (see the above discrediting links). Given enough letters, skip sequences, and layers, even if you don't find some initial result of interest, continued (indefinite?) looking (elsewhere) should eventually turn up something juicy (Presidential election results, terror attacks, assassinations, all apparently encoded in the Bible).
This continued searching, without regard to a hypothesis or the bounds of probability that go along with these result set permutations, suggest that actual significant events will be lost in the fray. The Look-elsewhere Effect is another example of how Big Data can be abused unwittingly.
- Extract from Matthew Mayo blog on KDnuggets(Thanx a ton )
Comments
Post a Comment