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
It will work properly if you make MT4Orders enclode before BestInterval.
The library concerns only trading operations and their history. Moreover, it can work in parallel with SB and others.
So indicators do not affect it in any way.
BestInterval on netting only in one specific case (made for myself) takes the trading history correctly.
What is this case, if it is not a secret? Maybe I can use something similar without shamanism.
What's the case, if it's not a secret? I might be able to use something similar without any shamanism.
A shapeshifting TC.
I can't answer that. I don't know yet.
To say I'm pleased is clearly an understatement..... BestInterval is awesome now. And the changes are minimal. As always, an example.
Here's a 24-hour pass.
We apply the classic BestInterval.
We can see that the profit has increased by one third, and other indicators have become better.
But we wanted flexibility. And here it is.
Profit didn't increase, it decreased! But look at the other indicators. Instead of finding the interval with the highest profit and probability of fitting, a much narrower interval was found, but much tastier than the classic.
The innovation is added like this
The quality of market pattern research is now very much improved. Significant implications for multi-tester work.
So 150 trades is a much more likely fit, no?
Thenumber of trades depends on the length of the interval.
Sometimes the deletion of intervals gets screwed up. Namely
const double Profit = dDeals[i].Profit + SlipPerLot * dDeals[i].Lots;
produces NaN because dDeals[i].Lots equals NaN at i=0.
It seems that the legs grow from the int Set( const DEAL &dDeals[] ) function where the Lots field is not filled when Amount=0. Or is it more correct to say that Lots is not filled in void ToNull( void )?
But in any case, the bug is very unpleasant, rarely occurring and not easy to debug.
But in any case the bug is very unpleasant, rarely manifested and not easy to debug.
Yes, I was happy to post it without checking it properly. I'll check it out, thanks.
I have corrected the int Set( const DEAL &dDeals[] ) function by filling Lots with zero. If I've fixed it wrong or missed something else, please write me back. Thanks.
So far I have done only this
The rest does not need to be corrected for Lots. But there are errors related to another (old). Need to be corrected.