Yes, that is the topic I meant.
JSParticipant
Senior
Hi,
Just to clarify…
You’re using “ignore1hourtimeframe” in the line “ignore1hourtimeframe, cb2 = CALL “indicator21″”…
Are you sure you’re allowed or able to use this? Where does it come from?
Also, cb2 = average[200](Close), but cb2 isn’t used in any specific condition.
So you’re just calling an average with: ignore1hourtimeframe, cb2 = CALL “indicator21”.
JS this has not been a problem for multiple years. I am testing the same code from 4 years back, which now has changed backtest results.
It is a serverside issue.
You can do it with any indicator and try. I just came up with a random one.
If you do not use updateonclose the backtest is shown wrongly. It does not matter what the indicator is.
And once again this has not been a issue for over 6 years of using multi timeframe. I litterelly tested over 10 systems even systems imported with correct backtest, which now shown wrong.
And there is nothing wrong with the calling I just did. I have been calling indicator for years even before on a version you could just have same ignore variable across different timeframes. After that the new version of PRT encourage you to rename it on a new timeframe.
You can name it ignore1, ignore2 etc. It does not work on ANY CODE which it has done for mulitple years, something has changed over the last week/weeks. I just wrote that code to show a simple explanation of it.
Also ProRealTime seems to be aware of this issue and it will hopefully be fixed any time soon.
It’s usually the same problem… most people forget “updateonclose” in complex MTF systems.
phoentzs this is not about forgeting. This has never been a problem for several years. I noticed it 2 days ago when backtesting a system and I was shocked by the results. Then I started testing all my systems with calling indicators. All systems that have been totally fine over the years (but changed totally now). It is a serverside problem on PRT, not about forgetting updateonclose.
It is only happening when CALL the indicator. If you have the same system without call function from indicator, you get another backtest result WITHOUT updateonclose.
Also PRT seem to have commented it on being adressed, so how come you still point at the updateonclose?
I’m not familiar with the calling function of external indicators… I simply don’t use it. I only use indicators, or let’s say, trading decisions, within a system. And if you omit “updateonclose,” you get a completely different result. But it’s always been that way.
But why do you comment it is the same problem as usual, if you do not understand the problem or checked yourself?
I am calm, I justed asked. It is just confusing you saying it is the same problem like there is some other underlaying issue. I just wanted to ask incase you had a solution.
Sorry if it came out wrong.
Because it often happened that people were surprised that their system didn’t do what they expected… the solution was this one little word.
