OPEN-SOURCE SCRIPT
Multiple divergences NON-REPAINT by PeterO

Divergences are well-known tool for finding trend reversals. Powerful, yet... unreliable. Sometimes they show up, sometimes they don't. Sometimes they really mean trend end, sometimes the trend continues. I've witnessed countless discussions about which indicator to hunt for divergences on. All pointless.
Earlier today I found a very inspirational script by Lonesometheblue, combining multiple divergences together. Actually - summing them up and showing hunted divergences count in a label. Because if a divergence shows up on a single indicator like RSI, it can indeed mean trend reversal, but... yeah, check previous pargraph. But if this divergence shows up on 8 different indicators at the same time, then chances increase, don't they?
I decided to do my own version of Lonesome's indicator, because that one is using Label.New, which doesn't allow analysing entire script, only latest 50 occurences or so. I'm not going to hide it - I copy-pasted a lot from Lonesome's code. And from Everget's built-in divergences script, which you can find in PineScript/New. I didn't even bother to modify variable names or cover tracks in any other way, pretending it is my work from scratch. All with these two gentlemen consent and blessing. I added labels from myself, plus bit of rework and here it is:)
I hope you'll find it useful.
P.S. While analyzing divergences today, I discovered one thing. Hidden divergences are not useless, as many people think. But they should be used at trend dips to join the trend, not at trend ends, as reversals. Experiment yourself.
P.S.2 Still, never use only divergences. They need confirmation, they are not self-fulfilling prophecy.
Earlier today I found a very inspirational script by Lonesometheblue, combining multiple divergences together. Actually - summing them up and showing hunted divergences count in a label. Because if a divergence shows up on a single indicator like RSI, it can indeed mean trend reversal, but... yeah, check previous pargraph. But if this divergence shows up on 8 different indicators at the same time, then chances increase, don't they?
I decided to do my own version of Lonesome's indicator, because that one is using Label.New, which doesn't allow analysing entire script, only latest 50 occurences or so. I'm not going to hide it - I copy-pasted a lot from Lonesome's code. And from Everget's built-in divergences script, which you can find in PineScript/New. I didn't even bother to modify variable names or cover tracks in any other way, pretending it is my work from scratch. All with these two gentlemen consent and blessing. I added labels from myself, plus bit of rework and here it is:)
I hope you'll find it useful.
P.S. While analyzing divergences today, I discovered one thing. Hidden divergences are not useless, as many people think. But they should be used at trend dips to join the trend, not at trend ends, as reversals. Experiment yourself.
P.S.2 Still, never use only divergences. They need confirmation, they are not self-fulfilling prophecy.
오픈 소스 스크립트
트레이딩뷰의 진정한 정신에 따라, 이 스크립트의 작성자는 이를 오픈소스로 공개하여 트레이더들이 기능을 검토하고 검증할 수 있도록 했습니다. 작성자에게 찬사를 보냅니다! 이 코드는 무료로 사용할 수 있지만, 코드를 재게시하는 경우 하우스 룰이 적용된다는 점을 기억하세요.
I auto-execute TradingView Alerts into MT4/MT5 using this: tradingconnector.com 1-second delivery. Ping me if you need support with installation.
면책사항
해당 정보와 게시물은 금융, 투자, 트레이딩 또는 기타 유형의 조언이나 권장 사항으로 간주되지 않으며, 트레이딩뷰에서 제공하거나 보증하는 것이 아닙니다. 자세한 내용은 이용 약관을 참조하세요.
오픈 소스 스크립트
트레이딩뷰의 진정한 정신에 따라, 이 스크립트의 작성자는 이를 오픈소스로 공개하여 트레이더들이 기능을 검토하고 검증할 수 있도록 했습니다. 작성자에게 찬사를 보냅니다! 이 코드는 무료로 사용할 수 있지만, 코드를 재게시하는 경우 하우스 룰이 적용된다는 점을 기억하세요.
I auto-execute TradingView Alerts into MT4/MT5 using this: tradingconnector.com 1-second delivery. Ping me if you need support with installation.
면책사항
해당 정보와 게시물은 금융, 투자, 트레이딩 또는 기타 유형의 조언이나 권장 사항으로 간주되지 않으며, 트레이딩뷰에서 제공하거나 보증하는 것이 아닙니다. 자세한 내용은 이용 약관을 참조하세요.