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
Have just updated the latest VisualSMAMTF which is now "anavisualsma". In the previous version I changed the "DATA" input series to TYPICAL. In this new version you have a seperate Price type for the Data Input for the indicator. If I put both of these input data to TYPICAL I get a different output line for the SMA as opposed to putting only one of them to typical. Which is the correct way of using this indicator now.
Changing the primary data input series to "Typical" does not have any impact on the outcome. The indicator values are calculated from a secondary bar series, so the settings for the primary bar series are simply ignored.
The new option effectively allows you to calculate the values from the typical price of the secondary bar series.
Hello @Fat Tails,
I have a question about the anaVisualSMA. Please refer to the two charts attached. On the first chart, I have an SMA of period 1 and an anaVisualSMA(8R, 1), which as I understand it, is an SMA of period 1 on an 8R chart, but transformed onto the 4R chart. I was thinking, perhaps erroneously, that if there is consistency in this transport, then if I substitute 4R for the 8R in the anaVisualSMA, then I should get an SMA of period 1 on the 4R chart that is identical with the SMA(1) that is already there. However, as you can see on Chart #2, it produces an SMA of period 1 that is shifted forward in time by one 4R bar. Am I suffering from flawed reasoning here and is my lack of complete understanding of this MTF/Higher Time Frame Transport process the problem? Thanks for your help.
The chart shows a lag of 1 bar, which is due to the fact that OnBarUpdate() calls the primary bar series, which is shown on the chart, first and the secondary bars only afterwards. This means that the values calculated from the secondary bars cannot be used for the current bar of the primary bar series, but only the following one.
This only creates a problem, if the primary and secondary bars have identical time stamps.
The only remedy to compensate this, is to repaint the previous indicator value, once the first tick of the next bar has been registered. I have already used the 1-tick repainting for fixed period bars in both VisualMode and FirstTickMode of the indicator, such that the indicator compensates for the one-bar delay. Maybe I should do this for range and tick bars as well.
Have modified the indicator code to include 1-tick repainting in VisualMode and FirstTickMode for other bar types than fixed period bars.
The 1-tick repainting will be activated, when
-> the primary bar series and the secondary bar series called by the indicator use the same bar type
-> the closing time of the primary and secondary candles is identical
-> VisualMode or FirstTickMode is selected
In StrategyMode nothing will be repainted, but the result of the calculation from the secondary bar series will only be used for the next bar of the primary bars.
Exported using NT Version 7.0.1000.11
Indicator will only run on NT 7.0.1000.4 or later.
The VisualSMA is a MTF (multi-timeframe) version of the Simple Moving Average. It will plot on any chart and allows to calculate the moving average
- from …
Exported using NT Version 7.0.1000.11
Indicator will only run on NT 7.0.1000.4 or later.
The VisualEMA is a MTF (multi-timeframe) version of the Exponential Moving Average. It will plot on any chart and allows to calculate the moving average
- …
@Fat Tails:
Thanks for the update. I am not having any luck installing these into Ninja Trader (v. 64-bit 7.0.1000.7). I am getting the attached error message.
Sorry, this is probably my fault. I had played around with the Traders Insight Indicator, which requires the Dundas gauge. Then I had forgotten to uninstall it. I also had another assembly installed, when I had exported the indicators and they could only be installed on your machine, if both other assemblies were installed as well.
My mistake.
I have exported the two indicators a second time and replaced the files in the download section. Please try again.
.
