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 would be nice to add a function to check the status of ticks uploaded/injected - in the local terminal database. Something like CheckXXX( symbol ). So you don't have to keep pulling the copitic all the time.
Will the order in the BuyLimit tester be triggered by Ask or Bid?
Of course by Ask.
Check it yourself, it is not difficult.
Was hoping the man was wrong, but no, checked on real ticks in Opening, he is. Here you go: bid below bylimit. Miracles of the glass. ))
And here's the flipper below the limit and it's still standing. What an unbreakable limiter. )))
But seriously - it's all nonsense. You still cannot completely reproduce the reality in the tester (at least because the orders placed in reality change the glass, which cannot be reproduced in the tester; otherwise it would mean that the tester changes the data on which it is testing), so should we be very meticulous about these nuances? Well, you can get an approximate picture of how the strategy works from the asc and the asc. The test does not guarantee anything.
I was hoping the man is mistaken, but no, I checked it on real ticks in the Open and it's true. Here you go: bid below bylimit. Miracles of the glass. ))
It has been said several times before that pricing is not affected by the tester.
I have another question for the developers. If the tester uses only Bids and Asks in "real ticks" mode, then why does it run the Expert Advisor throughCOPY_TICKS_ALL-ticks instead ofCOPY_TICKS_INFO-ticks? That's a waste of money.
It has been said several times before that pricing is not affected by the tester.
What does this have to do with my post?
Because BuyLimit in the tester is just an order to the tester that when the ask reaches BuyLimit, to make BUY. No more and no less.
But when the flipper falls below the bylimit it is already a mistake. It turns out that the deal was executed below the limit, while it was not executed, which cannot be. The flipper should be an order to the tester, not an ask.
You have to understand the nature of flipper emergence. A flipper on the real appears when someone decides to make a market, looking at the current trading environment. It is the trading environment (history + current state (stakes)) that affects someone's desire to make a market there. This means that if you are in the real world putting in and removing limiters, it may affect someone's decision whether or not to make a market. It may be that if that person saw your limit, they wouldn't or wouldn't send a market to it. Alternatively, if you put a big limit somewhere away from the best price, that person might not be able to market someone else's limit that was a best price.
All that said, the fins have nothing to do with the tester performance. Moreover, you have to be very careful to apply fin information at all in any trading logic. The tester should in no way take fins into account, nor should it influence pricing.
The tester is correct with execution.
In this sense, very strange is the construction of bars (source information for indicators) by fins. Historically, this has been the case, but it is, to put it mildly, questionable. Not mildly - it is erroneous. Much more informative would be bars built on the average price of the same spread.
You have to understand the nature of flipper emergence. A flipper on the real appears when someone decides to make a market, looking at the current trading environment. It is the trading environment (history + current state (stakes)) that affects someone's desire to make a market there. This means that if you are in the real world putting in and removing limiters, it may affect someone's decision whether or not to make a market. It may be that if that person saw your limit, they wouldn't or wouldn't send a market to it. Furthermore, if you put a big limit somewhere away from the best priced limit, that someone wouldn't file their market with someone else's limit that was a best priced limit.
All that said, the flippers have nothing to do with the tester performance. Moreover, one has to be very careful to apply fin information at all in any trading logic. The tester should in no way take fins into account, nor should it influence pricing.
Everything is correct in the Strategy Tester with respect to execution.This is the history of deals. It has nothing to do with the backtest. If there was an asc, the exchange was obliged to fill in, send you to the market. But if there was a flipper, it was for that environment where your limiters weren't.
In short, showing stupid stubbornness. You are annoying.
I had hoped the man was wrong, but no, I checked on real ticks in Otkritie, and he is. Here you go: the bid is below the bylimit. Miracles of the glass. ))
You are mistaken.
In the above screenshot you can see that Ask (namely, the buy limit is triggered by Ask) is higher than the buy limit.
And here's the flipper below the limit and it's still standing. What an unbreakable limiter. )))
Wrong again as Ask has not broken through the bylimit level downwards. What are you picking on the flipper for when the condition is triggered by the bylimit?
But seriously - it's all nonsense. You still cannot completely reproduce the reality in the tester (at least because the orders placed actually change the glass, which cannot be reproduced in the tester; otherwise it would mean that the tester changes the data on which it is testing), so why take such a scrupulous approach to these nuances? Well, you can get an approximate picture of how the strategy works from the asc and the asc. The test doesn't guarantee anything, anyway.
In all seriousness, you are simply illiterate.
Apparently you have some sketchy knowledge in your head and are not trying to understand what you are being told.