The Ultimate Historical and Implied Volatility Rank and Percentile Indicator

Forums ProRealTime English forum ProBuilder support The Ultimate Historical and Implied Volatility Rank and Percentile Indicator

  • This topic has 21 replies, 3 voices, and was last updated 5 years ago by avatarBard.
Viewing 7 posts - 16 through 22 (of 22 total)
  • #111688

    Afternoon @Nicolas, I got this reply from Ninza about there Implied Volatility Vix Fix code (because the won’t share the complete code with me) :

    The original Williams VIX Fix just includes the bottom-catching algorithm.
    Our indicator inverses that formula to add the (low volatility) top-catching algorithm, which is our improvement.
    For the bottom-catching part, you can compare our indicator with other source-code versions on the internet to check the accuracy.
    So.. it appears that we would need to amend the formula for the Williams’ Vix Fix High Volatility Market Bottoms code posted below here? :

    This IV indicator and specifically this line of code I think has been the basis for the confusion here and of which I’d asked a few times about the need to modify it in my Better Implied Volatility post and above (that’s my defence and I’m sticking to it!). I think by not modifying it (wfv) and using this code (wvflex) that seeks to establish extremes that is why we maybe only seeing mirror images between the two indicators from Vonasi’s and your conversion of his code, right? Re: mirroring, please refer to my image in my post #111235 just directly above or see this zoomed in scan of it posted here:

    The top indicator is Vonasi’s conversion from my request here: https://www.prorealcode.com/topic/a-better-implied-volatility-rank-and-percentile-indicator/

    Cheers,

    Ps/ It’s now very tricky adding code here? I got this on the first submit:

    <pre class=”lang:probuilder decode:true” title= “Williams’ Vix Fix High Volatility Market Bottom” etc.
    Basically it’s only on editing my post that I can truly get the indicator code to display properly in a grey highlighted box using the latest Safari browser.

    #111766

    I think this has sorted it @Nicolas: — although red/green IV can rank high for market tops if you use wvflev =100- ((wvf- etc) and IF (wvflev[i]) < (wvflev) THEN

    Low Implied Volatility Inverse Vix Fix (for Market Tops) with Rank, Percentile and Historic Rank:

    Ignore first image.

    #111911

    Creating an Inverse Low Volatility Vix Fix…

    Larry Williams’ original High Volatility Vix Fix IV proxy is:

    I initially only changed the original High Vol Vix Fix denominator from highest to lowest, but logic tells me  that the inverse of that high volatility wvf is not correct in line 10 above and should in fact be: (where pd = 22 periods)

    ..yet that produces a worse result for spotting market tops with green spike bars? Pls see images, the first being the correct code ( ((high-lowest[pd](close))/(lowest etc ). The top indicator (of four) is the one in question in both the attached images. Do you have any  ideas please @Nicolas because these volatility indicators are great but they’re driving me nuts!? Lol.

    #111985

    Normal behavior as these peaks mark the candle when the new highest value of WVF is, so that the normalization is doing its job.

    100% WVF is on that candle, so the oscillator is marking it with a spike in the curve.

    #112042

    Thanks @Nicolas, in your opinion though which would be the correct code to inverse the wvf code and find low volatility extremes:

    or

    Cheers,

    #112043

    The second one, as it is the almost exact same one as a Stochastic.

    1 user thanked author for this post.
    #112044

    Cheers, that’s what I thought although for some reason the first produces far better indications of the market topping out.

     

Viewing 7 posts - 16 through 22 (of 22 total)

Create your free account now and post your request to benefit from the help of the community
Register or Login