<?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>So many decisions for one script! Thought hot/cold would be easier...</title>
		<link>/blogentry/189941</link>
		<atom:link href="https://www.lotterypost.com/rss/blogcomments/189941" rel="self" type="application/rss+xml" />
		<description>hypersoniq's Blog: So many decisions for one script! Thought hot/cold would be easier...</description>
		<dc:language>en-us</dc:language>
		<generator>Lottery Post RSS Generator</generator>
		<item>
			<title>Original Blog Entry: So many decisions for one script! Thought hot/cold would be easier...</title>
			<link>/blogentry/189941</link>
			<guid isPermaLink="true">/blogentry/189941</guid>
			<pubDate>Sun, 09 Mar 2025 14:31:19 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>As the calculation of the standard deviation is almost complete, the need becomes apparent to create a back test, but at what intervals?<br /><br />There are 2 that move to the front of the pack right away...<br /><br />1. Process the data in chunks so the function is fed X+Y draws so the chunks are larger but separated by X+Y or...<br /><br />2. Process the data by chunking only Y draws back. This would allow the process to be back tested and provide a full output of observed HNC patterns for the entire draw history (to X+Y from the origin draw)<br /><br />The second option would be a more thorough exploration data set to find common HNC classification patterns because it only deals with data at a time that you would NOT have known beforehand, no a priori knowledge, which is ideal because moving forward you would not have that information.<br /><br />This would simplify the process of getting a pick by simply counting the most frequent HNC patterns. All that would need to be recorded are the Y classifications, which would match the draw history.<br /><br />A few challenges to overcome...<br /><br />1. Counting the remaining chunk sizes to ensure there are X+Y draws remaining to process. A simple count of the remaining data frame rows should handle this.<br /><br />2. Writing the Y classifications to a CSV file, because this requires buffering the output of each column and writing complete rows after all columns have run. This is mostly solved in the output, but I have to ensure it writes the data appropriately so that it is the same date ascending order of the original data.<br /><br />3. Figuring out the HNC to play, as the classifications are mostly a one to many relationship... there could, for example, be 3 Hots in a column, so which Hot to play?<br /><br />4. Refactor the input arguments. I will no longer need to specify the hot cold threshold percents, so perhaps input the expectancy so the calculated standard deviation can be added and subtracted from it to set the thresholds.<br /><br />And that is just for the pick N games... followers are a future add...<br /><br />Busy Hobby!... &#x5b;&#xa0;<a href="/blogentry/189941">More</a>&#xa0;&#x5d;</p>]]></description>
			<category>Blog Entry</category>
			<category>hypersoniq</category>
			<wfw:comment>https://www.lotterypost.com/blogentry/189941</wfw:comment>
		</item>
	</channel>
</rss>

