3D WAVE-PM (3x Res Log 625-2000) [acatwithcharts]

24. Dez. 2018

This is an (il)logical extreme adaptation of my (il)logical extreme adaption of Mark Whistler's WAVE-PM script, originally published in his book Volatility Illuminated as a MetaTrader script.

In 3D WAVE-PM, I plotted 32 period lengths from 14 to 600 at height equal to their length, reading out colors based on their value. I chose those lengths to create a relatively continuous indicator on log scale.

What I really wanted to do though was to (1) have the option to view this indicator in either linear or log and (2) not lose as much data resolution across nearly 600 periods. Within the limitations of Pinescript, the best solution I could find was to make multiple indicators hard-coding the different period lengths to create linear and log ranges such that I could make a composite heatmap with several different indicators on the same pane.

...but then I went a step further on the log scale version, noticing that I could easily make a 4th indicator that covers the 625-2000 period region at similar resolution to the other 3. So I did. This is therefore the "4th of 3 indicators" for log scale 3x resolution WAVE-PM.

It adds significant lag on top of what was already caused by 3x WAVE-PM, but I have found it broadly useful enough when looking at large expansions that I'm going to go ahead and launch it. I strongly recommend doing any other analysis in a separate tab from the one in which you have high-res 3D indicators open.





I'm excited to announce that we're putting the finishing touches on a subscription service for the volatility theory indicators, and assuming no hiccups will launch them within days. Subscriptions will be available in several packages through SharkCharts.live

Current pricing and subscription details will be kept up-to-date on SharkCharts.live

16. Juli 2019

Versionshinweise

Minor update to v4.

29. Sept. 2020

Versionshinweise

I'm making a round of updates to my scripts after testing some of the new Pinescript features and looking for ways to address loading issues that have arisen from changes over the past 6 months or so as to what thresholds cause scripts to fail on the back end.