Serious issue with QuantAnalyzer dealing with pending orders
QuantAnalyzer has a huge problem with the way it deals with pending orders.
Here's the situation. An EA has a pending order feature for limit orders that are placed X pips away and the pending order has expiration time. IF the pending limit order is not triggered before the expiration time the order is removed. A pending limit order that is placed now could be triggered after 3 hours. QA shows the hourly winrate statistics completely wrong when using pending orders. IT looks at the hour at which a pending order was triggered/activated and shows those hours as succesfull or bad. But it could be that a pending order was placed 3, or 4 or 8 hours ago. So, the results shown by QA are completely misleading and wrong. While normal trades show immediate entry hours, pending orders data is shown of when the order was activated.
In the end I can NOT tell for the statistical results when my EA should open/place a limit order. QA only showing win/loss based on hour that the pending order was activated. This is totally useless and very misleading/WRONG.
Please, fix this in an urgent manner.
-
Votes +1
-
Project QuantAnalyzer
-
Type Feature
-
Status Refused
-
Priority Low
History
anonymous
09.09.2017 18:20We'll be waiting for the fix.
Tamas
27.11.2017 15:15Status changed from New to Refused
© Copyright. All rights reserved. ProjectPanel.com
you actually are looking at super random trade results of which you have no clue at what out those trades were placed (and should better be placed)?! This is awful.
QA might show you that at 14.00 many trades were successful. So you filter out all other hours from your EA except 14.00 and run the backtest of the EA just to see you get terrible results.
Why such difference between day and night? Because QA was showing trigger times of the pending orders, while the pending orders were placed 4 hours ago.
This is why QA and SQ are not suited for professional/serious EA builders. And it is more shocking that an employee did not even know the above problem and had to research it before confirm it is really the case.