<?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>The plan for the big back test.</title>
		<link>/blogentry/190878</link>
		<atom:link href="https://www.lotterypost.com/rss/blogcomments/190878" rel="self" type="application/rss+xml" />
		<description>hypersoniq's Blog: The plan for the big back test.</description>
		<dc:language>en-us</dc:language>
		<generator>Lottery Post RSS Generator</generator>
		<item>
			<title>Comment #1</title>
			<link>/blogentry/190878#c276239</link>
			<guid isPermaLink="true">/blogentry/190878#c276239</guid>
			<pubDate>Fri, 02 May 2025 22:53:01 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>The setting was moved back to 150 draws as all of the early observations were made at 150 draws.&#x3c;br /&#x3e;Changed the program to only classify the first 7 draws, this will allow a faster run time. Even with writing to a file, the program should back test the entire pick 3 evening history starting with the first 150 draws for the X counts and proceed 7 draws at a time to the end... or to the last set of 7 full draws.</p>]]></description>
			<category>hypersoniq</category>
		</item>
		<item>
			<title>Original Blog Entry: The plan for the big back test.</title>
			<link>/blogentry/190878</link>
			<guid isPermaLink="true">/blogentry/190878</guid>
			<pubDate>Tue, 29 Apr 2025 13:29:46 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>After some thought, I think I found a way to have the backtest start at the farthest point in history and move forward, so each group of 7 classified draws will match up exactly with the draw history.<br /><br />It ends up as simple as starting with a high offset and subtracting 7 rows from the offset for each re run of the function, this will yield one large csv file with the majority of draw history being classified based on the previous 100 draws. This will allow calculating a confidence interval on the appearance of the NNN draws at least once every 7 draws.<br /><br />What I have observed with random sampling is a confidence level of maybe 95% for the mid day pick 3 and 100% for the evening pick 3. The evening is still a mechanical ball draw with the mid day being all PRNG.<br /><br />As stated earlier, the novelty of the approach so far is being able to almost guarantee a reduction in numbers to pick from to contain at least one draw that comes from the neutral set, after eliminating the hots and colds. So instead of trying to pick 1 combo in 1,000 it would allow me to pick 1 combo from around 300.<br /><br />This is the base setup for the system... safe reduction... it does not hold for one draw, or two... but it holds for 7. That 7 was found by experimentation. This number may increase when moving to the pick 5, but that game, if the cycle remains 7 games, could narrow the field of selection down from 100,000 to 30,000 or less... that will not be known until this phase is complete.<br /><br />Phase 2 will also be aided by the back test as percentages from the NNN draws can be analyzed. Here patterns will also be sought. If I can see that the majority of NNNs are based on a specific percentage, that is the key for picking 1 combo from the hundreds of possibilities.<br /><br />The goal, as with any system I have ever devised, is one best guess... no wheels or trapping, just one pick. Because I take the column at a time approach, there are no interdependencies in positions, therefore the code scales automatically based on the input file. Going from pick 3 to pick 5 simply involves changing the input file name.<br /><br />Ultimately jackpot style games will require a major rewrite because expectancies and number pools change. Wouldn&#x27;t it be interesting though if a duration cycle can be found where these jackpots produce NNNNNN or NNNNN + N hits and ~70% of those combos could be eliminated?... &#x5b;&#xa0;<a href="/blogentry/190878">More</a>&#xa0;&#x5d;</p>]]></description>
			<category>Blog Entry</category>
			<category>hypersoniq</category>
			<wfw:comment>https://www.lotterypost.com/blogentry/190878</wfw:comment>
		</item>
	</channel>
</rss>

