<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/">
	<channel>
		<title>A better explaination of what I am trying to do with my system.</title>
		<link>/blogentry/195465</link>
		<atom:link href="https://www.lotterypost.com/rss/blogcomments/195465" rel="self" type="application/rss+xml" />
		<description>hypersoniq's Blog: A better explaination of what I am trying to do with my system.</description>
		<dc:language>en-us</dc:language>
		<generator>Lottery Post RSS Generator</generator>
		<item>
			<title>Original Blog Entry: A better explaination of what I am trying to do with my system.</title>
			<link>/blogentry/195465</link>
			<guid isPermaLink="true">/blogentry/195465</guid>
			<pubDate>Tue, 04 Nov 2025 16:24:40 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>Starting with pick 3, since that is the simplest .<br /><br />Numbers are random, they form a discrete uniform distribution when looking at past draws.<br /><br />Frequencies, however, run from high to low (or low to high, depending on perspective)... frequencies are almost linear (almost but not quite)<br /><br />By rigid inter quartile classification, I am sorting the numbers in the 150 draw sample into bins.<br /><br />Every time I add new draws and run the script, the numbers change, but the frequencies stay in close proximity to previous runs.<br /><br />So I am NOT looking at specific numbers, just targeting a specific frequency range to pick from, playing whatever numbers happen to populate that frequency range on that particular run. This is why I do not look at individual numbers... skips won&#x27;t matter, even or odd won&#x27;t matter, high or low won&#x27;t matter, pairs won&#x27;t matter... it is still trying to find a needle in a haystack, but based on the classifications, the haystack got smaller... 1:~300 vs. 1:1,000.<br /><br />It is also why I make smaller history samples, because full history does not contain that volatility that changes the numbers with each run.<br /><br />I know I might be using a wrong sample size, or a wrong window size, but it is not like there is a resource for determining such things.<br /><br />To simplify, I have created a filter based on frequency. Classification is phase 1<br /><br />I am still experimenting how to interpret the data and make a better pick... this is phase 2.<br /><br />I have applied this idea to multiple games so far. Pick 3, Pick 5, Match 6 and Cash 4 Life.<br /><br />The other key element in this is play cycle... it is never going to give the next draw with any accuracy, so a range was determined for each game...<br /><br />Pick N plays the same combo for 21 draws<br /><br />Match 6 plays the same combo for 28 draws<br /><br />Cash 4 Life plays the same combo for 30 draws.<br /><br />What drives development is back test results... if picking from the 300ish possible neutral combos, there is over a 90% chance that at least 1 will appear straight in the next 21 draws... that is over the entire draw history of the pa pick 3 evening, with 17,000+ draws to look at.<br /><br />My level of difficulty is still high, as I am only playing one of those combos. Watching how the numbers churn through the frequency filter feels like almost seeing the mechanics of randomness itself. When pulling 17,000 randomly generated 3 digit combos from random.org, the same 90%+ is exhibited... this means that regardless of the source, ball draws, computer draws, or actual random numbers... the observation holds that frequency better explains the churn than the numbers themselves.<br /><br />Finding that needle is still vexing, but it is some progress with each cycle. I may never win anything big, but IF I do, this will be the way.... &#x5b;&#xa0;<a href="/blogentry/195465">More</a>&#xa0;&#x5d;</p>]]></description>
			<category>Blog Entry</category>
			<category>hypersoniq</category>
			<wfw:comment>https://www.lotterypost.com/blogentry/195465</wfw:comment>
		</item>
	</channel>
</rss>

