Quote from: spike on November 28, 2012, 04:53:58 AM
But random outcomes don't follow any cycle you
can depend on.

Oh! You are certainly right: nobody can really DEPEND on something as long as it's random.

We use this splitting the game in cycles only as points of reference, in order to being able to help us visualize the flow of the game.

Guarantees? None.

Anybody who talks about a "guaranteed outcome" in a random scenario isn't really to be taken in a serious light. Random is and will continue to be by definition an scenario where we can't get a probability of 1 (absolute certainty); we can at most use  our frame of reference (whatever that be: system, method, belief, vodoo, etc.) in order to speculate.

Steady locations are those who are appearing once or more in consecutive cycles.


When you tabulate your data in cycles, you can see the steady locations of the sessions as those which CURRENTLY have the longest vertical lines, having showed consistently during the most amount of cycles.


Try tabulating your data this way and you'll see the steady locations show naturally in the game.


This is the number of spins per cycle you should use:


- Even chance: 2 spins
- Dozen/Column: 3 spins
- Double-street: 6 spins.
- Corner/quad: 9 spins.
- Street: 12 spins.
- Split: 18 spins.
- Single number: 36 spins.


Proper programs can help too.

I do think you can perfectly measure winning and losing streaks if you divide the game in CYCLES.

Cycle's spins matching the location's payout (including the wager; as in the "break even" point). i.e. a straight-up number has a 36-spin cycle, a double-street has a 6-spin one and so forth for the rest of the betting locations.

Under this light, you can measure winning and losing streaks by checking how many consecutive cycles has it shown.

...When accounting for large chunks of spins, even numbers with plenty of misses can appear to be "hot" given their raw number of shows, but when measuring things in cycles, you can rapidly determine what's "on" right now (in the current cycle) and also automatically can avoid what is currently non-appearing or cold.

I like it since it is a way to "morph with the game"; and in this game, it is better to learn to be dynamic. A cycle-oriented approach can be of assistance for this.

My 2c.

Regards.

1) A method is posted.

2) Tester is made.

3) We reach conclusions.

---

Ideally, we end up having a library of systems/methods to test

It is up to fellow members to discuss upon the methods and test them.

Coders in the community would ideally provide the programs for their analysis to be done (myself included).

We end up enjoying the process from the first posting of an idea to the conclusion after testing them, perhaps making some tweaks on the way, and some would even ed up playing the method if it suits them.

Well, that's how I think the site should work 

Quote from: Ralph on November 27, 2012, 08:17:22 PM
Shall I type it

Yes, it is more reliable to do it by hand.


Given it's only a tiny bit of forum code to get proper formatting, I'd say it's worth it 

OK, I just wanted to mention there's hope for GUT analysis in full.

The GUT is definitely a must-add for the framework I'm coding, but that's a "2013 project", which means it goes in between January and December...

---

As a fellow coder, I do support the notion of it being very generous from Normand to give this one away to the community. Thumbs up for it! 

(Plus a well-deserved THANK YOU )

Thank you dear friends for your kind and encouraging words. I'm humbled by them 

---

@wannawin

ClickMate is the public clicker I'm going to support, this one is a tracker only.

I'm going to release the full project with resources on 0.1 version (non-dev), so you could hire a fellow coder to extend it (or hire me!) to make it a full clicker.

What I can do for you is to give it the ability to copy splits to clipboard in ClickMate format, so you can have both programs open and get the functionality you want: tracker + clicker. At no cost.

How about using:

[code=javascript]
// Your code here
[/code]

It should format the block using javascript syntax highlighting... 

I'm rewording the "bridge" post, better to use "longest zone by gap" or something along those lines, since it conveys the message in a clearer way ... making some illustrative charts too...

Feel free to continue posting. I'll just edit the posts above and advice here

Quote from: Ralph on November 27, 2012, 05:27:11 PM
The script is not displayed correct, I pasted it but some is gone, like the index at betarr the is gone.

Dear Ralph, in order to avoid re-formatting enclose your code with a [code] tag.

The longest zone bridge

Wheel-based.

You start noting numbers then bet the "1-number hole" that would make the longest zone bridge.


{REWORDING IT}

Quote from: Bayes on November 27, 2012, 04:07:59 PM
Boring to play but can be very profitable.

That's the only thing that matters dear friend 

It's never boring to win!

The Matrix Filler

On a 6 x 6 matrix, bet the number that completes a 6-number straight line, in any direction.


Illustrative examples:


Vertical:


[attachimg=1]


Horizontal:


[attachimg=2]


Diagonal:


[attachimg=3]


[attachimg=4]

The latest repeater

"Look backwards" on every spin, until you spot the first number to repeat.

Bet this number while keeping the backwards-looking process.

When a new number repeats, switch the bet. 

The patient waker

Mark off every until only one number is left.

Wait (patiently) until this number shows.

Bet on it until a hit or 36 spins at most.