Page 1 of 1

Package-Reduce-Optimize Coverage

PostPosted: Tue Mar 07, 2017 8:29 am
by Meisterkeks
Image

Hi Stan,
the smallest value for input % is currently 1,00.
It would be good if the input can also be changed to less than 1%.

For example, I have 13,697 tickets in the package, including 1 x 5 ticket from 6. This ticket has a share of 0,000073008688033876 % (= 1 / 13.697). So I would have to type:
0,00007%
5 of 6

Re: Package-Reduce-Optimize Coverage

PostPosted: Sun Mar 12, 2017 10:47 pm
by stan
First of all I think that optimizing your wheel for less than 1% chance of winning of anything is waste of your CPU time:)

Then what exactly do you expect to achieve when optimizing for such low coverage??

Re: Package-Reduce-Optimize Coverage

PostPosted: Mon Mar 13, 2017 6:43 am
by Meisterkeks
Hi Stan,

So a small cover always makes sense if you have reduced the tickets first and have a high hit rate. This was what I had achieved in my example above! However, I could then set the filter only to 1%. This has the disadvantage that then 540 tickets to play are determined - but they are too many.

Therefore, a reduced input as suggested would be very valuable. Each user must know, of course, that this makes sense only if you have few tickets to choose from.

Re: Package-Reduce-Optimize Coverage

PostPosted: Mon Mar 13, 2017 10:36 pm
by stan
Ok, I'll look into it.

Re: Package-Reduce-Optimize Coverage

PostPosted: Tue Mar 14, 2017 6:13 am
by Meisterkeks
:D :D :D

Re: Package-Reduce-Optimize Coverage

PostPosted: Sat Mar 18, 2017 11:49 am
by stan
So I looked into it and there's a problem with the spinner buttons - I can't lower the minimum allowed value below 0.01 and keep the spinner button for convenient mouse increments/decrements at the same.
The best I could do is lowering the min value to 0.01. But you need to type that value using keyboard instead of using spinner buttons.

Re: Package-Reduce-Optimize Coverage

PostPosted: Sat Mar 18, 2017 4:20 pm
by Meisterkeks
THANK YOU, that would already be a very good solution!

Re: Package-Reduce-Optimize Coverage

PostPosted: Thu May 04, 2017 8:20 am
by Meisterkeks
Demand: until when could the change be included in the update?

Re: Package-Reduce-Optimize Coverage

PostPosted: Tue May 23, 2017 7:35 am
by Meisterkeks
Meisterkeks wrote:Demand: until when could the change be included in the update?


:?: :?: :?:

Re: Package-Reduce-Optimize Coverage

PostPosted: Sun Jun 11, 2017 6:57 pm
by stan
It is available in dev builds already. And it'll be in the official release later on this year when I have enough new feature for a new version...

Re: Package-Reduce-Optimize Coverage

PostPosted: Fri Jan 05, 2018 7:53 am
by Meisterkeks
THANK YOU for the optimization! :D :D :D