<?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>How I see draw histories</title>
		<link>/blogentry/196877</link>
		<atom:link href="https://www.lotterypost.com/rss/blogcomments/196877" rel="self" type="application/rss+xml" />
		<description>hypersoniq's Blog: How I see draw histories</description>
		<dc:language>en-us</dc:language>
		<generator>Lottery Post RSS Generator</generator>
		<item>
			<title>Comment #6</title>
			<link>/blogentry/196877#c287335</link>
			<guid isPermaLink="true">/blogentry/196877#c287335</guid>
			<pubDate>Sun, 25 Jan 2026 19:14:30 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>And those first 1,500 draws are used to give the script something to count to get started... it gibes each digit a fair chance to have been followed by every other digit 15 times.</p>]]></description>
			<category>hypersoniq</category>
		</item>
		<item>
			<title>Comment #5</title>
			<link>/blogentry/196877#c287334</link>
			<guid isPermaLink="true">/blogentry/196877#c287334</guid>
			<pubDate>Sun, 25 Jan 2026 19:13:03 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>I won&#x27;t be looking for patterns in the backtest. I will be looking to count how many times a straight hit would have happened if I ran the same script every day against all but the first 1,500 draws of each history. That will be over 15,500 for the evening pick 3 in PA, which started in 1977</p>]]></description>
			<category>hypersoniq</category>
		</item>
		<item>
			<title>Comment #4</title>
			<link>/blogentry/196877#c287333</link>
			<guid isPermaLink="true">/blogentry/196877#c287333</guid>
			<pubDate>Sun, 25 Jan 2026 19:09:01 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>Oh, and this is strictly per column. For an example of 501, each digit would only contain it&#x27;s own distribution. What followed 5 in column A, then what followed 0 in column B, and finally what followed a 1 in column C.</p>]]></description>
			<category>hypersoniq</category>
		</item>
		<item>
			<title>Comment #3</title>
			<link>/blogentry/196877#c287332</link>
			<guid isPermaLink="true">/blogentry/196877#c287332</guid>
			<pubDate>Sun, 25 Jan 2026 19:01:18 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>&#x3c;br /&#x3e;The Markov Chain analogy holds because all 10 &#x22;next states&#x22; only need the &#x22;current state&#x22;.&#x3c;br /&#x3e;&#x3c;br /&#x3e;Of course, probability is not the same as certainty.&#x3c;br /&#x3e;In the ideal situation, they would all have been drawn the same number of times, but the distribution shows any variance from expextancy.</p>]]></description>
			<category>hypersoniq</category>
		</item>
		<item>
			<title>Comment #2</title>
			<link>/blogentry/196877#c287331</link>
			<guid isPermaLink="true">/blogentry/196877#c287331</guid>
			<pubDate>Sun, 25 Jan 2026 18:22:43 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>With a game like pick 3, there are 10 possible transitions... the digits 0 through 9. &#x3c;br /&#x3e;Given the random nature, each should have exactly a 10% chance of being selected.</p>]]></description>
			<category>hypersoniq</category>
		</item>
		<item>
			<title>Comment #1</title>
			<link>/blogentry/196877#c287328</link>
			<guid isPermaLink="true">/blogentry/196877#c287328</guid>
			<pubDate>Sun, 25 Jan 2026 17:34:49 GMT</pubDate>
			<dc:creator>Il2c</dc:creator>
			<description><![CDATA[<p>&#x3c;br /&#x3e;Take the lp calendar for example. I used to copy and paste the midday draws deleting stuff line by line (u know how tedious this can be) then I&#x27;d save it as a text file, feed the data to a generator that detects digit trends. Then it would detect pairs, filter out certain digits and combos.&#x3c;br /&#x3e;&#x3c;br /&#x3e;If I wanted to u can also filter out sums and dr.&#x3c;br /&#x3e;&#x3c;br /&#x3e;Kinda cool huh? It&#x27;s worked some time, but hasn&#x27;t worked &#xd83d;&#xdcaf; % of the time.&#x3c;br /&#x3e;&#x3c;br /&#x3e;All of this started from a guy doing 317 run... &#x5b;&#xa0;<a href="/blogentry/196877#c287328">More</a>&#xa0;&#x5d;</p>]]></description>
			<category>Il2c</category>
		</item>
		<item>
			<title>Original Blog Entry: How I see draw histories</title>
			<link>/blogentry/196877</link>
			<guid isPermaLink="true">/blogentry/196877</guid>
			<pubDate>Sun, 25 Jan 2026 15:40:25 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>I keep draw histories to use for developing systems. I do not view these as a model of the data produced by the mechanical or PRNG process (or in PA, BOTH). I view it as a collection of the results they paid on.<br /><br />Every single state lottery runs test draws, some even publish the results. I place no value in this data because the state never intended to pay on those results. Power Ball used to publish test draw data.<br /><br />Up until the end of last year, I excluded PA double draw data (where they picked an extra draw on some nights in the pick N games for a promotion) but I keep it in now because they paid on it. It was quite the project re doing every single history file I had with the new web scraper app. I made 2 versions. The first built the base file, with the header rows from day one of the game history to current. The second simply appends new data to those csv files. This replaced hours of manual copying into the files, particularly if I had not played a game for a long time (like pick 5) and needed to add years of data. Now, there are zero human transcription errors in the data sets, and updates happen with the click of a button... 2 minutes later 14 game histories are updated accurately!<br /><br />I also maintain separate files for bonus balls like the mega ball and power ball.<br /><br />Access to the history in or out of the app is a click away, this was the vision realized!<br /><br />So when processing this data, I am mostly looking for any micro biases in each column that hopefully points to the next number prediction that will pay out.<br /><br />There are some that hold zero stock in the usefulness of past draw data, and they make compelling arguments, but I see it differently... there might be a connection, and even if it is coincidental at best, it is better than nothing.<br /><br />This Markov Chain follower back test script may end up to be the single most complex function I will write, and even if there is no yield, I have honed some skill at trying to solve impossible problems with code, skills that will eventually transcend the lottery hobby.... &#x5b;&#xa0;<a href="/blogentry/196877">More</a>&#xa0;&#x5d;</p>]]></description>
			<category>Blog Entry</category>
			<category>hypersoniq</category>
			<wfw:comment>https://www.lotterypost.com/blogentry/196877</wfw:comment>
		</item>
	</channel>
</rss>

