1986issue C081-8
Construct a decision procedure that revises itself
A usable decision procedure is built so it can revise itself when market conditions change. Many inputs are encoded, every policy is scored, and later outcomes update the same weights.
- Build the procedure so it can revise itself when market conditions change, rather than stay fixed after the first rule set.
- Give the system enough input variety to match the many factors that move prices, instead of a few technical or earnings-and-dividend screens.
- Treat buy, sell, hold, do nothing, and sell short as distinct patterns, and take the policy with the largest score.
- Raise weights on features that improved results and lower weights on features that worsened them after reviewing whether the carried-out policy was correct.
Why the first rule set is not the system
A usable decision procedure is constructed so it can revise itself when market conditions change, rather than stay fixed after the first rule set is written. Construction here means a scoring loop that can be updated from later outcomes, not a finished list of rules.
Match the variety of what moves prices
The construction goal is to give the procedure enough input variety to match the many factors that move prices, instead of compressing the problem onto a few technical readings. Narrow technical or earnings-and-dividend screens are treated as information-destroying shortcuts that leave the decision system underpowered.
Price history alone is treated as insufficient for direction. A richer pattern that also includes fundamentals, psychology, and news is the proposed basis for anticipating trend changes.
Recognize each policy before an action is taken
Each well-defined policy is treated as a distinct information pattern that the procedure must recognize before an action is selected. Those policies are buy, sell, hold, do nothing, and sell short.
Inputs such as market indicators, earnings trends, and psychological measurements are encoded as a feature vector, then scored against a weight vector for every policy. The largest discriminant is the action taken.
What the computer holds and what the person keeps
The computer is assigned the dense information patterns a person cannot hold, while the person keeps judgment, supervision, and the final use of the scored alternatives.
The same scoring core is chosen because it can take many features, still work when some inputs are noisy or missing, and store only the current weights plus the latest feature vector.
Revise the same weights from later outcomes
Because the process that generates price changes is poorly understood, initial weights are expected to produce many poor decisions until feedback from later outcomes revises them.
A perceptron-style update raises weights on features that improved results and lowers weights on features that worsened them, using a review of whether each carried-out policy was correct.
Keep construction, psychology, and pattern work in one loop
Editorial: that review is how a Pre-trade checklist and the Trading psychology process stay attached to Pattern recognition. The checklist names the action, including doing nothing. The psychology process is the habit of scoring and then revising. Pattern recognition is the comparison of the current feature vector with the weights. None of the three is treated here as a separate system.
All readings on this track · 25 readings
- 1986Construct a decision procedure that revises itself
- 1989Finish the volume checklist before scoring the breakout
- 1989Constructing supervised forecasts on moving averages
- 1991Candlestick labels as stacked construction tests
- 1992Walk-forward evaluation of weekly price-change patterns
- 1993RSI price pattern templates and open interest
- 1994Constructing a dual-net day-ahead index direction forecast
- 1994A clocked stochastic second crest with a window-high stop
- 1996Volatility-ratio, inside-day and narrow-range-4 entry construction
- 1998Sliding-window correlation for cup-and-handle construction
- 2000Constructing rectangles for breakout hypotheses
- 2001Turning one candle into a ranked numeric object
- 2002Fuzzy-scored chart patterns as testable rules
- 2002From hot-zones to an open-close-matrix
- 2003Volume pressure and a band-clearing breakout case
- 2004Evaluating chart patterns against price objectives
- 2004Cobweb turning points from price structure
- 2005Hybrid decision trees and pattern recognition for trend rules
- 2005Two-bar zone codes for testable pattern systems
- 2005Price bar pattern construction and next-bar frequency
- 2008Observe markets before following pattern or system rules
- 2012Treat a four-leg Fibonacci completion as an unpaid hypothesis
- 2014Hidden three-channel regression signals for stock and call option entries
- 2014A shared daily-chart-level framework for session trades and swing holds
- 2015Condensed candlestick signatures