@sahil said in Design Document of Backtrader And Extending it for multiple marketplaces (India):

Is there any design document or data flow diagram available for backtrader?

No.

@sahil said in Design Document of Backtrader And Extending it for multiple marketplaces (India):

Can it be used(extended) for creating an live engine(trading for India marketplace)

You need to create your own Broker and data feeds. Some people have done it.

@sahil said in Design Document of Backtrader And Extending it for multiple marketplaces (India):

Also, is it possible to use it for trading strategies involving multiple assets

Yes. It's built-in.

@sahil said in Design Document of Backtrader And Extending it for multiple marketplaces (India):

ML algorithms?

That's up to you, not to backtrader. See https://github.com/Kismuz/btgym

@arrr said in Problem with custom ohlc vars:

However if I call same self.make_ohlc() from self.next() - it works

I fail to understand what the problem is. You have for sure a very clear idea about what troubles you, but you have already said it works. What you want to do with the data is of course unknown.

The world of algotrading is mostly an English speaking world. Although it's obvious that not everybody feels comfortable reading/writing it.

Feel free to do it.

You only have to consider the copyright and linking to the original documentation.

Indicators are not meant to be time dependent and are not meant to be calculated at specific moments. They are (re)calculated with each iteration.

You can always check if it's 10:00 and then act upon. Data feeds have a datetime component. Get the time

dt = self.data.datetime.datetime()  # returns a complete datetime instance
tm = dt.time()  # just the time of day

No, there are no limits.

Blog - Evaluating external historical performance

@arrr said in Problem with custom ohlc vars:

this gonna work fine, considering I'm using data replay?

What should work fine? The info you have provided in this thread is close to none. You simply say that you cannot get data in __init__, which is something obvious.

No, there isn't.

@arrr said in Problem with custom ohlc vars:

it's obvious that calling it every bar is not a proper way to handle this

I missed that before. The question is: why?

backtrader isn't pandas (which many people apparently believe). Evaluation of things happens with each new incoming tick, which is given to the user during next, where you have access to the data.

First thing when posting is reading how to post (at the top of each page in the forum). That helps.

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

If you don't do this, your code become basically unreadable.

In any case your code is not complete. From the log it seems an error related to observers. Not much more can be said.