Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Would be nice if NT would support management of orders/positions that are active in the account but not in the strategy. The situation that comes up regularly is having an open position or order when a disconnect occurs. Those open positions or orders are now orphaned which means the strategy no longer knows about them and therefore can not manage them. Inserting code in the OnStartUp() method to detect positions or orders is certainly doable. However, any attempt to close those orders or positions inside the OnStartUp() method results in the strategy being disabled. Would be really nice if the strategy would continue running.
This may have already been implied or stated, but it would be nice if NT8 was able to play nicer with emerging technologies such as CUDA and Machine Learning packages.
The biggest issue here might be the fixed .NET version NT7 (NET 3.5) runs upon, but it would be good to make sure this is not a limitation moving forward if possible.
Also, CUDA access might be a good hook to build into NT8 as some sections of the system could greatly benefit (Strategy Analyzer for one and highly computational Indicators, including ML or heavy filtering).
While I agree it is a nice wish list item, I first mentioned it to NT about 5 or 6 years ago, and my gut feeling is you won't see this any time soon (next 3-4 years).
I would instead focus on using things like Matlab or R that have existing OpenCL support and are well proven. You can find articles on futures.io (formerly BMT) on integrating NT with R or Matlab.
Currently it can be done, but I don't have time to compile the CUDAFY.NET libraries under NET 3.5. Then, it is likely I will not be able to use the internal NT7 development tools. It would be nice with the new Code Editor vendor if the compiler will support such features so I can say within NT8 environment. Right now, I will have to go to Visual Studio to accomplish this task.
Ray stated in one of the webinars that NT8 would not implement GPGPU features (CUDA/OpenCL) internally because the performance benefits for the backtesting engine were not there. But lets remember that the NT8 backtesting performance is greatly improved compared to NT7 (90% IIRC?).
I suspect it will be relatively easy to incorporate a .NET v4 GPGPU library to improve performance in a custom math heavy indicator.
I like NT for it does for me. But, it appears that this thread is going nowhere as far as ringing a bell with NinjaTrader echoing the wishes of the perhaps largest community of NT users anywhere.
It appears that NT's focus is more on their "Brokers" and "Partners" than the customers that actually use the software. Multichart and others are fast gaining on NT with addition of new features and tools while NT seems to have relegated that task to its fee-based partners.
So, another item for the wish list is for NT to at least read this wish list. Perhaps that would be a question for their next webinar.
Here is a list of the last few updates of NT with no sign of including the items on the wish list. The last 4-5 revisions are all about resolving brokers' issues.
I read this off and on and have yet to see a request for; the ability to add columns in the Strategies tab. To clarify, I want to add at least one or two additional columns that are in real time data that would allow me to see profit factor, percent profitable, etc.