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)
BarsType.Add method - how to always detect if (bars.Count == 0)?
I also posted this question on Ninja boards but wanted to try my luck here too since I know there are some NT7 experienced custom BarsType coders here...
I know that this is unsupported by NinjaTrader team, but if NT support can provide any help/hints, it would be appreciated as I'm trying to get some custom bar type code working in NT7. Otherwise, other NT7 custom bar type coders out there, if you have any ideas I'd love to hear them.
So, I'm getting some inconsistent behavior on always being able to reliably detect that bars.Count == 0 from within BarsType.Add method. I had assumed that I would get this if block to always enter per reloading or just loading of a chart. But It seems I can only get it to happen once (perhaps once per from/to combination, not sure yet what drives NT7 calling the Add method - I assumed per tick fed into my chart). For example, after compiling a new variation of my bars type, restarting NT7, and loading up exact same chart with same from/to periods, the bars.Count is automagically greater than 0 to my surprise already (as if the prior NT7 run has cached the generated bars and is not re-calculating them with potentially updated logic of my custom bar type code).
If it is due to cache, I can see that as beneficial for 99.99% of time, except when you are trying to debug your own bars type code and thus alter logic from run to run . So, if I'm hitting a caching issue, how can I work around it so that after I restart Ninja in between changes to my custom bars type code, it will always hit the bars.Count == 0 logic condition?
Or is there a better way to detect the very first tick from a chart that I want to *ALWAYS* detect for my Tick driven custom bar type within the Add method so I can properly initialize my chart building process?
Here's snippet of code for example - I use Trace.WriteLine (i.e., using System.Diagnostics) so that you can trace code paths within Ninja's trace log files:
My problem has been resolved over on Ninja forum. In a nutshell, to solve caching issue so that bars.Count == 0 is detected again, you'll need to clear out your database cache for this custom bar type which lives in NinjaTrader 7\db\cache\<SessionTemplate>\[tick|minute]\<Symbol XX-XX>\<CustomBarType>*.ntd
To do this properly, its easiest just to blow away the <SessionTemplate> folder living under db\cache. Or you can try to surgically remove specific *.ntd files appropriate for your debugging session with your custom bar types.
Notes:
where <SessionTemplate> refers to template for instrument you tested against - for example, "Eurex Equity Index Futures.Pacific Standard Time".
where <Symbol XX-XX> is specific contract of futures symbol - for example, "ES 09-10"
where <CustomBarType> is one of following Bar Types: Final0, Final1, Final2, Final3, Final4, Custom0, Custom1, Custom2, Custom3, Custom4, Custom5, Custom6, Custom7, Custom8, Custom9