Three reasons for this post:
1. I am working on replacements for the ATM strategy methods so that they work in backtesting while retaining the ability to submit ATM strategies on live data. And I want to gauge the interest from others.
2. I'd like this to be a shared development effort if possible. Is there an established place where NinjaTrader coders go to share code and collaborate on a project?
The thing I'm working on is called BAtm, for Backtestable ATM. The objective is to implement the features of ATM strategies using the Unmanaged orders approach in backtesting, in a way that is transparent to the strategy developer. Drop-in replacements for the existing ATM strategy methods would be developed. For example, AtmStrategyCreate() would become BAtmStrategyCreate(), and it would internally use the Unmanaged orders approach for historical data and automatically switch over to the regular ATM strategy methods for live trading.
A few set-up steps are required in Initialize() and OnStartup(), and a single call to a maintenance method would be needed in OnOrderUpdate() and OnBarUpdate(), but otherwise one would code things the same way as when using NinjaTrader's ATM strategies.
The set-up steps could be simplified if there were a way to access the user's ATM strategies from NinjaTrader's database, but I haven't figured that out, and NinjaTrader support won't support questions about it.
3. Finally, has anyone already done anything like this? Or already working on it? Contact me if you are.
Thanks.
-Alex
1. I am working on replacements for the ATM strategy methods so that they work in backtesting while retaining the ability to submit ATM strategies on live data. And I want to gauge the interest from others.
2. I'd like this to be a shared development effort if possible. Is there an established place where NinjaTrader coders go to share code and collaborate on a project?
The thing I'm working on is called BAtm, for Backtestable ATM. The objective is to implement the features of ATM strategies using the Unmanaged orders approach in backtesting, in a way that is transparent to the strategy developer. Drop-in replacements for the existing ATM strategy methods would be developed. For example, AtmStrategyCreate() would become BAtmStrategyCreate(), and it would internally use the Unmanaged orders approach for historical data and automatically switch over to the regular ATM strategy methods for live trading.
A few set-up steps are required in Initialize() and OnStartup(), and a single call to a maintenance method would be needed in OnOrderUpdate() and OnBarUpdate(), but otherwise one would code things the same way as when using NinjaTrader's ATM strategies.
The set-up steps could be simplified if there were a way to access the user's ATM strategies from NinjaTrader's database, but I haven't figured that out, and NinjaTrader support won't support questions about it.
3. Finally, has anyone already done anything like this? Or already working on it? Contact me if you are.
Thanks.
-Alex
