## Classical Technical Patterns

In my presentation about Seasonality Analysis and Pattern Matching at the R/Finance conference, I used examples that I have previously covered in my blog:

- Month of the Year Seasonality – I introduced the Seasonality charts in the Historical Seasonality Analysis: What company in DOW 30 is likely to do well in January? post. I also developed the Seasonality Tool a free, user-friendly, point and click, application to create Seasonality charts, statistics, and reports. The Seasonality Tool can be downloaded here.
- What seasonally happens in the first 20 days in May – I introduced intra-month Seasonality charts in the Happy Holidays and Best Wishes for 2012. The intra-month Seasonality charts are also available in the Seasonality Tool, and you can also see the current month intra-month Seasonality chart for SPY at the top right corner of this blog.
- Find historical Matches similar to the last 90 days of price history – I introduced Time Series Matching charts in the:

The only subject in my presentation that I have not discussed previously was about Classical Technical Patterns. For example, the Head and Shoulders pattern, most often seen in up-trends and generally regarded as a reversal pattern. Below I implemented the algorithm and pattern definitions presented in the Foundations of Technical Analysis by A. Lo, H. Mamaysky, J. Wang (2000) paper.

To identify a price pattern I will follow steps as described in the Foundations of Technical Analysis paper:

- First, fit a smoothing estimator, a kernel regression estimator, to approximate time series.
- Next, determine local extrema, tops and bottoms, using fist derivative of the kernel regression estimator.
- Define classical technical patterns in terms of tops and bottoms.
- Search for classical technical patterns throughout the tops and bottoms of the kernel regression estimator.

Let’s begin by loading historical prices for SPY:

############################################################################### # Load Systematic Investor Toolbox (SIT) ############################################################################### con = gzcon(url('http://www.systematicportfolio.com/sit.gz', 'rb')) source(con) close(con) #***************************************************************** # Load historical data #****************************************************************** load.packages('quantmod') ticker = 'SPY' data = getSymbols(ticker, src = 'yahoo', from = '1970-01-01', auto.assign = F) data = adjustOHLC(data, use.Adjusted=T) #***************************************************************** # Find Classical Techical Patterns, based on # Pattern Matching. Based on Foundations of Technical Analysis # by A.W. LO, H. MAMAYSKY, J. WANG #****************************************************************** plot.patterns(data, 190, ticker)

The first step is to fit a smoothing estimator, a kernel regression estimator, to approximate time series. I used sm package to fit kernel regression:

library(sm) y = as.vector( last( Cl(data), 190) ) t = 1:len(y) # fit kernel regression with cross-validatio h = h.select(t, y, method = 'cv') temp = sm.regression(t, y, h=h, display = 'none') # find estimated fit mhat = approx(temp$eval.points, temp$estimate, t, method='linear')$y

The second step is to find local extrema, tops and bottoms, using first derivative of the kernel regression estimator. (more details in the paper on page 15):

temp = diff(sign(diff(mhat))) # loc - location of extrema, loc.dir - direction of extrema loc = which( temp != 0 ) + 1 loc.dir = -sign(temp[(loc - 1)])

I put the logic for the first and second step into the find.extrema() function.

The next step is to define classical technical patterns in terms of tops and bottoms. The pattern.db() function implements the 10 patterns described in the paper on page 12. For example, let’s have a look at the Head and Shoulders pattern. The Head and Shoulders pattern:

- is defined by 5 extrema points (E1, E2, E3, E4, E5)
- starts with a maximum (E1)
- E1 and E5 are within 1.5 percent of their average
- E2 and E4 are within 1.5 percent of their average

The R code below that corresponds to the Head and Shoulders pattern is a direct translation, from the pattern description in the paper on page 12, and is very readable:

#****************************************************************** # Head-and-shoulders (HS) #****************************************************************** pattern = list() pattern$len = 5 pattern$start = 'max' pattern$formula = expression({ avg.top = (E1 + E5) / 2 avg.bot = (E2 + E4) / 2 # E3 > E1, E3 > E5 E3 > E1 & E3 > E5 & # E1 and E5 are within 1.5 percent of their average abs(E1 - avg.top) < 1.5/100 * avg.top & abs(E5 - avg.top) < 1.5/100 * avg.top & # E2 and E4 are within 1.5 percent of their average abs(E2 - avg.bot) < 1.5/100 * avg.bot & abs(E4 - avg.bot) < 1.5/100 * avg.bot }) patterns$HS = pattern

The last step is a function that searches for all defined patterns in the kernel regression representation of original time series.

I put the logic for this step into the find.patterns() function. Below is a simplified version:

find.patterns <- function ( obj, # extrema points patterns = pattern.db() ) { data = obj$data extrema.dir = obj$extrema.dir data.extrema.loc = obj$data.extrema.loc n.index = len(data.extrema.loc) # search for patterns for(i in 1:n.index) { for(pattern in patterns) { # check same sign if( pattern$start * extrema.dir[i] > 0 ) { # check that there is suffcient number of extrema to complete pattern if( i + pattern$len - 1 <= n.index ) { # create enviroment to check pattern: E1,E2,...,En; t1,t2,...,tn envir.data = c(data[data.extrema.loc][i:(i + pattern$len - 1)], data.extrema.loc[i:(i + pattern$len - 1)]) names(envir.data) = c(paste('E', 1:pattern$len, sep=''), paste('t', 1:pattern$len, sep='')) envir.data = as.list(envir.data) # check if pattern was found if( eval(pattern$formula, envir = envir.data) ) { cat('Found', pattern$name, 'at', i, '\n') } } } } } }

I put the logic for the entire process in to the plot.patterns() helper function. The plot.patterns() function first call find.extrema() function to determine extrema points, and next it calls find.patterns() function to find and plot patterns. Let’s find classical technical patterns in the last 150 days of SPY history:

#***************************************************************** # Load historical data #****************************************************************** load.packages('quantmod') ticker = 'SPY' data = getSymbols(ticker, src = 'yahoo', from = '1970-01-01', auto.assign = F) data = adjustOHLC(data, use.Adjusted=T) #***************************************************************** # Find Classical Techical Patterns, based on # Pattern Matching. Based on Foundations of Technical Analysis # by A.W. LO, H. MAMAYSKY, J. WANG #****************************************************************** plot.patterns(data, 150, ticker)

It is very easy to define you own custom patterns and I encourage everyone to give it a try.

To view the complete source code for this example, please have a look at the pattern.test() function in rfinance2012.r at github.

Really Great. Thanks. Seems to work a little better when I changed the periods to 250 from 150. Worked extremely well on “QQQ”. I was wondering if there is a way to scan a list of stocks (DOW 30 for example) with this?

Wow, very interesting, unlimited possibilities… It would be very interesting to backtest trading according to the different patterns to determine if the classical technical analysis patterns are of any use! This has never been done before according to my knowledge. However do the find extreme functions work in realtime trading, or a they lagging by multiple days?

Laurent, the Foundations of Technical Analysis by A. Lo, H. Mamaysky, J. Wang (2000) paper does have historical performance tables for each pattern at the back.

Nice!

Puzzled about the plot.patterns function though.

When changing the range to scan it doesn’t list all the

patterns in the range?

Eg. for 190 it finds the TTOP in sept

And for 200 it finds nothing?

The first step in the plot.patterns function is to fit kernel regression using cross-validation. This is done to determine tops/bottoms.

If you provide different number of points to the kernel regression, the fit will likely be different; hence, different tops/bottoms. This is why using 190 points the algorithm finds TTOP in September, but using 200 it finds nothing.

To see this, you can just visually compare compare kernel estimates and tops/bottoms using 190 and 200 days.

If you plan to back-test the trading strategy based on these patterns, I suggest you follow the steps described in the paper and run algorithm on a rolling window to determine patterns.