@jagesso I have also noticed this issue. From what I understand it is partly due to the data retrieved from binance is not the real closed bars. It seems like the bars loaded are only partial.
I'm running indicators on the 4h timeframe, so my solution is to start the script using cron every fourth hour. I still get partially loaded bars, but only the last one so it is quite close to what I'm backtesting.

However, it would be good to be able to backtest partially loaded bars, as this gives the opportunity to make decisions more often than the the timeframe dictates.
I don't understand how to do that though.

@yashagw It's very hard to help you with the limited question you ask. Please include your code and a sample of your data if you can. Thanks.

@hfrog713 It's hard to really provide any helpful information without knowing what "different results" means. Are you getting different EMA values? Are you getting different buy/sell signals from the crossover indicator? Are the signals the same but they result in different orders?

Additionally, without the full script and the data file, it's going to be hard to try it out locally. I ran your script against some AAPL prices and it just generates one sell signal during the period of test. Is that right or wrong? Is it consistent with what TradeView would show? It's hard for me to know.

@run-out Okay, thank you! That was my thought, and although different, I'm assuming that the averages will be a slightly different perspectives of the same data, neither right or wrong, just different.
The large-span minute-based version probably slower but more accurate.

@run-out Well I fixed it.
It was a stupid mistake.
I am initializing self.status outside of the if statement and it is becoming ='neutral' after each trade, which is why then the closing executions never meet part of the condition

@ab_trader Thought that the indicators worked like the strategy where self.datas is accessible. Instead only the first is accessible. You were right

Thank you, found the answer there https://community.backtrader.com/topic/730/non-0th-data-feed-unexpected-behavior-in-indicator-multiple-data-feeds

@ssbilis In your indicator, usually below params, you can control all your plotlines. Review this chapter for more details.

@ab_trader Ah. My bad for missing that comment.

@vladisld Thanks for the quick response! That solved my issue.

@brettelliot You can use python multiprocessing to run seperate backtest.

Data feed was changed, so the code is not a quickstart code anymore. I bet data feed is incorrectly imported. Hard to say since the script is shown badly. Pay attention to the top of the page where the requirement to how the code should be posted are written.

@yacc2000 That code is just expanding the buffer with empty values (NAN). Later in the routine, the value is appended to the buffer. If you notice, even if PANDIZE is false, it's still just expanding the buffer with NAN values, this time using a numpy array vs. a Pandas Series.

@run-out Thank you!

@run-out I don't think I would call this a small error. If I use a 100 EMA like I'm trying to it's 15.1 on 12/31/2019 compared to 14.35. That's a massive difference and will cause massively different results. If these four values are used to calculate the ema

2019-08-08T00:00:00, close: 16.91, ema: nan 2019-08-09T00:00:00, close: 17.97, ema: nan 2019-08-12T00:00:00, close: 21.09, ema: nan 2019-08-13T00:00:00, close: 17.52, ema: 18.37

Shouldn't it be the same from any source as long as the alpha is the same?

Thank you for your response @run-out
Okay, maybe that’s the way…

What if I will create an additional data feed OHLCV 1H time frame (I will be getting it from InfluxDB via influx_feed). Is there a way to get the last day data for calculation in 1H tf?