Conversion of SuperTrendVolatility Indicator from TradingView

Forums ProRealTime English forum ProBuilder support Conversion of SuperTrendVolatility Indicator from TradingView

Viewing 12 posts - 16 through 27 (of 27 total)
  • #193392

    Please what precise instrument and timeframe?

    #193400

    Hi Nicolas, so I use it on dax daily, nasdaq daily and 4 hours, crude oil 4 hours and daily, it doesn’t work anywhere; the units are 10000; however I noticed that when I download the prc_supertrendvolatility it appears with -1 instead of -2 as it is reported on the link … maybe the correct file has not been loaded?

    #193404

    It depends of the units displayed, it fails somewhere back in history because of lack of volume or .. let me check again! 🙄

    #193405

    Yes, because there are no volumes far back in history (which are needed for the correct calculation of the indicator), so limit the units displayed and add Volume indicator on the chart to be sure volumes are present.

    1 user thanked author for this post.
    #193408

    Hi Nicolas, first of all thank you for your availability, I have placed 1000 units, and I am not having any problems. You’ve been super nice, I’ve been looking for this indicator for a long time. Thanks again 🙂

    #193552

    Hi Nicolas,

    Thanks so much for your great help on conversion!
    May I ask you for further favor? Can you show me how to translate this indicator to a screener to indicate which stock fulfill the BUY/SELL signal?

    i.e. based on the following part of the original script
    long = trend == 1 and trend[1] == -1
    short = trend == -1 and trend[1] == 1
    //
    last_long = 0.0
    last_short = 0.0
    last_long := long ? time : nz(last_long[1])
    last_short := short ? time : nz(last_short[1])

    buy = crossover(last_long, last_short)
    sell = crossover(last_short, last_long)

    #193714

    Here is the screener version of that indicator:

     

    #196078

    Hi Nicholas,

    I try the screener version of SuperTrendVolatility SCREENER as provided by your last posted.

    I encountered 2 issues:

    1. The screener always return NO RESULT. However, when I try to comment out the condition “if barindex>28 then …“, there is result.  Can you enlight me? Is this condition need for screener?
    2. After commented out the barindex condition, I try to further analyze the result by try scanning out the stock with trend = -1 with the clause “SCREENER[trend = -1]“. There is result available. However, when I try to further analyze the result by try scanning out the stock with trend = 1, there is NO result available. I have ensure there is stock has trend = 1 by finding one stock manually, putting it in my personal list, and use the screener with clause “SCREENER[trend = 1]“, but no result is available. See attached for the stock chart with SuperTrendVolatility trend captured. Any idea?

    Appreciate your professional input!

    Mike

     

    #196597

    Hi Nicolas,

    do you have any idea of my queues on 25/Jun as recapped below, many thanks!

    I try the screener version of SuperTrendVolatility SCREENER as provided by your last posted.

    I encountered 2 issues:

    1. The screener always return NO RESULT. However, when I try to comment out the condition “if barindex>28 then …“, there is result.  Can you enlight me? Is this condition need for screener?
    2. After commented out the barindexcondition, I try to further analyze the result by try scanning out the stock with trend = -1 with the clause “SCREENER[trend = -1]“. There is result available. However, when I try to further analyze the result by try scanning out the stock with trend = 1, there is NO result available. I have ensure there is stock has trend = 1 by finding one stock manually, putting it in my personal list, and use the screener with clause “SCREENER[trend = 1]“, but no result is available. See attached for the stock chart with SuperTrendVolatility trend captured. Any idea?

     

     

    #196604

    1/ not needed

    2/ I think the problem could come from the vx variable which is cumulating values from the beginning of history, and since ProScreener doesnt share the same bars history as the one displayed on the charts (way less bars..), then the cumulation is different and the calculation of the indicator is different, therefore different results..

    This is the simplier explanation I have right now without much investigation.

    #196611

    Hi Nicolas,

    thanks so much for your speedy reply! Any suggestion to resolve the issue #2 so that the screener can work? Or under current ProRealCode capability it is infeasible?

    Mike

    #196718

    Sorry, but as long as the 2 data series are different, their cumulation will be different, so I don’t know how it could be “resolved” 😆

Viewing 12 posts - 16 through 27 (of 27 total)

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