We used a list of 20,300 keywords that were all exactly 10 characters long. Out of that list of 20,300 keywords, only 20 keywords where found within the entire OT. Which means that only .098% or only 1 out of every 1015 possible keywords in our list was discovered.
a = 20,300 possible keywords
b = 20 total keywords found
b/a * 100 = .098% of list found
a = 20,300 possible keywords
b = 20 total keywords found
Now, reduce both values by a factor of 20.
b/20 / a/20 = 1 / 1015 (1 out of 1015) = .098% ✓
See a full list of the 20,300 keywords that we used to gather the following results:
|Chronicles||3||BANDOLIERS, PRETESTING, RESOUNDING|
|Exodus*||3||CONTRITION, ERADICATES, OVERLOADED|
|Isaiah||3||RETROCEDED, RETROCEDES, STATISTICS|
|Song of Songs||0||N/A|
* Denotes one of the five books of Moses.
Our statistical analysis ends with calculating the probability value for each available keyword, because we do not have a sufficient amount of keywords at this time to perform a reliable t-test for groups of 10. Our results range from 0.000000541410 to 0.000008478672.
If the value listed under the column Unique is set to YES, then this denotes that its associated keyword could only be found one time within the entire Old Testament.
Although, our list of keywords were preselected, we still had absolutely no control over which keywords would be discovered. Many of these keywords are quite uncommon in everyday speech, therefore we define each available keyword for your convenience, below:
|BANDOLIERS||A shoulder-belt with loops or pockets for cartridges (ammo).|
|PRETESTING||A preliminary test that precedes the final test.|
|RESOUNDING||A long and loud sound.|
|RENOTIFIES||To inform or give notice to someone multiple times.|
|CONTRITION||Sincere and profound remorse for sin.|
|ERADICATES||To destroy someone or something completely and utterly.|
|OVERLOADED||To load beyond capacity; to be overburdened.|
|REBELLIONS||Resistance to or defiance of any authority, control, or tradition.|
|ADMITTANCE||The permission or right to enter into a certain location.|
|LEADENNESS||A profound sense of despair or loneliness; deep hopelessness.|
|RETROCEDED||To have gone back; to have retired; to have receded.|
|RETROCEDES||To go back; to retire; to recede.|
|STATISTICS||The study of probabilities and outcomes in the natural world.|
|TENDENCIES||A prevailing disposition to proceed toward some point, end, or result.|
|CONSIDERED||To have thought about or decided upon a subject with care.|
|REITERATED||To have repeated the same statement multiple times; often in excess.|
|NATIONALLY||Pertaining to an entire nation as an organized whole unit.|
|NEMERTINES||Any member of the invertebrate phylum Nemertea; ribbon worms.|
|STONEBOATS||A flat sledge or drag used for transporting heavy materials.|
|TANTALITES||A mineral consisting of a heavy dark lustrous oxide of mostly tantalum.|
The list of keywords that were found are quite amazing, not just because they are all defying the odds while weighing in at an astonishing 10 characters long, but also because many of them appear to summarize the plain-text from which they were extracted.
Have you ever wondered how Bible Code was encoded? Well, we have just spent the last 14 months answering this very question. In this article we will introduce to you our new 3D Bible Code Viewer, explain how it works, and we’ll even show you a few actual examples.
Our new 3D Bible Code Viewer is our take on the “Wheel of Formation”, described in the Sefer Yetzirah, that changes the way we view our results. Our users can now view their discoveries in a 3D geometric spiral projected upon a 2D surface and observe how Bible Code might have been encoded mathematically using a geometric algorithm.
In the examples below, you will see that our viewer will also draw a line that traverses about the spiral, therefore connecting each character in standard sequence, and by doing so we see a geometric shape within a geometric spiral take form and we can then see, quite clearly, how mathematics not only verifies our discoveries, but also defines how they were encoded.
How it Works
Our 3D Bible Code Viewer is easy to use and access via DivineCoders.com. You can access the 3D viewer online by clicking the new “3D Viewer” button located above each matrix.
Although the output generated by our 3D viewer appears quite complex, the logical process is actually quite simple. Our 3D viewer uses a special ID code that tells our viewer where to find all of the associated keywords, indexes, and their respective ELS values.
From this data our viewer calculates the required length and size of the spiral and creates it using actual text from the Bible in the precise location where the keyword was found. Our 3D viewer then draws a line connecting each character, thus forming a geometric shape.
Unfortunately, large keywords or keywords with a large ELS value are currently not viewable by our 3D Bible Code Viewer, because 3D geometric spirals projected upon a 2D surface tend to grow rapidly outward and therefore become much too large to be processed online.
In this instance, our 3D viewer will denote that the event has taken place and any remaining output generation will continue until there are no further keywords to process. Therefore, in some cases, there may not be any available output generated by the viewer.
Our 3D Bible Code Viewer displays a separate visual representation for each individual term that is associated to each discovery, so in order to navigate through each image, simply click the thumbnail that represents the keyword you would like to load in the 3D viewer.
Click any thumbnail below to view the full-size image.
To see our new 3D Bible Code Viewer in action, please checkout the free online demo.
See Also: New Advancements in Bible Code Research
A Brief Overview of Our Research
Using the Smith’s Bible Dictionary, we were able to compile a list of over 3000 keywords that were all between 3 and 8 characters in length. We then built specialized software that would allow us to automatically search for each keyword between an ELS range of 1 and 1500 and to calculate and record the p-value of each discovery, one book at a time.
This process ran 24 hours a day for 35 days straight and we were able to gather over 59000 samples. We then divided our samples into groups. We determined as many as 6 groups per book in most cases, because each book may consist of an array of groups and each group is determined by the character length of each sample we collected.
We then calculated the mean (average) value for each group by adding the p-vales together and dividing by the group’s total number of samples. We then calculated the significance level using the conventional .05 and dividing by the total number of samples per group.
We are now able to test for and determine statistical significance in Bible Code. Because, we have set our significance level at 5%, this means we now have only a 5% chance of producing inaccurate results, therefore not only have we achieved the ability to show evidence for true statistical significance in Bible Code, but we now have a 95% chance of being right.
Automatic Fine-Tuning Design
Our online software is responsible for fine-tuning the entire system. From the viewpoint of the system, this is an automatic process. When the world uses our online software, each result is saved to our database where they can be accessed and placed in a group.
As we continuously add more and more samples for testing, our mean values and significance levels will become more and more precise and our tests will become more accurate. Thanks to the support from thousands of people from all around the world, we have just recently added over 2000 additional samples and we are continuing to receive more each day.
Current Precision and N/A Results
Despite having gathered over 59,000 samples, we currently do not have a sufficient amount of samples to satisfy the requirements of our statistical significance test for all groups in each book. This means that, in some cases, our significance ratings may not be accurate. As a side effect you may notice a HIGH to MID rating for a keyword thought to be random.
Moreover, the same could happen in reverse, where we may rate a keyword as LOW but as our precision increases we may find that this keyword is actually MID to HIGH. So, never be too quick to accept or reject any result based on its significance level.
Furthermore, in rare cases, we may not be able to perform a significance test at all, because there were certain books where we could not locate any samples for certain groups. This was typical of keywords of 8 characters in length. So, by chance that you ever find yourself in this instance, our software will provide a significance rating of N/A to signify the event.
A Brief Overview of Our Analysis
When our initial results were compiled, we built a series of graphs based on the total number of samples in each group and when these graphs were compared, side-by-side, a pattern of normal distribution is revealed to exist throughout the entire series.
At first, these results were surprising to us, we did not expect to find any similarities in terms of what we would discover, especially a normal distribution pattern. We kept asking, ‘How is it possible for the same list of >3000 words to produce virtually the same frequency pattern in every book we searched?’ After all, we are not talking about verbatim text.
So, to find out what was causing this to happen, we processed our word list and all 39 books of the English TaNaK (JPS) to find out how many words were possible for each group and how many of these words were actually found, and it became clear why this happened.
In order to understand this concept, we must first understand what we mean when we refer to our “discoveries”. What we are referring to is a hidden message that was encoded using an equidistant letter sequence (ELS), which does not produce verbatim text.
Therefore, probabilities play a major role in what we discover.
It all goes back to what we have already known all along, which is that some words can and some words cannot produce statistical significance in Bible Code. However, we could never be sure where statistical significance actually began, until now. By graphing the mean values we were able to see the exact point where statistical significance universally begins.
Our results showed overwhelming evidence that statistical significance begins with keywords that are 7 characters in length and that significance grows rapidly beyond this point.