I am making assumptions that NT8 already has a finalized feature set and framework in place, and that changing the backtesting engine would not be considered. But you can ask Ray @NinjaTrader in the webinar Monday, only he knows for sure.
Due to time constraints, please do not PM me if your question can be resolved or answered on the forum.
Need help? 1) Stop changing things. No new indicators, charts, or methods. Be consistent with what is in front of you first. 2) Start a journal and post to it daily with the trades you made to show your strengths and weaknesses. 3) Set goals for yourself to reach daily. Make them about how you trade, not how much money you make. 4) Accept responsibility for your actions. Stop looking elsewhere to explain away poor performance. 5) Where to start as a trader? Watch this webinar and read this thread for hundreds of questions and answers. 6) Help using the forum? Watch this video to learn general tips on using the site.
If you want to support our community, become an Elite Member.
The following user says Thank You to Big Mike for this post:
When I do a "Reload all historic data" it appears that the ...db\cache remains unchanged to a certain extent. I noticed this when using a custom bar type for quite some time and then modified the code for it to produce a different behavior. The change worked properly for the current days but when looking at historic data I noticed that at some points in the past it didn't. I reloaded all historic data but no change in behavior. So, I figured I must have something coded incorrectly and worked on that for a while and finally gave up. The other day it occurred to me that I should try clearing the ...db\cache folder and see what effect that has. I cleared the cache and the custom bar type worked properly over 31 months of historic data. So, that tells me that all those times of reloading all data did not properly clear/reload the cache data. So, I'm suggesting for NT8 that a reload of historic data also clear cache or at least let it be an option to clear the cache.
The following user says Thank You to MWinfrey for this post:
1. Currently when testing an auto strategy in simulation vs market replay you do not get the same results because market replay does not use the simulation algorithm to book the trades. That kind of makes market replay almost useless to me. I would like to have the same simulation logic applied to trades booked in market replay. If it's not possible due to variable replay speed, could you make it available only at 1X speed?
2. Market replay control window can be closed with CTRL+F4. Once it's closed you cannot reopen it because market replay stays connected. I could offer ways to avoid that but I think this control should be redesigned from the ground up.
Platform: "I trade, therefore, I AM!"; Theme Song: "Atomic Dog!"
Favorite Futures: EMD, 6J, ZB
Posts: 798 since Oct 2009
Thanks: 216 given,
improvements in the data storage aspect of Ninja
the ability to replay data by simple doing a reload of data files, so that if one either looses internet connection or is not connected, he can download prior (historical) data, and capture it (save for replay)
easier transition from workspace to workspace, similar to how other trading applications (eSignal, TradeStation, etc) do their workspace and paging inbetween them
NT has really proven to be invaluable and superior to other platforms, and a thin enough application as not to pose signigicant overhead on the operating systems of a number of computers, unlike the other trading platforms that so many of us used to use....(names withheld to prevent product embarassment)