ProScreener and business day

• 08/06/2018 at 5:37 PM #77664
  NimceProfity

  Hi,

  I’m using the ProScreener, which calls my indicator with CALL.

  However, I need the ProScreener to CALL my indication only on business days.

  For example, if I refresh the ProScreener today, it will use the data from TODAY, but my indicator works only on business days, and because of that, my indicator returns 0 on the screener, but on the graph, it appears only on business days (as expected).

   

  1. Is there an option to force ProScreener to call my indicator on the last business day, and not today?
  2. If 1 is not possible, can I return values from my indicator that the ProScreener will ignore and proceed to the previous day? (until it reaches the last business day).

  Thanks

  

  NimceProfity

  Participant

  Topics: 2

  Replies: 5

  Been thanked: 0 times
  08/06/2018 at 9:05 PM #77666
  Vonasi

  Welcome to the forums. I see that this is your first post, Please try to post in the correct forum section. Your question is ProScreener related so I have moved it to that forum. You posted in the Platform Support forum which is for PRT platform issues and is a forum monitored by PRT to help solve any platform issues.

  

  Vonasi

  Moderator

  Topics: 192

  Replies: 5088

  Been thanked: 1811 times
  08/07/2018 at 7:08 AM #77678
  Nicolas

  In your ProScreener code, you could add a new variable that only populate if the result of your CALL is 1, that way you always have the last value stored in it.

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4773 times
  08/07/2018 at 2:38 PM #77721
  NimceProfity

  Thank you for your response, this is what I tried but it still doesn’t work:

  TIMEFRAME(daily) result = call "Indicator Info" if result = 1 then result2 = result endif SCREENER (result2 as "Criteria")

  1 2 3 4 5 6 7 8

  TIMEFRAME(daily) result = call "Indicator Info"   if result = 1 then result2 = result endif   SCREENER (result2 as "Criteria")

   

  

  NimceProfity

  Participant

  Topics: 2

  Replies: 5

  Been thanked: 0 times
  08/07/2018 at 3:04 PM #77726
  Nicolas

  Difficult to help more without the whole code, but give a try with:

  SCREENER [result2] (result2 as "Criteria")

  1	SCREENER [result2] (result2 as "Criteria")

   

   

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4773 times
  08/07/2018 at 8:06 PM #77736
  NimceProfity

  Hi,

  Thank you for your replies,

  It did help me a bit, but I decided to change my indicator to work differently, in order to solve this problem.

  I did encounter an unexpected behavior, which I suspect is a bug.

  Create an indicator with this code:

  hl=dpo[92](high[0]) i=0 h2=dpo[92](high[i]) return hl, h2

  1 2 3 4 5

  hl=dpo[92](high[0]) i=0 h2=dpo[92](high[i])   return hl, h2

  For some reason, this code generates 2 totally different graphs: https://monosnap.com/file/D3Rwxxq7h5fdmjqsXGcw4OUMeXyk4O

  I need to be able to specify the index for high with a variable, but to have the exact same effect as if I wrote a literal number.

   

  Thanks!

  

  NimceProfity

  Participant

  Topics: 2

  Replies: 5

  Been thanked: 0 times
  08/08/2018 at 8:13 AM #77744
  Nicolas

  You are right, something did not go well here, I suspect the DPO calculation as it is made with future datas that are obviously not present in real time (it will not give the same value in real time than if you reload the chart later).

  BTW, I’ll report this strange behavior to PRT team, using a variable for the period should not behaves differently.

  PS: Please next time embed your picture directly into the forum with the attachment tool, thank you.

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4773 times
  08/08/2018 at 11:59 AM #77761
  NimceProfity

  Great!

  Thank you, waiting for your update.

  

  NimceProfity

  Participant

  Topics: 2

  Replies: 5

  Been thanked: 0 times
  09/06/2018 at 7:40 AM #79855
  Nicolas

  I had news about this issue. It’s been fixed and be part of the next update of the platform.

  1 user thanked author for this post.

  robertogozzi

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4773 times
• Author
  Posts