3. Backfilling - Live Trading
For code/output blocks: Use ``` (aka backtick or grave accent) in a single line before and after the block. See: http://commonmark.org/help/

Backfilling - Live Trading

  • T

    When using the back-filling option for live trading, Backtrader will still request historical data for the instrument you are trading. This is great for filling up your indicators minperiod

    https://www.backtrader.com/docu/live/oanda/oanda.html?highlight=backfill#oandadata

    However, Backtrader will also open and close orders as it loops through the historical data.

    Just wondering how others are working around this? I have created a self.start_date attribute during __init__() (datetime.datetime.now()) and then I simply return from next() if the data date is not > than the start_date

    Just curious if anyone is using a different, more elegant solution?

    Also my solution can run into problems it you are not in the same timezone as your data feed provider. To workaround this, I have had to add some further hacky time zone conversion. i.e:

    self.start_date = datetime.now().astimezone(self._timezone).replace(tzinfo=None)

    1
  • P

    @ThatBlokeDave said in Backfilling - Live Trading:

    However, Backtrader will also open and close orders as it loops through the historical data.

    It seems you are blaming the devil instead of your code, which is the executor (unless the platform has achieved self-consciousness)

    Live feeds deliver a data.LIVE status notification when backfilling is over and real-time data is delivered. You can find it at least here:

    The sources for the ibtest sample show how to tackle that.

    0
    T
     1 Reply
  • T

    @Paska-Houso

    Not blaming anything. Just reporting what I am seeing.

    Thanks for the pointer - I will take a look.

    0
  • P

    Not intended to criticize, it just seemed funny that the platform would be opening and closing orders without any external intervention.

    0
    T
     1 Reply
  • T

    @Paska-Houso

    No worries. I probably was not clear. I was not sure how to stop next() being called before the live data. Naturally the code to open a position is in my next() method. :)

    Anyway, I will take a look at your suggestion. I do appreciate it.

    1 1 Reply

  • @ThatBlokeDave

    I use a LIVE notification to stop anything I don't want to happen during backfilling. For instance I have SMS alerts sent when orders occur only when LIVE but I don't want to send SMS messages when backfilling so I use it like this:

    buy_ord = self.buy()
buy_ord.addinfo(name="Long 3 Stack")
self.sell_ord = self.sell(exectype=bt.Order.Stop, price=long_stop)
self.sell_ord.addinfo(name='Long Stop Loss')

self.tradeid = 'LONG_STACK'
self.close_long_price = long_take_profit
                                
print('*' * 50)
print('ENTER TRADE')
print('*' * 50)
    
if not self.data_live: ##### NOTE: ONLY SENDS SMS MESSAGE WHEN LIVE BUT ALLOWS ORDERS TO BE PROCESSED WHEN BACKFILLING
    return
                                                               
message = SendSMS.client.messages.create(
    from_='xxxxxxxxx',
    to='xxxxxxxxxxx',
    body=('OPEN TRADE {}, Price {}'.format(
        self.productname,
        round(self.data0.close[0],2),
        )))

    You could apply the if not self.data_live: code above the buy_ord = self.buy() to stop orders showing when backfilling.

    0
Log in to reply
 
});