System stopped

• 10/12/2016 at 8:17 AM #14748
  Gordon Gekko

  Hi

  How can i render this?

  This trading system was stopped because the program used a negative or zero offset (ex: close[-10]) during the evaluation of the last candlestick. Please add protections to your code to prevent negative or zero offsets.

   

  

  Gordon Gekko

  Participant

  Topics: 2

  Replies: 8

  Been thanked: 0 times
  10/12/2016 at 9:29 AM #14750
  Nicolas

  Because you have calculation period somewhere in your code and it returns a null or negative value. You might be able to fix this with ABS instruction.

  If it doesn’t work, please post your code for a complete explanation of what happened.

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20830

  Been thanked: 4744 times
  10/12/2016 at 7:42 PM #14792
  Gordon Gekko

  Thanks for answer

   

   

  

  Gordon Gekko

  Participant

  Topics: 2

  Replies: 8

  Been thanked: 0 times
  02/21/2018 at 7:24 PM #63413
  namrevlis24

  Hi all,

  since I ran into the issue which Gordon Gekko describes, I would like to show you how I solved it for my case.
  The original code was:

  old code which ran on error

  ... IF NOT ONMARKET and (some conditions true) THEN BUY 3 CONTRACT AT MARKET ENDIF ... IF LONGONMARKET AND (highest[BarIndex - TradeIndex](high) < something) THEN do something ;-) ENDIF ...

  1 2 3 4 5 6 7 8 9

  ... IF NOT ONMARKET and (some conditions true) THEN BUY 3 CONTRACT AT MARKET ENDIF ... IF LONGONMARKET AND (highest[BarIndex - TradeIndex](high) < something) THEN do something ;-) ENDIF ...

   

  In every every trade, when the first candle ran through and the system tried to evaluate the next candle, it ran on error
  “… system was stopped because the program used a negative or zero offset (ex: close[-10]) during the evaluation of the last candlestick. …”

  I solved it by just preventing the code to check “BarIndex – TradeIndex” when it is 0. This is always 0 in the first candle of the trade. So I added a simple condition to my code so that it looks as follows:

  new code, which worked fine :-)

  ... IF NOT ONMARKET and (some conditions true) THEN BUY 3 CONTRACT AT MARKET ENDIF ... IF BarIndex - TradeIndex > 0 THEN IF LONGONMARKET AND (highest[BarIndex - TradeIndex](high) < something) THEN do something ;-) ENDIF ENDIF ...

  1 2 3 4 5 6 7 8 9 10 11

  ... IF NOT ONMARKET and (some conditions true) THEN BUY 3 CONTRACT AT MARKET ENDIF ... IF BarIndex - TradeIndex > 0 THEN IF LONGONMARKET AND (highest[BarIndex - TradeIndex](high) < something) THEN do something ;-) ENDIF ENDIF ...

   

  This worked well and the system doesn’t stop anymore 🙂

  1 user thanked author for this post.

  Nicolas

  

  namrevlis24

  Participant

  Topics: 1

  Replies: 4

  Been thanked: 1 time
  02/22/2018 at 10:47 AM #63471
  Nicolas

  Thanks a lot for your feedback about how to resolve this kind of error. We could also test the Highest period with MAX instruction, to “force” the period to be at least 1 if it is inferior or Barindex-Tradeindex if it is superior:

  ... IF NOT ONMARKET and (some conditions true) THEN BUY 3 CONTRACT AT MARKET ENDIF ... IF LONGONMARKET AND (highest[max(1,BarIndex - TradeIndex)](high) < something) THEN do something 😉 ENDIF ...

  1 2 3 4 5 6 7 8 9 10

  ... IF NOT ONMARKET and (some conditions true) THEN BUY 3 CONTRACT AT MARKET ENDIF ...   IF LONGONMARKET AND (highest[max(1,BarIndex - TradeIndex)](high) < something) THEN do something 😉 ENDIF ...

   

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20830

  Been thanked: 4744 times
• Author
  Posts