Page 1 of 2

dev build 110506

PostPosted: Fri May 06, 2011 1:15 pm
by stan
new development build is now available with the following updates:

- draw groups filter
- number group repeats
- coefficient of variation
- limit range for simulation estimates
- number movement pattern and digits movement pattern stats
- trend predictor filter
- combined statistics (see menu 'tools - options - statistics - combined statistics')
- 143
- online update of winning numbers for floria mega money

Re: dev build 110506

PostPosted: Fri May 06, 2011 3:27 pm
by Jerzy
Stan,

I can't find coefficient of variation statistics or filter in the latest build. Where can I find it?

Re: dev build 110506

PostPosted: Fri May 06, 2011 3:50 pm
by stan
Jerzy wrote:Stan,

I can't find coefficient of variation statistics or filter in the latest build. Where can I find it?

you need to toggle 'draw interval details' button in analyzer table

Re: dev build 110506

PostPosted: Fri May 06, 2011 4:22 pm
by Jerzy
Stan,

Thank you. I found it.

There are some interesting features in the latest build and I have to see how they work.
I noticed Combined Statistics in Tools --> Options --> Statistics with the possibility of adding statistics for filter combinations. Thank you again.

Re: dev build 110506

PostPosted: Sat May 07, 2011 5:05 pm
by Jerzy
Stan,
What is Ticket Interval (in Winning Numbers Properties table) ?

Re: dev build 110506

PostPosted: Sun May 08, 2011 2:19 am
by teoman
Hi, Stan,

Thanks very much for implementation 'limit range for simulation estimates', but it would have been even more extraordinary if the percentages it would be was with decimal, could be use more levels, thousands, so 1% is effective only up to 100 levels.
I hope not is too difficult for you to do and this improvement.

Re: dev build 110506

PostPosted: Sun May 08, 2011 9:15 am
by stan
Jerzy wrote:Stan,
What is Ticket Interval (in Winning Numbers Properties table) ?

the average value of the number of draws elapsed since the latest occurrence of each ticket number

Re: dev build 110506

PostPosted: Sun May 08, 2011 9:18 am
by stan
teoman wrote:Hi, Stan,

Thanks very much for implementation 'limit range for simulation estimates', but it would have been even more extraordinary if the percentages it would be was with decimal, could be use more levels, thousands, so 1% is effective only up to 100 levels.
I hope not is too difficult for you to do and this improvement.

the occurrence threshold relates to the occurrency of the most frequent value in the simulation. so if the most frequent simulated sum has occurrence of 1000, then settings 2% to 3% of maximum frequency will select sums that have occurrence of at least '20' on the left hand part of the histogram and '30' on the right hand part of the histogram.
it'll be described properly in updated documentation when version 5.1 is released officially

Re: dev build 110506

PostPosted: Mon May 09, 2011 4:12 am
by teoman
stan wrote:
teoman wrote:Hi, Stan,

Thanks very much for implementation 'limit range for simulation estimates', but it would have been even more extraordinary if the percentages it would be was with decimal, could be use more levels, thousands, so 1% is effective only up to 100 levels.
I hope not is too difficult for you to do and this improvement.

the occurrence threshold relates to the occurrency of the most frequent value in the simulation. so if the most frequent simulated sum has occurrence of 1000, then settings 2% to 3% of maximum frequency will select sums that have occurrence of at least '20' on the left hand part of the histogram and '30' on the right hand part of the histogram.
it'll be described properly in updated documentation when version 5.1 is released officially

Stan, I understand how it works, but if I want to use thousands of levels, I not can make an effective setting, especially on the left side aimed at negative values, which would be was desirable to have values of percentages with decimal. With 1% not can reduce the negative values ​​with 5% -10%. Here are a few percent of the values ​​that you see in the image, to 1% all is reduced with too much, with over 24%:

(-58) - (-43) = 15 => 25,86%
(-63) - (-43) = 20 => 31,75%
(-48) - (-28) = 20 => 41,66%
(-59) - (-44) = 15 => 25,42%
(-81) - (-56) = 25 => 30,86%
(-70) - (-48) = 22 => 31,43%
(-116)-(-80) = 36 => 31,03%
(-85) - (-57) = 28 => 32,94%
(-82) - (-53) = 29 => 35,37%
(-92) - (-70) = 22 => 23,91%
(-50) - (-34) = 16 => 32,00%
(-62) - (-41) = 21 => 33,87%
(-105)-(-75) = 30 => 28,57%

Re: dev build 110506

PostPosted: Mon May 09, 2011 4:14 am
by teoman
stan wrote:
teoman wrote:Hi, Stan,

Thanks very much for implementation 'limit range for simulation estimates', but it would have been even more extraordinary if the percentages it would be was with decimal, could be use more levels, thousands, so 1% is effective only up to 100 levels.
I hope not is too difficult for you to do and this improvement.

the occurrence threshold relates to the occurrency of the most frequent value in the simulation. so if the most frequent simulated sum has occurrence of 1000, then settings 2% to 3% of maximum frequency will select sums that have occurrence of at least '20' on the left hand part of the histogram and '30' on the right hand part of the histogram.
it'll be described properly in updated documentation when version 5.1 is released officially

If would use 0% to 0% all the values ​​would be higher with 1 and would go outside histogram and think that this it is incorrect.

Re: dev build 110506

PostPosted: Mon May 09, 2011 2:25 pm
by Jerzy
Stan,

In the Repeating Numbers filter (in the Winning Numbers group of filters) there is no indication from which draw or draws the numbers would repeat.

The filter has Min and Max both adjustable from 0 to 6. Depending on the settings, the filter accepts or rejects from the package all tickets only.

Re: dev build 110506

PostPosted: Tue May 10, 2011 11:34 am
by stan
Jerzy wrote:Stan,

In the Repeating Numbers filter (in the Winning Numbers group of filters) there is no indication from which draw or draws the numbers would repeat.

The filter has Min and Max both adjustable from 0 to 6. Depending on the settings, the filter accepts or rejects from the package all tickets only.

the filter first lists all pools numbers that were drawn in the selected past draws and then accepts only tickets that have the specified count of numbers from that list.

Re: dev build 110506

PostPosted: Tue May 10, 2011 11:37 am
by stan
teoman wrote:
stan wrote:
teoman wrote:Hi, Stan,

Thanks very much for implementation 'limit range for simulation estimates', but it would have been even more extraordinary if the percentages it would be was with decimal, could be use more levels, thousands, so 1% is effective only up to 100 levels.
I hope not is too difficult for you to do and this improvement.

the occurrence threshold relates to the occurrency of the most frequent value in the simulation. so if the most frequent simulated sum has occurrence of 1000, then settings 2% to 3% of maximum frequency will select sums that have occurrence of at least '20' on the left hand part of the histogram and '30' on the right hand part of the histogram.
it'll be described properly in updated documentation when version 5.1 is released officially

If would use 0% to 0% all the values ​​would be higher with 1 and would go outside histogram and think that this it is incorrect.

yes, i'll fix that

Re: dev build 110506

PostPosted: Tue May 10, 2011 12:22 pm
by stan
teoman wrote:
stan wrote:
teoman wrote:Hi, Stan,

Thanks very much for implementation 'limit range for simulation estimates', but it would have been even more extraordinary if the percentages it would be was with decimal, could be use more levels, thousands, so 1% is effective only up to 100 levels.
I hope not is too difficult for you to do and this improvement.

the occurrence threshold relates to the occurrency of the most frequent value in the simulation. so if the most frequent simulated sum has occurrence of 1000, then settings 2% to 3% of maximum frequency will select sums that have occurrence of at least '20' on the left hand part of the histogram and '30' on the right hand part of the histogram.
it'll be described properly in updated documentation when version 5.1 is released officially

Stan, I understand how it works, but if I want to use thousands of levels

i don't think you do:)
if you look at your screen shot the most common difference in simulation results has occurrence of approximately 24000 (in level 2). so 1% is 240 so the minimum value transfered to estimates hints are simulated differences with occurrence of 240 or higher - so the result -28.
the same applies to the maximum range transfered to estimates hints.

Re: dev build 110506

PostPosted: Tue May 10, 2011 1:27 pm
by teoman
stan wrote:i don't think you do:)
if you look at your screen shot the most common difference in simulation results has occurrence of approximately 24000 (in level 2). so 1% is 240 so the minimum value transfered to estimates hints are simulated differences with occurrence of 240 or higher - so the result -28.

I need a more small reduction from 24 to 24,000 (1% to 1.000% or 0.1% to 100%) so (-48) - (-28) = 20 => 41.66% to become (-48) - (-46) = 2 => 4,166% if they choose 0.1% but I choose 0.4% and then I will be (-48) - (-40) = 8 => 16.66%.
the same applies to the maximum range transfered to estimates hints.

For the maximum range transfered is OK.
All our interventions are with order to make this Expert Lotto more perfect and to work more correct.
Thank you for your understanding and for made effort to elaboration this grand Expert Lotto.