MetaEditor build 1490 - page 7

 
fxsaber:

The screenshots show the same place

The candles do not match each other

double accounting
 
A100:
double-entry bookkeeping

There are people on this forum, for all their love of MT5 they would be competent enough to write a smashing argumentative smear on MT5 with a remarkable reproducible evidence base.

If they knew MT5 at least on an average level, they would have succeeded in this task.

Well the quantity of features should not take precedence over their quality.

 

Error in the result of EnumToString

void OnStart()
{
    Print( EnumToString( SYMBOL_CALC_MODE_EXCH_FUTURES_FORTS ));
}
Result: SYMBOL_CALC_MODE_EXCH_OPTIONS
 
fxsaber:

1491 - Alpari-MT5-Demo. The screenshots show the same place

Terminal

Real tick tester

The candlesticks do not match each other - in the tester they are fluffy. Moreover, the historical time of the tester and the terminal differ by one hour.

CopyTicks in the terminal returns data as in the tester - one hour difference. Therefore, the ticks do not match the bars completely.

So how to trust MT5, the tester, when there is a complete self-discredit? Why don't the developers have benchmark EAs to run in the tester and know for sure that it works clearly? It's a complete mess.

Look at the logs during testing and contact Alpari technical support.

They uploaded themselves blatantly erroneous data that diverged from the ticks. It has nothing to do with the platform and you know it very well. Even the explicit indication of the discrepancy in the logs was ignored.

 
Renat Fatkhullin:

Look at the logs during testing and contact Alpari's technical support.

They uploaded themselves blatantly erroneous data that is at odds with the ticks. It has nothing to do with the platform and you know it very well. Even the explicit indication of the discrepancy in the logs was ignored.

Forum on trading, automated trading systems and strategy testing

Test EA based on ticks

fxsaber, 2016.12.07 12:31

The SD said they will think about how to make "foolproof" so that the "History Quality" field has an adequate value in the report.

In fact, the TC has been misled by the tester as there is no protection. And history mismatch errors can now only be detected in the tester's log not without difficulty - a needle in a haystack.

Unfortunately, the Market States suffer from the same malaise.

Have a look at SD's submission #1623308. You guys love to label things.

It's not those who report errors who discredit the platform, it's those who create those errors - Alpari in particular. Why are they allowed to sabotage MT5's reputation like this?

 
fxsaber:

Look at the BOD on application #1623308. You love to put labels on it.

It's not those who report errors who discredit the platform, it's those who create those errors - Alpari in particular. Why are they allowed to sabotage the reputation of MT5 in this way?

Discredited by those who understand everything, but pretend that the admin error is the platform's problem.

Are you allowed to crap like this?

 
Renat Fatkhullin:


They pumped themselves up with blatantly wrong data, at odds with the tics.

I don't get it - where did they get it from? Doesn't each DT have its own ticker history based on the LPs connected to their aggregator?
 
Renat Fatkhullin:

Discredit those who understand everything, but pretend that admin error is the platform's problem.

Are you allowed to crap like that?

Not allowed, of course. Unfortunately, I didn't realise it was an admin error. The SD said so, referring to the logs. But it's almost impossible to see this error in the logs, unless you specifically look for it. And in the report, the "Modeling quality" field says n/a. So how could one understand to look for this particular error in a log with many thousands of entries in addition to these?

I'm still more or less advanced in MT5 and I didn't find this error. And what about others who just take in the Market and enjoy the grail in the tester, as it happened in the mentioned thread?

 
ivanivan_11:
One thing I don't understand is where did they get them from? Doesn't each dtz have its own ticker history based on the LPs connected to their aggregator?
Good question. And why can they even do that, why the "market overview" does not match, not just in the history, not even on the open chart!
 
Interesting girls dance that's the news (
Reason: