placing an order when predefined levels achieved.

• 05/12/2021 at 3:12 PM #169483
  Slowlyslowly

  Hi Roberto that has fixed the problem of cancelling the trade when LINE B is breached – thank you it seems to work perfectly.

  And the suggestion for changing close to high or low is much better so have amended your code.

  Only issue that is left is that code ONLY  activates trading a 926 cross over when is price  below LONG A.

  In most cases the trigger LONG A is hit then price retraces so the 926 would activate ABOVE line A – so the code needs to TRIGGER looking for a 926 crossover once price is <LONG A BUT allow the trade to be placed when price is < or > LONG A on the 926 crossover ?

  added a screen shot of a live trade today that didn’t activate because the cross over happened above LONG A and your amended code so it gives you a clear picture.

  so trigger = <LONG A TO PLACE AN ORDER ON 926 CROSSOVER

  BUT THIS 926 MUST BE ALLOWED TO TAKE PLACE WHEN PRICE IS < OR >  LONG A  at the moment the code only allows the crossover below LONG A(which is the trigger instruction ) (and the reverse for a short)which is obviously not realistic as the trade is based on price retracing.

   

  the screen shot explains it better.

   

  If you  can fix this issue it is all sorted and an excellent code.

  

  Slowlyslowly

  Participant

  Topics: 15

  Replies: 23

  Been thanked: 2 times
  05/12/2021 at 3:25 PM #169486
  robertogozzi

  Not it enters (Long) when the price, after having sit bwtween A and B, is anywhere when the crossover occurs.

  Do you want the price to be ABOVE level A when the crossover occurs?

   

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17398

  Been thanked: 4188 times
  05/12/2021 at 3:50 PM #169490
  Slowlyslowly

  Hi Roberto

   

  No I have to disagree it does not . it failed to trigger LONG with LONG A set at 6988 on the FTSE  in a live trade today .

  Even if you back test (which I did several times) from 1410hrs today on the 1 minute time frame with LONG A set at 6988- PIPS set at 20 (so B is not breached) .

  price falls below LONG A to 6982 ( so triggers looking for ema crossover ) then reverses – the crossover takes place above LONG A at around 6995 but no trade is activated.

  my previous  testing today shows it works when the cross over is below LONG A but not above – its almost as though it takes the trigger point as <6988 but then doesn’t recognise a cross over when its above the trigger point only below  ?

  we obviously need the code to recognise the cross over at both < or > LONG A as both can occur once the trigger point is hit at A to B

  

  Slowlyslowly

  Participant

  Topics: 15

  Replies: 23

  Been thanked: 2 times
  05/12/2021 at 5:28 PM #169513
  robertogozzi

  The code you sent me entered a LONG trade at 15:33 (14:33 UK) following a crossover at 15:32 (14:32 UK) when the closing price was 7002.9.

   

   

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17398

  Been thanked: 4188 times
  05/12/2021 at 7:28 PM #169527
  Slowlyslowly

  Hi Roberto

  Well this did confuse me – I think we have a back testing issue here.

  if I run the back test from 1410 my time – it does not pick up the trade but picks up a later trade around 1727.

  if I run the back test from the time on your screen shot 11 may 1505 (1405 my time ) I get the same results as you ?

  I then ran back test from different times this morning 0800 and different time after that as Line A was hit several times and it picks up trades on the back test as it should.

  I ran it from 1310 it picks up a trade at 1345 even though level `b was breached – now I know from testing that the changes you made for level B on live trades worked perfectly (so far ) so that doesn’t make sense.

  I’m assuming this is a PRT backtesting issue/error – the main thing being a backtest from 11 may (yesterday) at 1405 my time agrees with your results BUT a back test from 1410 my time today and it doesn’t find the trade you found. and a backtest from 1310 today picks up a trade after level B is breached.

  so that is amazingly confusing ? not sure you have any ideas as to why …..

  anyway that to one side – I know live it did not trade hence my message to you.

  I think all I can do is trade live and screen shot the results as the back test clearly does not work –

  to ensure I did not make an error I got a friend to do the same tests and he got the same results as me with different start times on the back test ….all very strange 🙂

  

  Slowlyslowly

  Participant

  Topics: 15

  Replies: 23

  Been thanked: 2 times
• Author
  Posts