3D WAVE-PM Meow Mix [acatwithwithcharts]

19 sept. 2018

This is an (il)logical extreme adaptation of Mark Whistler's WAVE-PM script, originally published in his book Volatility Illuminated as a MetaTrader script. Instead of displaying WAVE-PM as several oscillator lines oscillating within a range, it plots 32 different period lengths at height equal to their length and reads out colors based on their value. The period lengths are spaced out such that it makes a relatively continuous heatmap when displayed on log scale. It has the same customization options as my regular WAVE-PM Meow Mix script.

(It may be necessary to move the scale around to see the indicator - it ranges from 14 to 600 and the scale on the chart seems to default to a range below it.)

It's experimental, it's a proof of concept for heatmap versions of indicators, it has a tendency to freeze up, and it gives a great deal of information in one snapshot (mcuh of which I'm still working out how best to use). It is particularly good at presenting a bird's eye view of the significance of a given movement relative to how much of an impact it has on higher period volatility expansions.


I'm publishing this as Invite-Only with a few specific people already in mind to help experiment with the concept, and do not have immediate plans for opening broad access to it.

20 sept. 2018

Notes de version

This update fixes a very idiosyncratic repainting bug, where as far as I can tell Pinescript draws a color change in a line plot as starting from the middle of of the bar that came before the bar where the color change actually is. As a result, any time a color changed it would actually display in line with the bar immediately before the signal and it always displays as if 2 bars (current and immediately previous) had the change in signal instead of just the current bar. Obviously this is wrong and potentially very misleading when trying to backtest the indicator.

I added a 1 bar forward offset on the plots. They now line up correctly rather than appearing to repaint the previous bar.

3 oct. 2018

Notes de version

This update fixes a bug that was causing the stdev() function menu choice to fail to display.

7 nov. 2018

Notes de version

This update overhauls the MA and STDEV calculations and menus to allow unweighted, volume-weighted, or volume-weighted STDEV relative to a wide variety of moving average types. It has options for "moving" STDEV of these types which measures STDEV relative to the moving basis or static STDEV which measures it relative to the current bar. Selecting "SMA" and "Unweighted STDEV" replicates the stdev() function and "Unweighted Moving STDEV" replicates the previous "Unweighted STDEV" behavior.

This calculation occasionally times out the indicator. Changing symbols or TFs will reload it and generally resolve the issue. If you just want to use ordinary SMA and STDEV, using the "lite" version of this indicator should avoid this issue completely.

9 déc. 2018

Notes de version

Relabels "VWAP" as "VWMA" which is the correct description (I've frequently seen the terms used interchangeably in crypto, where trading is 24/7 rather than confined to daily sessions, hence the prior labeling).

22 déc. 2018

Notes de version

Updated to change the attribution in the title from “acatwithcharts” to “SharkCharts.live”.

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

23 févr. 2019

Notes de version

This update should improve performance on SMA with Unweighted STDEV (though using the "lite" version of the indicator will still be even faster for that).

7 mars 2019

Notes de version

Bugfix to ZLEMA.

16 juil. 2019

Notes de version

Update to v4. Addition of several more moving average types.

29 sept. 2020

Notes de version

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.