Those notifications as such don't exist. You can track the Trade instances you get notified via notify_trade which will contain that information

• Docs - Strategy
• Docs - Trade

@han-chen said in Stop loss and profit taker orders triggered on the same candlestick?:

I found this situation happens in my 4h inside bar strategy too, where the take profit price and stoploss fall on the same candle stick because of large candle bars due to the momentum

No. It happens because

1. Your orders are not OCO and don't cancel each other out
2. Because the timeframe you use is large and a bar comprises a large amount of price development

@han-chen said in Stop loss and profit taker orders triggered on the same candlestick?:

Anyone confirms if adding two data frames could help this?

You can add 1000 ... it won't work by simply adding dataframes.

@han-chen said in Stop loss and profit taker orders triggered on the same candlestick?:

Orders placed based on the higher timeframe, will they be executed based on the lower timeframe?

You should read the reference of buy / sell. You decide the target. Docs - Strategy

@han-chen said in Stop loss and profit taker orders triggered on the same candlestick?:

In that case, I can add the 1 min bar which helps backtrader identify, which order should be filled first?

Orders are filled like in real life: FIFO style.

@gaya0007 said in Creating Bid/Ask pandas datafeed error:

    btfeeds.PandasData.datafields = btfeeds.PandasData.datafields + [u'RateDateTime', u'RateBid', u'RateAsk']

As pointed out many times before, this is no longer needed. Don't use it.

The rest is simply the standard extension mechanism.

@ciril-pl said in Logging enter/close a long/short position in SignalStrategy:

Hope this makes sense.

No it doesn't.

@ciril-pl said in Logging enter/close a long/short position in SignalStrategy:

What troubles me if there is a way to overwrite the default notifications to log information when we enter/close a long/short position instead of the common buy/sell

In order for it to make sense you may want to elaborate on what you mean with this. There is no difference in the notifications and how they are delivered, whether you use signals or you don't.

There is no "next simplest" thing.

Docs - Plotting - Section Plotted Elements

You either plot a data feed, an indicator or an observer and they all happen to be classes.

backtrader is a framework which is completely OO-based/oriented.

@cerberos said in Cheat on order execution price:

Could someone please answer @Traderone3 ? His remark is indeed correct, there seems to be no way to buy at Open price AND sell at Close price.

I thin you are mistaken. Let me quote from the other post

@traderone3 said in Cheat on order execution price:

I have activated coo and coc as you described.

cerebro.broker.set_coo(True)
cerebro.broker.set_coc(True)

the problem is that both of them wont work together. The last one takes priority

Priority over what? Orders are executed evaluated in FIFO order. cheat-on-close or cheat-on-open do only allow to take the prices which some shouldn't be able to take.

@cerberos said in Cheat on order execution price:

I did try the solution given 'Option 2' but it does not work, as the order issued during next is only executed the following bar (the following day) which is, from what i gather, what it is expected to do.

You say you want to execute two (2) orders but your post is only talking about one order. To which order are you referring?

To execute things with the open price with cheat-on-open you have to use next_open. Apparently you haven't.

You share no code, you share no data, you share no logs. Let us know something else.

I think you are confused in general. backtrader doesn't work with that notation. It uses the pivot point 0 as the current moment of time and negative indices point to the last (hence "past") values.

If you want to get a complete array of past values, you will get a standard Python array. - Docs - Platform Concepts

You don't have any other approach if you want to operate before the close. You need to have the price updated before you operate.

I would quote your code, but since you only plot images (it must be the new trend after cryptocurrencies)

Your code combined with a pristine installation of backtrader cannot generate the chart you show.

I don't know what your intent was ... but a pull-request which mainly consist of your personal preferences, like voloverlay=False ist not a pull-request.