When you get an order notified in notify_order you can assign them to a dict (probably appending it to a list) when the order is still alive (method of the order) and removing it when not alive.
As key you can directly use the data attribute from the order or its, for example _name which is set with the name you give to cerebro.adddata. See
To cancel them, just go over the list for an entry an issue cancel in the strategy.
@jackg101 said in Adding datafeeds mid-simulation for OTC trading:
is there a way to add datafeeds on-the-fly as the strategy decides to trade something?
No it doesn't. This is something which has been even discussed privately with option traders, but it's not something in the core of backtrader
@tizenhet said in Position size changes without buy or sell order:
self.buy(data=d, size=int_) self.order = self.buy()
@angles922 said in backtesting with manual trades:
I am trying to add a stoploss and takeprofit onto my manually imported order history.
You cannot. Because the order is executed right at once and has no binding to other orders (the brackets).
Set the brackets (as OCO orders) when you are notified in notify_order. See Docs - OCO Orders
@knolch said in Plot doesn't show up when running the code:
I will not use Spyder now for developing and testing my trading strategies but do you have any recommendations what I could use instead?
I mean IDLE works but it's very uncomfortable. Which Editor are you using for backtesting?
Apparently people like PyCharm for which a Free Community edition is available.
Unless you are comfortable with vim or emacs and don't mind using a standard shell (which for all intent and purposes happens to be bash these days)
@knolch said in Plot doesn't show up when running the code:
[[<Figure size 640x480 with 5 Axes>]]
That's the result of this in the code
cerebro.plot()
Because plot does actually return the created matplotlib figure, should the user desire to do something with it. If you were assigning the return value to a variable, you wouldn't see that.
The problem is Spyder. The configuration you have is preventing the chart from being displayed. Your options:
Try
cerebro.plot(iplot=False)
This disables automatic inline plotting detection in backtrader, but this is probably not going to help.
Have a look at the charting options in Spyder for plotting. If set to automatic, change it to inline and viceversa.
It's the problem with this Python kernel hijacking shells: they think they know better.
@s1000rr said in Generic CSV data feed, indicator problems on plot:
1: Not reading first ~11 lines of input file. I used a small sample of the data file 2006-day-001.txt from github
Minimum period. The lines are all being read. Read:
@s1000rr said in Generic CSV data feed, indicator problems on plot:
2: Buy and Sell indicators are shifted above/below the stock price
Read the documentation for the BuySell observer. It is an observer which simply indicates when and what happened. Detailed values are given to you in order execution.
@s1000rr said in Generic CSV data feed, indicator problems on plot:
3: Inconsistent time separation
Using the same plot from above we can see the varying distance that separates the vertical date lines.
You probably want to elaborate on what you mean here.
In any case if you are expecting a charting platform, backtrader isn't. The charts are meant only as a quick visual aid for inspection and are not the core of the platform. It's just an add-on built on top of matplotlib
The code must be a joke. A bad one, obviously.
Some of your posts:
https://community.backtrader.com/post/7664
You want to do things in notify_trade and yet you present code now which is like a random collection of characters. How have you managed to buy/sell anything?
https://community.backtrader.com/post/7632
You backtest twice over the same period (with an extended period once) and show random results for the common leading period, which is impossible. But how can you backtest when your code is random?
Your turn.
You could also simulate the gap entering with a simple Stop and link both the StopLimit and Stop to make them OCO orders, which guarantees that only one of them gets executed. See
The indicators use a generic notation to refer to the data with which they operate and don't care about indexing the array.
In any case I feel you are using the wrong approach imho. Instead of changing the data feeds, you should change what the data feed delivers, which at the end of the day delivers the same result, but is compatible with any way an indicator can be written.