827 midday. Funny thing about this number was I thought it was going to Ohio the night before and 88x would go to Florida. Instead , it was the other way around. 🤭

Maybe I got lost in the sauce between testing, performing updates and and adding new stuff and ideas.

Weeklies works for all states. Backtested and drafted, but for some reason when I post weekly pick 4s and pick 5s, they don't hit. Hmm?

I also figured out and knew for awhile what makes SBR work. Thanks to K for sharing the solution with me.

This isn't SBR, or 55555. It's a totally different system.

Right now I'm thinking....okay two methods work, but do they both predict the same thing at the same time?
This is the signal. A ______ takes too long and requires so many updates.

I.e. system 1 predicts 111
system 2 predicts 332 111 667

United system detects 111 between both.

But then later a new idea clicks and I create
System 3 and 4.
After testing and implementing both, I'd have to go back and implement system 3 and 4 to the United system. 🥵🥵🥵 See the dilemma?
🤬 Consuming and exhausting at times.

Currently there are 8 systems condensed into one. It was messy, but everything is talking and working together as one through a pipeline
Due pairs are talking to Nxpairs.

Straight order was the 2nd system I implemented that guaranteed ## straight hits a month. (Thanks again K!)

Finally implemented vtracs display for each combo created, cleaned up the UI, added alerts, and integrated a history tracker for each system with actual dates to see what's working with whatever state's data mapped to calendar dates.

Due combos are talking to the queue. Gpredict combos mapped to the DST.
Also utility shortcuts to delete and remove a draw from the loaded data.

So yeah even if the right numbers aren't posted, they're detected. v45 hit tonight but v33 is still due.

Previously, I had pair followers, but that seems messy so now I use vtrac followers which condenses much neater.

For me this is no longer about winning, it's more about creating a sound system that does it's own thing and comes together. The most I spend per game is $1.00 unless intuition tells me otherwise. I enjoy working on this.

The biggest was T1-T5 Pair Date rules.
If you look back at my previous post with the log of draws from January to x day, you'd see what rules matched.

So I took that idea converted it to vtracs, use ##  vtracs for dates. It's not 100% accurate, but allows me a reference to filter out and prioritize certain combos over others, including pair alerts. Then on top of that, filter and rank them.

For example, I know when digit 2 or 7 is coming. v3, from what I've seen has been out max 3 draws since it was due. This is another signal.

Then there are other implemented features that I haven't really been paying much attention to
Like maths that create combos
107 101 100 101 104 192 102 104 102

v12 and v25 will eat these up eventually. They've been generated, sitting and neither tracked or monitored. Things id do with these, count the occurrence, determine if they have pressure from other alerts where v12 or v25 hits. Iykyk.

v33 is due, my doubles list are v233 I wouldn't be shocked if v334 turns up.

This is the type of time I'm on rn 🤭🙂

Another thing I'm thinking about is tracking weekly combos to matrix hits. I.e. does a weekly combo appear in a matrix the draw before it hits?

I really should prioritize this so I can do it on paper.

Yep v233 hit tonight. 122 ??

Yay ???????