Bollinger Screener Bug

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #188657 quote
    KeyemingKeyeming
    Participant
    Junior

    Hello Nicolas,

     

    Why does this screener does bring back any result  ?

    ecartbol = Bollingerup[60](close)-Bollingerdown[60](close)
    SCREENER[ecartbol < average[200](ecartbol)]

    Thank you for your feedback

    WeChat-Screenshot_20220222212610.png WeChat-Screenshot_20220222212610.png
    #188662 quote
    robertogozzirobertogozzi
    Moderator
    Legend

    Because SCREENERS with IG have a 254-bar data history limit (1024 with PRT direct).

    You are using a 200 + 60  = 260 periods. Try using 50 periods for BB.

    You can still use 200 periods with SMA. Should you want to use an EMA, then you could barely use 80 periods for the average, since EMAs require many more bars to be calculated.

    Keyeming thanked this post
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.
ProRealAI ProRealAI New

Stuck on this ProBuilder code?

Describe what this topic is trying to build, in plain English, and ProRealAI writes the ProRealTime™ indicator, screener or system for you.

Available in 7 languages
Try ProRealAI

Bollinger Screener Bug


ProScreener: Market Scanners & Detection

New Reply
Author
author-avatar
Keyeming @keyeming Participant
Summary

This topic contains 1 reply,
has 2 voices, and was last updated by robertogozzirobertogozzi
4 years, 7 months ago.

Topic Details
Forum: ProScreener: Market Scanners & Detection
Language: English
Started: 02/22/2022
Status: Active
Attachments: 1 files
ProRealCode ProRealCode
Loading...