The current follower system has a setting for list length that can be unique to each game, but the same across positions. That is what I overlooked. The ability to set the list length for each position... I will remedy that!

Each position in pick 3 (and beyond) has it's own history, and might give better results if it had it's own list length. I will set up the unique variables to pass these in during the function call as parameters. I will determine in the short term here which lengths to use by solving tonight's draw BEFORE updating the csv draw files. Though it has the potential for over fitting, the limits will be to choose the lowest list length that contains the winning number... even if it was not the one picked. May take longer than one night to implement, but I think it is the next logical step.

I have already started the script that will perform the back test, begun by suppressing the verbose output and limiting it to list length (which will also be suppressed later) and the pick.

Going to try starting at between 2 and 3 years of seed data, for example pick 3 from the start to dec. 31st 1979 and begin that back test from January 1st, 1980, as the past draws are far back enough to allow follower data, and that information would have been a priori.

A statistics based system might not be glamorous or as fun as picking 100 numbers for all states, but if it works at an interval to hit enough to be profitable, then it will be worth the time, and for the jackpot games implementation, that only needs to work once.