Winnalotto-Sangoma 2

[black prince]

Hi HalfBee

Originally Posted by HalfBee
I've only been looking at this about a week and I have to say this:
I appreciate the work that's gone into this program. In backtesting I've found that when it hits... IT HITS HARD... but then there's some draws that produce nothing no matter how hard you whack it with a hammer...

Keep working on it...

Timing seems to be everything. I've been trying to figure out which filter(s)
are reliable in warning me that a major situation is coming and to watch out
for big hits. Saliu called them trigger situations by checking the sum of the
drawing numbers being below say 100. He noticed that that a draw with
the same or less than 100 would come in the next 1 to 4 drawings. I tested
this and it works. He also noticed that the draw would have no number
greater than 23. This means you could play numbers from 1 to 23 in the
next 1 to 4 draws. I determined this last number by visually looking at my
own lottery draws. It was different but it did cut off after a low sum of
draw numbers. We need a trigger filter to tell us when it's optimal to play
and what range.

-BP

 

[taaroa]

Hi Everybody,

Comment allez-vous? How are you today?

Does anybody have Euromillions 5/50 statistics about numbers divisible by 3,4,5 and so on... till 16 ?

I'm trying to code a filter for Euromillions with various filters.

Thank you.

taaroa

 

[barge]

Filter

Hi Turtle,

The top line is the name of the filter, use it to save. paste everything below it into the lower box and tick the filter button.

Cheers

 

[Springbok]

Filter building

I think some people out there would like to build their own filters. Start with skip(0) = 0. That will pull out trips and pairs which hit last draw or wherever you started from in the history file. Look at the reporting on the last 5 skip cycles. It makes lifie easier if you unclick the various columns so you only see the last 5 columns of the skips-it is easier on the eye. For example out of 18000+ trips nearly 7000 are represented(in this case the 7/49 game). So if you give your grandma a needle and ask her to point out a trip she will be correct once every 4 our of 10 picks or 39% of the time. Pick the biggest idiot you know and ask them to do the same. Take your pet chimpanzee and give it a banana and ask it to do the same. The statistics will be constant. Bobo the chimp will be as accurate as granny and the biggest idiot over time. Each will have their streaks of wins. You want to do better than that. Look at the second skip column and sort it. Around 80% will have skip 2 in that column. Look at the other columns. Write in your parameters using the = , < , > and work out your own filters and test them repeatedly and see what you can do. Aim to hit a pair or trip next draw. It is pointless to go on and try and hit all the trips and or pairs in the next draw if you cannot do that. If your strike rate in the next draw is way above 40% then you know you are doing something right. If you cannot do that then rely on Bobo, granny or the idiot to do it for you

 

[Springbok]

Filter construction

Just to amplify on the previous post. Remember I am using the 7/49 game. Set the filter to only pull out trips with the last skip of 0. Nothing else. Take a pad and a pencil. Pick 3 trips from the range. Make sure each trip has different numbers. Check the result for the next draw. At this stage you will be level pegging with Bobo etc. You will normally find one trip is right, one will hit 2 draws later and one is a complete hooligan. Now rumour has it us humans are a little bit smarter than chimps. So you have to build the filter to improve accuracy. The next stage is the 2nd column. You have to write a suitable arguement which will improve your strike rate and prove to Bobo who is the smarter. Have fun

 

[Springbok]

A bit more

Do the initial test over and over and over again until it is hammered into your mind. Keep records of the results so you can work out your strike rate. Always note where the trip strikes, next draw,2 or 3 draws later or a complete hooligan.Once this is hammered into your mind then expand the filter with another arguement and test. Remember the strike rate in the very next draw is uber alles. If you get a 100% strike rate then let me know for I will be all ears

 

[Springbok]

Gooie middag Patrick

Is it possible to have the facility of not including numbers when trips and pairs are generated. At the moment the full monty is given for each of those. The ability to exclude certain numbers would be highly beneficial.

 

[black prince]

To All

Originally Posted by Springbok
Is it possible to have the facility of not including numbers when trips and pairs are generated. At the moment the full monty is given for each of those. The ability to exclude certain numbers would be highly beneficial.

I'm working on this now. 'BPMedianD.flt' brings at least 4 out of 5, but with too
many numbers. For a 5/30, it brings 20 to 25 numbers. I've been trying to
develope filters that predict numbers that rarely show. So far, I have two filters
that look promising. Backtesting is very useful. Once I feel confident with
this method, I'll start on 5/43 CASH5. The filters will need some adjustments,
but the method is still very valid.

-BP

 

[Springbok]

Kunjani Patrick

I am having great fun in filter construction and experimenting. I am into pairs. Think of Saliu's dictum that a number repeats more often if its last 2 skips are equal or less than its median. Try current skip = 0 and skip(1) <= 2. Randomly pick 3 pairs which have different numbers and check and see when they hit. I am using the 7/49 game here.
The more I use this programme the more I realise how brilliant it is especially how easy it is to modify it to test ideas. Testing the idea of picking 3 pairs this morning gave me all 3 pairs in the next draw. OK you wont do this all the time but it makes you think.

 

[Patrick123]

Bonjour Springbok

Is it possible to have the facility of not including numbers when trips and pairs are generated. At the moment the full monty is given for each of those. The ability to exclude certain numbers would be highly beneficial.

I have been a bit tied up with month end issues at clients, so I've got a bit of catching up to do.

I've release WinnaLotto - 3 July 2008 - Build 1.

Essentially it adds in a 'Reverse Filter' check box on the 'Drawing Analysis' screen. When checked, it will exclude the numbers in the filter edit that's usually used for the Alpha, Zulu, etc lists.

The numbers can be next to each other or below each other, thus

1 2 3
and
1
2
3

are essentially the same, ALL balls, pairs & trips containing these numbers will be excluded.

Regards
Patrick

 

[Springbok]

Howzit Patrick

Great work! It is plum crazy to work the 6 or 7/49 game using all 49 numbers. Any idiot can delete 5 or more numbers and play it as a 44 number game or even less. A sharp eyed operator can often detect when a decade has overstayed its welcome and knock out 10 numbers one go. Work tends to be a nuisance especially when there are more important things to do To me a 2 day work week and a 5 day weekend would be ideal

 

[ganbatte]

Hi Patrick

I have been using WinnaLotto for a while now and totally agree with Springbok that it's brilliant in its versatility in testing and hopefully successfully using various filters/queries.

Would you be able to provide more information on your “mytesting” filter that you included a while back, especially the “span” and “same” functions.

I have noticed that the span results differ in the same filter after clicking ReCalc. I have also noticed that ExceedSkips(3), (4), etc. also sometimes differ when placed in different position within the same filter (eg. end vs middle).

 

[Patrick123]

Hi ganbatte,

Here is the details from the original Sangoma-number divination thread:
http://www.lotto649.ws/lotto-tips-strategies/8749-sangoma-number-divination-31.html

Hi All,

I managed to squeeze some time in and have done the following:

Added in various variables:

span - as you defined it, the span of the skip cycles for the ball, i.e. the number of skip cycles the ball has in its statistics.
same(X) - the count of the number of same as current skip cycles for the ball.
samehigh(X) - the count of the same as current + higher skip cycles for the ball.
less(X) - the count of the skip cycles lower than current skip cycle.
NumDraws - The number of draws that were loaded/analysed.

gspan
gsame(X)
gsamehigh(X)
gless(X)

The g prefix means the global value for the singles/pairs/trips.

X can be the column value (#5 for the 5th column), a valid value (7 the value seven) or possibly another function.
I'm using a recursive routine here so very likely gspan(skip(#3)) would work, but I have not tested it yet.

skip(X) will work as well. A slight difference though skip(0) will return the current skip cycle value, skip(1) will return the next skip value in the skip cycle and so forth.

If you try and return a value higher than the last skip cycle i.e. skip(35) when there are only 20 skip cycles in history, a value of 255 will be returned.

A division by zero will also result in a value of 255.

I reduce all to lowercase so it should not be CAPS-sensitive.

I hope this makes sense

Take Note:
Where I had defined columns #51 to # 60 to cover skip cycles 6 to 15, this will most likely be deprecated.

Regards
Patrick
Reply With Quote

At this stage, I've moved the span column & the ExceedSkips around, hit recalc & still get the same results. If I could ask you to give me an EXACT procedure how to duplicate the problem, I can then sort it out.

Thanks for the vote of confidence, I'm sure the program's just going to get better & better for all of us.

Regards
Patrick

 

[ganbatte]

Hi Patrick

Thanks for the info. I will look at replicating it while I'm backtesting filters for the 20 mil on Saturday.

 

[ganbatte]

Hi Patrick

Is there a way of retaining favourite/key numbers when purging?

 

[HalfBee]

Patrick,

Am a recent follower of this (and the other Sangoma threads) I'd like to suggest a program addition:

Could you have it remember the last settings used on the load draws screen? Everytime I need to reset it to a 39 number by 5 ball screen or whatever.

I reload the same type of game over and over and it should remember what my current lotto settings are for the game I'm working on.

Keep up the great work...

 

[black prince]

Patrick123

Patrick,

Can Winnalotto use a configuration ini file to hold settings that remain when starting
this program. The fields 'Number Balls:', 'Balls in Draw', 'No Key Field' and
'No Date Field' could be fixed by editing a config.ini file.

I have been backtesting quite a bit and wondered if the 'Drawing Analysis' screen
using 'Filter Evaluation' could take a filter and do two things. Produce the results
for say Balls starting from say 30 past draws. Produce it's results for draw 30 and then
test this against draw 29. Then test results for Balls using draw 29 and test this
against 28 and repeat this process until it gets to draw 1. A count is kept as to
how many hits were made during this process. This may be complicated to program, but
would speed up the process greatly. I hope I explained this clearly, but if not
please let me know.

Thanks

-BP

 

[Patrick123]

Hi Everyone,

Ganbatte, very likely I'll be adding in this feature.

HalfBee & Black Prince, I'll add in a configuration ini file, been wanting to do it just been lazy.

As what you explained BP, that is exactly what the program does, you load the history files for the past 30 draws, load your required filter and click filter evaluation, it compares the filter over a 4 draw period.

Regards
Patrick

 

[ganbatte]

Hi Patrick

I found out what happened when I was running the span function.

I have been backtesting over so many draws that I sometimes forget to reload the column filter or press recalc after loading the new data which gives very interesting results

Just out of interest sake, what results would Winnalotto display in the above senario where new data, skipping previous 1, is loaded and trips or pairs are clicked using the same column filter?

 

[Patrick123]

Hi ganbatte,

The next release, will do the re-calc on loading new data, I actually thought that I had done that already

When new data gets loaded, the lotto 'object' get released then re-created from scratch, as it's position in memory might not be where the old object was, whatever bits of old information that was in that spot gets returned, so it's basically random data.

Regards
Patrick