<?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>One week of the pick 3, no hits.</title>
		<link>/blogentry/197086</link>
		<atom:link href="https://www.lotterypost.com/rss/blogcomments/197086" rel="self" type="application/rss+xml" />
		<description>hypersoniq's Blog: One week of the pick 3, no hits.</description>
		<dc:language>en-us</dc:language>
		<generator>Lottery Post RSS Generator</generator>
		<item>
			<title>Original Blog Entry: One week of the pick 3, no hits.</title>
			<link>/blogentry/197086</link>
			<guid isPermaLink="true">/blogentry/197086</guid>
			<pubDate>Thu, 05 Feb 2026 03:45:02 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>So, as the first 7 days of the initial pick 3 attempt hits their last day (and eve) and it went winless (also as expected), the observations...<br /><br />1. All numbers appeared at least once in their predicted positions. Today&#x27;s mid day had position 2 AND 3 correct. This is the first look at lag testing.<br /><br />2. This was off of all raw data from the app, pick the most frequent follower from each column. Running the app again tonight for next week&#x27;s picks gives 2 different combos for week 2.<br /><br />3. The ideal window remains next draw, but I do not have the opportunity to play both games every single day. So the week long play frame is the better choice for now.<br /><br />It was interesting to see each number appear in position over just 7 draws, and I will be watching that over all 3 weeks of this first pick 3 run. Because the entire system is per column, I hope to see something similar in the pick 5.<br /><br />All of the questions I have about the data should for the most part be answered by the big sliding back test... but that will have to wait until I finish the Android version of the app, as the data presented will remain unchanged, the back test will provide information (hopefully) on how to better interpret the data.<br /><br />The process of getting picks, from launching and updating the draw histories to reading the data for both games was done in under 5 minutes... on that front, the app is already a major win! Once this is on the phone... max efficiency!<br /><br />On track with the plan, it&#x27;s fun to see an idea take form. Getting things right and meeting the challenge of getting ahead and back to stable with each coding session was rewarding in it&#x27;s own right. Hopefully a few wins will follow... the manual updates and expanding to 14 different games leave many options for future play ideas.<br /><br />Getting there one git commit at a time...... &#x5b;&#xa0;<a href="/blogentry/197086">More</a>&#xa0;&#x5d;</p>]]></description>
			<category>Blog Entry</category>
			<category>hypersoniq</category>
			<wfw:comment>https://www.lotterypost.com/blogentry/197086</wfw:comment>
		</item>
	</channel>
</rss>

