Parsing Error when Call Value from Indicator

• 10/05/2023 at 12:42 PM #222060
  SkySurferBlue

  I have been researching this topic and also tried creating the indicator with parameters but I still get this error when calling the value from the indicator into my code. Now I know the code of the indicator could have been done in the Builder itself but this is just the beginning and I wanted to keep it simple so we can get to the bottom of the problem.

  Error: Backtest cant start because of a parsing error in the code : line 1, column 0.

  Here is the Pro Builder code.

  Call value TradeOk from indicator TurnofMonth

  Tradeok = Call "TurnofMonth"[22,4] // Conditions to enter long positions IF NOT LongOnMarket AND Tradeok THEN BUY 1 CONTRACTS AT MARKET ENDIF // Conditions to exit long positions If LongOnMarket AND Not Tradeok THEN SELL AT MARKET ENDIF

  1 2 3 4 5 6 7 8 9 10 11

  Tradeok = Call "TurnofMonth"[22,4]   // Conditions to enter long positions IF NOT LongOnMarket AND Tradeok THEN BUY 1 CONTRACTS AT MARKET ENDIF   // Conditions to exit long positions If LongOnMarket AND Not Tradeok THEN SELL AT MARKET ENDIF

  Here is the indicator code

  Tradeok between days leading to month end and just thereafter

  Timeframe(Daily) IF Openmonth<>openmonth[1] Then Dayofmonth =1 else Dayofmonth= Dayofmonth+1 endif Tradeok=1 If Dayofmonth > End and Dayofmonth<Start Then Tradeok = Tradeok-1 else Tradeok = Tradeok endif Return Tradeok as "Tradeok"

  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

  Timeframe(Daily) IF Openmonth<>openmonth[1] Then Dayofmonth =1 else Dayofmonth= Dayofmonth+1 endif   Tradeok=1 If Dayofmonth > End and Dayofmonth<Start Then Tradeok = Tradeok-1 else Tradeok = Tradeok endif   Return Tradeok as "Tradeok"

  Thank you

  

  SkySurferBlue

  Participant

  Topics: 5

  Replies: 5

  Been thanked: 1 time
  10/05/2023 at 5:12 PM #222065
  JS

  Hi,

  Adjust the following in your indicator:

  Remove: Timeframe(Daily)

  Verander “If Dayofmonth>End OR Dayofmonth<Start then

  1 user thanked author for this post.

  SkySurferBlue

  

  JS

  Participant

  Topics: 26

  Replies: 1716

  Been thanked: 777 times
  10/05/2023 at 9:01 PM #222072
  SkySurferBlue

  How dumb of me, thank you.

  1 user thanked author for this post.

  JS

  

  SkySurferBlue

  Participant

  Topics: 5

  Replies: 5

  Been thanked: 1 time
  10/10/2023 at 9:41 AM #222224
  SkySurferBlue

  Just a follow up question why do the Timeframe(Daily) code line also cause an error?

  

  SkySurferBlue

  Participant

  Topics: 5

  Replies: 5

  Been thanked: 1 time
  10/10/2023 at 10:04 AM #222226
  SkySurferBlue

  SkySurferBlue wrote:

  Just a follow up question why do the Timeframe(Daily) code line also cause an error?

  So from further testing it looks like the Timeframe command is only to be used in ProBuilder not in ProBackTest or the Indicator module. Please confirm.

  

  SkySurferBlue

  Participant

  Topics: 5

  Replies: 5

  Been thanked: 1 time
  10/10/2023 at 2:53 PM #222236
  Nicolas

  the Timeframe instruction can be used in any editor (backtest, indicator or screener).

  I think you have a problem somewhere else in your code or maybe there is a typo?

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4773 times
  08/04/2024 at 2:42 PM #236119
  dsk2293

  I’m having the same issue , parsing error when I try to call an indicator with different timeframes.

  Has anyone figured out a solution for this?

  

  dsk2293

  Participant

  Topics: 0

  Replies: 2

  Been thanked: 0 times
  08/04/2024 at 5:33 PM #236120
  fifi743

  it’s not the other way round

   

  If Dayofmonth > End and Dayofmonth<Start Then

  1	If Dayofmonth > End and Dayofmonth<Start Then

  If Dayofmonth < End and Dayofmonth>Start Then

  

  fifi743

  Participant

  Topics: 10

  Replies: 905

  Been thanked: 420 times
  08/04/2024 at 6:18 PM #236121
  druby

  I can’t comment for screeners because I don’t use. For indicators this doesn’t seem to be a problem. With back-test and beyond it is.

  I don’t know the exact reasons why, but the ‘Parsing Error’ comes up when   ‘Timeframe()’ is placed in a ‘Call’ed file.

  In example above, ‘ Timeframe(Daily)’ is in the called file. This triggers the parsing error.

  Though above solution by @JS removed the need for ‘Timeframe(Daily)’ it indirectly removed the condition triggering the ‘parsing error’.

  To use the ‘Timeframe’ instruction and ‘CALL’ files, when this happens, is to put ‘Timeframe()’  in the Main file and call the other file(s) from within the timeframe block.

  The other file(s) will be generic and not use ‘Timeframe’.

  This is just to avoid this error with back-test, however if you skip back-test and  create an Auto trading file, it fails to run because of an ‘internal error’.

  When you look at the Auto code, the call files code is represented as a function, and after the main code. Maybe this points to a possible reason why it works one way but not the other. I’m assuming the same process happens when back-test is done. The lack of additional processing of the code values with BT and AT may be the reason why it works with indicators.

   

  

  druby

  Participant

  Topics: 1

  Replies: 354

  Been thanked: 265 times
  08/04/2024 at 7:12 PM #236122
  JS

  Maybe as a supplement….

  Of course, parsing errors can arise from different situations, but what I’ve seen in PRT is usually a combination of arrays with certain instructions, for example when you use the “Crosses Over” or “Crosses Under” instruction in combination with values from an array, a “parsing error” follows because the array is not related to the time frame in which these statements are used… (the times cannot be linked)…

  One solution could be to use “normal” variables instead of arrays… (if possible)

  Because arrays are not related to a time frame, statements such as, $myArray[n][1] also return a parsing error…

  As has been pointed out several times on the forum, a “Call” instruction, in combination with an indicator that uses MTF, also results in a passing error…

  The current solution is to incorporate the indicator into the system from which the “Call” takes place…

  When everything has been tried but has failed, the last option is to send a technical report and have your code checked for, syntax errors, unexpected symbols, incorrectly nested structures, wrong data format, etc.

  

  JS

  Participant

  Topics: 26

  Replies: 1716

  Been thanked: 777 times
  08/04/2024 at 8:45 PM #236124
  dsk2293

  Ok thank you, I’ll just copy the code to the main program then.

  

  dsk2293

  Participant

  Topics: 0

  Replies: 2

  Been thanked: 0 times
• Author
  Posts