Price Range function

• 01/20/2022 at 2:24 PM #186068
  micquan

  Hi, Has anyone been using the Range function instead of Close/Open/High/Low and does it works with IG ie PRT performs the Range function calculation but will PRT pass the result to IG, and can IG accept the result and execute it?

  // WPR Crossover EMA.

  indicator3 = Williams[14](Range)

  c3 = (indicator3 < -80)

  indicator4 = ExponentialAverage[5](Williams[14](Range))

  c4 = (indicator3 CROSSES OVER indicator4)

  IF c3 OR c4 THEN

     BUY 1 CONTRACT AT MARKET

     SET STOP %LOSS 5

  ENDIF

  

  micquan

  Participant

  Topics: 7

  Replies: 45

  Been thanked: 4 times
  01/20/2022 at 3:52 PM #186088
  robertogozzi

  RANGE is always used, unless you want to do the math yourself!

  Using it with averages as a trading signal is a bit weird on my side, but… if you feel like it, that’s fine!

  Data is passed on to the broker as with any other kind of data.

   

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17188

  Been thanked: 4064 times
  01/20/2022 at 4:18 PM #186095
  micquan

  Robert, I like the word ‘weird’ that’s because I am new to this and may seem weird or creative 🙂 Can you share how and where you would use Range so that I may stop being overly creative. Thanks.

  

  micquan

  Participant

  Topics: 7

  Replies: 45

  Been thanked: 4 times
  01/20/2022 at 4:55 PM #186098
  robertogozzi

  I use CLOSE, TYPICALPRICE, etc… when dealing with indicators. RANGE is not a price, it’s just a measure to evaluate bars (it’s their size).

  I happen to use it occasionally to detect if there’s any sudden spike or drop, but I mostly use it to calculate offsets when displaying graphics on the chart, such as this one:

  defparam DrawOnLastBarOnly = true Periods = 50 HH = highest[Periods](high) Offset = average[20,0](range) DrawText("Highest price in the last #Periods# bars: #HH#",BarIndex,HH + Offset) return

  1 2 3 4 5 6

  defparam DrawOnLastBarOnly = true Periods = 50 HH      = highest[Periods](high) Offset  = average[20,0](range) DrawText("Highest price in the last #Periods# bars: #HH#",BarIndex,HH + Offset) return

  1 user thanked author for this post.

  Midlanddave

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17188

  Been thanked: 4064 times
  01/21/2022 at 12:53 PM #186174
  micquan

  Robert, Thank you in advance again. My simple vix short trading script is shown below. This script executed a Short Sell on the 19th jan when the vix price went above the upper bollinger band but it did not execute a sell short on the 20 and 21 jan – why?

  // VIX SHORT STRATEGY // Definition of code parameters. DEFPARAM CumulateOrders = True // Cumulating positions activated. // Conditions to enter long positions. // Price Crossover EMA and Price Crossover Bollinger Lower Band. indicator1 = ExponentialAverage[10](Range) // Range = difference between High and Low hence provides the highest return, where TypicalPrice = average between High, Low and Close. c1 = (Range CROSSES UNDER indicator1) indicator2 = BollingerUp[20](Range) c2 = (Range CROSSES UNDER indicator2) // WPR Crossover EMA. indicator3 = Williams[14](Range) c3 = (indicator3 < -20) indicator4 = ExponentialAverage[5](Williams[14](Range)) c4 = (indicator3 CROSSES UNDER indicator4) // VIX Upper Price Range - Sellshort Zone. Closing price is used instead of the price Range to ensure the price that is below $25 will not be executed. c5 = (close > 23) IF (c1 OR c2 OR c3 OR c4) AND c5 THEN SELLSHORT 100 CONTRACT AT MARKET SET STOP pTRAILING 10 //SET STOP %LOSS 10 ENDIF // Conditions to exit short positions. indicator5 = BollingerDown[20](Close) c6 = (Close CROSSES UNDER indicator5) indicator6 = Average[50](Close) c7 = (Close < indicator6) indicator7 = Average[20](Close) c8 = (Close < indicator7) sma50GTsma20 = c7 > c8 // Compare the 2 SMA and choose the one that has the lower price to exit short ie increase return. IF c6 THEN EXITSHORT AT MARKET // Exit short when price is below bollinger lower band. ELSIF sma50GTsma20 THEN IF c7 THEN EXITSHORT AT MARKET // Exit short when price is below sma50. ELSIF c8 THEN EXITSHORT AT MARKET // Exit short when price is below sma20. ENDIF ENDIF

  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 37 38 39 40 41 42 43 44 45 46 47 48

  // VIX SHORT STRATEGY   // Definition of code parameters. DEFPARAM CumulateOrders = True // Cumulating positions activated.   // Conditions to enter long positions. // Price Crossover EMA and Price Crossover Bollinger Lower Band. indicator1 = ExponentialAverage[10](Range) // Range = difference between High and Low hence provides the highest return, where TypicalPrice = average between High, Low and Close. c1 = (Range CROSSES UNDER indicator1) indicator2 = BollingerUp[20](Range) c2 = (Range CROSSES UNDER indicator2)   // WPR Crossover EMA. indicator3 = Williams[14](Range) c3 = (indicator3 < -20) indicator4 = ExponentialAverage[5](Williams[14](Range)) c4 = (indicator3 CROSSES UNDER indicator4)   // VIX Upper Price Range - Sellshort Zone. Closing price is used instead of the price Range to ensure the price that is below $25 will not be executed. c5 = (close > 23)   IF (c1 OR c2 OR c3 OR c4) AND c5 THEN SELLSHORT 100 CONTRACT AT MARKET SET STOP pTRAILING 10 //SET STOP %LOSS 10 ENDIF   // Conditions to exit short positions. indicator5 = BollingerDown[20](Close) c6 = (Close CROSSES UNDER indicator5)   indicator6 = Average[50](Close) c7 = (Close < indicator6)   indicator7 = Average[20](Close) c8 = (Close < indicator7)   sma50GTsma20 = c7 > c8 // Compare the 2 SMA and choose the one that has the lower price to exit short ie increase return.   IF c6 THEN EXITSHORT AT MARKET // Exit short when price is below bollinger lower band. ELSIF sma50GTsma20 THEN IF c7 THEN EXITSHORT AT MARKET // Exit short when price is below sma50. ELSIF c8 THEN EXITSHORT AT MARKET // Exit short when price is below sma20. ENDIF ENDIF

   

   

  

  micquan

  Participant

  Topics: 7

  Replies: 45

  Been thanked: 4 times
  01/21/2022 at 12:59 PM #186178
  micquan

  Let me know if Range can be used as in the code above? will it works? and how can I improve it so that it will always execute when the sell short entry conditions are met. Thanks.

  

  micquan

  Participant

  Topics: 7

  Replies: 45

  Been thanked: 4 times
  01/21/2022 at 6:39 PM #186232
  robertogozzi

  A new position was entered on the 19th, then an additional one on the 20th (as from my pic).
  Append these lines to your code to monitor conditions candle by candle in the variable windows opend by ProBackTest:

  graph c1 or c2 or c3 or c4 graph c5 coloured(255,0,0,255)

  1 2	graph c1 or c2 or c3 or c4 graph c5 coloured(255,0,0,255)

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17188

  Been thanked: 4064 times
  01/22/2022 at 2:47 AM #186248
  micquan

  I can’t see the variable as per your snapshot in my probacktest, please advise? Also, my script is running Live so I was expected one execution on the 20th and 21st, as well as the backtest?

  

  micquan

  Participant

  Topics: 7

  Replies: 45

  Been thanked: 4 times
  01/22/2022 at 5:49 AM #186250
  robertogozzi

  Variables can only be monitored when backtesting, while autotrading can only be investigated by PRT, you should ask their assistance staff.

   

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17188

  Been thanked: 4064 times
  01/22/2022 at 2:17 PM #186293
  micquan

  I have raised a ticket with PRT support for missing live transactions, the back testing transaction can be seen from the dashboard. But my question to you is how do I see the variables as per you green box from my window – do I need to turn on something?

  

  micquan

  Participant

  Topics: 7

  Replies: 45

  Been thanked: 4 times
  01/22/2022 at 2:59 PM #186297
  PeterSt

  @micquan,

  Assumed I understood you correctly : Yes.

  Use the wrench in the top-left of the Editor. Set at least one variable there which can be as dummy as you like. Don’t let it iterate, so just one fixed value. See the 2nd attachment for an example.

  Now you will see the variable(s) graphed in a separate dedicated window.

   

   

  

  PeterSt

  Participant

  Topics: 73

  Replies: 2545

  Been thanked: 829 times
  01/22/2022 at 3:10 PM #186300
  robertogozzi

  ProBackTest, when there’s at least one GRAPH instruction, displays an additional window just below the position windows.

   

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17188

  Been thanked: 4064 times
  01/22/2022 at 3:42 PM #186303
  micquan

  Strange that we might not have the same PRT features in our Editor – thought?

  

  micquan

  Participant

  Topics: 7

  Replies: 45

  Been thanked: 4 times
  01/22/2022 at 4:02 PM #186306
  PeterSt

  You have. But you need to add a random variable (there called label). See below at the mouse pointer.

  

  PeterSt

  Participant

  Topics: 73

  Replies: 2545

  Been thanked: 829 times
  01/24/2022 at 8:03 AM #186422
  Nicolas

  Please refer to the rejection error to understand why an order was not accepted by the broker.

  Attached is a non-exhaustive list of the elements that can impact a live trading strategy and create differences with a demo account and/or backtests:

  • Spread
  • Slippage
  • Orders rejections due to one of the above reason, but also because of the allowed distance from current price to put pending orders (known as “minimal distance”)
  • Different trading hours (ProOrder code launched in a different time zone / custom hours, by the user)
  • Coding problem: division by zero error, null or negative periods for indicators, ..
  • Lack of responsiveness of IG demo servers (if IG is the broker), although this has improved considerably since last year.
  • Make backtests without tick-by-tick option
  • “set stop trailing” instruction that give IG the total control of your stoploss, can be moved differently between accounts due to points above
  • Limited risk accounts and their rules
  • Guaranteed stoploss rules and fees
  • Starting a strategy at a different time (1 hour or even 1 minute later): depending on the code of the strategy, the results of some calculations could be different.
  • Margin required on the trading account (no demo or backtest tests are made on this subject)
  • Overnight and overweekend fees
  • Automatic adjustement of stop orders checked or not when launching the ProOrder
  • Minimal distance used in backtests for pending orders, not the same as in real trading, due to broker requirement
  • Different contract size between backtests and live

  Because backtests are only tested on history *with no connection to live market* , you may encounter differences with real live trading environment subject to spread enlargement, slippage, etc.

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4774 times
• Author
  Posts