I have numerous indicators and methods that I would like to port over to NT but my programing attributes are disgracfully bad.
The idea would be to start simple and small with both my learning and in trying to find "help". I definetly do not want something for nothing and I believe that some of these ideas would help new and experienced people.
The ATR target is very simple in form and formula. It would be easy to code and easy for anyone to apply or evaluate.
This is a screen shot that includes a version of what I am talking about. The dashed purple and dashed green lines are 3 times the 34 period atr. The outer grey line is 4.23 times the 34 period atr. I also ploted a 2.618 times the 34 peratr. Perfect would be a set of bands where the atr multiple expands or contracts based on price volatility. I never figured that out but felt that I was close.
I have the script (two versions) in another platforms language They are both very similar to tradestation easy language.
The chart represents a hierarchy of non-colinears that was designed to trade price pressure. Some of the work is my own. Some is adapted from the work of others and some is the result of a colaboration here in Chicago. I would need to ask before sharing the colaborative effort here, but since that work is posted publically elsewhere I do not think it will be an issue.
Fat Tails let me know if you care to assist with the programing. I would be happy to share the details of trade set ups here. Some will find it valuable others will offer helpful ideas for improvment.
is it Fat Tails. That does look similar but I can't see direct comparison. I would be suprised or maybe not that much to have tried to create something that was easily available. There are a few things with how Keltners calc is a little different I think.
After I make my number, I will type out the code in a post. Maybe we can compare it to Keltner. What I was really looking for was a variable that would increase or decrease the band distance based on some, maybe the same, volatility condition.
Input has two periods, one for the moving average, one for the average true range. The standard Keltner Channels use the same period for both, the Universal Keltner Channel (Downloads) allows for two different periods. As both periods are set to 34, the default Keltner Channel would do.
The XAverage function of TradeStation is an EMA. The default Keltner Channel uses a SMA, so you cannot use the default Keltner Channel. Therefore you need to take the Universal Keltner Channel and set it to EMA/EMA, as both moving average and the average true range use exponential moving averages.
Attached is a 3-min chart for ES with the bands applied and multipliers set to 2.618 and 3.0. I noticed that you use different multipliers in your set up.
The following user says Thank You to Fat Tails for this post:
I am going to work on that a bit and study what you are telling me Fat Tails. The display does not have the same look so I'll review the math. The lines in your example ate 3 times and 2.618 times the 34 period average true range. That script I posted defines Keltner Channel?