Palinuro, response in bold below:
Quote from palinuro:
ScottD,
Interesting work - thanks for the report. Are the test results improving as a consequence of these additions?
Yes, the results are improving per se, but not where they need to be yet. Our Dec 10 focus day, for example, is not a profitable day yet. There are certain areas where I am unclear, and I suspect those are the most promising areas for improvement.
Does 'awayness' represent MacD histogram > 0?
Nope. Think of the Rocket style thresholding. Also think of the absolute values so that you are accommodative of longs and shorts.
Your new pace table is in line with the NT 'autopace' results - did you ever find out why TN has lower levels?
As you know, calculating Pace over a non stationary window is actually very simple at a concept level -- grab the relevant RTH bar data, sort it from max to min, and then slice it into deciles.
I did my original Pace table by hand in Excel. Then I automated it. Then I found Vorzo's very nice version. Vorzo's matched mine within a very small variation due to rounding -- specifically the way that he chose to slice datasets where the number of elements is not evenly divided by 10 (decile slices).
If Trade Navigator shows significantly different pace levels than posted here as at Dec 10, 2008, then TN probably has a bug in the code or a problem in its historical time/volume data set. To do a precise diagnosis as to why TN values seem significantly too low, one would need to know if TN excludes any of the first or last bars of RTH (i.e. pre-sync and pre-end effect bars) and whether it excludes unusually slow periods like holidays. Also would need to verify that it uses 22 trading (not calendar) days of data. Once the algorithm is validated, one would need to compare the data sets.
& congrats on the recovery-
thanks!
- palinuro