Calling an indicator from a system

• 02/21/2021 at 2:08 PM #162189
  umebon

  Is it possible too write an indicator with different timeframes and then call “Long” from a system? Cant get this too work out as I want.

  Indicator for long position

  // ============================= Variabler för olika tidsintervall TIMEFRAME(1 hours,updateonclose) ma1 = average[20](close) c11 = ma1 > ma1[1] // Lång position TIMEFRAME(30 minutes,updateonclose) ma304 = Average[4](typicalPrice) ma308 = Average[8](typicalPrice) c301 = ma304 > ma308 // Lång position TIMEFRAME(15 minutes,updateonclose) indicator2 = Average[4](typicalPrice) indicator3 = Average[8](typicalPrice) c151 = (indicator2 > indicator3) // Lång position TIMEFRAME(10 minutes,updateonclose) indicator4 = SuperTrend[1.4,6] c101 = close > indicator4 // Lång position TIMEFRAME(5 minutes,updateonclose) ma5 = average[20](typicalPrice) c51 = ma5 > ma5[1] // Lång position IF c11 AND c301 AND c151 AND c101 AND c51 THEN LONG = 1 ENDIF return LONG AS "LONG"

  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

  // ============================= Variabler för olika tidsintervall TIMEFRAME(1 hours,updateonclose) ma1 = average[20](close) c11 = ma1 > ma1[1] // Lång position   TIMEFRAME(30 minutes,updateonclose) ma304 = Average[4](typicalPrice) ma308 = Average[8](typicalPrice) c301 = ma304 > ma308 // Lång position   TIMEFRAME(15 minutes,updateonclose) indicator2 = Average[4](typicalPrice) indicator3 = Average[8](typicalPrice) c151 = (indicator2 > indicator3) // Lång position   TIMEFRAME(10 minutes,updateonclose) indicator4 = SuperTrend[1.4,6] c101 = close > indicator4  // Lång position   TIMEFRAME(5 minutes,updateonclose) ma5 = average[20](typicalPrice) c51 = ma5 > ma5[1] // Lång position   IF c11 AND c301 AND c151 AND c101 AND c51 THEN LONG = 1                                   ENDIF   return LONG AS "LONG"

  

  umebon

  Participant

  Topics: 29

  Replies: 48

  Been thanked: 4 times
  02/21/2021 at 2:39 PM #162195
  Vonasi

  Yes. Use the CALL instruction in your strategy.

  https://www.prorealcode.com/documentation/call/

  However it is normally easier and more efficient just to hard code the indicator into your strategy.

  Also remember that you will need to run the strategy in a time frame that is compatible with the fastest time frame used in your indicator.

  Note: I gave your topic a more meaningful title – please try to use more descriptive titles with future topics.

  

  Vonasi

  Moderator

  Topics: 192

  Replies: 5088

  Been thanked: 1810 times
  02/21/2021 at 3:01 PM #162198
  umebon

  Just checking so I understand you right. The code is OK and all I need to is to call the indicator in the system.

  

  umebon

  Participant

  Topics: 29

  Replies: 48

  Been thanked: 4 times
  02/21/2021 at 4:19 PM #162235
  Vonasi

  Yes.

  Personally I would just cut and paste the code (removing the RETURN line) into a strategy and then replace LONG = 1 on line 25 with BUY 1 CONTRACT AT MARKET thus avoiding using the CALL instruction entirely.

  1 user thanked author for this post.

  umebon

  

  Vonasi

  Moderator

  Topics: 192

  Replies: 5088

  Been thanked: 1810 times
  02/21/2021 at 4:25 PM #162236
  umebon

  I´m trying too practice too build an indicator too call and how it works. My indicator is more detailed then the one I posted here but i can’t get the easy one too work.

   

  

  umebon

  Participant

  Topics: 29

  Replies: 48

  Been thanked: 4 times
  02/21/2021 at 4:31 PM #162237
  umebon

  I get “pro backtest.error.parsing” sometimes when I try too run a system calling an indicator. What is wrong when that happens?

  

  umebon

  Participant

  Topics: 29

  Replies: 48

  Been thanked: 4 times
  02/21/2021 at 5:07 PM #162241
  umebon

  Even if I make a simple system as this ProRealTime give me a probacktest.error.parsing. Is it just me that have that problem?

  I contacted ProRealTime but they don’t answer me… is this a known problem or am I doing something wrong?

   

  suck Indicatore

  c11 = close crosses over average[20] return c11 AS "c11"

  1 2	c11 = close crosses over average[20] return c11 AS "c11"

  suck_system

  DEFPARAM CumulateOrders = false c11 = CALL "suck" IF c11 THEN BUY 1 Contract AT Market ENDIF

  1 2 3 4 5

  DEFPARAM CumulateOrders = false c11 = CALL "suck" IF c11 THEN BUY 1 Contract AT Market ENDIF

   

  

  umebon

  Participant

  Topics: 29

  Replies: 48

  Been thanked: 4 times
  02/21/2021 at 5:21 PM #162244
  Vonasi

  I just tested your code and it worked fine on my platform on the DJI daily chart.

  

  Vonasi

  Moderator

  Topics: 192

  Replies: 5088

  Been thanked: 1810 times
  02/21/2021 at 5:22 PM #162245
  umebon

  I run it on DAX 5m and i can’t get it too work, suspect

   

  

  umebon

  Participant

  Topics: 29

  Replies: 48

  Been thanked: 4 times
  02/21/2021 at 5:25 PM #162246
  umebon

  I get parsing error sometimes when I run a indicator to a system. What is a parsing error?

  

  umebon

  Participant

  Topics: 29

  Replies: 48

  Been thanked: 4 times
  02/21/2021 at 5:29 PM #162247
  Vonasi

  There was a discussion in the French forum last October about similar issues.

  https://www.prorealcode.com/topic/probacktest-error-parsing/

  The best work around is to avoid using CALL and hard code the indicator in your strategy for the time being.

  1 user thanked author for this post.

  umebon

  

  Vonasi

  Moderator

  Topics: 192

  Replies: 5088

  Been thanked: 1810 times
  02/21/2021 at 5:30 PM #162248
  umebon

  But if I want to sell a system and want too hide the code doesn’t I have too put in a indicator and call it from a system or is there any other way too do it?

  

  umebon

  Participant

  Topics: 29

  Replies: 48

  Been thanked: 4 times
  02/21/2021 at 5:33 PM #162250
  Vonasi

  Yes that is the best way to do it. We may have to wait for PRT to investigate and fix this ‘parsing’ error before being able to code in this way though.

  Out of interest I just tested your simple test code on the DAX 5m and it worked just fine for me.

  1 user thanked author for this post.

  umebon

  

  Vonasi

  Moderator

  Topics: 192

  Replies: 5088

  Been thanked: 1810 times
  02/21/2021 at 5:37 PM #162251
  umebon

  I still have the error but thanx for the help for now. It is a little bit annoying when this appears but i guess it is just too wait out any solutions…

  

  umebon

  Participant

  Topics: 29

  Replies: 48

  Been thanked: 4 times
  02/21/2021 at 5:58 PM #162254
  umebon

  When i change in my indicator it doesnt update, how do I save? Isnt autosave?

  

  umebon

  Participant

  Topics: 29

  Replies: 48

  Been thanked: 4 times
• Author
  Posts