There was one other issue I had some questions and will illustrate with the attached chart. The red down arrows at around 8 am on the 28th show short signals based on the price action lower low being valid and other signals. I am using the formula based on the older version:
Now the swing continues downwards after hours where you see 3 red arrows at the swing low point (-30.5 point swing and 17 bars). Exhaustive testing suggests entering too late into the trend reduces the probabilities of a winning trade significantly. This charts shows entries at bars 14, 15 and 16 as per the 3 down arrows which is too late for this NQ instrument. We can see in the statistics at the bottom that the average swing length is 9 bars down. What I would like to do is have a filter that limits the signal based on the number of bars that have elapsed in the swing so in this case it would be something like:
if priceSwingRel ==-1 && swing bars elapsed <9. Assuming you require 5 bars for a valid swing that leaves another 4 bars to play with. In the attached chart this would eliminate those 3 signals. Any ideas on how to achieve this would be appreciated.
I wanted to install the indicator for NT6.5 but wen I entry on NTs website to install the NT7 it said that I need Windows 7 but I have Windos Vista. Is there anyway to install it without having Windows 7?
Thank you Dorschden for such a good work.
Last edited by Felix trader; April 8th, 2011 at 04:31 PM.
Thanks again for posting the update. I had so many indicators linking to this one that the changeover from version 1 to 2 took so long to complete. Once installed I discovered a problem which not sure how to fix.
When I set the statistic to "bottom" or anything else, the statistics box is not showing up like it did with version 1. I am using the latest .4 version. I notice the priceactionswingrelation file is no longer used so not sure and has been updated with the new priceactionswingtrend indicator.
Yes this is possible. You can use the following code for this. Add the two variables in the variables region and the rest of this code in the end of the OnBarUpdate function (didn't test it, but something like this should do the trick):
The following 7 users say Thank You to dorschden for this post: