Degree of tilt - scatter overlaps visual chart simulation ...

[ego]

-

I speak to X about a simulation software that chart scatter overlaps using 2 and 3 pin game.
I want to code this with my personal programmer - but don’t know how the output should be - the charting method to get a good visual.

Guess what.
X has already develop this software and will release it soon - that is great news.
I don’t know the details as i still have dialogue with X and hope more information will get out that way.

First of all scatter overlaps manifest during specific rotor speeds - i know that after collecting some data about the subject.
Also after some discussion with some rare and really experience players.

The question that strike is the following.
1) Should i take only the distance/yardage from visual read and outcome with specific rotor speeds.
2) Or should i take where the ball strike deflector with distance/yardage with outcome with specific rotor speeds.

Then it boils down to how you would chart the method using different signs or colours wish would indicate that different deflectors donate into the same high probability area.
I like the idea of simple solutions.

One output file could look like this ...

-18
-17
-16
-15
-14
-13
-12
-11
-10
-9
-8
-7
-6
-5
-4
-3
-2
-1
0
+1
+2
+3
+4
+5
+6
+7
+8
+9
+10
+11
+12
+13
+14
+15
+16
+17
+18

Then the original way we would use X to mark the ball jumps using 1 pin game.
Where 0 stand for our visual read - that way we get distance/yardage ...


-18
-17
-16
-15
-14
-13
-12
-11
-10
-9
-8
-7 x
-6
-5
-4
-3 xx
-2
-1 x
0
+1
+2 xxx
+3 x
+4 x
+5 xx
+6
+7
+8
+9
+10
+11
+12
+13
+14
+15
+16
+17
+18

Now if we use a 2 or 3 pin game we should chart in the same way but using XYZ witch would indicate scatter or ball jumps from 2 or 3 different strike points ...


-18
-17
-16
-15
-14
-13
-12
-11 X
-10 X
-9
-8
-7 Z
-6
-5
-4
-3
-2 XXZ
-1
0
+1
+2
+3 XY
+4 X
+5 YY
+6
+7
+8 Z
+9 Z
+10
+11
+12
+13
+14
+15
+16
+17
+18

Personal i think it would be effective but not as good as visual ...
My self thinking about solutions witch is horizontal witch i think give a more acc visual about the subject.


                         y                y             
            x           x               x   z     y x
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 ...

One other alternative would be using round dots in different colours ...

Use a simulation software for scatter overlaps would pin point out witch rotor speeds and ball jumps create peaks and overlaps.
That would manfiest into witch octans or high probability areas to place our bets with specific conditions.

Using this simulation software with Laurance Scotts Roulette Analyzer will be a killer to make valid playing models to follow.

[ego]

The alternativ for the input of data - witch should it be ...

1) Rotor speed, Visual read, Witch deflector strike and number below it, Outcome ...
2) Rotor speed, Visual read, Outcome ...
3) Rotor speed, Strike deflector and number below, Outcome ...

Easy or complex solution ...

I need some input from our members here before i get the code done by my programmer ...

[ego]

I know how to chart the method using The Rotating Flexibiltiy Cross with pen and not pad.
I only record rotor speed and 4 numbers witch divide the wheel into 12 to 8 octans.
Then you just mark the octan with a circel or a straight line next to it and peaks emerge.
This with out using the traditional way of getting offset as the rotating cross adjust to any existing distance by it self.

But to compute the topic is a different story.

[ego]

Why would i need to record witch deflector hit - no need to do that.

Lets say i only use one particular rotor speed and main/focus pin at 3 a clock.
Rotor is moving ccw and ball cw then the two previous deflectors from 3 a clock will donate there ball jumps into the same direction.
Then i could use only visual read at main/focus reference deflector and take distance/yardage with final outcome.
We could chart the method using 12 to 8 octanes and see clear where the scatter overlaps manifest.

Lets say the visual read is 0 and main reference deflector.
Then the bi-modal sector is 6 and the line between them to get a cross or the four angel split is 3 and 9.

So my visual read is 0 3 6 9.
Next to 0 is 11 and 1 next to 3 is 2 and 4 next to 6 is 5 and 7 next to 9 is 8 and 10.

That means i list only four numbers and divide the wheel into 12 octans.
Now i only have to make mark or sign where the ball end up from my visual read.

0 3 6] 9

The outcome end up next to 6 witch is octan 7.

Then when you play you just list 4 numbers noting more ...

0 3 6] 9
2 5 [8 11
8 11 2 8]
3 6 9] 0

Then it becomes clear to follow the mark or signs where the ball end up using multi drop zone.
If there is peaks that manifest - scatter overlaps using this specific speed - then does will become very clear using this charting method.

Above we can see that the ball jumps manifest around the third number/octan using The Rotating Flexibility Cross - when we looking at the marks where the final outcome end up.
This way you don't need to calculate offset/distance the traditional way.

This is The Rotating Flexibility Cross.
No need to chart any thing else then rotor speed + 4 numbers.
That way you chart offset with out calculation of distance as it becomes self explanatory using the chart method using marks where the ball final end up.
You see a clear visual using 12 octanes where the ball end up and you get a clear visual where the scatter peaks emerge no matter degree of tilt or multi drop zone.

Conclusion is when we observe and play static rotor speeds - same speed.
We only need to chart the visual read and outcome using The Rotating Flexibility Cross.

Each new visual read creates a new cross - but the cross divide the wheel in the same static way each time - being rotating.
The four angel splits or four angel bi-modal effect divide the wheel into 12 octanes.
Charting with only 4 numbers that indicate the cross witch make calculating distance UN-nessery.
The marks or sign indicate the final outcome and if they do or not manifest into the same high probability area.

This is my private invention and solution to deal with multi drop zone and in the same time be simple but complex solution.

[ego]

[ego]

-

People forget the basic skills witch we can advance from.
The methodology of The Rotating Flexibility Cross comes from how you master or learn how to deal with the wheel layout.

Master the wheel for beginners.

When it comes towards visual ballistic or being into some kind of wheel signature - then the first basic lesson is to learn the wheel layout - the numbers order on the wheel witch is not the same as the table layout.
I also reckon that roulette system player would be better of master this basic skill.

Second some one should learn the basic to tell witch distance numbers has - witch might sound complicated - but is very easy basic skill.
It takes two to four weeks to master the wheel as i mention above using my basic solution.

To learn the wheel at the first level has a learning curve witch is static witch make it more easy.
After master this first level some one will gain experience and all numbers will float together.
This way some one can tell neighbours from any number or distance.

First we divide the wheel into sectors of three - where the first sector include zero and has four numbers - that is the only exception.
It is a great feeling to know everything in a split second with out using any card or pen and paper.

This is clockwise direction.

0. 26 0 32 15
1. 19 4 21
2. 2 25 17
3. 34 6 27
4. 13 36 11
5. 30 8 23
6. 10 5 24
7. 16 33 1
8. 20 14 31
9. 9 22 18
10. 29 7 28
11. 12 35 3

After you learn each sector in clockwise direction you will also learn the each sectors index number from 0 to 11 so you know witch numbers belong to witch group.
Then come one other useful basic skill to learn opposite or triangular or four Angel splits.

This is the opposite sectors using the index numbers.

0-6
1-7
2-8
3-9
4-10
5-11

Using triangular or four Angel splits you just move two sectors forward in same direction.

0-3-6-9
1-4-7-10

When it comes to distance you just know after mastering opposite, triangular and four angel splits how to move forward using the numbers.
After experience you will also at this level know how to reduce or add plus or minus one pocket in each sector - that is how you can measuring the exact distance between two numbers.
Witch will become a natural reflex with in a split second.
Index numbers to get the raw distance between two outcomes - then add or reduce plus or minus one pocket.

Personaly in the past i memorize one new sector each day and after i master them all in clockwise direction i memorize them anti clockwise direction.
Then when that was clear as water for me i memorize each sectors index number and memorize oppiste, triangual and four angual effect.
And at last i learn how to master distance.

Today i know all numbers by heart with split secound and same goes for distance.

That is what should teach beginners ...

This make it very clear how the four charting numbers create a rotating flexibility cross - four angel split with bi-modal effect.







It does not matter what position the rotor has below our main focus pin or reference deflector.
The Rotating Flexibility cross will always has the same position with 12 octanes.
And we only have to chart 4 numbers to maintain The Rotating Flexibility Cross.
Distance/Yardage becomes self explanatory with out the need to calculate offset.
Our marks indicate every individual octane and if peaks or scatter overlaps manifest.
We would only chart wheels where 7 to 8 hits of 2 to 3 pin game manifest.
Using the correct main focus pin or reference deflector depending on cw or ccw direction.

Cheers

[Steve]

Ego, the overlap you're talking about is considering only intersection points and targets specific rotor speed. It is more than enough for some wheels, but on others even slight rotor speed variations make a huge difference to scatter. A typical rotor, diamond hit and ball combination will have scatter vs rotor speed like:

2-2.5s/rev: scatter difference linear enough, but difference of 6 pockets between 2 and 2.5s/rev. On a simplistic scatter chart, this will look like a "broad peak" when it is really much narrower if rotor speed is considered.

2.6 - 3.0: scatter very predictable, with 1 pocket difference between 2.6 and 3.0s/rev. But you may find this is 20% or less of spins.

3.1 - 4.5: scatter getting progressively worse and less predictable with non-linear relationship

4.6 - 5.0 scatter varying again with close to linear relationship

5.1+ scatter getting progressively worse and less predictable with non-linear relationship

If you take yardage, you'll have more data than you need for vb. You need to develop a map of the relationship between the dominant diamond scatter, and scatter from other diamonds. This is without consideration to rotor speed. And if you target a specific rotor speed, you need enough of those speeds for the analysis to be viable.

It can be done, but a much better way is to take all available data from all spins, and CORRELATE IT. For example, determine what happens if one diamond is hit, and another scatter results, but the rotor speed is X. No data should be discarded. Every spin tells you something useful.

For this you need software. My auto software for my players does all of this with click of a button.. overlaps, rotor speeds, diamond hits and more, automatically. I don't mean to dangle a carrot but you are on the right path and I want to help you, but most of my players aren't even told what my auto analysis software does. It was designed to make complex analysis literally as simple and easy as possible. Speaking of the correlation of data, there are literally billions of calculations done for an analysis for about 1500 spins. For 300 spins, the analysis server takes about 30 seconds to complete analysis and its a very fast server. There are about 105 billion calculations for each analysis. If you see my blog you can see the server has trouble coping. My point is doing it properly cannot be done manually. I know you are developing software but you need to consider much more than overlaps at least to take full advantage of what is possible. The only thing my auto software doesn't do yet is automatically tell players the approximate edge with variable combinations. It does it manually, but the actual analysis part is completely automatic when to replicate it cannot be done manually even in years.

If you just want basic overlaps, chart the dominant diamond hits and other diamonds, then draw median lines for each, then correlate them. This will take some observations of which number is where at critical times. On the chart, where they intersect is where the values are the same. Parts where the average of both lines are above a horizontal median line are where you bet.

Also Laurence Scott's software does basic correlation charts (I call them primordial charts) with segregation. A manual segregation approach like this and what you describe is a very painful way to do it, and still it doesn't do the job fully. It sure makes it easier if rotor speed is very consistent, but most wheels will vary between 3-5s which is really quite a difference. And you will find some dealers plain make you lose. The rotor can look same speed, but even 0.5s / rev difference can shift peaks, or even move to a rotor speed where you then get two peaks instead of 1 because some spins are chopped by the frets, and some are rollers. But it may only happen on a knife-edge between two very similar rotor speeds.

The other option is use a roulette computer that saves all the data for each spin, then gives you the best prediction possible. I don't sell anything anymore so it doesn't matter, but my uber and hybrid computers do this.  If you use a typical computer, it is no different to vb.

Also other than the roulette computers, I have phone software that collects the data you mentioned and more, and soon it will be capable of uploading data to the analysis server so the player doesn't even need to leave the table, and the player is told via gsm mobile network where to bet. But that is for predictions before ball release. For now my players use it only to collect data without pen and paper. I'm not a fan of vb though because I fee if you bet late and reveal this behavior, you may as well use a computer. Betting before ball release is much more covert and I find more profitable than vb for many reasons, even if vb may seem to be a more logical approach at least in the home environment.

[ego]

Thanks for elaborating about the subject - even if you don't revile so much.
But i find my own solutions and don't agree to everything you say.

You pin point out the "Sweet" speed and not play various of speeds with rotor change.
Then you mark and sign the outcomes using The Rotating Flexibility Cross and all peaks and overlaps will manifest visually with 12 octanes.
That is using note pad with pen charting only four numbers with out using any complex or advance simulation software - that is for me very clever and spot on solution.
Works with 2 and 3 pin games where they hit ratio is 7 to 9 out of 10.
Ball cw and rotor ccw and the previous deflector from main focus pin donate there ball jumps in the same direction where the high probability area is.

[Steve]

as I said the approach increases edge, and if its all you need, thats good. But I'm just saying it is not enough for many wheels, and much more is often needed. Either way I always advise people to find a balance between what is required, and what is practical. So you need to keep it as simple as possible without sacrificing too much accuracy. so if it is doing well for you, no need to change it.