<?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>Passing the time while in a cycle</title>
		<link>/blogentry/194849</link>
		<atom:link href="https://www.lotterypost.com/rss/blogcomments/194849" rel="self" type="application/rss+xml" />
		<description>hypersoniq's Blog: Passing the time while in a cycle</description>
		<dc:language>en-us</dc:language>
		<generator>Lottery Post RSS Generator</generator>
		<item>
			<title>Original Blog Entry: Passing the time while in a cycle</title>
			<link>/blogentry/194849</link>
			<guid isPermaLink="true">/blogentry/194849</guid>
			<pubDate>Tue, 30 Sep 2025 10:59:22 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>The nice part about running in 4 week and 2 week cycles is not needing to be constantly updating the draw history. It is just as easy to grab the next 28 draws of Match 6 and the next 28 draws of pick 3 as it is to update weekly.<br /><br />There is an advantage to not updating during the test... I can run the program again in the exact state it was in when I made my selection to see how the pick may have been interpreted differently. When the paper play on the pick 3 reaches 14 days since the last update, I can see what I noticed and see where in the results the next 14 draws came from. Same with the Match 6 when the 4 weeks of the live trial are up.<br /><br />The sorting modification should be done on pick 3 by this weekend. When that goes live, I have 2 weeks to implement that in the Match 6 script.<br /><br />The pick 3 will be re run with the same data in 9 more draws, then the sorted list can be checked against the next 14 draws to see if a hit may have come on the other neutral lines, not just the central one. I have to understand the manual process before even beginning to imagine an automated phase 2 solution.... &#x5b;&#xa0;<a href="/blogentry/194849">More</a>&#xa0;&#x5d;</p>]]></description>
			<category>Blog Entry</category>
			<category>hypersoniq</category>
			<wfw:comment>https://www.lotterypost.com/blogentry/194849</wfw:comment>
		</item>
	</channel>
</rss>

