how to set target and stop for backtesting?

• 09/05/2019 at 10:33 AM #106570
  Malend

  Hello,
  I try to backtest a strategy in a tickchart. Everytime the a bullish candle crosses the bullish sma50 with the opening below the sma 50 and the close above the sma20, or a bearish candle crosses the bearish sma5o with the opening above the sma 50 and the close below the sma20, I want to buy 1 contract with a target from 5 and a stoploss from 2
  This is what I have created, but I see in the output of the backtest that something isn’t right. I see profits and losses far above my presets.
  Thank you, Marc

  // moving averages m50 = Average[50] //LONG - crossing bullish candle through bullish sma50 from below. // The body of the previous candle needs to be below the sma50 c1 = open[1] < m50 and close[1] < m50 c2 = open < m50 and close > m50 // bullish sma50 c3 = m50[1] =< m50 // Long conditions L = c1 and c2 and c3 //SHORT - crossing bearish candle through bearish sma50 from above. // The body of the previous candle needs to be above the sma50 c4 = open[1] > m50 and close[1] > m50 c5 = open > m50 and close < m50 //bearish sma50 c6 = m50[1] => m50 // Short conditions S = c4 and c5 and c6 // Buy Long IF L THEN BUY 1 CONTRACTS AT MARKET ENDIF // Sell Short IF S THEN SELLSHORT 1 CONTRACTS AT MARKET ENDIF // Stops en Targets  SET STOP loss 2 SET TARGET PROFIT 5

  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 29 30 31 32 33 34 35 36

  // moving averages m50 = Average[50]   //LONG - crossing bullish candle through bullish sma50 from below. // The body of the previous candle needs to be below the sma50 c1 = open[1] < m50 and close[1] < m50 c2 = open < m50 and close > m50 // bullish sma50 c3 = m50[1] =< m50   // Long conditions L = c1 and c2 and c3   //SHORT - crossing bearish candle through bearish sma50 from above. // The body of the previous candle needs to be above the sma50 c4 = open[1] > m50 and close[1] > m50 c5 = open > m50 and close < m50 //bearish sma50 c6 = m50[1] => m50   // Short conditions S = c4 and c5 and c6   // Buy Long IF L THEN BUY 1 CONTRACTS AT MARKET ENDIF   // Sell Short IF S THEN SELLSHORT 1 CONTRACTS AT MARKET ENDIF   // Stops en Targets  SET STOP loss 2 SET TARGET PROFIT 5

   

  

  Malend

  Participant

  Topics: 14

  Replies: 100

  Been thanked: 4 times
  09/05/2019 at 10:38 AM #106571
  Nicolas

  Please use the ProOrder forum for automated trading related question, and the ‘insert code button’ to add a embed a code in a post.

  If you want to use takeprofit and stoploss values in points, you should use the pprofit and ploss instruction instead:

  // Stops en Targets SET STOP ploss 2 //2 points/pips SET TARGET pPROFIT 5 //5 points/pips

  1 2 3

  // Stops en Targets SET STOP ploss 2 //2 points/pips SET TARGET pPROFIT 5 //5 points/pips

   

  

  Nicolas

  Keymaster

  Topics: 83

  Replies: 20899

  Been thanked: 4868 times
  09/05/2019 at 10:51 AM #106576
  Malend

  Thanks Nicolas,

  I will in the future. I was doubting where to post this, because I had problems with the coding.
  I was already looking for a way to embed the code.
  Thanks again, Marc

  

  Malend

  Participant

  Topics: 14

  Replies: 100

  Been thanked: 4 times
  09/05/2019 at 11:09 AM #106579
  Malend

  Hi again, I still have strange losses and profits in my backtest list. If 1 point = $50,- then the max of my loss will be constantly $100,- and my profits will be always $250,-
  Now I have variable profits and losses.

  I want to check how often the strategy as described above reaches the target or the stop.

  So I guess there is something else I didn’t do right.

  Thanks, Marc

   

  

  Malend

  Participant

  Topics: 14

  Replies: 100

  Been thanked: 4 times
  09/05/2019 at 11:28 AM #106586
  GraHal

  @Malend … you may like to consider attached … it’s your code but on DAX 5M over 10k bars with spread = 2

  

  GraHal

  Participant

  Topics: 222

  Replies: 9297

  Been thanked: 2462 times
  09/05/2019 at 11:29 AM #106590
  Malend

  Thanks a lot Grahal,
  I am gonna check it out right now.
  Marc

  

  Malend

  Participant

  Topics: 14

  Replies: 100

  Been thanked: 4 times
  09/05/2019 at 11:31 AM #106591
  GraHal

  Malend wrote:

  So I guess there is something else I didn’t do right.

  Try below as the 1st line of code

  DEFPARAM CUMULATEORDERS = False

  1	DEFPARAM CUMULATEORDERS = False

   

  

  GraHal

  Participant

  Topics: 222

  Replies: 9297

  Been thanked: 2462 times
  09/05/2019 at 12:12 PM #106599
  Malend

  Thanks Graham,

  Makes definitely sense.
  I also see some bugs in my strategy definitions and what happens when I am in a buy postion and a sell signal shows up.

  Work for me to do. Great.

  Thanks a lot, again. Marc

  1 user thanked author for this post.

  GraHal

  

  Malend

  Participant

  Topics: 14

  Replies: 100

  Been thanked: 4 times
  09/05/2019 at 12:17 PM #106600
  GraHal

  Be good to share any improvements please?

  I have the version I posted above running in Demo Forward Test.

  

  GraHal

  Participant

  Topics: 222

  Replies: 9297

  Been thanked: 2462 times
  09/05/2019 at 9:12 PM #106649
  Malend

  It works Graham, I am testing it also with other backtest variations.

   

  

  Malend

  Participant

  Topics: 14

  Replies: 100

  Been thanked: 4 times
  09/05/2019 at 9:16 PM #106650
  Malend

  The only thing I would like to have is that when I am in an a position that the TA or the SL stops that position, and not a start from a new postion the other direction. It can open a new position, but better for me would be to have only one psotion open.

  

  Malend

  Participant

  Topics: 14

  Replies: 100

  Been thanked: 4 times
  09/05/2019 at 9:43 PM #106656
  GraHal

  Malend wrote:

  but better for me would be to have only one psotion open.

  Which version / code are you referring to … your original code, my version or some new version of yours?

  Always best to post the code then others may spot the reason for your Issue.

  Also if you have optimised a lot of variables then it is very useful to post the .itf with the optimiser already set up with variable names, range and steps … as I did in the .itf I posted above to help you.  Makes it easier / quicker for folks to help and improve further.

  Cheers

  1 user thanked author for this post.

  Malend

  

  GraHal

  Participant

  Topics: 222

  Replies: 9297

  Been thanked: 2462 times
  09/06/2019 at 8:26 AM #106677
  Malend

  Thanks Graham for your feedback how to use this platform. I will post my latest update today with the questions and when itb works in the end.

   

  

  Malend

  Participant

  Topics: 14

  Replies: 100

  Been thanked: 4 times
• Author
  Posts