build 976 is available

[stan]

[quote=Picsou:1206996188]
Hello all

Good evening

Here is my vision of the segment calculator and how I believed that it to go to work.
My purpose is to find the occurrences of segments which leave 1 ticket from the segment 6 or 7 (i repeat go to Tax posts for that). It will be easier to find 6values of segments justs 11.
How should work the segment to calculator:

At first after a new draw , I update the base.

You can then update the table of segments by the button update. the good segments then appear for the last draw, but you don't know how nany tickets left in package after each segment.

At this moment I skip the last draw (expert lotto must remember the segments values), make a full package and lauch the segment calculator.
It's after "working" should indicate me for every good value of the segment the remaining number of tickets of one package suit.

I then have to feed a base Excel to update.
You can then repeter the operation after skipping an another draw and so on.

(to understood,Calculator, work like a 11 segments compound filter, but it's know each value segment to select for each steep).
result will be

321: 1674432, 222:196200, 132:23192, 303:1279, 024: 40, 501:5, 123:1, 051:1,321:1,330:1,330:1

after your analys of a lot of result in your excel file,you make your segments combinaison for your each 11 segments filter.

is it clear?
cdt
[/quote]

i can create a new calculator where you'd enter 11 segments and the calculator will show how many package tickets have the first segment, how many have the first two segments, how many have the first three etc...
maybe you could even enter multiple segment combinations from a text file (see the new multiple segments filter). would that be helpful?

[Picsou]

Hello Stan

for me it's ok you add this on calculator.
it's must work in two cases:

first: with all draws in the base, it's give indication of numbers of tickets leave for each segments for a previus draw after you have selected your selected "good" values of segment.

second: You note the values of the "good" segments from last draw, skip it, and put in calculator, it's give real numbers of tickets for each segment of the last real draw....

cdt

[stan]

[quote=Falcon:1205833451]
Stan,

Would like to add a further item to my request list in the previous post.

In 'Package Statistics' there is a column WNH Odd/Even Count. To complement the new neg/pos filter could there be a similar column WNH Neg/Pos Count.

Thanks

falcon
[/quote]

will be in version 1.0.3

[stan]

build 1001/1002 is available for download, pls read more here: http://www.expertlotto.com/en/download/beta.htm#news

[PadawanLotto]

I downloaded and installed build 1002 and there is a problem some where as when I try to use my group filter it is extremely slow and yes it is running multi-threading.

[stan]

[quote=PadawanLotto]
I downloaded and installed build 1002 and there is a problem some where as when I try to use my group filter it is extremely slow and yes it is running multi-threading.
[/quote]

hmm, it seems to be running fine for me.
maybe you have some other application running in background?...

[PadawanLotto]

I found it is running slow due to writing errors to the error log. I will e-mail you what I got when I'm done testing.

[PadawanLotto]

Build 1002 clashes with Joe's segment filters, everytime one of the filters tries to filter data an error occurrs and the error is written to the error log. This error writting can cause the error log to fill up fast and with just the little bit of testing I did the error log had over 1MB of data in it and that was starting with an empty log 0kb.

[stan]

[quote=PadawanLotto]
Build 1002 clashes with Joe's segment filters, everytime one of the filters tries to filter data an error occurrs and the error is written to the error log. This error writting can cause the error log to fill up fast and with just the little bit of testing I did the error log had over 1MB of data in it and that was starting with an empty log 0kb.
[/quote]

yes, i intentionally broke the api contract. it was necessary to avoid errors when filters were running in multiple threads. joe will need to fix that plugin to work with the new api (or you have to use older builds)

[PadawanLotto]

Good thing I saved the older builds as I like the segment filters and I don't see Joe fixing them any time soon.

[PadawanLotto]

None of Joe's segment filters work with build 1002 and that is a lot of segment filters (DistinctSegmentCounts, SegmentsSum, SingleSegmentCounts, SingleSeg123RepeatsAnyColumn, SingleSegRepeatsAnyColumnWithPreviousOne).

[PadawanLotto]

[quote=stan]
[quote=PadawanLotto]
Build 1002 clashes with Joe's segment filters, everytime one of the filters tries to filter data an error occurrs and the error is written to the error log. This error writting can cause the error log to fill up fast and with just the little bit of testing I did the error log had over 1MB of data in it and that was starting with an empty log 0kb.
[/quote]

yes, i intentionally broke the api contract. it was necessary to avoid errors when filters were running in multiple threads. joe will need to fix that plugin to work with the new api (or you have to use older builds)
[/quote]
Stan, at what build did you do this, my last build was 998.

[stan]

[quote=PadawanLotto]
[quote=stan]
[quote=PadawanLotto]
Build 1002 clashes with Joe's segment filters, everytime one of the filters tries to filter data an error occurrs and the error is written to the error log. This error writting can cause the error log to fill up fast and with just the little bit of testing I did the error log had over 1MB of data in it and that was starting with an empty log 0kb.
[/quote]

yes, i intentionally broke the api contract. it was necessary to avoid errors when filters were running in multiple threads. joe will need to fix that plugin to work with the new api (or you have to use older builds)
[/quote]
Stan, at what build did you do this, my last build was 998.
[/quote]
in build 998, i think
if it's a big problem i can remove the log message so that filters keep working (and using default segment sizes from app preferences)

[PadawanLotto]

In build 998 all of Joe's segment filters work, in build 1002 they don't work and I get error log that reads *** Error Tue Apr 29 13:46:36 EDT 2008
*** App Version: 4.2.1 Build: 1002
*** Java Version: 1.6.0_05
*** OS Version: Windows XP 5.1
*** Lottery: Rolling Cash 5 OH
*** Message: Method DrawWnHistory.segSegmentEnd() is deprecated, please update your plugins.

[stan]

i've just uploaded new jackpot build 1004 which write only a single message into error log per expert lotto session