In preparation to code the 8PS EMAIL ALERT, need to test a method that can reduce the FOUR(4) pairsums involved in the LOW COUNT down to one(1) pairsums that has the higher probability of hitting next when a LOW COUNT hits.
This is NOT an easy task as it is complex and needs further investigation to determine the best method to automate it into an email alert where members would receive numbers to play.
STEP1
Email Alert simply determines whether a LOW COUNT is due to hit by counting the back to back HIGH COUNT hits (This step is customizable)
![](https://images9854.s3.amazonaws.com/Screenshot+2023-08-22+at+2.33.48+AM.png)
STEP2
Email alert then focuses on each of the four(4) pairsums to determine which one has the higher probability of hitting next when a LOW COUNT hits. This part is complicated as the program must further analyze which pairsum has the higher probability of hitting a LOW COUNT itself. FOR EXAMPLE, 11/3,1 is dominated by HIGH COUNTS and creates a low probability of hitting next wth a LOW COUNT.....10/2,3 similarly is dominated by HIGH COUNTS and also creates a low probability of hitting next with a LOW COUNT. Especially given the fact that only 2 HIGH COUNTS had hit after L3.....9/2,1 frequently hits a LOW COUNT over all the other pairsums. THUS, it creates the HIGHER PROBABILITY it will hit next IF LOW COUNT hits next....As for 9/3,3, this pairsum would normally be ruled out BUT a LOW COUNT has been out so long, it has created a HIGH PROBABILITY it could hit next when a LOW COUNT hits.
This is the type of LOGIC that needs to be coded into the email alert system. Question is what is the best logic to employ in coding this feature and whether there are other unforeseen factors that can help determine with more certainty which pairsum would hit next when a LOW COUNT hits.
![](https://images9854.s3.amazonaws.com/Screenshot+2023-08-22+at+2.02.09+AM.png)
![](https://images9854.s3.amazonaws.com/Screenshot+2023-08-22+at+2.02.18+AM.png)
![](https://images9854.s3.amazonaws.com/Screenshot+2023-08-22+at+2.02.25+AM.png)
![](https://images9854.s3.amazonaws.com/Screenshot+2023-08-22+at+2.02.32+AM.png)
![](https://images9854.s3.amazonaws.com/Screenshot+2023-08-22+at+2.02.38+AM.png)
![](https://images9854.s3.amazonaws.com/Screenshot+2023-08-22+at+2.02.45+AM.png)