Software Used to Trade Jack Hershey Methods
- Thread starter Tums
- Start date
Hi Ljyoung,
There are a "special" set of keys for the Channel drawing for those who are using a laptop that don't have the usual Numpad
(I had the same problem when I code the script)
key "INSERT" = Create new Channel
key "DELETE" = Delete new Channel
key "OEM6" (in my keyboard it is labeled "«") = Change Color
key "OEM1" (in my keyboard it is labeled "+") = Increase Width
key "OEM2" (in my keyboard it is labeled " ' ") = Decrease Width
But you probably need to find these OEM keys yourself, as they change depending of the keyboard.
HTH,
Pepe.
PS: This logic is done in the "chart_KeyDown" method (line 1024) of the PP_Channel.cs script, for those who want to know.
There are a "special" set of keys for the Channel drawing for those who are using a laptop that don't have the usual Numpad
(I had the same problem when I code the script)
key "INSERT" = Create new Channel
key "DELETE" = Delete new Channel
key "OEM6" (in my keyboard it is labeled "«") = Change Color
key "OEM1" (in my keyboard it is labeled "+") = Increase Width
key "OEM2" (in my keyboard it is labeled " ' ") = Decrease Width
But you probably need to find these OEM keys yourself, as they change depending of the keyboard.
HTH,
Pepe.
PS: This logic is done in the "chart_KeyDown" method (line 1024) of the PP_Channel.cs script, for those who want to know.
I have noticed that pace-levels vary a lot across different platforms. I'm using TN (Thanks Spyder), and I'm very happy with it so far. In the Interative Thread people regularly post their pace-levels, last time some days ago.
These posted values are very different from the autogenerated ones in TN. A lot higher levels. That also goes for the pace line code in NinjaTrader.
Have anyone thought about this issue?
(the algorithm should be fairly simple)
These posted values are very different from the autogenerated ones in TN. A lot higher levels. That also goes for the pace line code in NinjaTrader.
Have anyone thought about this issue?
(the algorithm should be fairly simple)
Spydertrader described the method to calculating pace lines in this post.
http://www.elitetrader.com/vb/showthread.php?s=&postid=1660501#post1660501
Aside from data vendor issues, the next thing that comes to mind is that the "starting point" for the calculation differs from person to person. What Spyder has said is what makosgu said, so I don't think there has been anything lost in that translation. As you say the algorithm is straightforward. That taps me out this AM.
HTH
lj
Morten,
I really don't think it's worth worrying that much about absolutely precise values for DU. I rechecked my script for accuracy; here, just for informational purposes, are the parameters and stats for Monday-Thursday of last week:
Current Date = 07/11/2008 3:35:00 PM
Total Days = 4
Total Bars Included (1530 - 2200) = 312
Total Bars on Chart = 324
Highest Volume = 127773 @ 05/11/2008 10:00:00 PM
5 Minute decile 10 Volume > 47436 H-L Range = 6.99, C-O Range = 3.1
5 Minute decile 9 Volume < 47436 H-L Range = 5.31, C-O Range = 2.93
5 Minute decile 8 Volume < 39621 H-L Range = 4.35, C-O Range = 1.9
5 Minute decile 7 Volume < 32805 H-L Range = 4.49, C-O Range = 2.18
5 Minute decile 6 Volume < 28257 H-L Range = 3.97, C-O Range = 1.96
5 Minute decile 5 Volume < 24359 H-L Range = 3.6, C-O Range = 1.71
5 Minute decile 4 Volume < 20886 H-L Range = 3.54, C-O Range = 1.42
5 Minute decile 3 Volume < 17345 H-L Range = 3.02, C-O Range = 1.13
5 Minute decile 2 Volume < 14209 H-L Range = 2.71, C-O Range = 1.15
5 Minute decile 1 Volume < 11232 H-L Range = 2.27, C-O Range = 0.94
Lowest Volume = 5649 @ 04/11/2008 6:55:00 PM
Obviously that's too small a sample for the values to be used, but you can see that nothing magical happens when you go from DU to Slow, or from any one level to another.
IMHO the most important thing is to understand the general significance in terms of pace and relative strength of the levels you are using, whatever their precise values.
- palinuro
Here's the updated AutoPace indicator for NT. Aside from a few corrections, the main differences are:
1. Now all deciles, plus lowest and highest, are available. The defaults are set to the standard levels, plus the lowest.
2. A "suspiciously low volume" filter has been added. This was a workaround for a bug in NT 6.5 (now fixed), but it works well for filtering out half days, holiday trading, etc., so I've kept it. You can comment out lines 90 and 108 if you don't want it.
3. The "printstats" option now prints the stats (in my post above) to the output window and to a file in the "Documents/NinjaTrader 6.5" folder.
As before, the user selects the number of days for daily charts. On intraday charts, all days loaded into the chart are processed, while the user selects start and stop times. (Note that NT's "days back" parameter refers to calendar days, not market days.)
- palinuro
1. Now all deciles, plus lowest and highest, are available. The defaults are set to the standard levels, plus the lowest.
2. A "suspiciously low volume" filter has been added. This was a workaround for a bug in NT 6.5 (now fixed), but it works well for filtering out half days, holiday trading, etc., so I've kept it. You can comment out lines 90 and 108 if you don't want it.
3. The "printstats" option now prints the stats (in my post above) to the output window and to a file in the "Documents/NinjaTrader 6.5" folder.
As before, the user selects the number of days for daily charts. On intraday charts, all days loaded into the chart are processed, while the user selects start and stop times. (Note that NT's "days back" parameter refers to calendar days, not market days.)
- palinuro