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)
But whatever I set x to, it doesn't affect my strategy,. The exact same orders are placed, so I'm wondering what I am doing wrong? Do I need to make a function like, current ADX or?
Thank you in advance!
Can you help answer these questions from other members on NexusFi?
I could only guess without seeing the full code, but the first thing I'd check is what the value of trendADX is on each bar.
If this doesn't qualify for an entry, but the entry is taken anyway, the problem is somewhere else within your code.
I have a strategy that produces orders and works. EURUSD, 15min.
I have added in the condition1: .......ADX(14)>20;
This does affect the netprofit slightly, but it still produces orders when ADX is below 20 which is very weird. If I then change the value to ADX>50, then it also affects the net profit slightly, but number of trades is almost the same and this does not make any sense at it is quite rare that ADX is above 50 for my signals....
My question is therefore, is my value for ADX "wrong"?
your code snippet appears to call the function correctly - under the condition that this is the original build in function of course.
I am afraid with your code snippet no one but you will be able to answer if "is my value for ADX "wrong"". You need to check the values on your end (either with prints or by making them available to an indicator using i_SetPlotValue for example).
However the problem is likely somewhere else in your code. But for anyone to be able to help you, you'd either have to post the full code or create a demo code that shows the same behavior.
sounds even more like the ADX not being the issue here.
One thing I would suggest though is, not to call the functions directly within the conditions. Call it upfront, store the value in a variable and then use the variable in your checks. You can refer to the build in ADX indicator as an example.
Otherwise you risk that "Series functions can return incorrect results if called within conditional statements" (this quote is from the Tradestation wiki).
