Bollingerup/down

• 08/30/2017 at 12:52 PM #44921
  Despair

  There are this to commands BollingerUp/BollingerDown implemented in PRT. The given syntax is:

  bolUp=BollingerUp[20](close)

  1	bolUp=BollingerUp[20](close)

  The parameter is obviously the period of the used SMA but is it possible to define how many standard deviations the band is above/below the SMA?

  Of course I can program this manually but I wonder if this command allows to define the stdv.

  

  Despair

  Blocked

  Topics: 97

  Replies: 1034

  Been thanked: 217 times
  08/30/2017 at 1:07 PM #44923
  David

  you do it like this which is how PRT does it when you modify the Standard Deviations on the chart and use the visual builder:

  bolup= Average[20](close)+3*std[20](close)

  1	bolup= Average[20](close)+3*std[20](close)

   

  

  David

  Participant

  Topics: 24

  Replies: 170

  Been thanked: 31 times
  08/30/2017 at 1:10 PM #44924
  Despair

  I’m aware of it (like I wrote). I’m just wondering if one can specify the stdv when using  the PRT command for the bands.

  

  Despair

  Blocked

  Topics: 97

  Replies: 1034

  Been thanked: 217 times
  08/30/2017 at 1:19 PM #44927
  David

  Sorry I’m confused about your question because I thought my response, answers your question. In my example the bands will now be 3 standard deviations.

  

  David

  Participant

  Topics: 24

  Replies: 170

  Been thanked: 31 times
  08/30/2017 at 1:23 PM #44929
  robertogozzi

  I’ve always programmed it myself manually, I’ve no knowledge of a way to override built-in parameters.

  I would be glad if there was one!

  1 user thanked author for this post.

  Despair

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 16475

  Been thanked: 3643 times
  08/30/2017 at 2:09 PM #44934
  David

  Do you mean you want to compute the standard deviation yourself instead of using the built in function?

  If yes, I do have Example Bollinger Indicator code from PRT but it does run much slower than the built-in function.

  

  David

  Participant

  Topics: 24

  Replies: 170

  Been thanked: 31 times
  08/30/2017 at 2:39 PM #44936
  robertogozzi

  If I got what Despair said, he was thinking about something like this in a modified built-in BollingerUp:

  bolUp=BollingerUp[20,2.0](close)

  1	bolUp=BollingerUp[20,2.0](close)

  hopefully in a future release!

   

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 16475

  Been thanked: 3643 times
  08/30/2017 at 2:55 PM #44938
  Despair

  Roberto nailed it as so often. 😉 Would be nice to have this command in a future version.

  

  Despair

  Blocked

  Topics: 97

  Replies: 1034

  Been thanked: 217 times
  08/30/2017 at 3:05 PM #44939
  David

  Okay but how would this make a difference you still get the same result – what am I missing?

  

  David

  Participant

  Topics: 24

  Replies: 170

  Been thanked: 31 times
  08/30/2017 at 3:24 PM #44941
  robertogozzi

  You are not missing anything David, the point is just “why not having this feature built in?”.

  Furthermore, to keep existing code work seamless, the second parameter could be omitted, in which case 2.0 could be assumed by default.

  That’s all!

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 16475

  Been thanked: 3643 times
  09/06/2017 at 12:54 PM #45608
  Nicolas

  added in my wish list: https://www.prorealcode.com/topic/centralization-of-queries-and-suggestions-on-prorealtime/page/9/#post-45607

  (capability to change the default standard deviation coefficient) as suggested by Roberto.

   

  2 users thanked author for this post.

  robertogozzi, Despair

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20828

  Been thanked: 4742 times
• Author
  Posts