Welcome Guest
Log In | Register )
The time is now 7:12 pm
You last visited October 24, 2014, 7:07 pm
All times shown are
Eastern Time (GMT-5:00)

Help wanted: manual's system

Topic closed. 6 replies. Last post 2 years ago by adobea78.

Page 1 of 1
51
PrintE-mailLink
Avatar
Florida
United States
Member #135620
November 27, 2012
356 Posts
Offline
Posted: January 7, 2013, 1:06 am - IP Logged

I've had a few PMs about my system. As I've said, I'm stuck on a problem. I'm going to try and outline where I'm stuck at so maybe the LP collective can come up with a solution. The nuts and bolts of the system is fairly simple. It's based on deviations. I wanted to create a system that was played for 7 days or until a hit occurred. Hopefully, with 9 sets or less, per draw, to minimize cost. I'm a programmer so any system I made would be based on data. After you get past the initial idea, it gets a little more involved… For now, I'd like to focus on the problem:

The current version of the system is written in SQL (for proof of concept and testing). So it's a bit difficult to share this for anyone that doesn't know SQL. So I'll try to just stick to examples and data. For the sake of saving time, just know that at some point a set is generated based on how a set differs from the previous draws (i.e. if Position 1 of a draw is 5, and Position 1 of the draw before it is 8, the deviation is 3. 8 - 5 = 3).

Using my deviation system, I input a date of 12/1/12 (so this includes 12/1 draws). It goes through back data (not much, maybe ten days or so, or twenty draws. It's hard to explain without really getting into the boring stuff) and generates a deviation set. In the case of 12/1, I have a deviation set of 6-2-4. Now my problem presents itself. I have to do something with this deviation set so it affects the last drawn set. The last drawn set in FL on 12/1 EVE was 7-0-9. I can either add the deviation set to it or subtract it. If you subtract each deviation position from the last drawn position, you miss out on a bunch of straight hits. Same thing goes for addition. However, if you mix up the positions, you get 50%+ straight hits for the month.

Still using 12/1 as an example here's the workout:
Position 1 deviation is 6. The last drawn is 7. Using lotto math, the possible values are 3 and 1
Position 2 deviation is 2. The last drawn is 0. Using lotto math, the possible values are 2 and 8
Position 3 deviation is 4. The last drawn is 9. Using lotto math, the possible values are 3 and 5

Since this is deviation based, it's a guess where numbers will hit. With that in mind, I do a +1/-1 workout on Positions 2 & 3. Assuming I went addition on each position, here is a set this system would come up with.

334, 333, 332, 324, 323, 322, 314, 313, 312 (312 hit on 12/3 EVE)

Here's another example for 12/2: Position 1 (deviations match): 9. Position 2 (deviations match): 0. Position 3 (addition deviation): 4. Position 3 (subtraction deviation): 6

On 12/3 Mid, 9-0-7 hit. Keep in mind I add +1/-1 to positions 2 & 3. Position 1 (9) matches exactly. Position 2 (0) matches exactly. Position 3 matches subtraction +1. If you don't add the +/- 1 to positions 2 & 3, you miss out on a lot of straights. So the key question remains, do I apply addition or subtraction to position X? Keep in mind, this changes for each and every draw. Playing all positive on 12/1 was good. On 12/2, I would've missed a straight. If you're still with me and have any suggestions, it would be greatly appreciated.

 

Since I used 12/1 and 12/2, here's 12/3, it didn't hit within 7 days (but, for the sake of arguement, straights did happen on 12/26 and 12/27 but it's not all that cost effective to play numbers for that long, hoping for a hit...):

Pos1APos1S Pos2APos2S Pos3APos3S
51 86 15
51 86 04
51 86 93
51 75 15
51 75 04
51 75 93
51 64 15
51 64 04
51 64 93
    lakerben's avatar - waveform
    New Mexico
    United States
    Member #86100
    January 29, 2010
    8505 Posts
    Offline
    Posted: January 7, 2013, 1:25 am - IP Logged

    Try taking the average root over 15 draws and then use this as the "x.

    No bs, just numbers.

     

    Patriot

      Avatar
      Florida
      United States
      Member #135620
      November 27, 2012
      356 Posts
      Offline
      Posted: January 7, 2013, 3:37 pm - IP Logged

      Try taking the average root over 15 draws and then use this as the "x.

      11/1 - 11/8 Average SUM: 13
      11/1 - 11/8 Average Root: 4.7
      Running numbers for 11/8, the next hit was 8-8-3 on 11/16. 8-8-3's SUM is 19, Root is 10.

      11/2 - 11/9 Average SUM: 12
      11/2 - 11/9 Average Root: 4.3
      Running numbers for 11/9, the next hit was 9-6-2 on 11/19. 9-6-2's SUM is 17, Root is 8.

      Neither one of those examples is following the 7-day rule but I was just testing the Root theory. Based on these two examples, one can hypothesize that if the SUM or Root of the workout picks is close to the average, it won't hit. If I go +/- 4 on the SUM, and +/- 1 on the Root, it's reducing the workout numbers by a very good margin and not removing the winners. This may be different for hits that follow the 7 day rule. Might have to go the other way. In any case, it's giving me something to test.

      Thank you very much for the suggestion.

        lakerben's avatar - waveform
        New Mexico
        United States
        Member #86100
        January 29, 2010
        8505 Posts
        Offline
        Posted: January 7, 2013, 3:56 pm - IP Logged

        11/1 - 11/8 Average SUM: 13
        11/1 - 11/8 Average Root: 4.7
        Running numbers for 11/8, the next hit was 8-8-3 on 11/16. 8-8-3's SUM is 19, Root is 10.

        11/2 - 11/9 Average SUM: 12
        11/2 - 11/9 Average Root: 4.3
        Running numbers for 11/9, the next hit was 9-6-2 on 11/19. 9-6-2's SUM is 17, Root is 8.

        Neither one of those examples is following the 7-day rule but I was just testing the Root theory. Based on these two examples, one can hypothesize that if the SUM or Root of the workout picks is close to the average, it won't hit. If I go +/- 4 on the SUM, and +/- 1 on the Root, it's reducing the workout numbers by a very good margin and not removing the winners. This may be different for hits that follow the 7 day rule. Might have to go the other way. In any case, it's giving me something to test.

        Thank you very much for the suggestion.

        I use rootsa in different ways.  In NM 191 was drawn over a week ago.  I put the root in my pick 3 step down program and 5 draws later a hit. 757. 

         

        222  
         222 
          222
        464
        575
        675
        775
        875
        975
        075
        175
        275
        375
        475

        No bs, just numbers.

         

        Patriot

          Avatar
          Florida
          United States
          Member #135620
          November 27, 2012
          356 Posts
          Offline
          Posted: January 7, 2013, 9:33 pm - IP Logged

          Well, roots are taking out a fair amount of 'bad' picks but it's weeding out some good ones as well. Doesn't seem to matter if I go off of SUM, Root, or both. Removing or keeping +/- 1 on Root produces the same results. Pity... ah well, back to the grind.

            Avatar

            United States
            Member #116348
            September 8, 2011
            2350 Posts
            Offline
            Posted: January 7, 2013, 10:18 pm - IP Logged

            I've had a few PMs about my system. As I've said, I'm stuck on a problem. I'm going to try and outline where I'm stuck at so maybe the LP collective can come up with a solution. The nuts and bolts of the system is fairly simple. It's based on deviations. I wanted to create a system that was played for 7 days or until a hit occurred. Hopefully, with 9 sets or less, per draw, to minimize cost. I'm a programmer so any system I made would be based on data. After you get past the initial idea, it gets a little more involved… For now, I'd like to focus on the problem:

            The current version of the system is written in SQL (for proof of concept and testing). So it's a bit difficult to share this for anyone that doesn't know SQL. So I'll try to just stick to examples and data. For the sake of saving time, just know that at some point a set is generated based on how a set differs from the previous draws (i.e. if Position 1 of a draw is 5, and Position 1 of the draw before it is 8, the deviation is 3. 8 - 5 = 3).

            Using my deviation system, I input a date of 12/1/12 (so this includes 12/1 draws). It goes through back data (not much, maybe ten days or so, or twenty draws. It's hard to explain without really getting into the boring stuff) and generates a deviation set. In the case of 12/1, I have a deviation set of 6-2-4. Now my problem presents itself. I have to do something with this deviation set so it affects the last drawn set. The last drawn set in FL on 12/1 EVE was 7-0-9. I can either add the deviation set to it or subtract it. If you subtract each deviation position from the last drawn position, you miss out on a bunch of straight hits. Same thing goes for addition. However, if you mix up the positions, you get 50%+ straight hits for the month.

            Still using 12/1 as an example here's the workout:
            Position 1 deviation is 6. The last drawn is 7. Using lotto math, the possible values are 3 and 1
            Position 2 deviation is 2. The last drawn is 0. Using lotto math, the possible values are 2 and 8
            Position 3 deviation is 4. The last drawn is 9. Using lotto math, the possible values are 3 and 5

            Since this is deviation based, it's a guess where numbers will hit. With that in mind, I do a +1/-1 workout on Positions 2 & 3. Assuming I went addition on each position, here is a set this system would come up with.

            334, 333, 332, 324, 323, 322, 314, 313, 312 (312 hit on 12/3 EVE)

            Here's another example for 12/2: Position 1 (deviations match): 9. Position 2 (deviations match): 0. Position 3 (addition deviation): 4. Position 3 (subtraction deviation): 6

            On 12/3 Mid, 9-0-7 hit. Keep in mind I add +1/-1 to positions 2 & 3. Position 1 (9) matches exactly. Position 2 (0) matches exactly. Position 3 matches subtraction +1. If you don't add the +/- 1 to positions 2 & 3, you miss out on a lot of straights. So the key question remains, do I apply addition or subtraction to position X? Keep in mind, this changes for each and every draw. Playing all positive on 12/1 was good. On 12/2, I would've missed a straight. If you're still with me and have any suggestions, it would be greatly appreciated.

             

            Since I used 12/1 and 12/2, here's 12/3, it didn't hit within 7 days (but, for the sake of arguement, straights did happen on 12/26 and 12/27 but it's not all that cost effective to play numbers for that long, hoping for a hit...):

            Pos1APos1S Pos2APos2S Pos3APos3S
            51 86 15
            51 86 04
            51 86 93
            51 75 15
            51 75 04
            51 75 93
            51 64 15
            51 64 04
            51 64 93

            Can you do a manual workout  for few combined draws of a State with  'deviation concept'?.

            Visual illustration may help members to see the solution or come up with ideal. Use this Cal. data for example, explain the concept  from dates dec 29 to Jan 1. 

            Drawing DatePick 3
            MiddayEvening
            Mon, Jan 7, 2013235753
            Sun, Jan 6, 2013964531
            Sat, Jan 5, 2013984849
            Fri, Jan 4, 2013393347
            Thu, Jan 3, 2013850449
            Wed, Jan 2, 2013190453
            Tue, Jan 1, 2013711762
            Mon, Dec 31, 2012855535
            Sun, Dec 30, 2012063547
            Sat, Dec 29, 2012779781
              Avatar

              United States
              Member #116348
              September 8, 2011
              2350 Posts
              Offline
              Posted: January 7, 2013, 10:53 pm - IP Logged

              I've had a few PMs about my system. As I've said, I'm stuck on a problem. I'm going to try and outline where I'm stuck at so maybe the LP collective can come up with a solution. The nuts and bolts of the system is fairly simple. It's based on deviations. I wanted to create a system that was played for 7 days or until a hit occurred. Hopefully, with 9 sets or less, per draw, to minimize cost. I'm a programmer so any system I made would be based on data. After you get past the initial idea, it gets a little more involved… For now, I'd like to focus on the problem:

              The current version of the system is written in SQL (for proof of concept and testing). So it's a bit difficult to share this for anyone that doesn't know SQL. So I'll try to just stick to examples and data. For the sake of saving time, just know that at some point a set is generated based on how a set differs from the previous draws (i.e. if Position 1 of a draw is 5, and Position 1 of the draw before it is 8, the deviation is 3. 8 - 5 = 3).

              Using my deviation system, I input a date of 12/1/12 (so this includes 12/1 draws). It goes through back data (not much, maybe ten days or so, or twenty draws. It's hard to explain without really getting into the boring stuff) and generates a deviation set. In the case of 12/1, I have a deviation set of 6-2-4. Now my problem presents itself. I have to do something with this deviation set so it affects the last drawn set. The last drawn set in FL on 12/1 EVE was 7-0-9. I can either add the deviation set to it or subtract it. If you subtract each deviation position from the last drawn position, you miss out on a bunch of straight hits. Same thing goes for addition. However, if you mix up the positions, you get 50%+ straight hits for the month.

              Still using 12/1 as an example here's the workout:
              Position 1 deviation is 6. The last drawn is 7. Using lotto math, the possible values are 3 and 1
              Position 2 deviation is 2. The last drawn is 0. Using lotto math, the possible values are 2 and 8
              Position 3 deviation is 4. The last drawn is 9. Using lotto math, the possible values are 3 and 5

              Since this is deviation based, it's a guess where numbers will hit. With that in mind, I do a +1/-1 workout on Positions 2 & 3. Assuming I went addition on each position, here is a set this system would come up with.

              334, 333, 332, 324, 323, 322, 314, 313, 312 (312 hit on 12/3 EVE)

              Here's another example for 12/2: Position 1 (deviations match): 9. Position 2 (deviations match): 0. Position 3 (addition deviation): 4. Position 3 (subtraction deviation): 6

              On 12/3 Mid, 9-0-7 hit. Keep in mind I add +1/-1 to positions 2 & 3. Position 1 (9) matches exactly. Position 2 (0) matches exactly. Position 3 matches subtraction +1. If you don't add the +/- 1 to positions 2 & 3, you miss out on a lot of straights. So the key question remains, do I apply addition or subtraction to position X? Keep in mind, this changes for each and every draw. Playing all positive on 12/1 was good. On 12/2, I would've missed a straight. If you're still with me and have any suggestions, it would be greatly appreciated.

               

              Since I used 12/1 and 12/2, here's 12/3, it didn't hit within 7 days (but, for the sake of arguement, straights did happen on 12/26 and 12/27 but it's not all that cost effective to play numbers for that long, hoping for a hit...):

              Pos1APos1S Pos2APos2S Pos3APos3S
              51 86 15
              51 86 04
              51 86 93
              51 75 15
              51 75 04
              51 75 93
              51 64 15
              51 64 04
              51 64 93

              How many deviation sets was generated for the pool size  (0-9)? You might take a look at  generating the deviations from the pool ( this will be  very random), instead of deviations based on  historical data, this just a thought.

              can you generate all possible deviations between all digits in the pool 0-9?