NeoTraders NB Indicator Lab

[Allonso]

Hi NeoTrader,

Sorry about posting on the wrong thread "TMA discussion Thread", I hope I won't make the same mistake twice. After playing around I now understand what the indi is doing, so have removed the M1 imput.

If you will allow and I havent committed another faux pas I would like to ask what difference the Server location makes to the Pivot calculation?
I ask this, as whilst looking at the various Pivot indi's, I noted that they were all different to the actual calculation of previous days (High+Low+Close)/3. Also I have a Pivot indi SDX-TzPivots which allows for different server time zones, intraday time frames plus a few other interesting additions.
Again it does not produce the correct Pivot value according to the formula, Shame really as I like it.
Not a coder so can't fathom out what the error may be.

Any information you can give will help the light to go on in my old brain.

Regards Allonso

[NeoTrader]

Hi Allonso,

Sorry about posting on the wrong thread "TMA discussion Thread", I hope I won't make the same mistake twice. After playing around I now understand what the indi is doing, so have removed the M1 imput.

Thats good... I mean that you put some time into the indicator and learned its behavior. Nothing is better then trial and error to experiment with an indicator and to look how it actually works or behaves.

If you will allow and I havent committed another faux pas I would like to ask what difference the Server location makes to the Pivot calculation?
Any information you can give will help the light to go on in my old brain.

Since the daily pivot calculations are based on the daily candles the server location plays then a role if you have additional candles on your daily chart...like a candle on Sunday or some also have Saturday candles. This could and probably will falsify your pivot calculations (mainly the daily pivot).

Some pivot indicators allow you to adjust the calculation if you have additional candles (like baludas DWMPivots) it is some additional Parameter in the Indicator settings..like addSundayToMonday or ignoreSunday or whatever.

hope this helps,

happy Sunday,

NeoTrader

-

[spotdespot]

Hi Neo,

I started using Baluda's TMASlopeMTF, with the MA on D1 and your indi's on the lower timeframes (so I could use different periods etc) but I am getting the following entries for all pairs every second:

00:00:04 TMASlopeMTF GBPAUD,Daily: unknown subwindow number -1 for ObjectCreate function

When I switched back to your NT TMA_CSS-SP and I am getting it with that too.

I only noticed when my HDD had a space issue as the logs were huge!

I am sure I have seen this mentioned somewhere before but I can't find it.

Any ideas?

Cheers,
Dave.

EDIT: OK - found the issue searching - must have done something wrong. Anyway this is related to indicators being overlaid with other indi's. It looks like it might be related to the order indi's are added - I'll update here if I find a definitive solution in terms of indi ordering.

[spotdespot]

Ok - it isn't avoidable by adding in a particular order. It seems if you add 2 x NT TNA-CSS-SP indi's on the same window you get the issue.

There is a solution - if you use the MTF version it doesn't happen, although, as I am using different tmaPeriods on lower than D1 timeframes I have to add one indi for each tmaPeriod, for each timeframe, that can only be viewed on that time frame - for me that means 3 indi's per timeframe..

Neo - any chance you would share the NT TMA-CSS-SP source and I can try to adapt so that it shows multiple TMA slopes each for a different tmaPeriod? To be honest it miught be beyond me though

Cheers,
Dave.

[NeoTrader]

Hi spotdespot,

Ok - it isn't avoidable by adding in a particular order. It seems if you add 2 x NT TNA-CSS-SP indi's on the same window you get the issue.

There is a solution - if you use the MTF version it doesn't happen, although, as I am using different tmaPeriods on lower than D1 timeframes I have to add one indi for each tmaPeriod, for each timeframe, that can only be viewed on that time frame - for me that means 3 indi's per timeframe..

Neo - any chance you would share the NT TMA-CSS-SP source and I can try to adapt so that it shows multiple TMA slopes each for a different tmaPeriod? To be honest it miught be beyond me though

Ok... I will try to clarify why this error happens.

If you want to create any Object on the Chart you must assign a specific Window Number to this Object. A Window is the main chart and also any separate subwindow of any Indicator.
The only way to find the Window related to an Indicator is via the IndicatorShortName and the WindowFind() Function.

But since our beloved Empty4 Platform seems to change the the IndicatorShortName when you add a second Indicator on top of it (it concatenates the Names) the Indicator is not able to find the proper Window anymore and cannot create the Objects it wants and this Error occurs.

The only solution to this is to deactivate the objects if you want to use multiple instances of this indicator on top of each other.
I think this is also why it works with my MTF Indicator. Because you already set the Parameter showInfo to false. If you had it set to true the error would also occur (I tested it).
The reason for this error is the info Table that creates Label Objects to show the value of the slopes.
The MTF version has this parameter (showInfo) available. The CSS-SP Indicator has it not.
I will soon release the fix for it.

But I still don't understand why you use the CSS-SP if you only want to use the TMA on it. The MTF has the same Parameters for the TMA and should work as you want it to and has already the Feature to not produce the Error. With the CSS-SP you also need to put three Instances on top of each other or not?

happy trading,

NeoTrader

-

[spotdespot]

But I still don't understand why you use the CSS-SP if you only want to use the TMA on it. The MTF has the same Parameters for the TMA and should work as you want it to and has already the Feature to not produce the Error. With the CSS-SP you also need to put three Instances on top of each other or not?

happy trading,

NeoTrader

-

Thanks Neo - yes expected Empty4 to be the issue somewhere. The work-around is ok, so no big deal.

The reason I have been using the CSS-SP rather than the MTF is that the MTF indi is timeframe specific - I will need to explain what I mean

For the CSS-SP I can add 3 indi's with the various tmaPeriods and have them show with AutoTimeframe = True and allow visualization on all relevant time frames (I set as H4-M15), on D1 I don't use the multiple tmaPeriods so it isn't an issue.

With the MTF indi the indicator is fixed to one or more timeframe REGARDLESS of the chart timeframe displayed. So If I want tmaPeriod 14 on an indi then I have to add a MTF indi for each individual timeframe for tmaPeriod 14 and allow visualization only on the corresponding timeframe. There is no point in using the MTF indi and setting multiple timeframes on the one indi for one tmaPeriod setting as the chart then just looks a total mess and is unreadable for what I need (or for what it was designed for really).

Hopefully this will makes sense to you, if not everyone who reads this!

Cheers,
Dave.

[NeoTrader]

With the MTF indi the indicator is fixed to one or more timeframe REGARDLESS of the chart timeframe displayed. So If I want tmaPeriod 14 on an indi then I have to add a MTF indi for each individual timeframe for tmaPeriod 14 and allow visualization only on the corresponding timeframe. There is no point in using the MTF indi and setting multiple timeframes on the one indi for one tmaPeriod setting as the chart then just looks a total mess and is unreadable for what I need (or for what it was designed for really).

Hopefully this will makes sense to you, if not everyone who reads this!

Hehe... Why you didn't ask about this before?

I already implemented that feature for another fella who wanted to use this indicator on renko charts. you can set the timeFrames to 0 so it will always use the current chart TF.

But this is not officially released yet.
I will send you a version that already has this implemented...I hope to release the final version soon...


happy trading,

NeoTrader

-

[spotdespot]

Excellent - thanks.

[Thunder123]

Hey Neotrader,

I have a request for the MTF indicator. I was thinking if we could get the angle of the slope for x number of bars (user definable). It could be shown on the side, like under the slope value. Also, the values for the angle calculation would require unnornalized values. Looking at this number maybe better than looking at MA for several reasons.

Also if I attach multiple multiple MTF Slope indicators the slope values get messed up. I realize it's Empty4 problem, but is there any fix/workaround?

Thanks

[NeoTrader]

hi Thunder,

I have a request for the MTF indicator. I was thinking if we could get the angle of the slope for x number of bars (user definable). It could be shown on the side, like under the slope value. Also, the values for the angle calculation would require unnornalized values. Looking at this number maybe better than looking at MA for several reasons.

I also thought about this already... but the problem I have is that I only have 8 IndicatorBuffers.

I wanted to show the Angle also as a slope to be able to find proper settings thru backtesting.

Since the next version will already be reduced to 4 TF because I also want to show up to 4MAs my buffers are already full...but maybe I will reduce it further to only 3 TFs and 3 MAs as most of the case we really don't need more then 3 TFs to watch. Then I could try to include the angle also...will see...let me think about it...

Also if I attach multiple multiple MTF Slope indicators the slope values get messed up. I realize it's Empty4 problem, but is there any fix/workaround?

The workaround for this Problem is to right click on the tma slopes and to open the indicator properties and then just press the ok button again.
I know about the problem and think that I have finally found a fix for that and it will be available in the next version.

Thanks for the Request and Report,

happy weekend,

NeoTrader

-