Package-Reduce-Optimize Coverage

Package-Reduce-Optimize Coverage

Postby Meisterkeks » Tue Mar 07, 2017 8:29 am

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
Thank you

Best Regards!

Meisterkeks
Meisterkeks
 
Posts: 221
Joined: Fri Aug 19, 2016 7:42 am
Location: Germany

Re: Package-Reduce-Optimize Coverage

Postby stan » Sun Mar 12, 2017 10:47 pm

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??
Expert Lotto Team
User avatar
stan
Site Admin
 
Posts: 6338
Joined: Thu Sep 23, 2004 1:01 pm

Re: Package-Reduce-Optimize Coverage

Postby Meisterkeks » Mon Mar 13, 2017 6:43 am

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.
Thank you

Best Regards!

Meisterkeks
Meisterkeks
 
Posts: 221
Joined: Fri Aug 19, 2016 7:42 am
Location: Germany

Re: Package-Reduce-Optimize Coverage

Postby stan » Mon Mar 13, 2017 10:36 pm

Ok, I'll look into it.
Expert Lotto Team
User avatar
stan
Site Admin
 
Posts: 6338
Joined: Thu Sep 23, 2004 1:01 pm

Re: Package-Reduce-Optimize Coverage

Postby Meisterkeks » Tue Mar 14, 2017 6:13 am

:D :D :D
Thank you

Best Regards!

Meisterkeks
Meisterkeks
 
Posts: 221
Joined: Fri Aug 19, 2016 7:42 am
Location: Germany

Re: Package-Reduce-Optimize Coverage

Postby stan » Sat Mar 18, 2017 11:49 am

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.
Expert Lotto Team
User avatar
stan
Site Admin
 
Posts: 6338
Joined: Thu Sep 23, 2004 1:01 pm

Re: Package-Reduce-Optimize Coverage

Postby Meisterkeks » Sat Mar 18, 2017 4:20 pm

THANK YOU, that would already be a very good solution!
Thank you

Best Regards!

Meisterkeks
Meisterkeks
 
Posts: 221
Joined: Fri Aug 19, 2016 7:42 am
Location: Germany

Re: Package-Reduce-Optimize Coverage

Postby Meisterkeks » Thu May 04, 2017 8:20 am

Demand: until when could the change be included in the update?
Thank you

Best Regards!

Meisterkeks
Meisterkeks
 
Posts: 221
Joined: Fri Aug 19, 2016 7:42 am
Location: Germany

Re: Package-Reduce-Optimize Coverage

Postby Meisterkeks » Tue May 23, 2017 7:35 am

Meisterkeks wrote:Demand: until when could the change be included in the update?


:?: :?: :?:
Thank you

Best Regards!

Meisterkeks
Meisterkeks
 
Posts: 221
Joined: Fri Aug 19, 2016 7:42 am
Location: Germany

Re: Package-Reduce-Optimize Coverage

Postby stan » Sun Jun 11, 2017 6:57 pm

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...
Expert Lotto Team
User avatar
stan
Site Admin
 
Posts: 6338
Joined: Thu Sep 23, 2004 1:01 pm

Re: Package-Reduce-Optimize Coverage

Postby Meisterkeks » Fri Jan 05, 2018 7:53 am

THANK YOU for the optimization! :D :D :D
Thank you

Best Regards!

Meisterkeks
Meisterkeks
 
Posts: 221
Joined: Fri Aug 19, 2016 7:42 am
Location: Germany


Return to Comments, suggestions, feature requests

Who is online

Users browsing this forum: No registered users and 2 guests

cron