Post
by lottoarchitect » Thu Feb 06, 2020 1:43 pm
At its current implementation it scans augmentative tables just like what GAT 3.0 delivers with the inclusion of internally used Hits+Delay information. As it goes through each produced GAT table, it picks it as the current candidate if that table results in more total hits production + Hits/delay score compared to its previous pick. The GATs it scans are the same that end up in current GAT 3.0 augmentative panorama when you request X picked numbers, with the exception it does not sort them in columns as per the hit category. So, in reality the online service typically picks among the GATs at the top row and stop the scan if no new GATs make it there in a given time. One distinction here is the stat.data/tested draws setting used for the online service has been manually determined over lengthy runs. The benefit of GAT 3.0 is it has an automatic stat.data evaluator, something that will be added at the online system at some point. So, currently GAT can deliver better outcome compared to the online simply because of a better stat.data selection it can make.
Given this is a work in progress which is aimed to eventually end up in GAT as a complete automatic analysis, I have attempted various approaches, some involve averaging picked numbers among GATs, mixing scans of various stat.data, mixing results of various "request X numbers" etc. When I conclude what will be the most preferred approach, it will end up in GAT and the exact same methodology will operate for the online service too. No matter what, the building blocks and primary information are the GAT tables themselves.