Distance Tracker w/ Pattern Definition

[Kon-Fu-Sed]

KFS' Distance Tracker - the "Define Pattern" version


NOTE!
If you are not familiar with my regular Distance Tracker, I strongly suggest that you read all about it here:
nolinks://vlsroulette.com/other-software-for-roulette/kfs%27-distance-tracker/
... as this thread will only show the differences.


Also NOTE!
Although this tracker WILL show when your pattern triggers a bet THIS IS AN ANALYZING SOFTWARE - not a SYSTEM.
Therefore it will only show the next DISTANCES to check ("bet") but NO NUMBERS and ONLY WHEN IT TRIGGERS (no re-bets on a miss f ex).



THIS VERSION CANNOT BE USED for one-directional wheels!


The zip-archive (four files) is found in the MEMBERS download area - name dtdefpat.zip
Unzip and open dtdp10.html in your browser.



WHAT'S THIS "DP" VERSION?

I need a tool that is able to find patterns that I define. Like the one I used for the first "experiment".
The problem with that one is that the pattern is static - I have to re-write the program if I want to check another pattern.
In this version of the tracker it is possible to define close to any pattern and the software will look for it.


So - what's a "pattern" - in this context?

Suppose that you find a lot of CW results similar to these:

[attachimg=#1]

Look at the relations between the first and the second distances:
Ex 1: From +9 to +7 - that's -2 for the second value.
Ex 2: From +2 to +2 - that's +-0 for the second value.
Ex 3: From -5 to -2 - that's +3 for the second value.
Ex 4: From +8 to +11 - that's +3 for the second value.
Ex 5: From -14 to -14 - that's +-0 for the second value.

So you have a span here from +3 to -2 for the relation between the first and the second distances.
OK?


Now, look at the relations between the second and third distances:
Ex 1: From +7 to +6 - that's -1 for the third value.
Ex 2: From +2 to +3 - that's +1 for the third value.
Ex 3: From -2 to +-0 - thart's +2 for the third value.
Ex 4: From +11 to +11 - that's +-0 for the third value.
Ex 5: From -14 to -17 - that's -3 for the third value.

So the span for the relations between the second and third values are +2 to -3 in these examples.


And finally, let's look at the relations between the third and the fourth distances:
Ex 1: From +6 to +8 - that's +2 for the fourth value.
Ex 2: From +3 to +3 - that's +-0 for the fourth value.
Ex 3: From +-0 to +-0 - that's +-0 for the fourth value.
Ex 4: From +11 to +12 - that's +1 for the fourth value.
Ex 5: From -17 to +18 - that's -2 for the fourth value,

Regarding Ex 5: From -17 to +18 are two steps ClockWise (left to right).
Going "left to right" in the ClockWise results means minus - compare to the index / header:

[attachimg=#2]

So; two steps left to right = -2.

OK?

And the span for the relations between the third and the fourth distances are +2 to -2.


Now we can define this pattern in the tracker.
In the next post...

/KFS

[Kon-Fu-Sed]

In the previous post we found the relation-spans for the four distances that makes up the selected pattern.

The span for the first/second distances was +3 to -2.
The span for the second/third distances was +2 to -3.
The span for the third/fourth distances was +2 to -2.


Now, fire up the file "dtdp10.html" in your browser.

This is the interface:

[attachimg=#1]

As you can see it's THREE parts:
The "Definition interface" is fully visible at the top. Use it to define your patterns.
The "Ordinary interface" is only partially visible. This is the ordinary Distance Tracker.
Make it visible by dragging the upper separator bar upwards.
The "Output window" at the bottom. All results will be output here.


In the FROM and TO boxes for "Relation DIST 1 / DIST 2" you enter the two values of the span: From = +3 and To = -2.
[attachimg=#2]

For the second relation, you select the option "Relation DIST 2 / DIST 3" as it was this relation we investigated.
The other option is used if your relation is based on the first distance instead of, as in this case, it is based on the second.

In the FROM and TO boxes you enter the two values of the span: From = +2 and To = -3.

Do NOT select the radio button "BET Dist 3" as we have a four-level pattern and we will "bet" the fourth.
This option is for THREE-LEVEL patterns - simply don't bother with the next level if you use it...
[attachimg=#3]

For the third relation, you select the option "Relation DIST 3 / DIST 4" as it was this relation we investigated.
The other options are used if your relation is based on the first or the second distance instead of, as in this case, it is based on the third.

In the FROM and TO boxes you enter the two values of the span: From = +2 and To = -2

Also SELECT the option "BET Dist 4" as this is the last distance in our pattern and thus is the span to "bet".
[attachimg=#4]

Your CW pattern is defined.
The tracker is ready to look for ALL distances that have the TWO FIRST relations, and place a note of what distances to "bet", in the output, according to the third relation.

Now you simply "drag" the top separator bar upwards to reveal the ordinary DT interface - except the check-box for one-directional spins that is gone.
This version handles ONLY BI-DIRECTIONAL results.

Suppose you input all of the spins for February 28, 2008, from the Wiesbaden table #8, you will find:

[attachimg=#5]

* ND -4 to -8

The first relation is, as you can see, the relation between -4 and -5 = -1 and the first relation is found.
The second relation is -5 to -6 = -1 and also the second relation is found.
So the * Next CW Distances to check are -4, -5, -6, -7 and -8.

Measured from the NEXT (CC) RELEASE-NUMBER!


The next distance is +15 and it was not within +2 to -2 from the previous distance (-6) and so we missed.
The fifth distance is +18 and we again have a first relation - this time +3.
The sixth distance is -18 and as the relation between the previous and this distance is +1 the second relation is found.
From +18 to -18 is one step "right to left" and thus PLUS one - right?

(As you understand it is important to look for "wrap-around" - as in this case - because -18 and +18 are in reality neighbours. OK?)


* ND +18 to +17 AND -16 to -18

So the * Next CW Distances to check are +18, +17, -16, -17 and -18. Again:

Measured from the NEXT (CC) RELEASE-NUMBER!


More to come...
KFS

[Kon-Fu-Sed]

How to define "wrap-around" patterns

The "normal" CW pattern is defined by a HIGHER value in the FROM input-box and a LOWER value in the TO input-box.
(The opposite for CC patterns - more on this later)

For example this:

[attachimg=#1]

will cover these distances (supposing measuring from "V" or +-0):

[attachimg=#2]

When you want to define a pattern that "wraps around" the edges (+18 and -18) you enter the values in OPPOSITE ORDER:
[attachimg=#3]

will cover these distances (again supposing measuring from "V" or +-0):

[attachimg=#4]

Rule-of-thumb:
You always go LEFT to RIGHT from the value in the FROM-box - also if you pass -18 (+18 in CC results).


And Regarding CC-results:

As the wheel and ball both travel in the opposite direction compared to CW results, you have to ALWAYS replace "-" by "+" and vv.
Compare the subscripts below the input boxes for definition values.
And also compare the headers in the output.

When you enter higher values in the "FROM" box for CW results you enter LOWER values in the FROM input box and HIGHER values in the TO box. Exactly the opposite.

'Got that?
All CC values are NEGATIVE of the corresponding CW values.



And some more stuff:


There's a new RESET-button in the "ordinary" (input) interface:
[attachimg=#5]

"P RESET" is short for "PARTIAL RESET".
Clicking this button will reset this (the "ordinary") interface and the output window.

It will NOT reset the "Definition interface"!


There are TWO reset-buttons in the "Definition interface".

This one:
[attachimg=#6]

works exactly as the "P RESET" in the "ordinary interface".

This one:
[attachimg=#7]

will reset EVERYTHING.
Use this button - NOT your browser's "Re-load" function.



When you use the AUTOMATIC INPUT - processing a sequence - you can now run it, change the definition settings and IMMEDIATELY re-run the sequence.
There is NO NEED to reset anything in these cases.



I think that's all.

Please report errors. TIA.

And have fun!
KFS


"All" that's needed now is a software to SELECT those patterns...

[Kingpin]

Truly GREAT work as usual 

I can't wait to try it out tomorrow, when i have time.
I will also try to collect some more spins from DB to test with.

THANKS!

Kingpin

[Kingpin]

Hi,
Sorry for not replying earlier, but i haven't had time to try this out yet.
But rest asured that it's not because i've given up on this rock-solid idea 
Just dont have the time at the moment thats all.

BR
Kingpin

[Kon-Fu-Sed]

Hi Kingpin,

No worries man!

Myself, I'm waiting for the second build of a "pattern selecting" software I have designed and my friend Peter writes.
(This is a compiled, stand-alone app - no JavaScript; it's too much work)
It selects the most found patterns that can be defined in the tracker.
The plan is to feed this software with data for ... say, one day ... then define it in the tracker to use the next day, f ex.
I will probably have it tomorrow for testing during the weekend.
(And so maybe I will be too busy to post here )

Best regards,
KFS

[Kingpin]

Ok mate sounds good.
Good luck with it.
Looking forward to hear more about it 

BR
Kingpin

[Kingpin]

-