I've been working with NT8 for about 3 months now. Have also played with Sierra Charts and Thinkorswim.

I have a base strategy which I've developed two working strategies from, both sharing the same code.

One is full autotrade, the other hands off entries to existing ATM strats.

On stress-testing these two (by running them on MES with low tick setting of 50 ticks, so they make many trades while I watch), I'm running into many problems, including:

- auto-trailing stop orders that trip over themselves and generate errors for trying to place stop orders above the market price

- severe crashes that put up dozens of error dialogs and take the whole program down

- Strat generating orders that enter > 1 position (which should never happen, as 'EntriesPerDirection = 1' is set in State.SetDefaults);



Just to note: the logic of the strategies is working perfectly when it does work--entries are executing correctly; exits are executing correctly.

And, I've so far had no issues trading live (with the exception of the trailing stop issues noted above).

It's quite possible some of these issues may stem from coding errors on my part. But before I proceed further in development, I wanted to get other's advice regarding their experience with autotrading strats and stability in NT. And how NT compares to any other platforms you've used.

Just trying to gauge if it's worth continuing. I want to spend my time on improving my strategy profitability, rather than chasing down bugs, which may or may not be mine.

one of the things i would recommend is using an indicator sending a mkt order rather than auto trailing.... a lot depends on the bar types you are using....unirenko, ticks, minutes. I think you may have said 50 tick....has to be a responsive indicator...maybe lbr310 crossing below or above 0....just a thought....the 50 ticks looks a little herky jerky.....tough to latch onto a trend....I can see why you would get a lot of errors using autotrailing....I used 200 with and SMA 50....got some good exits...but lots of chop....maybe a bollinger would be better...had better success with a 2/4/8 unirenko....

StickRustler 

I've been working with NT8 for about 3 months now. Have also played with Sierra Charts and Thinkorswim. I have a base strategy which I've developed two working strategies from, both sharing the same code. One is full autotrade, the other hands off entries to existing ATM strats. On stress-testing these two (by running them on MES with low tick setting of 50 ticks, so they make many trades while I watch), I'm running into many problems, including: - auto-trailing stop orders that trip over themselves and generate errors for trying to place stop orders above the market price - severe crashes that put up dozens of error dialogs and take the whole program down - Strat generating orders that enter > 1 position (which should never happen, as 'EntriesPerDirection = 1' is set in State.SetDefaults); Just to note: the logic of the strategies is working perfectly when it does work--entries are executing correctly; exits are executing correctly. And, I've so far had no issues trading live (with the exception of the trailing stop issues noted above). It's quite possible some of these issues may stem from coding errors on my part. But before I proceed further in development, I wanted to get other's advice regarding their experience with autotrading strats and stability in NT. And how NT compares to any other platforms you've used. Just trying to gauge if it's worth continuing. I want to spend my time on improving my strategy profitability, rather than chasing down bugs, which may or may not be mine.

Without seeing your strategy, it would be difficult to diagnose what the issue is.

I have coded both types of strategies. One which uses the ATM to handle the order once executed and the other is a fully hard coded strategy that manages quantity, entries, exists and a trailing stop.

As you are getting the errors in both the ATM and the hard coded strategy tells me there is likely something wrong globally.

It is puzzling you are having an issue with the strategy running the ATM. Once the strategy has passed over the handling of the position to the ATM that should be it, other than perhaps a circle back to prevent another order from executing if a position is already open.

So, unless I can see your strategy code/working I can't really help you that much.

loantelligence 

one of the things i would recommend is using an indicator sending a mkt order rather than auto trailing....

I use both types, but was using an ATM strategy that had auto-trailing stops.

Quoting 

the 50 ticks looks a little herky jerky.....tough to latch onto a trend....I can see why you would get a lot of errors using autotrailing

As I said, it was for testing: so I could see a lot of trades while I watched, and to see if the Strat created any errors/problems.

JonnyBoy 

Without seeing your strategy, it would be difficult to diagnose what the issue is. I have coded both types of strategies. One which uses the ATM to handle the order once executed and the other is a fully hard coded strategy that manages quantity, entries, exists and a trailing stop. As you are getting the errors in both the ATM and the hard coded strategy tells me there is likely something wrong globally. It is puzzling you are having an issue with the strategy running the ATM. Once the strategy has passed over the handling of the position to the ATM that should be it, other than perhaps a circle back to prevent another order from executing if a position is already open. So, unless I can see your strategy code/working I can't really help you that much.

Still not sure what's happening with the Strats, except to say that NT doesn't fail gracefully when there's a problem (and maybe this is a Windows / C# issue, and not related to NT).

For now, I'm not going to attempt to autotrade at all--just going to backtest and optimize my strats, then trade them live.

StickRustler 

I've been working with NT8 for about 3 months now. Have also played with Sierra Charts and Thinkorswim. I have a base strategy which I've developed two working strategies from, both sharing the same code. One is full autotrade, the other hands off entries to existing ATM strats. On stress-testing these two (by running them on MES with low tick setting of 50 ticks, so they make many trades while I watch), I'm running into many problems, including: - auto-trailing stop orders that trip over themselves and generate errors for trying to place stop orders above the market price - severe crashes that put up dozens of error dialogs and take the whole program down - Strat generating orders that enter > 1 position (which should never happen, as 'EntriesPerDirection = 1' is set in State.SetDefaults); Just to note: the logic of the strategies is working perfectly when it does work--entries are executing correctly; exits are executing correctly. And, I've so far had no issues trading live (with the exception of the trailing stop issues noted above). It's quite possible some of these issues may stem from coding errors on my part. But before I proceed further in development, I wanted to get other's advice regarding their experience with autotrading strats and stability in NT. And how NT compares to any other platforms you've used. Just trying to gauge if it's worth continuing. I want to spend my time on improving my strategy profitability, rather than chasing down bugs, which may or may not be mine.

Here's the technique I'd use.

Convert the ATM strategy into a standard strategy.

If the standard strategy behaves differently than the ATM, and they should behave exactly the same, then that tells you something about NT.

Either way ...

Use Print(), and/or "pseudo break points," and/or try/catch, and/or Visual Studio to debug the standard strategy.
If you can get the standard strategy to work correctly, use that instead of ATM.

Note: My understanding is that you can run a standard strategy via market replay. I've never confirmed this.