I am quite surprize to see that you did not implemented that option into your device yet...Do it in a hurry...You will hit them like thunderbolt....you will increase your hit ratio no question about it...especially if you join this whit a history control of some kind and if you join the whole set up with the open pair theory....Take it from you know who!winhunter said:Hey peter, you gave me a possible idea for a rule within WINHunter for an existing processor.
Currently, WINHunter has a pairhit processor where it counts how many times pairs of numbers have hit with each other. A similar Data Array could be generated that simply counts how many times a number "Announced" the next number's arrival. This type of calculation though almost seems more like a "Position Vector" type of calculation. You have to back off one draw, then compare the next most recent draw to the most recent draw after the skip/use history has been calculated.
How many draws do you consider to be the "Announced" draw? IS it the immediate Draw after a draw? So, for a 6/49 game, you would have 36 data points for a single announcer draw, because you have the draw that is being announced, and the draw doing the announcing. Thus you have 6 numbers times 6 numbers, which yields 36 points, which map to 49 times 49 points 2401 points.
This would graph as a simple X/Y/Z plot, with the Announcers being the Y-axis, and the Announced being the X-axis and the number of times being announced is the Z-axis.
Due to the type of Code required, and the fact that this has more to do with Announcers, I think this is best suited for it's own Processor Code.
Thanks peter for the excellent visualization of the announcer theory. I have understood what it was, but your brief comment just solidified it for me!!
P.S. - WINHunter users, I should have this processor included with the next release!!
Dennis Bassboss said:01 ann. 02=38
02 ann. 03=45 and 02 ann. 01=45
03 ann. 04=36 and 03 ann. 02=40
04 ann. 05=36 and 04 ann. 03=46
05 ann. 06=36 and 05 ann. 04=49
47 ann. 48=37 and 47 ann. 46=55
48 ann. 49=52 and 48 ann. 47=49
––––––––----------49 ann. 48=41
Peter is right on here I (and also Beaker as I made this not free program available to him free from one of my contacts tough he also had other programs to find them...lottoman for an example...)have all of this already and I had this since a very long time now......and more....winhunter said:Dennis,
This is a straight linear progression of announcers, right? The data I was considering building was of this nature:
1 ann. 2
1 ann. 3
1 ann. 4
2 ann. 1
2 ann. 3
Sounds like I need a Linear Announcer Method, and then a Full Announcer Method (I call them rules inside a processor. Rules tend to use the same Dataset, they just crunch the numbers differently.)
And yes Dennis, as always, WINHunter allows you to test/specify the amount of history to use, as well as where to start using the history (It's called Skip/Use in WINHunter.)
I will see what I can do to try to get it out this week sometime! I am setting up a Distribution Server this week as well, so I am somewhat busy dealing with issues surrounding that.
I am getting a better grasp as what data to produce, and how to score it for WINHunter regarding Processors. This will inevitably cause a few more processors to be coded, that is for sure!!
And, I do expect you (Dennis) to get into WINHunter once I develop a Processor (or two or three) based upon your announcers. *Grin* Seriously, I do hope you will take a look at it and give me feedback. Already Brad/Combo/Beaker/Thornc have contributed alot since I started here. I know there is alot more to be gleened from members here that have not yet taken the WINHunter plunge!!
I assume that you only speak about single announcers...I would say...winhunter said:Announcers are calculated on which of the following methods?
1> The immediate draw previous to the draw in question is the draw that "Announces" the next draw. Thus the annoucer database is calculated ONLY upon the IMMEDIATE previous draw.
2> A group of immediate draws
3> A group of OFFSET immediate draws
I can design WINHunter to handle all cases, based upon user input. But I guess I just need to know which one is basic.
That is the twist Andrew....In my opinion It is best that the last set of numbers gives how many times each numbers came up as a whole (adding them)winhunter said:Dennis,
Ok... I need some ideas/help here.
So far, I have WINHunter configured so that it will build an announcer history based upon user set amount of past history to build the annoucer data from.
Now, what this results in, is a history (counts) of which number "annouced" what other numbers.
With that history built, how do I score the most recent draw based upon the past history, just select which number/numbers for each position that was announced the most?
By looking at different time frame....You see in the entire history some are overwelmingly announced....in the recent history it is not the same ones.....But those that are the most announced on top usually and at the bottom are the ones to watch for...But generally you get one from the top announced in the recent draws anyways...winhunter said:Add them eh? Ok.
Once added, how do you determine which numbers are the best ones to pick from that bunch?