Pattern Breaker Edit & New Feature Request

[karmacoin]

Hey knowitnothing,

Good day to you.

I had a small request, one for a small feature edit as well as a new feature request. The

feature edit would be awesome. The new feature you coudl take a look at the idea and feel if it valuable enough. I felt it might make it give stronger swings.

Feature edit,

You had asked me this when I had asked you for multiple breaker pattern. I was thinking

of simultaneous detection. Simultaneous detection would mean when it is sending out

breaker bets if it detects another pattern, it follows the new pattern breaker settings, it

has to continue till the patterns are removed as per the last breaker hit. I have been playing with the bot. It is giving amazing results, But I am still scared to bring more money in unless I get a bit more comfortable.

New feature request. ( totally at your discretion )

I think this might be an interesting addition to the bot. This is a trigger condition for the

pattern breaker, it is based on gamblers fallacy. If a pattern is found, the breaker bets are

triggered only if the the below conditions are met.

Ideally it would be have the below options.

No: of bets to analyse : 100 Breaker trigger Loss % : 20

Just to clarify, in the above case......if a pattern breaker is hit, the breaker bets are

only sent out if, in the last 100 bets, 20 or a lesser number of losses have occured. If the

losses are close to 21 or greater...then it dosen't trigger the pattern breaker.

Please clairfy if you think this option is worthwhile. I felt it gives better swings. I tried it

manually only over a short range though.

I am on just-dice.com if you are hanging out there gimme a buzz.....

thanks & cheers, It would be awesome if you could do this. please everything at your discretion................

cheers karma

[karmacoin]

Hey,

FYI, I think that making the pattern breaker on simultaneous mode like you had mentioned earlier would be better. This I am sure would make the profit curves longer.

cheers

[knowitnothing]

Hello karmacoin, thanks for the suggestions once again.

Right now I'm in doubt if looking for pattern breakers inside pattern breakers is a good idea. If this is done, it also requires setting both depth and wide limit. The first one would restrict how many patterns inside another ones the bot should go for at max, the second one would limit how many to look for after the first one has been found but is still active. That is, supposes a pattern A is found and there are n bets to be placed there, pattern B is then activated to place m bets after i < n bets, then m bets are placed, after more 1 bet another pattern is found, and so on... it could take a much longer time to leave the initial pattern A than only its n bets.

The second idea is more doable without any especial considerations. I will look into that for the moment, if you have stronger considerations for the pattern into pattern idea, I might look at it later.

See you.

[karmacoin]

Hello Know'

Thanks for your reply. Regarding the simultaneous system, what I Imagined was more in the line that when for eg.

Pattern A is discovered, breaker bets are on, before they get over,Pattern C is hit, what happens then is from that point the Pattern A cancels and Pattern C breaker bets take over.......basically when a new pattern is hit while the breaker bets are on the new pattern settings take over and old pattern settings get killed.....sort like replacing rather than adding and complicating the code structure. I noticed that the pattern breaker given me nice profits like I imagined, but notice that a lot of loss patterns come together as bunches, those are the ones to avoid, now the system I mentioned above works fine in removing those long runs of approximately 32/68 loss/win streaks on an 80%, which could make all the difference.

I am not aware how it is coded, but I felt what I was looking for is different from what you have mentioned above, am I correct. So if it is easy then please take a look at it.

Also the second idea, is very relevant right now. If the pattern in pattern idea like I explained is difficult, please take your time as you feel.

As far as strategy_karmacoin.py is concerned. We are at the end. I can guarantee you that there is nothing more I can add to improve that strategy. That is the final layer. These two additions when done, we shall be done with the development of the strategy finally.

I have spent the last two days running the bot for almost 16+16 hours.........we are almost there. Once that is done I shall update the wiki with detailed info once the test runs are over. With all sort of patterns for various multipliers etc, with images from actual betting on site.

thanks so much for your continuing help. cheers karma

[karmacoin]

Just FYI, As far as number of patterns simultaneously being watched, I have never used more than 4 patterns. I on the average use only two patterns at a time. But according to my earlier explanation, we don't need depth as when the second is discovered, the first loses importance. More a series than a parallel if I am correct.

thanks again karma

[knowitnothing]

Your suggestion on how to handle the first situation is much simpler than I thought. I will look into it.

[karmacoin]

Hey Know'

Thank god its simpler. Cheers, take your time. The bot is chugging away nicely now....but like I said small bets only now, consistently doubled my capital, but losses also sometimes the usual game.

thanks karma

[karmacoin]

Hey Know'

Thanks a lot. Just going to give it a run right now.

cheers karma

[karmacoin]

Hey Know

The first edit is working as expected and perfect.

Thanks karma

[knowitnothing]

Just pushed the code for handling that other point.

As for the first point, observe that now a sequence of LLL (loss, loss, loss) will trigger the pattern LL twice. So if this pattern had 5 breaker bets, for example, 6 breaker bets would be placed in this situation.

[karmacoin]

Hey Know,

Thanks a lot. I am on it right now. The first commit I tested on a bot run for 5 hours and everything is fine. Just about to setup and use the second concept developed also. Will update you as it progresses. I think strategy_karmacoin.py is complete except for this final bit of testing.

cheers & thanks karma

[karmacoin]

Hello Know'

I have been testing, was having a small issue, funny thing is not always and only sometimes. When I start a run, it mostly runs fine, sometimes only it stops and spits out the message attached as an image. About 10 starts, it occurred only twice.

http://i.imgur.com/Bta1irL.jpg

thanks karma

[karmacoin]

Hello Know'

I tested on site direct and noticed that the above crash occurs when it hit a pattern.

cheers karma

[karmacoin]

Hello Know,

I am creating a detailed analysis and report spread over a 1000 rolls. It should place you well in checking for the problem. Please only look at it once I send you the report. finished the rolls, just analyzing it right now. Will update you

cheers karma

[knowitnothing]

Thanks for the report, I'm looking into it right now.

[knowitnothing]

Don't put too much effort into, I can manage to hit the bug too.

[karmacoin]

Hello Know,

Good you have fixed the bet starting issue. I did the 1000 roll run and the new set is running perfectly except for one nagging issue. It happened earlier before our new additions, but you had fixed it once. I am attaching an image link which explains it in detail.

Please do not worry about the effort being put in. I am more interested in developing this strategy to be playable against any game of chance anywhere in the future, I am really looking at building the wiki also in detail because with the amount of options available, we can do some really crazy stuff both ways with it. Basically it is like a personal project I have taken up to develop a solid gambling strategy....my hope.....

the image link of our issue has been attached. http://imgur.com/Sk8d6Sr

hope I haven't confused you

thanks, karma

[karmacoin]

Hey Know,

I think I can explain now in a few words, basically the last bet of the pattern should be considered as part of the main betting streak,

So in a LWLW scenario, the LWL(W) the last win should be considered as part of the main strategy, so when we exit after breaker, only one more win is required for two wins in a row.

similarly for LL, we will consider the L(L). This has to be relevant if breaker bets are triggered or not.

Now in the case of our simultaneous breaker, the last bet of the pattern which triggered the breaker should be considered.

now this explains it more clearly. I think. cheers karma

[knowitnothing]

Uhm, that has more to do with when the checks for the patterns happens than with that bet_before_pat variable. Right now those checks are called before updating anything related to a win/lose condition, so that is why you see the issue you are mentioning.

Ideally, we need to fix a server seed in these reports, so I can easily replicate the problem and check whether the fix matches what you expect. So I just pushed some code that shows the server seed used when running with "-d". Can you possibly run the strategy in simulation mode (with -d) and give me a seed that replicates your problem ? It is easier to keep track of what needs to be done then. Hope you understand; I know it is harder to look at the text output than the output shown by the interface in just-dice.com.

[karmacoin]

Hello Know,

Thanks Know, good day to you. I shall use the -d flag and try and find a sample of error happening. I am just running the bot, just for the heck of it on the site. Have a couple of meetings in the morning. Will get back and send you the info ASAP.

This sequence happens on every run. I will find the SERVER SEED with the -d flag and send the seed to you.

thanks a lot karma

[karmacoin]

Hello Know,

I have been running the bot for 3-4 hours now. Was watching it intermittently. The problem doesn't seem to be replicating now. It seems to be working fine, also I am able to deal with the issue, by changing by base patterns, so no problem for now. You can consider this issue closed. In case I face the same issue again. We shall bring it back into discussion.

I shall update and send across optimized default settings for the bot to be updated in the github repo.

thanks karma

[knowitnothing]

Hello. Note that I didn't fix the last issue you reported, it is still there.