Difference in candle Values

ayyaz
Pulled at -10:16:3-
Processing Candle of tmstr=10:0:0 dtstr=2019-1-7 epoch_time=1546835400 min=0 hr=10 sec=0
processing last_epoch_processed=1546834500 epoch_time=1546835400 candle={'volume': 8100, 'high': 514, 'low': 513, 'date': datetime.datetime(2019, 1, 7, 10, 0, tzinfo=tzoffset(None, 19800)), 'close': 514, 'open': 513}
where as kite show


Please resolve it ASAP

  • sujith
    Are you comparing the candles generated at your end and the candles on Kite?
  • ayyaz
    no candle pulled from Historical APIs and on kite
  • rakeshr
    @ayyaz
    We checked the same scenario at our end, historical APIs 15minute OHLCV and Kite web chart 15 minutes OHLCV is matching correctly. In historical APIs, to get exact 15minute/any interval OHLCV data, you need to request it post 10-15 seconds after completion.
  • ayyaz
    Pulled at -10:16:3-
    Processing Candle of tmstr=10:0:0 dtstr=2019-1-7 epoch_time=1546835400 min=0 hr=10 sec=0
    processing last_epoch_processed=1546834500 epoch_time=1546835400 candle={'volume': 8100, 'high': 514, 'low': 513, 'date': datetime.datetime(2019, 1, 7, 10, 0, tzinfo=tzoffset(None, 19800)), 'close': 514, 'open': 513}
    where as kite show


    Note again i am requesting it 15 min candle of 10:0:0 at 10:16:3
    do you want to suggest further . do u want me to delay a little further ?
  • rakeshr
    @ayyaz,
    We checked it multiple time, can't find any difference in OHLCV data of historical data and live kite chart. Can you log all historical APIs request along with time stamp at your end?
  • ayyaz
    i think when i pull it later value changed again but when i try to pull it in real time , issue exists , let me see i have delayed pulling little later
  • rakeshr
    @ayyaz
    The way historical APIs work is, all the ticks in a given period is captured and is written to the database. There can be a delay in write operation to the database. So, to get complete candle OHLCV data, you need to add a buffer period of 10-20 seconds. Eg: For 10:30 AM 15 minute candle, you need to request it at 10:45:15 AM or later.

    PS: The historical data is provided only for backtesting purpose. We don't recommend using it for live strategies. You can use Web sockets data to generate candle data at your end.
  • ayyaz
    Processing Candle of tmstr=9:30:0 dtstr=2019-1-8 epoch_time=1546920000 min=30 hr=9 sec=0
    processing last_epoch_processed=1546919100 epoch_time=1546920000 candle={'volume': 25650, 'high': 156.45, 'low': 156.25, 'date': datetime.datetime(2019, 1, 8, 9, 30, tzinfo=tzoffset(None, 19800)), 'close': 156.25, 'open': 156.45}

    at curTime=9:46:18 b
  • rakeshr
    @ayyaz
    Are you getting any difference? For Scrip/instrument token?
    Can you check if, your system request time is in sync with real time, not in different time zone?
  • ayyaz
    time is perfectly synced no issues
Sign In or Register to comment.