Not about playing it, have no plans on that at the moment, but on including it into the app. I have not yet found the ID that corresponds to a data page like I have for the other games. If they did not create one, then there is no pathway for creating one using that method. So I will explore the options...

1. Writing a quick script to run through a group of IDs, using the scraper to extract the H3 page element containing the game name, and excluding the H3 message for an ID with no data.

2. Look at another participating state that either has an api or a similar page of year at a time data.

3. Explore the MUSL site for the same.

Or

4. Drop support for the game in the app.

The current setup has data separated for bonus ball games, but it does not need to be separated if it is the only workaround. It will just not have correct settings for the bonus ball itself and the stats will be off.

Either way, I am removing the Cash 4 Life data and metadata.

Have an idea for visualizing the classifications from the back test data... running an animation of the classifier changes in each column side by side using the matplotlib and Seaborn libraries. This will be a stand alone side script not intended to make it into the app.

Also taking the next steps with vertical sums, which is still in the spreadsheet stage. The changes will include summing 10 draws instead of 3 (pick 3 example) and taking both the AVERAGE() and MODE() of 30 samples instead of the whole column. This incorporates the size calculation I did where k=number of balls in the game x N samples, which is 30. I am designing this vertical sum to be a drop in function for the app.

At this point, the plan is to have 3 separate functions to analyze the data, and find a way to infer from the 3 results to make a best guess. This week, the expense is only $8 as the days of play were reduced from 7 to 4, but the mostly winless annual tally is -$104.

I did plan on playing all year. The goal of completing the app was met almost 10 months early, so now I can use the time on refinement and learning how to better interpret the data.

The new routine is to first check where the winning numbers sat on both functions before updating the draw history, so I will wrap that up before the python/spreadsheet work for today gets into full swing.

So far it has been determined that the endpoint I use has not been updated for new games since the introduction of the Cash 4 Life 10 years ago... yet the data is updated daily... so they must point to a table or database that is the single source of truth for all game data. Time to investigate the front end "view past winning numbers" page to determine where the new data for Millionaire for Life is stored.