Jump to content

Welcome to the new Traders Laboratory! Please bear with us as we finish the migration over the next few days. If you find any issues, want to leave feedback, get in touch with us, or offer suggestions please post to the Support forum here.

  • Welcome Guests

    Welcome. You are currently viewing the forum as a guest which does not give you access to all the great features at Traders Laboratory such as interacting with members, access to all forums, downloading attachments, and eligibility to win free giveaways. Registration is fast, simple and absolutely free. Create a FREE Traders Laboratory account here.

LS_Chad

Measuring/Quantifying Divergence

Recommended Posts

I'm often asked if we have an "indicator" for divergence/convergence, and right now, the answer is no. So I'd like to open a thread to discuss how one would measure the divergence between price and any indicator (such as RSI), or between two indicators. In essences, how would you quantify divergence, on a bar to bar basis, between any two series of data points (whether that series be price data, volume data, or any technical indicator values).

 

It is my understanding, that when looking for divergence, you would identify two consecutive significant highs (or significant lows), and look for price increasing between those two bars, while an indicators value decreased (or visa versa).

 

The first question....do we really need a "divergence" value on every bar...or do we only need it on specific bars where these significant highs or lows occurred?

 

And should that divergence just be "true" (we have divergence) or "false" (we don't) or should it have a magnitude?

 

And can we calculate this value over a specific period, or is that period variable? This is what makes measuring/calculating divergence so difficult. It's easy to identify visually on a chart, but trying to put it into code is a different story.

 

I'll begin the discussion by overly simplifying things:

 

Here's an example that uses this custom indicator:

 

(CL > CL.10) * (RSI < RSI.10) - (CL < CL.10) * (RSI > RSI.10)

 

to measure divergence over a 10 bar period between price and RSI on a 3-min chart. The bottom pane shows the custom indicator giving us a value of 1 when we have divergence of price increasing over the 10 bars while RSI decreased, and a value of -1 when price decreased yet RSI increased:

 

Divergence.png

http://www.charthub.com/images/2009/03/24/Divergence.png

 

Here's another, that puts some amplitude (change in RSI over 10 bar period) into the value of the histogram (bottom pane):

 

Divergence_2.png

http://www.charthub.com/images/2009/03/24/Divergence_2.png

 

And here is the syntax for that custom indicastor:

 

((RSI.10 - RSI) * (CL > CL.10) * (RSI < RSI.10)) - ((RSI - RSI.10) * (CL < CL.10) * (RSI > RSI.10))

 

Again, I know this overly simplifies the concept, but something we can build on. I'm sure there are a few who have tackled this issue already that could weigh with some good insight.

 

Chad

Share this post


Link to post
Share on other sites

http://www.charthub.com/images/2009/03/25/Diverg_MACD_Ergod

1. Three lines on price pane show price trending down. Some people may dispute the exact placement of those lines, but the fact remains: price declines.

2. The corresponding MACD lows are trending up. May suggest price reversal but not quite. The first declining price trend line is accompanied by a decisive rise in corresponding MACD trend but initially, at least , prices continue to fall. Only the second signal (Dec 8) is followed by price increase.

3. The forth pane shows CI kindly supplied by Chad some time ago -- ergodic signal. The false signal created by MACD -- Price divergence is absent here.

 

The 4 bottom panes are CIs (code provided above by Chad, called "amplified divergence") .

First out of 4 cranks MACD over an arbitrary period of 10 bars.

Second cranks Ergodic over a period of 10 bars.

Third cranks Ergodic over a period of 20 bars.

Forth cranks MACD over a period of 20 bars.

 

 

 

First thing that comes to mind is that the user should be able to adjust the period (number of bars) for analysis. Second: leave the choice of an indicator to the user.

You can slide the dates backward looking at "MACD amplified divergence 20 bars" and spoting former occurrences. The false signal created by "raw" MACD is eliminated.

Third: it allows to quantify the divergence !

Share this post


Link to post
Share on other sites

This subject was covered in the RTL tutorial (and ongoing project) that can be found at:

 

Investor/RT - Tutorial - RTL 101

 

Specifically, the section on Divergence can be found here:

 

Investor/RT - Tutorial - RTL 101

 

Several new functions have been added to RTL which will provide more tools to attack divergence:

 

SLOPE(exp, n) - change-based slope of exp over past n bars: (exp - exp.n)/n

ACCEL(exp, n) - change-based acceleration of exp over past n bars, or slope of current bar minues slope of last bar

SLOPER(exp, n) - regression-based slope of exp over past n bars.

ACCEL(exp, n) - regression based acceleration over past n bars. Difference between the reg-based slope of current bar and reg-based slope of prev bar.

YINT(exp, n) - current value of a regression line through the past n bars of exp

Share this post


Link to post
Share on other sites

Hi Chad,

 

I was interested in your method of determining divergence, but for Trade Navigator, and came up with the following.

 

Original code by Chad:

 

((RSI (Close , BarsToUse , False).(BarsToUse) - RSI (Close , BarsToUse , False)) * (Close > Close.(BarsToUse)) * (RSI (Close , BarsToUse , False) < RSI (Close , BarsToUse , False).(BarsToUse))) - ((RSI (Close , BarsToUse , False) - RSI (Close , BarsToUse , False).(BarsToUse)) * (Close < Close.(BarsToUse)) * (RSI (Close , BarsToUse , False) > RSI (Close , BarsToUse , False).(BarsToUse)))

 

Indicator independent version:

 

(((UserExprOne).(BarsToUse) - (UserExprOne).0) * ((UserExprTwo).0 > (UserExprTwo).(BarsToUse)) * ((UserExprOne).0 < (UserExprOne).(BarsToUse))) - (((UserExprOne).0 - (UserExprOne).(BarsToUse)) * ((UserExprTwo).0 < (UserExprTwo).(BarsToUse)) * ((UserExprOne).0 > (UserExprOne).(BarsToUse)))

 

Example of implementation with chart:

 

TLabQuantDiverg (Regression Value (Close , 7 , 0) , Regression Value (Momentum (Close , 7) , 7 , 0) , 7)

 

attachment.php?attachmentid=12683&stc=1&d=1249381472

 

Note: the use of Regression is merely to smooth-out some of the wrinkle in the input values.

 

Regards,

QuantDiverge.thumb.PNG.c3aeffa920f13a35fdb545d55cc9705f.PNG

Edited by phase21
Clarification of usage

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Topics

  • Posts

    • Back in the early 2000s, Netflix mailed DVDs to subscribers.   It wasn’t sexy—but it was smart. No late fees. No driving to Blockbuster.   People subscribed because they were lazy. Investors bought the stock because they realized everyone else is lazy too.   Those who saw the future in that red envelope? They could’ve caught a 10,000%+ move.   Another story…   Back in the mid-2000s, Amazon launched Prime.   It wasn’t flashy—but it was fast.   Free two-day shipping. No minimums. No hassle.   People subscribed because they were impatient. Investors bought the stock because they realized everyone hates waiting.   Those who saw the future in that speedy little yellow button? They could’ve caught another 10,000%+ move.   Finally…   Back in 2011, Bitcoin was trading under $10.   It wasn’t regulated—but it worked.   No bank. No middleman. Just wallet to wallet.   People used it to send money. Investors bought it because they saw the potential.   Those who saw something glimmering in that strange orange coin? They could’ve caught a 100,000%+ move.   The people who made those calls weren’t fortune tellers. They just noticed something simple before others did.   A better way. A quiet shift. A small edge. An asymmetric bet.   The red envelope fixed late fees. The yellow button fixed waiting. The orange coin gave billions a choice.   Of course, these types of gains are rare. And they happen only once in a blue moon. That’s exactly why it’s important to notice when the conditions start to look familiar.   Not after the move. Not once it's on CNBC. But in the quiet build-up— before the surface breaks.   Enter the Blue Button Please read more here: https://altucherconfidential.com/posts/netflix-amazon-bitcoin-blue  Profits from free accurate cryptos signals: https://www.predictmag.com/ 
    • What These Attacks Look Like There are several ways you could get hacked. And the threats compound by the day.   Here’s a quick rundown:   Phishing: Fake emails from your “bank.” Click the link, give your password—game over.   Ransomware: Malware that locks your files and demands crypto. Pay up, or it’s gone.   DDoS: Overwhelm a website with traffic until it crashes. Like 10,000 bots blocking the door. Often used by nations.   Man-in-the-Middle: Hackers intercept your messages on public WiFi and read or change them.   Social Engineering: Hackers pose as IT or drop infected USB drives labeled “Payroll.”   You don’t need to be “important” to be a target.   You just need to be online.   What You Can Do (Without Buying a Bunker) You don’t have to be tech-savvy.   You just need to stop being low-hanging fruit.   Here’s how:   Use a YubiKey (physical passkey device) or Authenticator app – Ditch text message 2FA. SIM swaps are real. Hackers often have people on the inside at telecom companies.   Use a password manager (with Yubikey) – One unique password per account. Stop using your dog’s name.   Update your devices – Those annoying updates patch real security holes. Use them.   Back up your files – If ransomware hits, you don’t want your important documents held hostage.   Avoid public WiFi for sensitive stuff – Or use a VPN.   Think before you click – Emails that feel “urgent” are often fake. Go to the websites manually for confirmation.   Consider Starlink in case the internet goes down – I think it’s time for me to make the leap. Don’t Panic. Prepare. (Then Invest.)   I spent an hour in that basement bar reading about cyberattacks—and watching real-world systems fall apart like dominos.   The internet going down used to be an inconvenience. Now, it’s a warning.   Cyberwar isn’t coming. It’s here.   And the next time your internet goes out, it might not just be your router.   Don’t panic. Prepare.   And maybe keep a backup plan in your back pocket. Like a local basement bar with good bourbon—and working WiFi.   As usual, we’re on the lookout for more opportunities in cybersecurity. Stay tuned.   Author: Chris Campbell (AltucherConfidential) Profits from free accurate cryptos signals: https://www.predictmag.com/   
    • DUMBSHELL:  re the automation of corruption ---  200,000 "Science Papers" in academic journal database PubMed may have been AI-generated with errors, hallucinations and false sourcing 
    • Does any crypto exchanges get banned in your country? How's about other as Bybit, Kraken, MEXC, OKX?
    • Does any crypto exchanges get banned in your country? How's about other as Bybit, Kraken, MEXC, OKX?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.