Some ideas for new filters

[Trust]

Hi!
I have some suggestions for new filters:
The numbers range filter could maybe be enhanced to
filter tickets that has the same range(distance)
Example:The ticket 1 6 17 22 27 32 have 4 instances with same range(5)

So the filter would be like:Remove/Leave tickets that have min x to max
y instances of the same range.

Another idea relates to Last Digits -filter sets with increasing/decreasing
instances of last digit in tickets. According to the statistics it could be
nice to have a filter that limits the number of increasing /decreasing
value on last digits in the ticket.

Something like this?
Remove/Leave tickets with max x increasing/decreasing value in last digit

Last idea is to have a option to generate tickets according to the index
value of the tickets- Generate tickets from start index to max index value.
Example of use could be based on statistic on what is the least to the max
difference of index number from a draw to next draw.
Maybe a idea to split the ticket in all indexes from 2 first to all numbers
in ticket.
I am not sure of how usefull this feature could be- just a thougt.
What do you think?

[stan]

[quote=Trust:1118586911]
Hi!
I have some suggestions for new filters:
The numbers range filter could maybe be enhanced to
filter tickets that has the same range(distance)
Example:The ticket 1 6 17 22 27 32 have 4 instances with same range(5)

So the filter would be like:Remove/Leave tickets that have min x to max
y instances of the same range.
[/quote]
quite an easy change but it seems a bit exotic to me

Another idea relates to Last Digits -filter sets with increasing/decreasing
instances of last digit in tickets. According to the statistics it could be
nice to have a filter that limits the number of increasing /decreasing
value on last digits in the ticket.

Something like this?
Remove/Leave tickets with max x increasing/decreasing value in last digit

what are increasing instances??

Last idea is to have a option to generate tickets according to the index
value of the tickets- Generate tickets from start index to max index value.
Example of use could be based on statistic on what is the least to the max
difference of index number from a draw to next draw.
Maybe a idea to split the ticket in all indexes from 2 first to all numbers
in ticket.
I am not sure of how usefull this feature could be- just a thougt.
What do you think?

what is index value? is it a sequence index, e.g. ticket 1,2,3,4,5,6 has index value 1 and ticket 44,45,46,47,48,49 has index value 13983816?

in this case it's a problem to calculate such index value for an arbitrary ticket, e.g. 10,15,19,33,44,48 (except for iterating the list of all combinations which is too slow to calculate any stats or filter). we've spent some time developing a fast algorithm/mathematical formula but without luck - it would have made the minimizer faster...

[Trust]

what are increasing instances??

What i meant was increasing/decreasing values like
if the last digit numbers are 3 4 6 4 7 5 then the number of increasing
values are 3

what is index value? is it a sequence index, e.g. ticket 1,2,3,4,5,6 has index value 1 and ticket 44,45,46,47,48,49 has index value 13983816?

Yes-that is what i meant.I have seen some code examples of how
to calculate the index/sequense from combination to index and index
number to combination in a fast way. (In Visual Basic).
If you want to have a look at it -let me now.

[stan]

ok, got it.

if you have any examples for sequence index calculation pls email them to me (or post them here if it's not a secret )
i only hope the algorithm is fast enough to allow stats/filter calculations to finish in a reasonable time.

[Trust]

Hi!
If webmaster is your email adress i just sent you
a mail regarding this.
Check your mail.

[stan]

many thanks for the email, the algorithm looks useful.

so your idea is to have an extra column in the winning numbers table stats like this:

[m]
draw index diff
1,2,3,4,5,6 -5
1,2,3,4,5,10 +2
1,2,3,4,5,8 n/a
[/m]

and then a filter when you can define min & max index values.

is that correct?

i think the problem is that the stats provide a relative value while the filter would work with absolute values.
it may be better to have a filter similar to number movement filter where you can select a 'reference draw' (usually the latest draw) and then define 'how far' tickets can be from the reference draw (i.e. the min/max values for index differences)

[Trust]

and then a filter when you can define min & max index values.

is that correct?

Yes that is correct.
BTW the differences will probably be in the number of millions in
a real draw history.

i think the problem is that the stats provide a relative value while the filter would work with absolute values.
it may be better to have a filter similar to number movement filter where you can select a 'reference draw' (usually the latest draw) and then define 'how far' tickets can be from the reference draw (i.e. the min/max values for index differences)

That sounds OK with me.
Thanks!

[stan]

[quote=Trust]
BTW the differences will probably be in the number of millions in
a real draw history.
[/quote]
that's what i was thinking too. i hope the new stats will be usable - at least it'll be possible to sort the table column to find min/max values for e.g. past 20-30 draws.

[Trust]

that's what i was thinking too. i hope the new stats will be usable - at least it'll be possible to sort the table column to find min/max values for e.g. past 20-30 draws.

That sounds OK.Maybe it could be a idea to call statistics particilar
to the filter directly from the filter window?
That way the main statistics window could be cleaner.
Maybe useful for several filter types that could be defined as
"exotic"? Just a thought.

[stan]

in this case the filter window would have to copy most functionality of the stats page.
it'll be better to have an option in the stats page to hide some table you're not interested in (planned for the next release).

[Trust]

in this case the filter window would have to copy most functionality of the stats page.
it'll be better to have an option in the stats page to hide some table you're not interested in (planned for the next release).

Yes,that is probably a better solution.