Next draw, next number

peter

Member
Beaker, in your announcers chart, can you tell me:
How many times does the 1 announce the 2, the 2 announce the 3, the 3 announce the 4, etc.
I'm looking at next draw, next number. Thx buddy,:agree2:
 

winhunter

Member
Announcer theory...

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.

Hmmmm....

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!!


Andrew


P.S. - WINHunter users, I should have this processor included with the next release!!
 
Being the :king: of announcers....And being the first person to ever talk about this on these boards....
Here's your thing Peter and I added the preceding numbers...I often look at this to spot possible consecutives....Remember put everything into context.....
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
06 ann. 07=33 and 06 ann. 05=41
07 ann. 08=44 and 07 ann. 06=39
08 ann. 09=42 and 08 ann. 07=42
09 ann. 10=33 and 09 ann. 08=35
10 ann. 11=38 and 10 ann. 09=47
11 ann. 12=44 and 11 ann. 10=39
12 ann. 13=41 and 12 ann. 11=35
13 ann. 14=39 and 13 ann. 12=43
14 ann. 15=32 and 14 ann. 13=45
15 ann. 16=33 and 15 ann. 14=38
16 ann. 17=47 and 16 ann. 15=32
17 ann. 18=45 and 17 ann. 16=40
18 ann. 19=43 and 18 ann. 17=43
19 ann. 20=47 and 19 ann. 18=46
20 ann. 21=52 and 20 ann. 19=31
21 ann. 22=38 and 21 ann. 20=45
22 ann. 23=38 and 22 ann. 21=57
23 ann. 24=31 and 23 ann. 22=41
24 ann. 25=37 and 24 ann. 23=50
25 ann. 26=55 and 25 ann. 24=39
26 ann. 27=45 and 26 ann. 25=40
27 ann. 28=42 and 27 ann. 26=39
28 ann. 29=43 and 28 ann. 27=36
29 ann. 30=37 and 29 ann. 28=36
30 ann. 31=55 and 30 ann. 29=39
31 ann. 32=39 and 31 ann. 30=40
32 ann. 33=40 and 32 ann. 31=48
33 ann. 34=53 and 33 ann. 32=43
34 ann. 35=40 and 34 ann. 33=46
35 ann. 36=41 and 35 ann. 34=62
36 ann. 37=51 and 36 ann. 35=44
37 ann. 38=36 and 37 ann. 36=40
38 ann. 39=41 and 38 ann. 37=43
39 ann. 40=39 and 39 ann. 38=46
40 ann. 41=43 and 40 ann. 39=53
41 ann. 42=53 and 41 ann. 40=43
42 ann. 43=49 and 42 ann. 41=38
43 ann. 44=46 and 43 ann. 42=54
44 ann. 45=50 and 44 ann. 43=45
45 ann. 46=44 and 45 ann. 44=46
46 ann. 47=42 and 46 ann. 45=46
47 ann. 48=37 and 47 ann. 46=55
48 ann. 49=52 and 48 ann. 47=49
––––––––----------49 ann. 48=41
 
Last edited:
Re: Announcer theory...

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.

Hmmmm....

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!!


Andrew


P.S. - WINHunter users, I should have this processor included with the next release!!
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! :agree2:
 

peter

Member
When I add up the numbers Dennis, 4101 times out of 2028 draws we get a number that announces either up one or down one in the very next draw. Impressive!!!!!:agree2:
 

peter

Member
An interesting note when you look at the Chart Dennis provided, and look at it as it is laid out, side by side, there are some wild swings in differences. For example, it is interesting to see
the 35 has annouced the 34 a total of 62 times,yet the34 has announced the 35 only 40 times, a difference of 22.
A great chart Dennis, thx again!!:agree2:
You are truly the :king: of announcers.
 

winhunter

Member
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
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
...
etc.

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* :D 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!!



Andrew
 

peter

Member
Andrew, the information , I was seeking from Dennis was just the next number for the next draw. However Dennis And Beaker both have the Entire annoncers, ie: 1...2...1..3...1..4 etc. This is a great tool.
 
is there a way to set up a formula or macro in excel to automatically create an announcer chart? or was this all done by hand?
 
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
...
etc.

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* :D 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!!



Andrew
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....
Implementing this into Winhunter would put your software on the next level...But here's a question for you what is more powerfull than one number announcing an other??
Of course the answer is ...two numbers announcing another number is even more powerfull...After put everything into context (meaning criss-cross references with these announced histories and the recent current normal history)and you might be hitting these hot and middle range cold numbers and the very cold pairs that might show up in the upcoming draws more and more... I'll let you start with it and after I'll tell you a lot more that can be added here of course I can tell you for about 15 others possibles parameters processors that my program already takes into account and even some others ...like the delta-pairing that George was talking about and you can go another step higher....(This one is a powerfull filter)

And to Hypersonic...I don't use excell (got rid of it quite a while ago):eek: ....And I have this at the touch of a button...and more...
 
Last edited:

winhunter

Member
Dennis

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.



Andrew
 
Re: Dennis

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.



Andrew
I assume that you only speak about single announcers...I would say...
All of the above...But the basic principle is the immediate previous draw because this is what would give you the history whithin history chunks that you must take into account...
Of course you can use a group of recent draws(like the last 2 or 3 or 4 draws and so on..) But this is not the direction that I am taking with these...Keep in mind that after compiling them you got to compare it to the actual trend in the normal history and this is where you can see the relevant aspects of the whole theory...
Now if you use the double announcers you will find out that the history whithin history created is a lot of times different than the one created by single announcers in terms of most announced numbers....The same thing is seen when looking at different history time frames...
:agree:
 

winhunter

Member
WINHunter's take

WINHunter is meant to have options for those "fixed" items you mentioned. This is mostly due to the fact that not all lotteries are created equal. And thus, it is hoped that WINHunter will be able to discover the best settings for any given lottery.

With what you have clarified in mind, I will push forward with the single announcers Processor. I am curious as to how you store the information for double announcers, but I think I might usilize the same storage method for double announcers as I do for the new triples processor.

The only difference that I can see that I might introduce is an Offset, which will be a gap between the draw to be announced, and the draws being the announcers. Sometimes WINHunter discovers that some history not immediate to the previous draw is more relevant than the immediate history. Perhaps this OLD history introduces an element of Randomness, thus pitting the Lottery machine against itself.


Andrew
 

winhunter

Member
Work in Progress

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?


Andrew
 
Re: Work in Progress

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?


Andrew
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)
Example lets take this winning set
07-12-23-25-29-31bonus 45
Now lets say that
07 has announced 09 for a total of 40 times and 12 has announced 09 for a total of 32 times and so on ....in the end all of these should be added to give the most announced by the entire set....
taken individually it is like choosing from seven different directions and it could be misleading...Now how could you score them?? I do not know what kind of score you want exactly...
We know that by cutting down the time frame and by getting the most recent hit by all the numbers (lets say the last 10 draws from the announced history)you will see that many are announced 0 time and 1 time only ...now compare these with the entire announced history often what is announced the least is where the most numbers come from....
 
Re: Oic

winhunter said:
Add them eh? Ok.

Once added, how do you determine which numbers are the best ones to pick from that bunch?


Andrew
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... :agree:
One way to score them is by giving some + values to the ones on top and to the ones at the bottom of the recent announced history...
 

winhunter

Member
okies

since WINHunter has a selector method that allows you differing ways to cross the chart, here is what I came up with....

13: 11, 5 of 6
12: 10, 0 of 6
11: 10, 1 of 6
10: 10, 2 of 6
9: 11, 1 of 6
8: 12, 2 of 6
7: 12, 2 of 6
6: 10, 2 of 6
5: 11, 2 of 6
4: 18, 2 of 6
3: 17, 3 of 6
2: 12, 0 of 6
1: 16, 5 of 6

Using the "additive method" as you described, and using just the HIGH numbers from the addition of the numbers that scored based upon the SINGLE last draw. Now I am using the filter optimizer to tell me what depth settings are best suited for the last TEN draws.

Here is another history setting results...

25: 17, 1 of 6
24: 18, 2 of 6
23: 10, 1 of 6
22: 11, 2 of 6
21: 12, 0 of 6
20: 16, 3 of 6
19: 16, 0 of 6
18: 12, 0 of 6
17: 10, 1 of 6
16: 13, 3 of 6
15: 10, 3 of 6
14: 17, 2 of 6
13: 16, 2 of 6
12: 12, 4 of 6
11: 12, 1 of 6
10: 14, 5 of 6
9: 16, 2 of 6
8: 15, 5 of 6
7: 12, 1 of 6
6: 16, 2 of 6
5: 14, 2 of 6
4: 13, 3 of 6
3: 13, 1 of 6
2: 11, 1 of 6
1: 11, 2 of 6

These look VERY promising Dennis!

Such low predicted counts with such decent match counts.

We will have to talk more on the double announcer theories and such. I need to run and build an installation setup and upload it to sourceforge now... I will have to play with this Processor next week though!

Andrew

BTW, thanks again for your valuable input!!
 

winhunter

Member
25: 12, 2 of 6
24: 11, 0 of 6
23: 11, 1 of 6
22: 16, 3 of 6
21: 17, 1 of 6
20: 11, 2 of 6
19: 11, 1 of 6
18: 11, 1 of 6
17: 11, 4 of 6
16: 13, 0 of 6
15: 10, 1 of 6
14: 17, 1 of 6
13: 13, 0 of 6
12: 13, 1 of 6
11: 16, 2 of 6
10: 13, 1 of 6
9: 15, 2 of 6
8: 14, 0 of 6
7: 10, 0 of 6
6: 11, 2 of 6
5: 11, 1 of 6
4: 12, 0 of 6
3: 16, 6 of 6 ***
2: 17, 3 of 6
1: 15, 3 of 6


*GRIN*


Andrew
 
Top