WN History filter

[PadawanLotto]

While working with the WN History filter, if you filter one or more columns then, filter the other columns later you get your ticket reduction. But then you reset the package and run the filter as a whole and you get a different amount of reduction. Is it best to filter all columns at the same time?

[stan]

when AND condition applies then there should be no difference between filtering 'one column at a time' and filtering 'all columns at once' (of course you must use the same range values, the same winning numbers database etc)

can you pls give an example where the filtering differences are?

[PadawanLotto]

After setting the sum value +/-10 varience for one column run the filter and then set the next value and run the filter until you have set and run all of the columns. The number of combinations are lower than if you run all of the same sum values at once on a full package.

[stan]

i tried step-by-step filtering and as i expected i got exactly the same results as when filtering all columns at once.

i used the demo 6/49 lottery and filter for ideal sum values for the last skipped draw +10/-10:

* step 1 (column 0): 7233535 tickets left
* step 2 (column -1): 3739131 tickets left
* step 3 (column -2): 1021461 tickets left
* step 4 (column -3): 198630 tickets left
* step 5 (column -4): 80225 tickets left
* step 6 (column -5): 21515 tickets left
* step 7 (column -6): 8388 tickets left
* step 8 (column -7): 4359 tickets left
* step 9 (column -8): 2139 tickets left
* step 10 (column -9): 578 tickets left
* step 11 (column -10): 135 tickets left

when filtering all columns in one step: 135 tickets left

as you can see above filtering the wn history sum in just one column reduces the number of tickets by approximately 50%

[PadawanLotto]

I tried it again and your right either way filters the same, COOL!

[zooz]

Hi Satn

I'm playing 7/35 lottery, and when i use the WN History Filter with +/-10
margins for the estimated sums i got 0 left tickets in the package.
I wonder if the margin i'm using is the same as the ( 6/49 ) one described
in the help contents.
Should i use more or less margins?

[stan]

[quote=zooz]
I'm playing 7/35 lottery, and when i use the WN History Filter with +/-10
margins for the estimated sums i got 0 left tickets in the package.
I wonder if the margin i'm using is the same as the ( 6/49 ) one described
in the help contents.
Should i use more or less margins?
[/quote]

were you able to reproduce the example from application's help?
you can also try wider ranges and decrease them gradually to find out how many tickets will be left

[Bobes]

It can happen (zeroed package after filtering) in particular if you chose close margin.

Common mistake is that one (or more) margin is set too high or too low. Pls check the margins you set using History Differences Tabs for each column against the Max(-) and Max(+) values (Right-hand upper corner of screen). If you are close to these margins but yet inside the interval between, try to set condition "at least "xx" to "yy" must pass the filter" to eg. "at least "09" to "11" must pass the filter".
However in case of 7/35 type of the lottery the +/-10 condition seems to be the most suitable condition iń decision making process. You can also use setting in WN History →History Charts→Options→Default Range +/- 6% (the best value could be from 6 to 8%) . Such setting should consider trends for unexpected behaviour of lotto in the past in better way.