Aroon+ indicator discrepancy between 1min and 10sec

• 12/03/2020 at 2:25 PM #152488
  BobOgden

  Hey everybody,

  I’ve come across an issue with the Aroon indicator that I cannot solve .

  From what I understand about the Aroon+, it reads 100 when the current candle reaches a new high among a determined number of candles.

  So I tried the Aroon+ on a 1-minute timeframe with a period of 42.

  On the first screenshot you may see that at midnight on November 30th-December 1st, the candle has reached a new high for the last 42 minutes and therefore the Aroon+ indicator reads 100. So far so good.

  I then tried the Aroon+ on a 10-second timeframe with a period of 252 to match the above 1-minute period (252 x 10 sec = 2,520 seconds = 42 minutes).

  On the second screenshot, you may see that at the exact same time, the candle reaches the new high seen above but the Aroon+ indicator doesn’t change a bit (blue circle on the screenshot). It should have reached its highest high at 00:00:40.

  However, 3 minutes later, the Aroon+ value goes up to 92.85… This value shows that, 18 10-sec candles earlier, a new high had been reached.

   

  This feels like the Aroon indicator missed it in the first place, but realized its mistake 3 minutes later… Am I doing something wrong or is that a bug?

  Might it have something to do with the fact that it’s another month and therefore the wrong data is used?

  I tried on both v10.3 and v11.

   

   

  

  BobOgden

  Participant

  Topics: 3

  Replies: 27

  Been thanked: 12 times
  12/03/2020 at 7:08 PM #152523
  robertogozzi

  Multiplying periods in indicators to mimick other TF’s doesn’t work, not just for Aroon, but for all of them.

  Your pic shows that you are using v11, which supports MTF (Multi Time Frame) for indicators.

  You can read the basic how-to at https://www.prorealcode.com/topic/multi-timeframe-mtf-indicators-for-prorealtime/.

   

  1 user thanked author for this post.

  BobOgden

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 16466

  Been thanked: 3641 times
  12/03/2020 at 11:17 PM #152542
  BobOgden

  Ooooh perfect thx roberto! I should have thought about it. I’ve just read Nicolas’s article to make sure I understand.

  So I could use the “not updateOnClose” (i.e. normal) mode on a higher timeframe, say 3 minute, so that it calculates the Aroon+ value every 3 minutes at each close; and use a lower timeframe on default mode, say 10 seconds, that would enable the Aroon+ to be recalculated every 10 seconds too, but still with the 3-minute timeframe?

  

  BobOgden

  Participant

  Topics: 3

  Replies: 27

  Been thanked: 12 times
  12/04/2020 at 1:05 AM #152548
  robertogozzi

  Yep.

  But there’s no NOT UPDATEONCLOSE instruction, you may:

  – use UpdateOnClose to update values only when a bar closes

  – use Default, or nothing at all (Default is assumed when missing) to update values at the pace of the faster TF (called Default since it updates values continuously, according to its timing).

   

   

  1 user thanked author for this post.

  BobOgden

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 16466

  Been thanked: 3641 times
  12/04/2020 at 8:47 AM #152558
  BobOgden

  Oh right.

  I thought that there were 3 different modes, the updateOnClose mode, the Default mode and the “nothing at all” mode. I now realize that the last two are the same.

  Makes more sense.

  Thank you very much for your help!

  

  BobOgden

  Participant

  Topics: 3

  Replies: 27

  Been thanked: 12 times
  12/04/2020 at 9:34 AM #152565
  Vonasi

  Yes – if nothing is entered the default is default!

  Topic moved to ProBuilder forum as it is an indicator question rather than a platform issue.

  1 user thanked author for this post.

  BobOgden

  

  Vonasi

  Moderator

  Topics: 192

  Replies: 5088

  Been thanked: 1810 times
• Author
  Posts