opentime bug or not?

• 02/08/2021 at 9:57 AM #160633
  Paul

  is it a bug or not?

  If using criteria like this

  ctime = opentime >= 153000 and time < 160000 // entry if ctime then

  1 2 3 4

  ctime = opentime >= 153000 and time < 160000   // entry if ctime then

  it still can open a trade sometimes at 000000 (assuming the rest of the code is good.)(on a 30s timeframe tested)

  Changing opentime to time fixes it.

  

  Paul

  Participant

  Topics: 40

  Replies: 812

  Been thanked: 660 times
  02/08/2021 at 10:53 AM #160641
  robertogozzi

  OpenTime is the time when a candle opens, Time when a candle closes.

  It seems correct.

  Try this indicator:

  ctime = opentime >= 153000 and time < 160000 Return ctime

  1 2	ctime = opentime >= 153000 and time < 160000 Return ctime

   

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17656

  Been thanked: 4367 times
  02/08/2021 at 11:25 AM #160645
  Paul

  with that indicator, it gives value 1 often at 23:59:30 for 1 bar

   

  

  Paul

  Participant

  Topics: 40

  Replies: 812

  Been thanked: 660 times
  02/08/2021 at 11:33 AM #160649
  Paul

  same on dax & other timeframes like 5m, it’s off.

  switching to a stock, it’s ok

  strange!

  

  Paul

  Participant

  Topics: 40

  Replies: 812

  Been thanked: 660 times
  02/08/2021 at 11:53 AM #160653
  robertogozzi

  That’s correct on a 30-second TF:

  • 23:59:30 is > 15:30:00  (OpenTime, the candle that OPENS at 15:30:00)
  • 23:59:30 is 00:00:00 when the last bar CLOSES and it’s < 16:00:00

  you probably should avoid mixing Opening and Closing times.

   

  1 user thanked author for this post.

  Paul

  

  robertogozzi

  Moderator

  Topics: 69

  Replies: 17656

  Been thanked: 4367 times
  02/08/2021 at 11:59 AM #160658
  Paul

  haha your right! I assumed you can use both, but I will stick to time and double check if I use opentime 🙂

  Thnx for the explanation!

  

  Paul

  Participant

  Topics: 40

  Replies: 812

  Been thanked: 660 times
• Author
  Posts