Stacks, Processors and Selectors
The term that may interest you at most at this point is Processor. Inside WINHunter a Processor is what actually reviews the specified amount of historical data and converts it into a raw score value for each drawn ball. Take for example the Single Hit Processor. This processor contains several functions which output a final rough score. This score value can be graphed, but most importantly it is passed to another object within WINHunter called a Selector. The selector uses its settings to review the score values (high, low, etc) and determines which balls to keep, and which balls to toss out.
It sounds as if you are using several methods together here, which some may already exist inside WINHunter. With this in mind, perhaps just designing a Stack which mimics your method could be done. Now you may be asking "what is a stack". A stack is an arrangement of processors in a defined way that produces a final prediction.
Before we go on though, I noticed that you utilize odds in calculating some of your data. Winhunter does not use odds in any of its calculations. Instead, WINHunter simply calculates raw data, and crunches that data into score values. By converting data into a simple score value, other score values can be tallied together and a combined score realized. This combined score is what the selector then utilizes to generate a final output.
With all of that said, I need to fully understand each stage of your logic, and determine how you are calculating your results.
Andrew
The term that may interest you at most at this point is Processor. Inside WINHunter a Processor is what actually reviews the specified amount of historical data and converts it into a raw score value for each drawn ball. Take for example the Single Hit Processor. This processor contains several functions which output a final rough score. This score value can be graphed, but most importantly it is passed to another object within WINHunter called a Selector. The selector uses its settings to review the score values (high, low, etc) and determines which balls to keep, and which balls to toss out.
It sounds as if you are using several methods together here, which some may already exist inside WINHunter. With this in mind, perhaps just designing a Stack which mimics your method could be done. Now you may be asking "what is a stack". A stack is an arrangement of processors in a defined way that produces a final prediction.
Before we go on though, I noticed that you utilize odds in calculating some of your data. Winhunter does not use odds in any of its calculations. Instead, WINHunter simply calculates raw data, and crunches that data into score values. By converting data into a simple score value, other score values can be tallied together and a combined score realized. This combined score is what the selector then utilizes to generate a final output.
With all of that said, I need to fully understand each stage of your logic, and determine how you are calculating your results.
WINHunter's capabilities enable you to design a method which might closely (if not match completely) your logic in picking numbers from your final output.
Don't give up yet! It is my firm belief that because each individual lottery is based upon a constant method that the results contain a "signature". Successful prediction methods do work again in future draws.
Andrew