Elite indicators :) - page 279

Hercs
2970
Hercs  

Report back..

mladen:
ValeoFX

Made this one instead.

A couple of reasons : making alerts on "regular" SSA would cause "alert dancing" (since the SSA recalculates). This way we are avoiding alerts backwards and since the current value of SSA is the same in end-point version and the "regular" version it can easily be used for alerts even on previous closed bar without a danger of being revoked at some point of time (previous bar had to close value at the value end-point version is showing, so even the previous - closed bar alert is correct from that point of view).
Added on more thing : the dotted line in this one is the "regular" normalized SSA so one can see the end-pointed history as well as the complete current regular normalized SSA - and I think that watching it will be explanatory as of what exactly the end-point one does as well as how SSA fits it self to data. Also, alerts are for level crosses in both directions (4 type of alerts in total)

regards

Mladen

======================

I attach here for your kind perusal and comment 2 screen-prints. The first one is the indicator as you intended it to be, but "alas" I just don't "get it". It does not do for me what the original does and that is the indicator in the first sub-window. (Your dotted-line in the bottom (new) version)

The 2nd screen-print I switched them around and got the original to show seeing that I am used to it and have the new version dotted.

Q: what added benefit is there to see this new calculation, plse. I just do not see the added value.

Thanking you in advance for your reply.

Mladen Rakic
151208
Mladen Rakic  

In the end I am going to hate SSA

ValeoFX,

I told repeatedly that "regular" SSA recalculates (or to use the popular word "repaints") and that I do not recommend the "signaling mode" usage of it to anyone since it will change its past Lag bars. So, in "signaling mode" it is going to show you one value now and a couple of bars later it is going to change the whole thing (it is fitting itself to changes) and that way it is going to make any signal worthless.

_______________________

I will repeat once more what I always say : please people do no use "regular" SSA in signaling mode but please, please use it as an aid in decision.

_______________________

The end-point version I posted does not recalculate but also it can not be made to show same values as "regular" SSA. That is the "cost" of making it causal (not depending on future values). "Regular" SSA had to have those values before it recalculated the rest and that was the idea if already signals and alerts were made for it : to signal and alert what is not going to be changed (and it will be, as it is clearly seen from the comparison of the end-point and "regular" SSA, and thus makes the "signals" just a simple guesswork)

regards

Mladen

ValeoFX:
======================

I attach here for your kind perusal and comment 2 screen-prints. The first one is the indicator as you intended it to be, but "alas" I just don't "get it". It does not do for me what the original does and that is the indicator in the first sub-window. (Your dotted-line in the bottom (new) version)

The 2nd screen-print I switched them around and got the original to show seeing that I am used to it and have the new version dotted.

Q: what added benefit is there to see this new calculation, plse. I just do not see the added value.

Thanking you in advance for your reply.
Hercs
2970
Hercs  

Thank you..

mladen:
In the end I am going to hate SSA

ValeoFX,

I told repeatedly that "regular" SSA recalculates (or to use the popular word "repaints") and that I do not recommend the "signaling mode" usage of it to anyone since it will change its past Lag bars. So, in "signaling mode" it is going to show you one value now and a couple of bars later it is going to change the whole thing (it is fitting itself to changes) and that way it is going to make any signal worthless.

_______________________

I will repeat once more what I always say : please people do no use "regular" SSA in signaling mode but please, please use it as an aid in decision.

_______________________

The end-point version I posted does not recalculate but also it can not be made to show same values as "regular" SSA. That is the "cost" of making it causal (not depending on future values). "Regular" SSA had to have those values before it recalculated the rest and that was the idea if already signals and alerts were made for it : to signal and alert what is not going to be changed (and it will be, as it is clearly seen from the comparison of the end-point and "regular" SSA, and thus makes the "signals" just a simple guesswork)

regards

Mladen

=====================

I also do NOT use SSA as a signal for entries as you made it very clear right at the outset, but what I am looking for is when it reaches the max/min levels. This indicator is brilliant and I must compliment you again for developing it.

I just don't see the value of the new one as I am only interested in "exhaustion" of the original. I do not see how this new one will show me the max/min on the original and THAT is really my only concern from the outset.

I guess in the end I will have to make do without this new version and I apologise for having taken you back to SSA which remains a brilliant pice of work nevertheless.

Thanks for the speedy reply. Much appreciated.

Mladen Rakic
151208
Mladen Rakic  

ValeoFX

It will reach maximum levels after the fact

Please, observe it as it builds the "maximums" and "minimums" backwards. And by all means, "maximums" and "minimums" are "signals". There is no way (and I state it safe and sound) to find maximums and minimums in a form of peaks without repainting

regards

Mladen

ValeoFX:
=====================

I also do NOT use SSA as a signal for entries as you made it very clear right at the outset, but what I am looking for is when it reaches the max/min levels. This indicator is brilliant and I must compliment you again for developing it.

I just don't see the value of the new one as I am only interested in "exhaustion" of the original. I do not see how this new one will show me the max/min on the original and THAT is really my only concern from the outset.

I guess in the end I will have to make do without this new version and I apologise for having taken you back to SSA which remains a brilliant pice of work nevertheless.

Thanks for the speedy reply. Much appreciated.
Hercs
2970
Hercs  
mladen:
ValeoFX

It will reach maximum levels after the fact

Please, observe it as it builds the "maximums" and "minimums" backwards. And by all means, "maximums" and "minimums" are "signals". There is no way (and I state it safe and sound) to find maximums and minimums in a form of peaks without repainting

regards

Mladen

=====================

Thanks Mladen. I trade it every day on my M5-chart and know this indicator well enough now to be comfortable with it. Your point is taken.

Best regards.

yuhu
89
yuhu  

Hello All

Not sure if this is the place, but can Mladen make a non repainting Trend Magic, please?

Preferably in bar format (separate window)

Attached is the indi.

Thank you

Files:
Codex
94
Codex  

Hi Yuhu,

Mladen actually made this fix for me quite some time ago. I asked for the exact same thing.

Here is his post: (Trend Magic got renamed to SuperTrend nrp)

Cheers

Codex

biddick
339
biddick  
mladen:
In the end I am going to hate SSA

Mladen Rakic
151208
Mladen Rakic  

A little toy to play with

It is a Sigmoidal (Softmax) normalized jurik filter (so made an oscillator) If you set the NormalizeHyperbolicparameter to true, range will be from -1 to 1, otherwise the range will be from 0 to 1 (at a first glance you may even miss that lower bound change).
Hercs
2970
Hercs  

Change to indi...

mladen:
newtrader100

Here is the "first step".

What this indicators does :
it finds out the trends from a desired time frames (assignable through TimeFrames parameter), multiplies each time frame trend with its weight (assignable though TimeFramesWeightsparameter) and adds them up to get an "over all" trend. Here is an example of 9 time frames NonLagMA trend :
What it (still) does not do :
It does not alert. The problem is that in one moment more than 1 time frames trend can change and then it can change way back the overall trend (just imagine : one month trend changes and changes "trend score" back 1 month (since all have to be changed). Will try to solve this (to be able to uniquely identify when an alert should be triggered, but so far no idea how to solve this "back changing" issue when alerts are concerned) i can alert when alertsLevelis reached, but then you can get alerts on every new bar and not just the first time the desire level is reached

Try it in run time and you will see what am I talking about. But I think that even like this it can be a useful indicator

PS: indicator requires to be attached to at least the smallest time frame chosen from time frames parameter (that is the only way how "historical trends" can be calculated accurately)

________________________________

PPS: added a version that alerts once per direction (so if it reaches up, it will alert and until down is not reached it will not alert up any more and vice versa)

regards

mladen

=======================

Good morning Mladen,

Please would you be kind enough to change this attached indicator so that I can preselect each TF? As you know it now only gives you one option for all TFs.

Thanks in advance.

Much appreciated.