Development - G.A.T. Engine 2.3
Posted: Tue Nov 27, 2012 10:54 am
GAT's development is well underway. The version is by no means complete since there are a lot to be added. So far the following are in place:
- Delay graph to show a line of actual delay data (requested feature). This shows the actual delays in a graph for a given hit to occur. So now we have a summary (current version) and a line showing the actual delays. To access this feature, we must observe a specific hits delay (i.e. delay of 3 hits) and it is available by right-clicking the delay graph. The most recent delay (not the current delay shown at the bottom) is the right-most point.
- Copy the predicted numbers in sorted order (requested feature). The "copy to clipboard" function currently copies the predicted numbers as shown (unsorted). SInce it is easier to see what numbers are in there when sorted, the copy button now copies the numbers sorted and if someone needs the order of preference decided by GAT, right-clicks on the copy button for this function.
- Colouring GAT cells in the panorama to compare their hits to a given set of numbers. This can be used to instantly show which GATs managed to predict the actual draw (draw must be removed from the history or not adding the new actual draw for this comparison to make sense) and the darker the colour, the more numbers actually predicted. Dark green means more numbers correct, light green means fewer. This function needs further improvement e.g. it will be possibly moved to the functions toolbox but it is functional as it currently is. This feature is enabled if we enter any number for comparison at the options. Also, when the comparison is active, additionally the predicted numbers of each GAT are colored green to indicate which numbers have been predicted (that was a feature of GAT 2.1). The colors used are spread from 0 to the minimum of current requested numbers and total numbers to compare. So if e.g. we enter 5 numbers to compare and show req.numbers 3 at the panorama, obviously the maximum possible is to match only 3 numbers from out set. Therefore the dark green will show up when 3 matches occurred (the maximum) and the other cases will gradually fade to light green (the default color used in panorama) which indicates 0 hits. Similarly for the same 5 set of numbers, if we display req. numbers 20 at the panorama, the maximum possible will be 5 matches (all the numbers in the compare set), therefore dark green is assigned to any GATs that will match all 5 numbers and gradually fade to light green (the default color of the panorama) if 0 hits achieved when compared to that set. This feature is really an eye-opener! Also makes a very nice visual mosaic
- Max GATs shown per column (up to 999). This is another speedup mechanism. This actually will be used to limit the need to keep track of more GATs in a given column since most good GATs are expected to show up at the initial few top cells shown. Even having 99 GATs to check in a column is already too much. Not sure if anybody will set this to a higher setting but it is available if he wants to do that.
- X, X-1, X-2 feature. This is a very important addition. It is fully operational but still needs work to be faster in operation and it is recommended to use the Max GATs per column along with the req.numbers/category speedups. Currently the panorama shows only the top X hitters. However they can be in a cold cycle and since fewer and fewer make it to the panorama as we progress the scan there are more chances to pick a cold performing GAT. This feature is selectable (enable/disable). If disabled, the engine works as it currently does. If enabled, it displays all the top performing GATs in terms of hits produced in descending order till all cells in the column are filled up. So e.g. the initial top cells will have GATs producing X hits, the following ones X-1 hits etc till all the cells are filled up. This feature used together with the compare numbers feature show right away where the best GATs show up where the best ones are expected to be close to the top, if they are not the top X hitters due to their cold cycle. A selection of a good GAT is expected to occur within the X, X-1, X-2 hitters anyway (the whole point of this feature really!). Also, when browsing a column with this feature enabled, the order is preserved so we'll have the top hits performing GATs shown first.
- Directly export predictions from the panorama to the clipboard. The selection box will be used to identify which GATs we want to export the predictions and right-clicking in the panorama will bring up the function.
Prerelease versions will become available as new features are added since the features list to be added is huge. Please keep in mind, prereleases are not fully verified for correctness (bugs might slip in) but given the official version with all the added features will take time, it really makes no sense to delay features that are already implemented, even if they can take further improvement later. The GUI might look a bit mess (i.e. boxes and options or even functionality might move around till the final official release) due to development.
So, if there is demand for this current prerelease I can prepare one for download at the account management. The point is to use and comment on existing added features along with other proposals till the final version is formed in due time. Finally, since there is no help file yet for these new features, any usage questions should be posted here.
cheers
lottoarchitect
- Delay graph to show a line of actual delay data (requested feature). This shows the actual delays in a graph for a given hit to occur. So now we have a summary (current version) and a line showing the actual delays. To access this feature, we must observe a specific hits delay (i.e. delay of 3 hits) and it is available by right-clicking the delay graph. The most recent delay (not the current delay shown at the bottom) is the right-most point.
- Copy the predicted numbers in sorted order (requested feature). The "copy to clipboard" function currently copies the predicted numbers as shown (unsorted). SInce it is easier to see what numbers are in there when sorted, the copy button now copies the numbers sorted and if someone needs the order of preference decided by GAT, right-clicks on the copy button for this function.
- Colouring GAT cells in the panorama to compare their hits to a given set of numbers. This can be used to instantly show which GATs managed to predict the actual draw (draw must be removed from the history or not adding the new actual draw for this comparison to make sense) and the darker the colour, the more numbers actually predicted. Dark green means more numbers correct, light green means fewer. This function needs further improvement e.g. it will be possibly moved to the functions toolbox but it is functional as it currently is. This feature is enabled if we enter any number for comparison at the options. Also, when the comparison is active, additionally the predicted numbers of each GAT are colored green to indicate which numbers have been predicted (that was a feature of GAT 2.1). The colors used are spread from 0 to the minimum of current requested numbers and total numbers to compare. So if e.g. we enter 5 numbers to compare and show req.numbers 3 at the panorama, obviously the maximum possible is to match only 3 numbers from out set. Therefore the dark green will show up when 3 matches occurred (the maximum) and the other cases will gradually fade to light green (the default color used in panorama) which indicates 0 hits. Similarly for the same 5 set of numbers, if we display req. numbers 20 at the panorama, the maximum possible will be 5 matches (all the numbers in the compare set), therefore dark green is assigned to any GATs that will match all 5 numbers and gradually fade to light green (the default color of the panorama) if 0 hits achieved when compared to that set. This feature is really an eye-opener! Also makes a very nice visual mosaic
- Max GATs shown per column (up to 999). This is another speedup mechanism. This actually will be used to limit the need to keep track of more GATs in a given column since most good GATs are expected to show up at the initial few top cells shown. Even having 99 GATs to check in a column is already too much. Not sure if anybody will set this to a higher setting but it is available if he wants to do that.
- X, X-1, X-2 feature. This is a very important addition. It is fully operational but still needs work to be faster in operation and it is recommended to use the Max GATs per column along with the req.numbers/category speedups. Currently the panorama shows only the top X hitters. However they can be in a cold cycle and since fewer and fewer make it to the panorama as we progress the scan there are more chances to pick a cold performing GAT. This feature is selectable (enable/disable). If disabled, the engine works as it currently does. If enabled, it displays all the top performing GATs in terms of hits produced in descending order till all cells in the column are filled up. So e.g. the initial top cells will have GATs producing X hits, the following ones X-1 hits etc till all the cells are filled up. This feature used together with the compare numbers feature show right away where the best GATs show up where the best ones are expected to be close to the top, if they are not the top X hitters due to their cold cycle. A selection of a good GAT is expected to occur within the X, X-1, X-2 hitters anyway (the whole point of this feature really!). Also, when browsing a column with this feature enabled, the order is preserved so we'll have the top hits performing GATs shown first.
- Directly export predictions from the panorama to the clipboard. The selection box will be used to identify which GATs we want to export the predictions and right-clicking in the panorama will bring up the function.
Prerelease versions will become available as new features are added since the features list to be added is huge. Please keep in mind, prereleases are not fully verified for correctness (bugs might slip in) but given the official version with all the added features will take time, it really makes no sense to delay features that are already implemented, even if they can take further improvement later. The GUI might look a bit mess (i.e. boxes and options or even functionality might move around till the final official release) due to development.
So, if there is demand for this current prerelease I can prepare one for download at the account management. The point is to use and comment on existing added features along with other proposals till the final version is formed in due time. Finally, since there is no help file yet for these new features, any usage questions should be posted here.
cheers
lottoarchitect