ProBacktest: Parabolic SAR indicator issues

• 05/26/2025 at 11:56 AM #247612
  NeoTrader

  Hi there PRT coders.

  Backtesting the Parabolic SAR indicator, and testing one range optimisation of mySARmin, there seems to be no end of errors with the code!

  Have I found a limitation in the PRT platform and the backtesting of said indicator?

  And I am right to place the SAR math code in the backtest, to optimise the range of mySARmin ?

  > This can be coded, I just wanted to know if this is the case, or my coding skills and AIM’s are not coding correctly?

  *I have run this past a couple of AIM’s and all three concluded, eventually, that the PRT platform has a limitation!

   

  As always, any guidance towards a solution is much appreciated.

  NT 🙂

  

  NeoTrader

  Participant

  Topics: 8

  Replies: 65

  Been thanked: 16 times
  05/26/2025 at 4:33 PM #247620
  Iván

  Hi. I can’t see your code so I don’t know what happens…
  Here you have an example of PSAR working:

  //minSAR=0.02 //accSAR=0.02 //maxSAR=0.2 pSAR = SAR[minSAR,accSAR,maxSAR] YourConditions = close CROSSES OVER pSAR[1]

  1 2 3 4 5 6

  //minSAR=0.02 //accSAR=0.02 //maxSAR=0.2   pSAR = SAR[minSAR,accSAR,maxSAR] YourConditions = close CROSSES OVER pSAR[1]

  You can see in screenshots variables configuration and optimization results.

  1 user thanked author for this post.

  NeoTrader

  

  Iván

  Moderator

  Topics: 0

  Replies: 1565

  Been thanked: 612 times
  05/27/2025 at 9:39 PM #247668
  NeoTrader

  Iván wrote:

  Here you have an example of PSAR working:
  You can see in screenshots variables configuration and optimization results.

  Now that is a fab answer, plugged in, and works right away.

  My error was using a non standard term for the SAR indicator name in the code 🤦‍♂️
  Thank you Iván

  For your correction
  NT 🙂

   

  

  NeoTrader

  Participant

  Topics: 8

  Replies: 65

  Been thanked: 16 times
• Author
  Posts