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)
Coding Multi Time Frame (MTF) Indicators with NinjaTrader
The real-time chart from September 5 was created with the old version of VisualSMA. You now compared the new version on historical data with the old version on real-time data. However, what was changed, is how the new version works on real-time data. So the comparison has no meaning.
Are you sure that you uninstalled the old assembly and replaced it with the new one. The real-time behavior of the indicator suggests that it is the old version. Also you have again hidden all the settings, please display them on the chart!
Here you have confused yourself. The top indicator mimics an SMA(1) on an 8-range chart. But the bottom indicator is a SMA(1) calculated from a 4-range bar series, which you have placed on the false panel. They cannot match! If you set the VisualSMA(1) to 8-range, please compare it to an SMA on a 8-range chart which is calculated from that 8-range chart.
By the way, I appreciate your tests. It is a great help, if somebody else has an in-depth look at the indicators!
This wheelchair user test subject made some mistakes. Glad I have an excellent doctor! Now I only need a hot nurse
#1...Yesterday I removed the previous VisualSMA assembly and uploaded the new one into ninja without restarting it...didn't know I should have done that. Think that's what might have caused the charts to look as if nothing had changed.
#2...Ran a new test the same way as the previous one. They now seem to match perfectly. I would really like to understand why that is (if that's not asking for too much).
#3...Yesterday I actually inserted the SMA on the first panel and after realizing that mistake dragged it to the lower one without changing its settings...Nurse!!
But now I went a little bit further. We can see from the picture "Tops + Bottoms" that the VisualSMA matches perfectly with the SMA on the bottom panel and that's a picture taken on the 06-09-2011 where I made a trade. You can see that trade on the "TRADE#9" picture (The 8range VisualSMA is the hot pink dashed line) and compare the new version with the old one. Yes, they do not match at all (I've also attached the template I used for the charts).
Final thoughts : The new version plots completely different from the previous one in real-time, only now it is a perfect match with the corresponding SMA. This means that now we can look back on our charts and backtest for setups/entries, the problem no longer exists.
Sorry, I had not noticed that post, as there were several posts afterwards.
It is possible to transform the VisualSMA and the VisualEMA into a single indicator. It is also possible to add other moving average types.
However, I did not want to go too fast, because it was an experiment. The latest version of VisualSMA is actually release 8, and it is probably not the last one. The indicator already has over 500 lines of code, which is a lot for an SMA. Hot subjects are differences between historical and real-time data, taking into account session begin and session end, different timestamps on tick-based and minute-based charts, repainting to compensate for lag, different algorithms for interpolation on equidistant and non-equidistant charts, dependence of algorithms on underlying bar types for price projections.
Once the VisualSMA is fine, I will proceed to the next step. But as you notice, I have just removed a bug yesterday. So let us first see, whether there is more feedback.
In the end, the concept can be applied to any indicator.
Was easier to create two indicators. Took the VisualSMA and substituted "SMA" for "EMA". This was ways faster than to add an enum, 30 lines of code and a property. I am sometimes lazy.
This morning Ninja kept giving me the following error message :
09-09-2011 07:29:34 Default Connection to NinjaTrader historical market data server lost: The process cannot access the file 'C:\Users\BP\Documents\NinjaTrader 7\db\tick\6E 09-11\201109090800.Last.ntd' because it is being used by another process.
I logged on and off, restarted Ninja and it the error message kept popping up everytime I tried to connect but then I noticed something : all the windows (I have 13 chart windows open) were being updated with data (I can see the candles and all the indicators, etc) EXCEPT the charts that have VisualSMA's...they were blank. Because that got me a little suspicious, I decided to close all the charts that have VisualSMA's and restart Ninja. Now the error message is gone.
After a successful connection, I re-opened my charts with VisualSMA's and everything seems fine.
Might there be an issue with the VisualSMA's accessing tick data on these files?
The top indicator mimics an SMA(1) on an 8-
dont believe anything you hear and only half of what you see