More unexpected returns !

Forums › ProRealTime English forum › ProScreener support › More unexpected returns !

  • This topic has 9 replies, 3 voices, and was last updated 6 months ago by avatarJS.
Viewing 10 posts - 1 through 10 (of 10 total)
  • 07/29/2023 at 8:41 PM #218296
    sgrech

    ma=average[20](close)

    timeframe(monthly)
    m1=ma>1

    timeframe(weekly)
    w1=ma>1

    timeframe(daily)
    d1=ma>1

    SCREENER [m1 and w1 and d1]

    Should variable ma=average[20](close)
    be positioned within the relevant timeframe(s) or can it be situated at the top of the code outside of the timeframes?

    07/30/2023 at 9:55 AM #218309
    JS

    This allows you to display the different averages in the graph with the lowest time frame…

    timeframe(daily)

    ma=average[20](close)

    timeframe(weekly)

    ma1=average[20](close)

    timeframe(monthly)

    ma2=average[20](close)

    Return ma, ma1, ma2

    This allows you to screen whether the “close” (lowest time frame) is larger than the different average:

    timeframe(daily)

    C1=Close>average[20](close)

    timeframe(weekly)

    C2=Close>average[20](close)

    timeframe(monthly)

    C3=Close>average[20](close)

    Screener[ c1 and c2 and c3]

    07/30/2023 at 12:57 PM #218325
    sgrech
    07/30/2023 at 2:30 PM #218328
    JS

    What do you mean by “ma>1″…?

    The moving average (ma) is always greater than 1…

    07/31/2023 at 7:48 AM #218347
    sgrech

    “The moving average (ma) is always greater than 1…”

    The condition being tested is not really of importance here, rather I am seeking clarification as to whether the indicator (in this case average[20](close)) can be positioned once above the timeframe() coding or within each timeframe seperately?

    07/31/2023 at 8:15 AM #218348
    JS

    I’ve already shown you that…

    timeframe(daily)

    C1=Close>average[20](close)

    timeframe(weekly)

    C2=Close>average[20](close)

    timeframe(monthly)

    C3=Close>average[20](close)

    Screener[ c1 and c2 and c3]

    1 user thanked author for this post.
    avatar sgrech
    05/12/2024 at 9:20 AM #232565
    sgrech

    Long break i know….

    I’ve already shown you that…

    with respect you didn’t

    Can your code above be rewritten thus

     

    ma20=average[20](close)

    timeframe(daily)

    C1=Close>ma20

    timeframe(weekly)

    C2=Close>ma20

    timeframe(monthly)

    C3=Close>ma20

    Screener[ c1 and c2 and c3]

    Thanks in advance

    05/12/2024 at 9:30 AM #232566
    robertogozzi
    sgrech wrote:

    be positioned within the relevant timeframe(s) or can it be situated at the top of the code outside of the timeframes?

    code placed outside of the timeframes is considered part of the default timeframe, same as inside the timeframe(default).

    1 user thanked author for this post.
    avatar sgrech
    05/12/2024 at 1:20 PM #232580
    sgrech
    robertogozzi wrote:

    code placed outside of the timeframes is considered part of the default timeframe, same as inside the timeframe(default).

    Thanks Roberto the clarifies things somewhat although with regards to the timeframe(default), how do I know what this is – if that isn’t a daft question?

     

    05/12/2024 at 1:44 PM #232581
    JS

    The timeframe of the graph is the “default timeframe” …

    When it comes to a screener, the “default” timeframe” is the “period” you can set in the ProScreener window…

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 10 total)

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
unexpected returns in screen

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