<?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>Expanding on the brute force concept...</title>
		<link>/blogentry/199615</link>
		<atom:link href="https://www.lotterypost.com/rss/blogcomments/199615" rel="self" type="application/rss+xml" />
		<description>hypersoniq's Blog: Expanding on the brute force concept...</description>
		<dc:language>en-us</dc:language>
		<generator>Lottery Post RSS Generator</generator>
		<item>
			<title>Original Blog Entry: Expanding on the brute force concept...</title>
			<link>/blogentry/199615</link>
			<guid isPermaLink="true">/blogentry/199615</guid>
			<pubDate>Wed, 08 Jul 2026 12:54:39 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>The idea is to look for things, patterns, coincidences... not limited to any one thing. They can be tracked as well... such as if you are looking at the individual situation of odds and evens, check the rolling percentage over several draws. The end goal is to develop a list of things that hold over multiple draws. Things you might otherwise miss if doing bulk statistics over many draws.<br /><br />You may end up with some odd collections...<br /><br />Perhaps odd follows odd at a higher percentage than odd follows even... remember, this is per column as well as across the combo.<br /><br />There could also be some way to re imagine the history, rather than a flat 2D file, it could be a 3D array with the tine series step as the third dimension.<br /><br />There are no rules here, be creative... regular classical statistics have not been able to crack the code .... &#x5b;&#xa0;<a href="/blogentry/199615">More</a>&#xa0;&#x5d;</p>]]></description>
			<category>Blog Entry</category>
			<category>hypersoniq</category>
			<wfw:comment>https://www.lotterypost.com/blogentry/199615</wfw:comment>
		</item>
	</channel>
</rss>

