Libraries: BestInterval - page 16

New comment
 
I would love this for mt4. Please create a update for mt4.
 
Revo Trades:
I would love this for mt4. Please create a update for mt4.

This library should work on this platform.

 

I have the following problem.

With BestInterval Action == false everything is fine.

With BestInterval Action == true I have the following:

Enable Section:

#include <MT4Orders.mqh>  // https:// www.mql5.com/en/code/16006  

#define BESTINTERVAL_ONTESTER  // Optimisation criterion - profit of the best interval.  
 
// # define VIRTUAL_TESTER // Launch in a virtual trading environment  
 
#include <fxsaber / Virtual / Virtual.mqh>  // https:// www.mql5.com/en/code/22577  
 
#include <fxsaber / BestInterval / BestInterval. mqh>  // https://www.mql5.com / ru / code / 22710  

#include <../ Experts / fxsaber / TesterEA / TesterEA.mq4>

I downloaded the latest files (from the Russian section). There are no compilation errors or warnings. I am running MT5 build 2085.

What could be the problem?

Files:
tester.log  5 kb
 
Enrique Dangeroux:

What could be the problem?

There was a discussion in private messages last week about the operation of this library. Once again, it was found to be working correctly.

Please attach the tester logs in full.

 
fxsaber :

There was a discussion in private messages last week about the operation of this library. Once again, it was found to be working correctly.

Please attach full logs of the tester.

Thanks for the reply. The log is attached to the previous post.

 
Enrique Dangeroux:

Unfortunately I can't reproduce the problem.

It is better to download fresh mqh files separately.

 

Yes, the code base files are all a mess (no Deal_Base.mqh in the BestInterval zip file, different versions for different languages, etc. Д.).

I downloaded separate files for BestInterval, Virtual and MT4Orders from the Russian section. That solved the problem.

Thanks again for your support!

 

I got these results:

You can see that 2 segments of 2 seconds each are cut. Perhaps it makes sense to limit the minimum size of the cut interval?


ps: the latest build of MT5 has a lot of warnings "deprecated behaviour, hidden method calling will be disabled in a future MQL compiler version" during compilation.

 

Is there an easy way to leave your OnTester working after connecting BestInterval?

It doesn't help:

#define  BESTINTERVAL_CALL_ONFUNCTIONS // In BESTINTERVAL_ONTESTER mode OnTester and OnTimer will be called.

It still returns the final balance (and you need your own complex criterion, BESTINTERVAL_ONTESTER_FORMULA doesn't solve the problem).

 
Andrey Khatimlianskii:

I got these results:

You can see that 2 segments of 2 seconds each are cut. Perhaps it makes sense to limit the minimum size of the cut interval?

You have one trade being thrown out at a time. This means that you can still trade a second BEFORE it opens and a second AFTER. Hence you get two seconds.

ps: the latest MT5 build has a lot of warnings "deprecated behaviour, hidden method calling will be disabled in a future MQL compiler version" when compiling.

Sent it to a private message. Unfortunately, kodobase does not accept the corrected version yet.

1...91011121314151617181920212223...29
New comment