Quote from Sky123987:
why couldn't you just add a little bit more to slippage & comission to account for this
Quote from chinook:
The way I'd like to do it gives me a more realistic view of what can happen. All of my orders are limit orders...Otherwise I have to figure out how to estimate slippage for this situation. For instance I have to figure out the probability of trades being missed out and then estimate a slippage for that. THis is too much hand waiving. I get a much cleaner picture if I can 'avoid' getting into positions at the high/low of the bars in backtesting.
I can do this in Tradestation using ADE dll...
Quote from Sky123987:
well said. Well if you really want the answer I'm sure you can get it, but at a cost. Check out the OQ forums under General Discussion >> Premium Support

Quote from Sky123987:
Gun,
Not really sure as I really don't use that kinda stuff. On a basic level all the ATS out there do a fine job. However once you start to add an element of complexity to your strategy coding in the others is a nightmare. Especially when you are dealing with limit orders that are filled / partially filled / if it is partially filled and you want to add a profit target, if you send an order and a black box that is co'loed right near the exchange sends an order to counteract your order and it's processed quicker than the latency for the message to get back to your computer, and many others ---> all these can lead into very complex and harry situtions. IMO the openquant framework enable you to write code to get around these situations better than any others