VERSE PERMUTATION EXPERIMENT FOR ELS MAP 1 START

     On July 19, 2009, after a decade old request by me for a control text in CodeFinder that was based not on the existing letter-permuted text, but rather on a verse-permuted Torah text, Dr. Robert Haralick finally sent me 10 such control texts.  Why is this important?  It is important because the commercially available control scrambles the Torah so thoroughly that the file is useless for matching axis terms to words in the open text of Torah.  For example, in the Torah the word Israel appears 591 times at skip +1.  Egypt appears 365 times in like manner   But in the existing control at the same +1 skip Israel appears just once, and Egypt does not appear at all.  In the new verse-permuted control files by Dr. Haralick, Israel again appears 591 times, and Egypt is there 365 times again.  Thus, although axis terms will appear at different ELSs than in the real Torah, when using a verse-permuted Torah text as a control, we are just as likely to get matches of an axis term (generally appearing vertically) running through an open text term (or verse) as in the Torah.  Unlike the letter-permuted Torah text which is pure nonsense to the reader, we are given a legitimate chance to explore the value of matches, especially where course angles between terms are of interest.  Tables below will show how the 10 new files stacked up with comparison to the Torah and original letter-permuted files currently available on CodeFinder.  This exploration is conducted based on key terms on ELS Map 1, which I believe points the way to where the Ark of the Covenant will be found.

     In the first Table below we find that the minimum ELS of Ark of the Covenant found in Torah is clearly lower than all of the ELSs of this term in the 10 verse permuted and one letter permuted Torah texts.  With CodeFinder with the row skip function disabled, and a maximum window of 80 columns and 80 rows, there were no matches of Ark of the Covenant with Egyptians were burying, the phrase that started my 12 year ( and ongoing) quest to find the Ark via ELS Maps in the Torah Code.  This compares to the 104 letters required to put Ark of the Covenant in a box with the minimum ELS of Egyptians were burying in the Torah. When I enabled the row split function, there still were no matches seen in the verse permuted Torah with Egyptians were burying in unwrapped Torah when the computer makes only one pass through Torah.   What does this mean?  Well, when excluding the open text hits for Ark of the Covenant, there were 45 ELSs of Ark of the Covenant in the 10 verse permuted files, each with 8 verses that ran directly through an ELS of Ark of the Covenant.  So we had 45 X 8 = 380 lines where an Egyptians were burying could theoretically appeared in the matrix with Ark of the Covenant. When we hit the row split function, we opened up another 380 lines that might have worked for a match, but with no positive results. Each window seen had 6,400 letters in it.  Table 2 below shows what happens when we turn on the wrapped matrix function and allow more than one pass through the verse permuted Torah?  That will surely produce many more opportunities to match Ark of the Covenant with Egyptians were burying.

     While the Code required only  117 letters to show Ark of the Covenant with Bardawil, the lake the surrounds the suspect site, in the 11 control texts used, the best match (smallest matrix) under the conditions specified in Table 1 required 357 letters. 

TABLE 2

MATCHES OF ARK OF THE COVENANT

WITH

EGYPTIANS WERE BURING

IN WRAPPED AND UNWRAPPED TORAH AND VERSE PERMUTED TORAH

     With the wrapped matrix function enabled there were 414 ELSs of Ark of the Covenant in the 10 verse-permuted Torah texts, and 35 ELSs of Ark of the Covenant in the Torah file (again, the ELS at skip -306 is the lowest skip seen on any of these files).  In addition, each of these files includes the 6 open text occurrences of Ark of the Covenant, however these 6 are not germane to the current discussion.  So, with the 34 additional ELS of Ark of the Covenant in the Torah, added to the 414 in the verses permuted files, we had 448 ELSs of Ark of the Covenant (with 8 lines for each) in which there might be a match with the one occurrence in each file of Egyptians were burying.  How many matches were there?  With row splitting adding to the 448*8 or 3,581 lines where we would first look for matches, there were 43 matches in the verse permuted wrapped texts, and one more in wrapped Torah.  The smallest matrix after the match in Torah with the -306 ELS was 110 letters (compared to 104 letters needed to show Ark of the Covenant with Egyptians were burying on ELS Map 1).  This occurrence was with the 9^th permuted file, at skip 55,538 in wrapped text.  Chi square values for matches of Ark of the Covenant with Egyptians were burying were as expected with the permuted files when they were not wrapped (i.e., the computer made one pass through the text), but there were many more matches than expected when the permuted files were allowed to wrap.  This might indicate a need for my spreadsheet to factor in number of computer passes through the Torah when computing the significance of matches with wrapped text.  If so, the new files by Dr. Haralick are already leading to a better comprehension of what it means to wrap text, especially when matching an axis term with an open text term or phrase.  As can by seen by Table 3, the average row split required to match Ark of the Covenant with Egyptians were burying was close to 4.  This would indicate an need to downgrade the value of such matches by a factor of 4.

TABLE 3

ROW SPLITS REQUIRED FOR

MATCHES OF ARK OF THE COVENANT

WITH

EGYPTIANS WERE BURING

IN WRAPPED AND UNWRAPPED TORAH AND VERSE PERMUTED TORAH

# These numbers do not include the 6 open text mentions of Ark of the Covenant in Torah and in each of the 10 verse permuted Torah texts used.

     The addition of these 10 verse permuted files to CodeFinder would constitute a tremendous aid for researchers trying to evaluate the significance of ELS terms intersecting open text material, especially when that material is a priori.  While Egyptians were burying was not a priori on the night that I tried to find a map in the Torah, the subsequent course angles found as seen in ELS maps 1,2,3,4,5,11,2,13,14, and 15 were certainly a priori in that they were linked to real world maps.