As promised, I have listed more things I believe the proposed TW-Channel Tool should do to make this channel easier to use and enhance its capabilities. I've done so, by editing my original proposal post, adding more ideas, and making the text a bit more readable, too. Please click on this link to my old Post 011 "WANTED: A TeamWork Channel Tool!" to see what I'd like to add to it. I highly recommend you watch Post 011, as I may update it more in the future.
You know, I really should have made the title of that post "NEEDED!!: A TeamWork Channel Tool!" Hopefully, with the number of people reading my blog growing steadily, I'll be able to get input from others to better define the NEED for this tool!
An instructional Blog aimed at teaching Traders and Technical Analysts about the Enhanced Raff Regression Channel™ (ERRC™) and TeamWork Channels™ (TW-Channels™ or TW Channels™); which can predictively chart Support and Resistance levels in MetaStock charts! Also, the FenceLine Channel™ (FL-Channel™ or FL Channel™) can help you validate breakouts from the trend!
Tuesday, November 11, 2014
Sunday, November 9, 2014
New Posts: 003 - Why I Believe Day Traders Can Use TW-Channels
First, let me make THREE things clear:
1. I have never attempted to day-trade, even though in the past I have had occasion to use MetaStock Pro, which tracks the markets live in any level of trading chart you want. You can trade "tick", 1-minute, 5-minute, 10-min, etc., or go with Daily, Monthly, whatever. You can do a mixture of multiple time frames, if you wish.
2. Although I fully believe that TW-Channels should be implemented in the End-of-Day version of MetaStock, and in MetaStock Pro as well, I cannot say whether it would be a good idea to actually plot TW-Channels in day-trading time interval charts, such as "tick", 1-minute, 5-minute, and the like. Certainly they would be useful in Daily, Weekly, Monthly charts, but I've never had a chance to try using them in any time-interval less than Daily.
3. I have, however, watched 1-minute and 5-minute chart prices react to the Support/Resistance price-levels in my Daily charts having well-drawn TW-Channels in them. I'm certain that with well-drawn TW-Channels in a Daily chart, any day-trader could strengthen his/her trading with regard to using Support/Resistance levels to make trading decisions. Assuming, of course, that the Day Trader is willing to try it long enough to see it work.
The trouble with doing this now, though, is the tedium and time needed to place valid TW-Channels in a Daily chart of the targeted trading instrument. In order for TW-Channels to be as useful as they could be, a new tool is needed,...
the TW-Channel Tool that I've proposed for MetaStock.
the TW-Channel Tool that I've proposed for MetaStock.
The illustration below is a crude one, but it will serve to show how TW-Channel Daily charts could help the day-trader see Support/Resistance areas before they are actually hit:
On the left you see an image of the candlestick that appeared on my Daily chart, with lines crossing it at various angles and prices. On the right is an OHLC Bar of the same date's price movement. Note the purplish and reddish Std-Err Channel Lines that draw a flat sort of X across the candle and the bar. Also note that the mid-point of the X is just to the right of the mid-point of the candle and just to the right of the OHLC Bars vertical line.
![]() |
| Candlestick on Daily Chart of GM on 11/07/14 |
|
| OHLC Bar on Daily Chart of GM on 11/07/14 |
![]() |
| Two screen-shots of Google's 1D chart of GM for 11/07/2014. |
If you are a day-trader, can you not picture yourself being able to use the extra "intelligence" that these lines provide to help you make a trading decision?
Tuesday, November 4, 2014
New Posts: 002 - NEW!!! My TEAMWORK CHANNELS(tm) Plug-In PROPOSAL!
Updated New Post 004 --- My Proposed TEAMWORK CHANNELS TOOL plug-in !!!
In early April this year, I met with Jeff Gibby at MetaStock's office to show him my PowerPoint Presentation about the new TeamWork Channels Tool. He was impressed and asked me for some details, and, how much I'd like to charge for the Plug-in! He said that the programming team was fully booked getting the newest version of MetaStock ready for release in May. He said that after the release, we would get together to begin developing my plug-in. Meanwhile, I am working on an instruction manual and a curriculum for a training class to introduce my Plug-in.
In early May, my wife and I took a two-week trip to Hong Kong. We stayed with her older sister and met other relatives in Hong Kong. We had planned to visit Xiamen, China, where my wife was born. Sadly, because of Roxana new US Citizen status, China's representatives said China could not give her a visa. She would have to get it from the US Government because she is now a US Citizen. She must get it from the US Government, they insisted. Unfortunately, the US Embassy in Hong Kong was closed. Roxana was very upset, but we will try again next year.
The trip was not wasted, though. We had a good couple of weeks visiting my wife's older sister, and her cousins, etc. Her nephew, Michael, drove us all over Hong Kong, showing us the sights, etc. He is a brave and skilled driver, and that is a VERY good thing, or I might not be typing this right now. Hong Kong is an amazing place, but the TRAFFIC is horrendous! Thankfully, Hong Kong is VERY SERIOUS about making people learn to drive well, and I'm grateful for that! We returned home safely, hauling my wife's many gift items, and sadly, a Major Case of JET LAG!
After our return, Jeff contacted me to let me know that as he was going to Sales trip to Europe for the latest release of MetaStock. He would be back in late May or Early June. We planned to meet in June to begin the development of my plug-in. The tentative retail price currently is $299.00, but that could change once development-costs are considered.
As soon as I can, I plan to update my PowerPoint Presentation, after Jeff and I have discussed the details of the development, and perhaps I'll be able to post a copy of it here, along exactly what the price might be. As the details of development and programming are not known, as yet, we cannot give you a specific time that it might become available. But, we will announce it, and its purchase cost, as soon as we can. Hopefully, that will be before the end of July this year.
Meanwhile, watch this BLOG for announcements, please. I would welcome your feedback and emails, although I may need to defer specifics until later. I promise to keep you updated as soon and as often as I can. I hope to be able to offer a discount for readers of my blog, especially if you'll pass the word around about my plug-in becoming available.
Robert B. McKinnon
TeamWork Channels(tm) Creator
In early April this year, I met with Jeff Gibby at MetaStock's office to show him my PowerPoint Presentation about the new TeamWork Channels Tool. He was impressed and asked me for some details, and, how much I'd like to charge for the Plug-in! He said that the programming team was fully booked getting the newest version of MetaStock ready for release in May. He said that after the release, we would get together to begin developing my plug-in. Meanwhile, I am working on an instruction manual and a curriculum for a training class to introduce my Plug-in.
In early May, my wife and I took a two-week trip to Hong Kong. We stayed with her older sister and met other relatives in Hong Kong. We had planned to visit Xiamen, China, where my wife was born. Sadly, because of Roxana new US Citizen status, China's representatives said China could not give her a visa. She would have to get it from the US Government because she is now a US Citizen. She must get it from the US Government, they insisted. Unfortunately, the US Embassy in Hong Kong was closed. Roxana was very upset, but we will try again next year.
The trip was not wasted, though. We had a good couple of weeks visiting my wife's older sister, and her cousins, etc. Her nephew, Michael, drove us all over Hong Kong, showing us the sights, etc. He is a brave and skilled driver, and that is a VERY good thing, or I might not be typing this right now. Hong Kong is an amazing place, but the TRAFFIC is horrendous! Thankfully, Hong Kong is VERY SERIOUS about making people learn to drive well, and I'm grateful for that! We returned home safely, hauling my wife's many gift items, and sadly, a Major Case of JET LAG!
After our return, Jeff contacted me to let me know that as he was going to Sales trip to Europe for the latest release of MetaStock. He would be back in late May or Early June. We planned to meet in June to begin the development of my plug-in. The tentative retail price currently is $299.00, but that could change once development-costs are considered.
As soon as I can, I plan to update my PowerPoint Presentation, after Jeff and I have discussed the details of the development, and perhaps I'll be able to post a copy of it here, along exactly what the price might be. As the details of development and programming are not known, as yet, we cannot give you a specific time that it might become available. But, we will announce it, and its purchase cost, as soon as we can. Hopefully, that will be before the end of July this year.
Meanwhile, watch this BLOG for announcements, please. I would welcome your feedback and emails, although I may need to defer specifics until later. I promise to keep you updated as soon and as often as I can. I hope to be able to offer a discount for readers of my blog, especially if you'll pass the word around about my plug-in becoming available.
Robert B. McKinnon
TeamWork Channels(tm) Creator
Sunday, October 19, 2014
New Posts: 001 - FINALLY!
CHANNEL CHALLENGES for
TECHNICAL ANALYSTS
is
REBORN AGAIN at last!!
I sometimes thought I might never be in a position to begin this blog again, but now, ready or not, I must relaunch it! A recent car accident wherein I or my wife could have been seriously injured convinced me I should not wait any longer.
I am starting with what I consider to be inadequate preparation, so please forgive me if you find this blog somewhat clumsy and uncoordinated. Please forgive me if my grammar and spelling are not quite right, too. I will try to edit and correct as needed, including errors I may discover in my old posts.
Click on each chart image to view enlarged in a new window.
General Motors (GM)
![]() |
| General Motors, showing DCB pattern, with some commentary. |
You can see my "paper" Short position started in the chart at the left. I decided I would Short 1000 paper-shares of the stock. (I currently have no real-world funds to apply to trading, so paper-trading is all I can do for now.)
![]() |
| Did not close outside FenceLine |
![]() |
| Will GM drop this far? |
I needed to estimate how far GM might drop, if the pattern were to continue developing. I measured the distance from the peak (where the red-line starts in my chart at the left), to the bottom-line of the ERRC. I plotted this distance in the chart at the right with the orange line that drops well below the current prices, showing a Short position would have some good potential. If my drop estimate is accurate, it could fall to $28.00, but could take a week or two to do so.

How My Short Position Has Gone So Far
As of 10/17/2014, my "raw profits" from this short position (in paper-shares) on GM are quite encouraging. See my spreadsheet charts at the right.
This does not mean that charts using ERRCs and TW-Channels will always go your way, but I find them very helpful when support and resistance in the area of the current price needs to be evaluated.
GM and FORD Short-term Longs
As I was watching GM, I noted Ford (F) getting very similar signals from my Expert. Waiting until both hit support that warranted the buy signal, I "bought" 1000 paper-shares of both. My Short position in GM is still in play, but I thought I'd take a little profit from what is likely to be a short-term Bullish move to the next ERRC line above the current price. The comparison chart at the left is as of 10/17/2014.Update: GM and F Longs Closed, Short Study Continues
![]() |
| Sold both on the Open Friday |
![]() |
| NEW! UPDATED CHART OF MY GM SHORT POSITION |
With the Start Date (SD) and End Date (ED) for each
of these TW-Channels, you could recreate them
on your own General Motors (GM) chart.
=============================
of these TW-Channels, you could recreate them
on your own General Motors (GM) chart.
![]() |
| Do you have a chart on which you'd like me to position TW-Channels for you? |
=============================
ARE YOU NEW TO THIS BLOG? WELCOME!!
If you are new to Channel Challenges for Technical Analysts, I welcome you, and would be glad to get to know you and how you found my site. To make the most of what I offer, I suggest you read at least some of my earlier posts to gain a basic understanding of my methods. Of course, reading all my posts, in order, would make sense, but reading those I list below will give you an idea of what has gone before, and provide a good foundation for future learning.
Post 001: "Channel Challenges for Technical Analysts Reborn" introduces me, my methods, and why I began my blog. It mentions the ERRC Color Coder Expert that I initially used in my charts. Unfortunately, over the years, the original version's code was lost as I sought to improve upon it. Its replacement, which is under development, will not only color-code the Over-Bought (OB) and Over-Sold (OS) candles to help place the ERRCs, but also provide various other feedback on the state of the chart. Buy/Sell Signals, Bullish/Bearish Conditions, Volume Greater than Average indications, and even Commentary are my intent. I will make this Expert available for a fee.
Post 004: "How to Draw ERRCs and TeamWork Channels" is a good basic tutorial on how to create TW Channels, beginning with placing an accurate ERRC, following up with placing Standard Error Channels (Std-Err Channels), and/or Standard Deviation Channels (Std-Dev Channels), as needed. Note, I almost never use Std-Dev Channels in my TW-Channels now, unless an obvious support/resistance location is noted in my chart which a Std-Err Channel doesn't "explain".
Post 005: "TeamWork Channels On the Nasdaq 100 Index" gives a good illustration of using TW-Channels on Index charts, in this case the Nasdaq 100 Index. It also provides the Start Dates (SD) and End Dates (ED) of the channels in the chart, so you can reproduce them in your own. It then gives samples of how the TW-Channels, drawn on trends way in the past, chart areas of Support and Resistance in the more current prices, essentially proving their value.
Post 006: "The Fenceline & Overall TW-Channels' Utility" introduces how to draw FenceLine Channels, and Overall TW-Channels, and gives you an idea of why you may wish to include them in your charts.
Post 007: "Why do TW-Channels Work?" answers this question in a rather technical way, but there is a paragraph in the middle that sums up my opinion as to why they work. After re-reading it just now, I realize it could be wording a bit better, so I'll probably expand on it in a future post.
Post 009: "TeamWork Channel Drawbacks" seeks to point out aspects of ERRCs, TW-Channels, etc., that are not, shall we say, optimal? Every indicator I've ever seen has some kind of drawback, including my channels tools. This post gives a good idea of what they are, but also proposes ways that these could be eliminated or at least reduced, with the help of MetaStock's programmers.
Post 011: "WANTED: A TeamWork Channel Tool" is my first effort to propose how a tool could be designed in MetaStock to facilitate and enhance the use of TeamWork Channels. These are effectively the collective form of using ERRCs, Std-Err Channels, Std-Dev Channels, and/or FenceLine Channels, all of which use the same SD and ED for any given TeamWork Channel's parts. Altough my current methods with them work, the tool I describe could take most of the tedium of the task away, and have the added benefit of reducing the level of memory-usage need in MetaStock to produce TeamWork Channels in charts, by eliminating the lines that are not needed in the chart. Since I wrote that post, more ideas on how and why this tool should be built have occurred to me. I will write a post specifically about this issue again in the near future.
===========================================
Topics for Future Discussion
I Just Enrolled in TD AmeriTrade's
thinkorswim
Virtual Trading Program
Why I believe Intraday Traders can benefit
from using TW-Channels in Daily Charts!
Enhancements to My Proposed TW-Channel Tool
===========================================
Wednesday, June 6, 2007
Post 011: WANTED: A TeamWork Channel Tool!
Wouldn't it be nice to have a TeamWork Channel Tool in MetaStock that would make them easy to draw? It certainly would overcome most of the drawbacks of using them.
In conclusion:
I've envisioned this tool, not just because I'd like TeamWork Channels to be easier for me, but so that they'd be easier for everyone. Plus, with this tool available in MetaStock, people who've never read my article or practiced TW-Channels in the tedious way we do now, will have a chance to use it. If MetaStock were modified this way, a lot of my own work would be easier, but it would also allow me to more readily share what I've learned about TW-Channels with the trading public.
JUMP TO MY NEXT POST
================================

INSERTED ANNOUNCEMENT
MID-APRIL 2018
IMPORTANT NOTICE !!!
THINGS ARE FINALLY HAPPENING!!!
I HAVE MET WITH METASTOCK'S MANAGEMENT,
AND HAVE GOTTEN THEIR PROMISE TO HELP ME GET
A PLUG-IN FOR MY TEAMWORK CHANNELS DEVELOPED
STARTING IN MAY. HOW LONG IT MAY TAKE IS UP TO
THE PROGRAMMER'S AND HOW WELL WE INTERACT
TO GET IT DONE. I AM GOING TO STAY ON THEM
UNTIL MY PLUG-IN IS COMPLETED THE WAY
I HAVE IT CURRENTLY ENVISIONED.
I HAVE EDITED OUT THE IMAGES OF
TEAMWORK CHANNEL TOOL,
AS I HAVE A NEW, BETTER TOOL DESIGN!
WATCH MY CURRENT POSTS FOR MORE INFORMATION!!!
MID-APRIL 2018
IMPORTANT NOTICE !!!
THINGS ARE FINALLY HAPPENING!!!
I HAVE MET WITH METASTOCK'S MANAGEMENT,
AND HAVE GOTTEN THEIR PROMISE TO HELP ME GET
A PLUG-IN FOR MY TEAMWORK CHANNELS DEVELOPED
STARTING IN MAY. HOW LONG IT MAY TAKE IS UP TO
THE PROGRAMMER'S AND HOW WELL WE INTERACT
TO GET IT DONE. I AM GOING TO STAY ON THEM
UNTIL MY PLUG-IN IS COMPLETED THE WAY
I HAVE IT CURRENTLY ENVISIONED.
I HAVE EDITED OUT THE IMAGES OF
TEAMWORK CHANNEL TOOL,
AS I HAVE A NEW, BETTER TOOL DESIGN!
WATCH MY CURRENT POSTS FOR MORE INFORMATION!!!
In conclusion:
I've envisioned this tool, not just because I'd like TeamWork Channels to be easier for me, but so that they'd be easier for everyone. Plus, with this tool available in MetaStock, people who've never read my article or practiced TW-Channels in the tedious way we do now, will have a chance to use it. If MetaStock were modified this way, a lot of my own work would be easier, but it would also allow me to more readily share what I've learned about TW-Channels with the trading public.
JUMP TO MY NEXT POST
================================
Sunday, May 20, 2007
Post 010: Sorry for delay, technical difficulties!
I apologize for how long it has taken to come back and make a new posting. My old HP with XP on it got messed-up and when I got it back 'corrected' suddenly I could no longer log in to my Blogger editing tools, it would just keep redirected me back in an endless loop. I found that I could access it from any other computer, so now that I have a new system, I'm going to be posting again.
I'm surprised but pleased to note that I have several pretty consistent visitors that have spent a fair amount of time reading my posts. I am grateful to all visitors, but I'd really like to see some posts from you out there.
I'm going to be posting my desires for a TeamWork Channels tool in MetaStock, hopefully tomorrow. See you in my next post. -Robert
JUMP TO MY NEXT POST
=================================
I'm surprised but pleased to note that I have several pretty consistent visitors that have spent a fair amount of time reading my posts. I am grateful to all visitors, but I'd really like to see some posts from you out there.
I'm going to be posting my desires for a TeamWork Channels tool in MetaStock, hopefully tomorrow. See you in my next post. -Robert
JUMP TO MY NEXT POST
=================================
Friday, February 23, 2007
Post 009: TeamWork Channel Drawbacks
There is no Holy Grail of trading!!!Every indicator, system, and technical analysis tool out there has some weakness or drawback. Even fundamental analysis has its weaknesses. I will never say that the ERRC and TeamWork Channel are perfect and without drawbacks. If I did, even I wouldn't trust me!
The first, most obvious drawback is... ALL THOSE LINES make a very busy chart. To tell you the truth, when I first began working with TeamWork Channels, some of my teammates actually laughed at my charts. Did it hurt? Well,... the fact that I could put these channels to effective use, even if only for paper-trades, made it easy to ignore them.
Also, as mentioned in an earlier post, each line drawn in the chart adds a bit more workload for the CPU, and it's important for real-time charting to keep this to a minimum. As I've pointed-out before, you would normally reduce the total number of lines down until you only had those needed to surround the current price.
Unfortunately, because the ERRC, the Standard Error Channel, and the Standard Deviation Channel tools are designed to draw an upper- and a lower-line, you're always going to have and upper-band and a lower-band of channel lines, and almost always only of the two bands is doing anything useful. I've often wished there was a way to turn-off either the upper- or lower-line of the channels, to do away with the band that is doing nothing.
Drawing all the Std Err/Dev Channels needed for a TW Channel can be tedious. For now, one has to perservere, focusing on one's faith that the end-result will prove valuable. Creating one channel, and copying and pasting it, then changing the Units value is the best way to do this. There are other tips I can provide later.
If you happen to have some indicator in the chart, near where you are trying to drawn a TW Channel, it may tend to cause the channels to not drawn on the price plot but on the indicator. This is especially true of indicators that are placed in price window using the Overlay Without Scale option, like I do with my Serendipity Indicator.

On a chart like the one at the left, the thin solid-line of the ERRC is often hard to see amongst all those other lines.If you have a reason to make it stand-out, you can click on the ERRC line and choose to thicken the line, as shown in the chart on the right. You will find, though, that this will somewhat reduce the precision of the line's ability to chart the Support and Resistance points. I'm sure you'll see what I mean when you try it.
Finally, there is the the drawback of subjectivity. Before I came up with the ERRC, Raff Regression Channels were drawn in many different ways. In fact, I'd bet if you put 10 MetaStock users in a room, and gave them each the same chart to draw Raff Regression Channels on, no two charts would look alike. In fact, I'd be surprised if even one pair of channels between any of the charts shared the exact same dates for the Start Date and End Date.
The use of the Willaims%R indicator to draw the channel was, for me at least, the first step toward reducing the subjectivity of the Raff Regression Channel. The ERRC is a much more accurate and useful tool. It speeds placement, and increases the accuracy of the placement. The addition of my ERRC Color Coder Expert helped reduce subjectivity also. I've seen some charts on web pages that had Raff Regression Channels that not only were not extended to the right, but were willy-nilly drawn on every little switchback tertiary trend in the chart. To me, drawing these channels that way made no sense at all.
Extending the channel lines to the right helps validate/invalidate the channel, because it will show how effectively the lines 'predict' the Support and Resistance points. The parallel lines of a TeamWork Channel will also help validate the channel placement, and reduce subjectivity, by giving even more points for validity-testing.
We will never fully be able to eliminate subjectivity in drawing these channels, but I believe I have some strong and worthwhile ideas on reducing subjectivity to a minimum.
See you in my next post. -Robert
JUMP TO MY NEXT POST
=================================
Tuesday, February 20, 2007
Post 008: Are Channels Dynamic?
Many people have the opinion that the channel tools in MetaStock change their direction with each new tick of data that comes in. Well, they are right, IF they have made the mistake of placing the End Date of the channel on the last bar/candle of data in the chart. If the End Date (or End Time in Intraday charts) is the last data point in the chart, as new data comes in the end-point shifts up or down based on the new data, and that makes the channel's direction shift, making it virtually worthless for trading.
Properly drawn (or placed) ERRCs or TW Channels don't behave this way, as they will never use the last point of data for the End Date.
Once an ERRC or TeamWork Channel is properly placed and extended into the future, it will be ready to chart Support and Resistance levels as they happen; however, they DO NOT change as new data comes in. A channel that changes with new data is of no value at all for a trader, particular not for a real-time trader. So, every effort should be made to place these channels accurately. Be as certain as you possibly can be as to their accuracy before making trading decisions based on them.
Formulaic Versions of the Channel Tools Do the Same Thing
A co-worker of mine at my former employer, who was very skilled in writing formulas for MetaStock was asked to write a formula to reproduce the Raff Regression Channel. Did he succeed? Yes and No! Yes, he managed to create a formula that seemed to duplicate the Raff Regression Channel, but actually, it drew it backward.
His formula, perforce, initially he used the last date of data in the chart and picked the 'start date' for the channel virtually at random. Later, he 'refined' it to allow the entry of a specific Start Date back to which it would be drawn, but he still used the latest incoming data for the End Date/Time, hence it was dynamic and kept changing the direction of the lines as new data came in, making it, in my view, worthless for trading.
In other words, he could produce a very real looking pseudo-Raff Regression Channel, but it differed from the real thing in two critical ways. First, it was dynamic, because, since it used the last data point in the chart as the 'end date', as new data came in, the path of the channel changed; and, 2) any calculated formula in MetaStock cannot extend to the right beyond the last point of data in the chart, thus it has no ability to project the path of the channel into the future.
A formulaic channel like this, being calculated, instead of drawn, makes it possible for MetaStock to determine whether the price is above or below one of the lines of the channel, but the changing nature of the channel's path makes this aspect of little real value.
I've seen other formulaic reproductions of the various channels that are hand-drawn in MetaStock, but they each have the same flaws, so in my view, they are not worth much.
The ERRC and TeamWork Channel must be drawn on historical data, and extended to the right (into the future), thus the Start Date (SD) and End Date (ED), which make up the Hand-Drawn Range (HD Range) are fixed points in the past that cause the channel to follow a specific path into the future. If drawn correctly, this path will cause the channel to accurately chart points of Support and Resistance in the future that the savvy trader can use to aid with trading decisions.

As you review this chart from Post 004, I'll summarize and emphasize: The last point of data in the chart MUST NEVER BE USED for the end date of an ERRC or a TeamWork Channel! If you do this, you're wasting your time, as the unstable nature of the last point of data would very likely negatively impact your trading results.
So what are the drawbacks, if any, of using the ERRC and TeamWork Channel? We'll discuss this in the next post.
JUMP TO MY NEXT POST
=============================
Properly drawn (or placed) ERRCs or TW Channels don't behave this way, as they will never use the last point of data for the End Date.
Once an ERRC or TeamWork Channel is properly placed and extended into the future, it will be ready to chart Support and Resistance levels as they happen; however, they DO NOT change as new data comes in. A channel that changes with new data is of no value at all for a trader, particular not for a real-time trader. So, every effort should be made to place these channels accurately. Be as certain as you possibly can be as to their accuracy before making trading decisions based on them.
Formulaic Versions of the Channel Tools Do the Same Thing
A co-worker of mine at my former employer, who was very skilled in writing formulas for MetaStock was asked to write a formula to reproduce the Raff Regression Channel. Did he succeed? Yes and No! Yes, he managed to create a formula that seemed to duplicate the Raff Regression Channel, but actually, it drew it backward.
His formula, perforce, initially he used the last date of data in the chart and picked the 'start date' for the channel virtually at random. Later, he 'refined' it to allow the entry of a specific Start Date back to which it would be drawn, but he still used the latest incoming data for the End Date/Time, hence it was dynamic and kept changing the direction of the lines as new data came in, making it, in my view, worthless for trading.
In other words, he could produce a very real looking pseudo-Raff Regression Channel, but it differed from the real thing in two critical ways. First, it was dynamic, because, since it used the last data point in the chart as the 'end date', as new data came in, the path of the channel changed; and, 2) any calculated formula in MetaStock cannot extend to the right beyond the last point of data in the chart, thus it has no ability to project the path of the channel into the future.
A formulaic channel like this, being calculated, instead of drawn, makes it possible for MetaStock to determine whether the price is above or below one of the lines of the channel, but the changing nature of the channel's path makes this aspect of little real value.
I've seen other formulaic reproductions of the various channels that are hand-drawn in MetaStock, but they each have the same flaws, so in my view, they are not worth much.
The ERRC and TeamWork Channel must be drawn on historical data, and extended to the right (into the future), thus the Start Date (SD) and End Date (ED), which make up the Hand-Drawn Range (HD Range) are fixed points in the past that cause the channel to follow a specific path into the future. If drawn correctly, this path will cause the channel to accurately chart points of Support and Resistance in the future that the savvy trader can use to aid with trading decisions.
As you review this chart from Post 004, I'll summarize and emphasize: The last point of data in the chart MUST NEVER BE USED for the end date of an ERRC or a TeamWork Channel! If you do this, you're wasting your time, as the unstable nature of the last point of data would very likely negatively impact your trading results.
So what are the drawbacks, if any, of using the ERRC and TeamWork Channel? We'll discuss this in the next post.
JUMP TO MY NEXT POST
=============================
Monday, February 12, 2007
Post 007: Why do TW Channels Work?
Hopefully, by this time, you've seen enough to believe in the effectiveness of TeamWork Channels in charting Support and Resistance levels well into the future. Perhaps the thought has crossed your mind, "why/how are TeamWork Channels able to do this?" Here are my thoughts on this issue.
First, let's review what the various lines in TeamWork Channels are. Each TW Channel contains one ERRC, or Enhanced Raff Regression Channel; which is a Raff Regression Channel placed using the Williams'%R Indicator as a guide (my ERRC Color-Coder Expert helps me do this) and it is extended to the right. The TW Channel's parallel lines are created using Standard Error Channels and/or Standard Deviation Channels that use the same Start Date (SD) and End Date (ED) as the ERRC, but with incremental Units values to place them at different levels.
Let's review these three types of channels.
The makers of MetaStock, Equis International, describe the differences in the three channel tools in MetaStock on their web site's FAQs section:
What are the differences between the three channel tools...?
(There are actually four channel tools available in MetaStock now,
but the new Equi-Distant Channel is of no relevance to our discussions.)
Here's how MSN's Encarta defines: Standard Deviation
Here's how MSN's Encarta defines: Standard Error
Check out this Wikipedia article on: Standard Deviation
Check out this Wikipedia article on: Standard Error
The ERRC places its outer lines at the extreme distance from the Regression Line (RL)that the price moved anywhere in the SD to ED Range of the channel, either above or below the RL.
The Standard Deviation Channel places the outer lines based on the number of Standard Deviations you wish to use. The Standard Deviation is calculated on a Moving Average of the price movement within the SD to ED range, inclusive. It is a measure of how well the prices are adhering to the path of Moving Average.
The Standard Error Channel uses Units of Standard Errors to place the lines. Standard Error is calculated on the Regression Line, and is a measure of how well the prices are adhering to the path of the Regession Line. This is why I tend to have a preference for using Std Err Channels over Std Dev Channels for my TW Channels.
The ERRC and the TW Channel essentially measure the concensus of feeling for the stock during a particular trend, and when extended, they predictively chart levels of Support and Resistance based on the attitudes present during that trend.
TeamWork Channels don't just chart Support and Resistance to vertical price levels, but Support and Resistance to Rate/Speed of Price Change as well, indicated by the relative slope of the trend. Some move up rapidly, some down rapidly, others slope up/down gradually, and, in some cases the prices are moving sideways. You'll often see a TW channel impact the price plot and suddenly the price movement takes on the Rate of Change aspect of the TW Channel.
There is also a Volatility aspect of TW Channels. Some can use whole single-digit changes in the Units value to produce effective results, whereas others may require Units values incremented by half- or even quarter-Units. To put it another way, if you check the Units increment of the Standard Error Lines in a TW Channel, they may increment like this: 1, 2, 3, 4, 5,... 99. Others may run .5, 1, 1.5, 2, 2.5,... 99. Others, .25, .50, .75, 1, 1.25, 1.50, 1.75, 2.0,... 99. Experience in drawing TW Channels will give you skill at guessing which increment should be used.
I hope I've managed to express my opinion on why these channels work. I suppose the important thing is...they do!
JUMP TO MY NEXT POST
================================
First, let's review what the various lines in TeamWork Channels are. Each TW Channel contains one ERRC, or Enhanced Raff Regression Channel; which is a Raff Regression Channel placed using the Williams'%R Indicator as a guide (my ERRC Color-Coder Expert helps me do this) and it is extended to the right. The TW Channel's parallel lines are created using Standard Error Channels and/or Standard Deviation Channels that use the same Start Date (SD) and End Date (ED) as the ERRC, but with incremental Units values to place them at different levels.
Let's review these three types of channels.
The makers of MetaStock, Equis International, describe the differences in the three channel tools in MetaStock on their web site's FAQs section:
What are the differences between the three channel tools...?
(There are actually four channel tools available in MetaStock now,
but the new Equi-Distant Channel is of no relevance to our discussions.)
Here's how MSN's Encarta defines: Standard Deviation
Here's how MSN's Encarta defines: Standard Error
Check out this Wikipedia article on: Standard Deviation
Check out this Wikipedia article on: Standard Error
The ERRC places its outer lines at the extreme distance from the Regression Line (RL)that the price moved anywhere in the SD to ED Range of the channel, either above or below the RL.
The Standard Deviation Channel places the outer lines based on the number of Standard Deviations you wish to use. The Standard Deviation is calculated on a Moving Average of the price movement within the SD to ED range, inclusive. It is a measure of how well the prices are adhering to the path of Moving Average.
The Standard Error Channel uses Units of Standard Errors to place the lines. Standard Error is calculated on the Regression Line, and is a measure of how well the prices are adhering to the path of the Regession Line. This is why I tend to have a preference for using Std Err Channels over Std Dev Channels for my TW Channels.
The ERRC and the TW Channel essentially measure the concensus of feeling for the stock during a particular trend, and when extended, they predictively chart levels of Support and Resistance based on the attitudes present during that trend.
TeamWork Channels don't just chart Support and Resistance to vertical price levels, but Support and Resistance to Rate/Speed of Price Change as well, indicated by the relative slope of the trend. Some move up rapidly, some down rapidly, others slope up/down gradually, and, in some cases the prices are moving sideways. You'll often see a TW channel impact the price plot and suddenly the price movement takes on the Rate of Change aspect of the TW Channel.
There is also a Volatility aspect of TW Channels. Some can use whole single-digit changes in the Units value to produce effective results, whereas others may require Units values incremented by half- or even quarter-Units. To put it another way, if you check the Units increment of the Standard Error Lines in a TW Channel, they may increment like this: 1, 2, 3, 4, 5,... 99. Others may run .5, 1, 1.5, 2, 2.5,... 99. Others, .25, .50, .75, 1, 1.25, 1.50, 1.75, 2.0,... 99. Experience in drawing TW Channels will give you skill at guessing which increment should be used.
I hope I've managed to express my opinion on why these channels work. I suppose the important thing is...they do!
JUMP TO MY NEXT POST
================================
Tuesday, February 6, 2007
Post 006: The Fenceline & Overall TW Channels' Utility
THE FENCELINE CHANNEL
In Post #004, I mentioned that I almost always draw a "Fenceline Channel" just outside an ERRC that I've drawn, by setting the Units value so the Std Err Channel line is drawn just a little outside the ERRC's outer lines. Setting the distance it falls outside the ERRC outer line is a bit tricky, but it is critical to provide a worthwhile test of potential breakouts from the channel.
It's a bit hard to describe how I get the Fenceline Channel where I want it. Please review the two charts I'll post below. The one just below is similar to one we saw in Post #004. Note how the Outer Line of the ERRC falls almost half-way between the Fenceline Channel and the nearest Std Err Channel line just inside the ERRC. This makes for a good Fenceline Channel.

My rule of thumb for the distance a Possible Fencline Channel (PFC) must be outside the ERRC's outer line, can be stated like this, "the ERRC's outer line must be no closer to the PFC than 1/3rd the distance between the PFC and the first Std Err Channel line within the ERRC's outer line." If it is too close to the PFC another Std Err Channel will be used just a bit farther out, using a Units value at least .25 Units larger than the Units value used for the PFC.
Specific measurements are not needed,... "eye-balling" the distance is sufficient.
In the last illustration in this post, you'll see an upward-trending green TW Channel that shows a PFC that proved to be much too close to the ERRC's outer line. I set that line to red, though it's hard to see because it sits right next to the ERRC's outer line. I drew another Std Err Channel at another .5 Units distance outside the ERRC, to use as my Fenceline Channel.
My comments and illustrations thus far were aimed at giving you some hints on how I use the Fenceline Channel to test whether the price has exited sufficiently to be deemed a 'validated break-out' from the ERRC, ending the current trend. Basically, in a Daily chart, if the price Closes outside the Fenceline Channel, I deem it a "likely/tentative breakout", and I make a note to watch it the next day. If it then Closes back inside the ERRC's outer line, I assume the trend continues and the current ERRC is still in force. If on the next day the price continues is apparent breakout through the Fenceline Channel, I then assume the breakout from the ERRC is "real", meaning the trend has ended...and I use this to guide my trading decisions. Remember, it must Close outside the FenceLine Channel to be deemed even a "likely/tentative breakout".
THE OVERALL TW CHANNEL
In Post #005, I mentioned that I often draw an "Overall TW Channel" and promised you an illustration of how useful it can be. Below are two illustrations, both using a Daily chart of Microsoft (MSFT). The first shows a full view of all the data so you can see the placement of the Overall TW Channel. The second shows a close view near the end of the chart. You can see in both charts how the Overall TW Channel lines provide Support and Resistance at key places. The second chart makes this more readily visible.

Overall TW Channel SD: 07/01/1986 & ED: 09/26/2000

I think you can see that the Overall TW Channel can indeed provide strong clues as to how the price will behave. It can often explain why the price stalls (finds Resistance/Support) at certain levels where, on a normal chart, there is no clue as to why it is doing so. It is my belief that when such mysterious price behavior occurs, placing additional accurately placed Teamwork Channels in the chart will reveal the Resistance/Support that is causing the seemingly anomalous price behavior.
Remember, please, that in these illustrative charts, I will draw more Std Err/Dev Channels than I would normally use in my charts. For instance, in the first of the two charts just above, I've drawn them top to bottom of the Overall TW Channel. Initially, when analysing the validity of the Overall TW Channel, this many lines would be useful, but once assured it was placed properly, I would normally remove all but a few of them. All I really need is enough of them to surround the current price, to give me clues as to what the price might do.
JUMP TO MY NEXT POST
========= See you in my next post....-Robert ========
In Post #004, I mentioned that I almost always draw a "Fenceline Channel" just outside an ERRC that I've drawn, by setting the Units value so the Std Err Channel line is drawn just a little outside the ERRC's outer lines. Setting the distance it falls outside the ERRC outer line is a bit tricky, but it is critical to provide a worthwhile test of potential breakouts from the channel.
It's a bit hard to describe how I get the Fenceline Channel where I want it. Please review the two charts I'll post below. The one just below is similar to one we saw in Post #004. Note how the Outer Line of the ERRC falls almost half-way between the Fenceline Channel and the nearest Std Err Channel line just inside the ERRC. This makes for a good Fenceline Channel.
My rule of thumb for the distance a Possible Fencline Channel (PFC) must be outside the ERRC's outer line, can be stated like this, "the ERRC's outer line must be no closer to the PFC than 1/3rd the distance between the PFC and the first Std Err Channel line within the ERRC's outer line." If it is too close to the PFC another Std Err Channel will be used just a bit farther out, using a Units value at least .25 Units larger than the Units value used for the PFC.
Specific measurements are not needed,... "eye-balling" the distance is sufficient.
In the last illustration in this post, you'll see an upward-trending green TW Channel that shows a PFC that proved to be much too close to the ERRC's outer line. I set that line to red, though it's hard to see because it sits right next to the ERRC's outer line. I drew another Std Err Channel at another .5 Units distance outside the ERRC, to use as my Fenceline Channel.
My comments and illustrations thus far were aimed at giving you some hints on how I use the Fenceline Channel to test whether the price has exited sufficiently to be deemed a 'validated break-out' from the ERRC, ending the current trend. Basically, in a Daily chart, if the price Closes outside the Fenceline Channel, I deem it a "likely/tentative breakout", and I make a note to watch it the next day. If it then Closes back inside the ERRC's outer line, I assume the trend continues and the current ERRC is still in force. If on the next day the price continues is apparent breakout through the Fenceline Channel, I then assume the breakout from the ERRC is "real", meaning the trend has ended...and I use this to guide my trading decisions. Remember, it must Close outside the FenceLine Channel to be deemed even a "likely/tentative breakout".
THE OVERALL TW CHANNEL
In Post #005, I mentioned that I often draw an "Overall TW Channel" and promised you an illustration of how useful it can be. Below are two illustrations, both using a Daily chart of Microsoft (MSFT). The first shows a full view of all the data so you can see the placement of the Overall TW Channel. The second shows a close view near the end of the chart. You can see in both charts how the Overall TW Channel lines provide Support and Resistance at key places. The second chart makes this more readily visible.
Overall TW Channel SD: 07/01/1986 & ED: 09/26/2000
I think you can see that the Overall TW Channel can indeed provide strong clues as to how the price will behave. It can often explain why the price stalls (finds Resistance/Support) at certain levels where, on a normal chart, there is no clue as to why it is doing so. It is my belief that when such mysterious price behavior occurs, placing additional accurately placed Teamwork Channels in the chart will reveal the Resistance/Support that is causing the seemingly anomalous price behavior.
Remember, please, that in these illustrative charts, I will draw more Std Err/Dev Channels than I would normally use in my charts. For instance, in the first of the two charts just above, I've drawn them top to bottom of the Overall TW Channel. Initially, when analysing the validity of the Overall TW Channel, this many lines would be useful, but once assured it was placed properly, I would normally remove all but a few of them. All I really need is enough of them to surround the current price, to give me clues as to what the price might do.
JUMP TO MY NEXT POST
========= See you in my next post....-Robert ========
Subscribe to:
Posts (Atom)








