The passed variables work as expected. I even discovered an unused variable that remained from when I used expectancy +/- 1 standard deviation instead of the inter quartile range.

The universal version of the script had worked for the Match 6, Cash 5, and Treasure Hunt data sets, but it is throwing some strange errors when trying to run the pick N game data...

I have a feeling that tracking down these errors will take some stretch of time. Fix one, another, different one appears... good thing my version control has all of the previous working scripts intact!

So far...

Index Out Of Range... that was fixed by passing in the low and high balls for each game. Also by creating a new variable that adds one to the high range as python's range works as range(includes this number, excludes this number) such that for pick N, the range(0,9) only includes 0 to 8, the correct approach for 0 to 9 is range(0,10).

Error processing the frequency list... this worked for the jackpot games, because you ignore zero values to get the distribution of the present numbers... there are no zero values in the pick N games. That was fixed with a peek inside the frequency list with an if statement... if zeroes exist, it is a jackpot game, if not, it is a pick N game.

Had to rework the flowchart to make sure the execution was still following the original design. It is.

So this is another time killer. I have to print the contents of the frequency data ahead of the line that is crashing execution for the pick N games. I need to see that the passed variables are passing and that the frequencies appear as expected. The comment for sections like this is always "TEST PRINTS - REMOVE WHEN RESOLVED" so I do not forget to remove the troubleshooting code.

This is the type of project where resolving the operation to just one function is required because I want the app to run with as few functions as possible. I know it is possible to reduce it to 2 scripts, because that is how the updater works... 1 script for 11 games and 1 script for the 3 with bonus balls as they update an extra bonus ball csv.

I may end up having to do the same with this part as well, one script for the jackpots and one script for the pick N games.

That is the interesting part of kivy, a button click can set up and launch an entire script... so when a game is chosen from the menu, it will choose both the correct script AND the correct settings.

I could be overthinking this...

Never mind... figured it out!

So far tested with 2 distinct game types, pick 4 mid and Match 6... will test the others.

Summarizing the project so far...

Updater... 2 scripts, ALL games.

Classifier... 1 script, ANY game.

Crushed the goals remaining for this year. Onward to GUI development!