Our members are dedicated to PASSION and PURPOSE without drama!

Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - VLS

#616
General Discussion / MOVED: I miss albalaha
January 28, 2014, 03:06:17 AM
#617
Off-topic / Re: I miss albalaha
January 27, 2014, 10:17:58 PM
Quote from: Bayes on January 27, 2014, 04:04:39 PMI'm asking you politely to remove your signature and email address.

Via media here:

Signature MSG removed, but contact email kept (Since just an email link by itself doesn't convey anything else than, well, an email address --I have mine in my signature too, for instance).

Cheers.
Vic
#618
Dozen/Column / Re: Steady Dozen/Column
January 27, 2014, 04:07:44 PM
Quote from: Sputnik on January 27, 2014, 02:52:47 PMI made a short test and notice that you sometimes can get two dozen to qualify three times in a row.
Do you skip does triggers or just pick random one of does two dozen ?

"Look back" in the spins for the current strongest one to resolve it. Since the whole point is we're following a certain path in the stream I don't recommend "just random". Better to wait for some more cycles, until a stronger one (even if by only one cycle) is bound to show.

Obviously not every session is a winner, but it does tend to go down somewhat smoother than blind betting, at least in my own tests. Remember this is more in line with a "betting principle".

It is also worth that the worst times are clearly spotted in this methodology, in order to make informed decision, when in-game.
#619
Dozen/Column / Re: Steady Dozen/Column
January 27, 2014, 05:17:00 AM
Yes I talked about it here too: http://betselection.cc/meta-selection-105/steady-locations-concept/

It's worthy to note the "many timelines" at once concept hasn't been discussed, and it's quite an interesting one as you see it realized with this steady locations approach.
#620
 :o ! Excuse the Newsbot, it has a lot of catch-up to do (a.k.a old-o-bot for a while :upsidedown: )
#621
Dozen/Column / Re: Steady Dozen/Column
January 27, 2014, 05:04:37 AM
One last thing. It's up to each person's money management to decide when it's time to disable a dozen/column on a "holed" patch:


X
-
X
-
X
-
X


Some money management schemes might surf that without a problem, but for those who don't it's not carved in stone to be stubborn and keep the active one to the end of the "pierced" episode, especially when there's a more consistent one raking it, in this (current) or another timeline (if being tracked).
#622
Dozen/Column / Re: Steady Dozen/Column
January 27, 2014, 04:04:15 AM
Quote from: TwoCatSam on January 27, 2014, 03:22:41 AM
So it is basically a reduction of volatility.

That's the main goal, yes  :nod:

There can be long chained "vertical strings" of enabled cycles with this methodology. The trick then goes more in line of not using progressions that lay all eggs in a single progression line, but those that rise smoothly. Bearing in mind that once the hit is obtained, the location is not bet for the rest for the cycle.

(By the way, ZERO is ignored, as in not accounted for in the 3-spins for the cycle. i.e. we take the loss if laying a bet but not count that zero as part of the three spins for the cycle)
#623
Dozen/Column / Re: Steady Dozen/Column
January 27, 2014, 02:11:42 AM
Since each line represents a 3-spin cycle, two misses equal six (6) consecutive spins without showing for the active location to be disabled.
#624
Dozen/Column / Re: Steady Dozen/Column
January 26, 2014, 10:12:36 PM
It doesn't beat the house edge flat betting, but can go very even:

[attachimg=1]

(Which if you know a bit of money management, would have caught your attention  ;) )
#625
Dozen/Column / Steady Dozen/Column
January 26, 2014, 09:57:27 PM
Straightforward method, single dozen/column bet:

Track the dozens/columns in 3-spin cycles.

1) Wait until one has been spun for three (3) consecutive cycles (enabling point).

2) Bet on it until it has missed two consecutive cycles (disabling point)

3) Go back to step one.




123
-xx
xxx
xx- <- Spun 3 consecutive cycles = Enabling point for Dozen #2
-xx
xx-
-x-
x-x
xx-
xxx
-xx
xxx
x--
-xx
-x-
xx-
x--
--x <- Missed 2 cycles = Disabling point for dozen #2
xxx
x-x <- Spun 3 consecutive cycles = Enabling point for Dozen #3
xx-
-xx
#626
Hi mate, welcome to the forum.

All of these modules are being superseded (slowly, one by one) by our BetSoftware:

http://betselection.cc/betsoftware

Hope to see you active over those sections!  :thumbsup:

Cheers!
Vic
#627
BetSoftware is GPL'd.





Viva la libertad! / Long live freedom! :applause:

Vic
#628
General Discussion / Re: Small BV sofware
January 24, 2014, 12:21:14 AM
Well, it's merely an comparison with previously captured images (i.e. images for 0,1,2,3,4,5,6,7,8,9 + point) and translating them to an integer plus decimal.

My advice is for you to try to get somebody with experience in creating optical readers. I have absolutely no problem in assisting someone who wants to help you if him/her is stuck with the coding, but I just can't commit to another new project until I'm clear of what I have on my plate.

Hint: don't pay for it!

There are many documented ways online to capture the screen, i.e.

http://www.codeproject.com/Articles/5051/Various-methods-for-capturing-the-screen#Capture%20It%20the%20GDI%20way

And even more ways to match images, from simple pixel to pixel comparison to SIFT:

http://www.codeproject.com/Articles/5051/Various-methods-for-capturing-the-screen#Capture%20It%20the%20GDI%20way

Another easy approach would be to let a free and proven OCR do all the recognition job. i.e. Tesseract OCR:

https://code.google.com/p/tesseract-ocr/
#629
Usage support / Re: Trying the 'inner forum'
January 21, 2014, 10:38:18 PM
It's "alive"  :applause:
#630
Quote from: esoito on January 20, 2014, 02:43:28 AM[The Powers of Coding Darkness]

I'm no doctor, but this sure feels like opening up an organism and handling its entrails. Creating something right inside another live project is indeed "gory", in its own coding way...  ^-^