XDN Posted November 17, 2016 Report Share Posted November 17, 2016 (edited) On 11/10/2016 at 5:37 AM, McVince said: SAP needs to be re-vamped. No one will see the true value of this tool unless old theories are thrown out and new, more innovative theories are brought in........Find the guys that you can trust and do it as a team. McVince since you wrote this a few days ago i've been giving some thought to this subject and IMHO I think you are right. I've come up with an SAP idea (not proven yet) that more closely follows what we are discussing on the board these days. We all know that the shoe biases don't last, worse, many times they change extremely fast, within 3-8 events. Thats that is the main reason for the "Follow The Shoe" / Short Term NOR / Last 3 Event Methods development. But we haven't done this to SAP yet. My "Short Term SAP" thoughts are as follows.... 1. Reset SAP Counts on a loss trigger (say 3 LossIAR on the bias you are playing) or on an obvious shoe change (SS goes ZZ). 2. Change the count method from addition to multiplication for short term tracking. Since this would be a short term method we need to generate a MC/LC spread quickly, within just a 2-4 events. This will make the numbers bigger quicker, so it might be unwieldy if a bias lasts the whole shoe but really it shouldn't be....the numbers will just be bigger. We could multiply by the existing count instead of simply adding the counts. I think this works logically because if we are tracking/looking for a concentrated set of events in a short term "set" of events. In other words if we see 2122 2's are WAY over represented in those 4 events, we need a multiplier to build a spread quickly to represent that overage of 2's in that small set of events. Example using 2122 First 2 Event = SAP Count = 2 (Starting Point) ****Ignore the 1 event for this example*************** Second 2 Event = SAP Count = 4 (Previous SAP Count(2) X SAP Multiplier(2)) Third 2 event = SAP Count = 8 (Previous SAP Count(4) X SAP Multiplier(2)) etc..... Note... We may have to change the multiple for 1s as multiplying 1x anything is always 1, we would never get a multiplier effect This would be a companion SAP method to FTS. I'll try to get some testing in on this in the little free time I have. If anyone wants to test some shoes to see if this works, please do so. Edited November 17, 2016 by XDotNet Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.