Comment #2

hypersoniq — Wed, 19 Feb 2025 01:28:18 GMT

The code functions properly! Now to see if the interpretation of the output can lead to a win...

Comment #1

hypersoniq — Tue, 18 Feb 2025 19:01:46 GMT

Also, for the classification output of the Y draws in a program that operates on a "per column" basis, the obvious choice is to capture the output in Y lists, appending each to the appropriate list and just printing the series of lists...<br />Since it is still unclear what constitutes membership in hot or cold, the percentages can also be passed as arguments to the main function, which allows additional flexibility. Now a call would look like<br />shortTermTrend(35,7,12,8)<br />Where the inputs... [ More ]

Original Blog Entry: Planning for edge cases when coding.

hypersoniq — Tue, 18 Feb 2025 13:53:45 GMT

As I am getting ready to start coding the hot/cold script, I realize that after seeing these distributions before, there is a real possibility of numbers at a boundary (such as the 3rd hot number and the first neutral number) having the same frequency. For example, in X draws a 4 is drawn in a column 6 times, but a 7 is also drawn 6 times... if the 4 is H3 and the 7 is N1 then the hot/neutral designators don't really apply...

In this situation, I wonder if it would be best to grow the neutral zone for that situation, which would result in H1, H2, N1 ... N5, C1, C2, C3. Likewise for the barrier of N and C...

The other solution would be to calculate the percentage, such that a number needs to be greater than it's expectancy of 10% of the draws to be classified as HOT, and below it's expectancy of 10% to be counted as COLD.

Maybe H would be = 12%, C would be =8% and all others default to neutral... This solution could also completely cut a category if none of the hots or colds reach their respective thresholds.

This is definitely a programming life cycle thing, spend weeks planning so the relatively small amount of time spent coding has the best chance of success... programs can complete because they are free of syntax errors, but the results may not be useful if there were any semantic errors that you fail to plan for...... [ More ]