Development - G.A.T. Engine 2.3

Any latest news will be posted here...
baalhabait
Advanced
Advanced
Posts: 80
Joined: Wed Apr 11, 2012 9:58 pm

Re: Development - G.A.T. Engine 2.3

Post by baalhabait » Tue Dec 11, 2012 6:48 am

I guess 2.5GHz Core2Due with 4GB 667Mhz DDR2 is not good enough for making it in 5-6 hours, isn't it?

Skirrow
Regular
Regular
Posts: 49
Joined: Tue Jan 29, 2008 8:23 pm
Location: UK

Re: Development - G.A.T. Engine 2.3

Post by Skirrow » Tue Dec 11, 2012 8:47 am

Hi Baalhabait,

just for comparison , I run Win 7 with an intel 2 Core Duo CPU, T8300 @2.4 GHz ( 2 CPUs ) with 3 Gb Ram on my Laptop.

Setting of 20 Data & 50 Draws , 12 Numbers requested , hits range of 4 - 7 Selected , GAT produces around 400,000 GATs per hour .

Hope this helps for a comparison .......................

Regards
Skirrow

baalhabait
Advanced
Advanced
Posts: 80
Joined: Wed Apr 11, 2012 9:58 pm

Re: Development - G.A.T. Engine 2.3

Post by baalhabait » Tue Dec 11, 2012 7:33 pm

Which type of RAM is installed in your laptop? Is it DDR2 or DDR3? What is its speed? Do you know the CAS latency of the memory modules?

Skirrow
Regular
Regular
Posts: 49
Joined: Tue Jan 29, 2008 8:23 pm
Location: UK

Re: Development - G.A.T. Engine 2.3

Post by Skirrow » Tue Dec 11, 2012 9:37 pm

Hi baalhabait ,
you've lost me when you talk about cas latency etc , but I just ran the "Crucial RAM Scanner" and it says ............. DDR2 PC2-6400, DDR2 PC2-5300, DDR2 (non-ECC) if that helps !!

Regards

Skirrow
Regular
Regular
Posts: 49
Joined: Tue Jan 29, 2008 8:23 pm
Location: UK

Re: Development - G.A.T. Engine 2.3

Post by Skirrow » Tue Dec 11, 2012 10:03 pm

P.S
I think we have gone off topic with this discussion , should really be in GAT General discussion .................

Regards
Skirrow

User avatar
lottoarchitect
Site Admin
Posts: 1395
Joined: Tue Jan 15, 2008 5:03 pm
Location: Greece
Contact:

Re: Development - G.A.T. Engine 2.3

Post by lottoarchitect » Wed Dec 12, 2012 5:42 pm

Further news on the development. The new additions include:

- Start point in history. This effectively replaces the need to keep track of the run factor as discussed at viewtopic.php?f=24&t=484. The Run Factor display is still used for ease of use but without the need to adjust the run factor for every subsequent run. In practice, the start point parameter is set once at a new run, this produces automatically the run factor needed by the engine and everything else works as we know it. At the options panel you'll see the start point parameter and next to it there is an "R" button - which means reset. We press that when we want to start a new run with run factor 0, so the program automatically computes the needed start point in history (which translates as run factor = 0). Now, when we add new draws in history, this start point value must stay the same (the correct run factor is computed based on that start point value), so in practice we don't have to adjust anything, unless if we want to perform a new run.

- Added auto-save of the options used. These are restored when opening a lotto game and also saved when closing a lotto game automatically. The start point discussed above is also supported by that auto-save, thus eliminating the need to keep track of it.

- I have also added for the next prerelease another coloring to the predicted numbers besides the green which indicates exact matches. The new addition colors yellow any predicted number that is 1-off from the compare numbers set. That yellow coloring assumes that we didn't have an exact match, so if the actual draw is 5 10 15 20 25 30 and the prediction (10 picked numbers) is 5 9 10 11 15 19 23 28 29 31 it will be colored as 5 9 10 11 15 19 23 28 29 31. Numbers 9 & 11, although are 1-off to actual 10 are not colored yellow because there is an exact prediction of 10. 19 is yellow because it is 1-off to 20 and 20 is not predicted. 23 & 28 are far from any actual number (no coloring) and 29 & 31 are both colored yellow because they are both 1-off from actual 30 (yellow for both numbers refer to 30 which hasn't been predicted).

- Added support to save all the internal predictions of a GAT table to EXCEL. To access that feature, we display a GAT table and right-click on its ID, or we can directly export from the panorama (use the selection box to mark which GATs to export) and right-click. The export colors the correctly predicted numbers in green when compared to a test draw. In this export report you'll see exactly what the red line shows and also you'll see how different are the predictions (the dynamic nature of GAT's predictions) among the draws. For this function to work, EXCEL must be installed on the computer.

- Removed support for enable/disable X, X-1, X-2 feature. Now the engine works always with that mode active since keeping track of only the top X hitters is just a subset of that feature.

- To the more serious stuff, current GAT displays hits in the panorama based only on the X hits achievement over a given hit category; if an equal GAT is found, it is just appended to the column. Now, the panorama expanded to also put higher GATs that although deliver the same X hits, those that produce higher hits in higher categories and if these are the same, in lower hit categories. In practice that means we'll have at the top GATs that deliver the highest X hits on its given category and more hits on the other categories compared to the sequential increasing order we have now.

- Added a new search criterion mode, named "build up". This tries to find GATs that produce a sequence of increasing hits over its last part of the tested draws. So, if the hits produced (e.g. over the last 6 tested draws) are 1, 1, 1, 2, 2, 3 this GAT shows a steady increase of hits. It may be a very good GAT to pick at least for the next draw to come as this translates it may continue its good hit sequence at least for the next draw. This GAT will appear at column 3 because its last hit is 3. GATs that deliver the biggest such sequence (increasing or keeping the same hit ratio) will show up higher in the panorama. Also, among those GATs that produce the same sequence, the GAT that produces more hits overall is placed higher.

cheers
lottoarchitect

User avatar
lottoarchitect
Site Admin
Posts: 1395
Joined: Tue Jan 15, 2008 5:03 pm
Location: Greece
Contact:

Re: Development - G.A.T. Engine 2.3

Post by lottoarchitect » Sat Dec 22, 2012 7:01 pm

A new prerelease (2) is made available at the account management. Use the same procedure used for prerelease 1. You can have all the various versions of GAT running, so you may have 2.2 2.3-pre1 & 2.3-pre2 running at the same time. The additions include all the features mentioned at the previous post. Any questions should be asked here. Cheers and Happy Christmas!

lottoarchitect

baalhabait
Advanced
Advanced
Posts: 80
Joined: Wed Apr 11, 2012 9:58 pm

Re: Development - G.A.T. Engine 2.3

Post by baalhabait » Sun Jan 20, 2013 7:46 pm

Hi Anastasios,

Unlike prerelease 1 and earlier releases, prerelease 2 hangs for a few seconds every few minutes in the course of computation.
It may happen because of additional computation that required to take into account Gats hits,
Anyway, since gat that offer the best hits does not necessarily means it is the best to be picked, i think it would be better to make this option to be user selectable.
Apart of that, would it be possible to add a parameter to define the desired total amount of gats to be computed, so when it reaches the desired amount - the process would be terminated automatically?

User avatar
lottoarchitect
Site Admin
Posts: 1395
Joined: Tue Jan 15, 2008 5:03 pm
Location: Greece
Contact:

Re: Development - G.A.T. Engine 2.3

Post by lottoarchitect » Mon Jan 21, 2013 12:35 pm

Hi baalhabait,
Unlike prerelease 1 and earlier releases, prerelease 2 hangs for a few seconds every few minutes in the course of computation.
Yes it does every 10000 scanned GATs. At that point, it makes an internal cleanup of GATs that didn't make it to the panorama. This is more apparent on slower computers.
Anyway, since gat that offer the best hits does not necessarily means it is the best to be picked, i think it would be better to make this option to be user selectable.
What should be shown at the panorama if the user deselect that option?
Apart of that, would it be possible to add a parameter to define the desired total amount of gats to be computed, so when it reaches the desired amount - the process would be terminated automatically?
I'll add it.

baalhabait
Advanced
Advanced
Posts: 80
Joined: Wed Apr 11, 2012 9:58 pm

Re: Development - G.A.T. Engine 2.3

Post by baalhabait » Mon Jan 21, 2013 2:36 pm

So you're saying prerelease 1 does not make an internal cleanup of gats every 10000?
If the user deselect this option, it should list gats in a simple ascending order, like in prerelease 1.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest