
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
...
OK. Lets try this way :
How many bars does the indicator have to recalculate?
Second case :
Now how many bars have to be recalculated now?
_______________________________
In both case it must be 100
_______________________________
That problem is solved with "asking" EURGBP chart how many bars it has changed and then using the bigger of the 2 : current chart changed bars and EURGBP changed bars. And you do not have to attach it to any other chart : the indicator is doing all that for itself
hope this helped
Dear Mladen,
please ,what's mean of this line code ? why does it try to compare symbol with "returnBars" ? should i attach another MACDTest with symbol="returnBars" on the current symbol?
returnBars = (symbol=="returnBars"); if (returnBars) return(0);acushnir,thanks for your patience,i got it.
But one more question please,to my understanding,if for EURUSD, 2 bars are changed,i feel that EURGBP also have 2 bars changed since each bar garnered by each 15 mins(15 timeframe) even if there is no price changed,so i think the number of bars should be same regardless of whether it is EURUSD or EURGBP. Please advice me.
I changed a bit and I tested it and works fine to me:
I've used a EURUSD chart and I've choosed USDCHF for the indicator.
To be sure, then I've opened a USDCHF chart and attached a standard MACD indicator and the figures match perfectly
Check it :-)
Best regards and happy trading!!!
OK. Lets try this way :
How many bars does the indicator have to recalculate?
Second case :
Now how many bars have to be recalculated now?
_______________________________
In both case it must be 100
_______________________________
That problem is solved with "asking" EURGBP chart how many bars it has changed and then using the bigger of the 2 : current chart changed bars and EURGBP changed bars. And you do not have to attach it to any other chart : the indicator is doing all that for itself
hope this helped...
It is not so
Each symbol "has a life of its own". They do not have to be synchronized (in the times of change) at all. It is not working on a "generate a tick per nnn seconds or milliseconds, but a tick is generated if the price have changed. So, treat each and every symbol as a complete different entity
acushnir,thanks for your patience,i got it. But one more question please,to my understanding,if for EURUSD, 2 bars are changed,i feel that EURGBP also have 2 bars changed since each bar garnered by each 15 mins(15 timeframe) even if there is no price changed,so i think the number of bars should be same regardless of whether it is EURUSD or EURGBP. Please advice me.
Hi mladen,i did test your MACDTest indicator with demo account,it works well.but when i tried to do Backtesting with history data,the wrong chart again...
How did you test it ? does it work well with history at your machine ?
Thanks!
It is not so Each symbol "has a life of its own". They do not have to be synchronized (in the times of change) at all. It is not working on a "generate a tick per nnn seconds or milliseconds, but a tick is generated if the price have changed. So, treat each and every symbol as a complete different entity
...
Use this one
Also make sure that you have data for the target symbol (EURGBP by default) downloaded for the period you are testing too) Otherwise you are nt going to get data calculated in the back test (back test does not work as the run-time normal execution)
Hi mladen,i did test your MACDTest indicator with demo account,it works well.but when i tried to do Backtesting with history data,the wrong chart again...
How did you test it ? does it work well with history at your machine ?
Thanks!wow ,great!! it works well with history data! Mladen, i appreciate your help!
Use this one Also make sure that you have data for the target symbol (EURGBP by default) downloaded for the period you are testing too) Otherwise you are nt going to get data calculated in the back test (back test does not work as the run-time normal execution)