Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Perry does not mention the ADX in post 71 which documents his rules. However, unless I'm mistaken he mentions in other posts that we need to confirm the ADX as rising for longs and shorts as well as the relative position of the DMPlus and DMMinus lines. The 2 bars you marked on your chart have the dmplus and dmminus lines in correct position but the ADX isn't rising. Therefore, no trigger bar.
Also just to clarify, this indicator encapsulates the strictest interpretation of Perrry's rules which includes what I mention above. I understand that Perry doesn't require the rising ADX 100% of the time. I saw a post from him that said he doesn't always wait for the ADX. However, I opted to include the ADX requirement in this indicator.
Regarding the proximity to 20EMA...the only requirement per post 71 is that the 20ema is rising or falling appropriately.
Just to be sure, if anyone has another take on Perry's rules, please correct me but they seem to be pretty clear regarding the things I've mentioned.
I think you are missing a rule per Perry's method for determining the signal bar.
The low of the range bar has to touch or be less than the EMA 20 and the high has to be greater than the EMA 5 to qualify as a signal bar (in addition to the other rules).
No problem at all. I could have been wrong too. Good that others are looking at it critically. That's the only way to truly find out if I have it coded correctly. The other thing I've wondered is if I should modify it so it colors the dot and line one color if Perry's rules are met exactly as post 71 says and color the dot differently if the post 71 rules are met as well as the DMPlus conditions.
Based on the conversation I've had with a couple people, I revisited the rules as I have them coded. Currently, they are coded in the strictest way using both the rules in Perry's post #71 plus the ADX, DMPlus, and DMMinus being in the proper condition. However, in the conversations it became apparent to me that I should probably open up the rules a bit to allow for signals when the basic rules as defined in post #71 are true as well. As Perry has mentioned, he takes some entries when the ADX is against him. So, when you load version 2, you will notice black lines which show entries that meet only the post #71 rules. You will also see dots and lines of the same color when both post #71 rules, ADX, DMPlus, and DMMinus conditions are met.
I am attaching a picture along with the zip files.
I would like some feedback on whether or not this indicator is useful to anyone. If it isn't useful, I will stop my effort and move on to something else that you all think is useful. I'm soliciting ideas if anyone has any they want help with.
The following is an UPDATE of how to trade method 1 in an easy and more relaxed fashion increasing the probabilty for success.
1. Take an 8 Range chart and put the exact setup indicators on this charts.
2. Next to the 8 range chart have your usual 4 …
, page47, post # 465, multi- time- frame may give higher probabilities and maybe less stress.
I used 4 and 8 Range to generate ES 13October 2010 chart in NT 7.0.0.22 using the curent updated DMPlussignal_v2. The attached screenshot shows uneven bar spacing in 4 Range (main data series) as well as 8 Range (sencondary data series).
I'm not able to write a custom indicator to correct the shortage of NT 7 Multi Data Series. Could you kindly help? TIA!
Thanks for your efforts. Can you tell me why you use Round2TickSize on the close/low/high price values?
The price values should always be at the tick intervals for the particular instrument so could the rounding issue you talked about a few posts back be solve by not rounding price?
Unfortunately not. Even though you see price as 83.00, under the hood of NT it may or may not be 83.00. Most likely it's 83.00000000045678. Don't blame that on NT either. That's a precision issue with programming languages.
