1) Track 12 spins (Base cycle).
2) Take note of any formed Zone-4 on the Street-wheel + any formed square on the Street-felt.
3) From spin #13 to #24 (Paired cycle), bet on any street that would form any of the previously realized Zone-4 or Square formation.

---

Halt betting on any win or break even.

Since it's a cycle-Pairing method, the bets evolve with the game, progressively.

BetSoftware Proprietary GRATIS

Has Dozen/Column Lw Tracker.

Thread for downloads announcements.

Main space at: http://betselection.cc/betsoftware/

If you continue betting then the new cycle always pairs with immediate former one:


Spins 38-74: collection.


Spins 75-111: bet for any number which completes a full corner as seen in immediate previous cycle (38-74).


Same concept goes for streets, splits, etc.

Straightforward methodology:

Cycles are considered in couples/pairs.

First cycle = collection.

Second cycle = bet for recurrent patterns.

---

Example: "FULL SQUARE IN FELT":

Spins 1-37: collection cycle.

Spins 38-74: bet every possible number which could complete a realized full square as seen on previous cycle.

Quote from: Xander on June 07, 2014, 04:31:06 PM
On a more serious note, there are plenty of people on various math and physics forum, like myself, that could teach and mentor you on roulette and basic probability

Xander, would you like to have a section dedicated to the concepts of statistics and probabilities?

Not to mention serving as an ordered place for the fellows to point to and be directed towards when dealing with those very matching topics which recurrently appear. A quality model with your brand.

...How about naming it "Xander's Cookies"? --You know, because of the cookies & BIAS folk-minted relationship

It would be really great to have you in command of an open educational space about roulette's math.

Cheers!

Thanks for participating GG, it makes a good point too.


Please remember in roulette (as well as for any independent-trials game) everything is officially labelled as not useful, since it is the exact same thing as long as it doesn't beat the house edge.


Kindly take everything published in the forum with this in mind. We're mostly doing this with the simple aim of sharing observations without claiming we have the final universal answer to roulette (because we don't!  )


Cheers!

Glad you liked it Seykid!

A little bit more on triggers and filters:

http://betselection.cc/article-development/(draft)-triggers-and-filters/

Vic

Quote from: wannawin on June 01, 2014, 11:17:29 AMA library of systems for study

Hello again dear Walter.

Enjoy your new space: http://betselection.cc/wannawin's-library/

[smiley]cps/handshake.gif[/smiley]

Thanks for the appreciation dear friend, this is a true community effort.

In the honor of truth, we aren't even at 10% of the finished product. We still have plenty to offer [smiley]cps/clapping.gif[/smiley]

It's a very happy opportunity for all of us to be here; I truly love being part of this & every like-minded soul is welcome [smiley]cps/heart.gif[/smiley]

Vic

Independent-trial games poll here: are there better or worse methods?

Can we say we have a better system than the next guy / bettor?

...surely every one of us has an opinion regarding this; so... what's yours?

(Feel free to elaborate about your side / opinion at length - So we all can contrast and make the most from the discussion from this interesting -and fundamental- topic).

Nice to hear these news Walter.

Let me check if we can get the exact betselection.cc/wannawin URL back without much problem.

Welcome back to the blogging fray [smiley]afb/tup.gif[/smiley]

Target for vMTK is to be the "catch-all" toolkit for our programming languages. These are the points we have in mind:

It defines a cross-platform standard for widgets and core functionality which utilizes native implementations for each platform.

It allows similar widgets to spawn among platforms with matching capabilities, with no extra effort.

When targeting a single platform, vMTK allows full use of that platform's capacities, keeping track of available features and advising about limitations when a port is attempted to a new platform.

Languages using vMTK for graphical user interface are future-proof. While the underlying native implementation changes, vMTK aims to be as backwards-compatible as possible. i.e. A button is a button in windows 3.11 and windows 9. While the native implementation changes in the target platform, the matching vMTK standard for a button remains the same, which means there is stability across years for the programmer using vMTK.

Quote from: ezmark on May 30, 2014, 01:02:46 AM
yep that's me.

haha, LOVE it!


Congrats EZ [smiley]blacy/blacy-victory.png[/smiley]

Quote from: wannawin on May 23, 2014, 03:53:48 PMSorry, it is hopeless. I tried with various programming languages

Walter, can you please elaborate more on the languages you tried?


It is interesting to know what puts people off from general-purpose programming.


I have various theories which I would like to contrast.