AND refers to both the condition holding true/false and or refers to one of the conditions holding true/false.
for example:

val1 = 5.0
val2 = 6.0
if val1 > 2.0 and val2 < 10.0:
    print(True)

this would fail if val2 was infact greater than 10.0
for the 'OR' case:

val1 = 5.0
val2 = 6.0
if val1 > 2.0 or val2 == 10.0:
    print('only condition one is true')

Well, technically you can do that pretty easy. Make a custom indicator that follows the same formulation as your target one, and normalize it to output +1, if it goes above a certain threshold value and vice-versa for the -1. Take a look at the indicator reference and see how you can go about doing this.

I am not too sure what would the problem is here, however, I think it may be linked to your feeding of data. I would suggest taking a look at the values, see where the error might be.

Hello @mamos so there is a workaround this. You would need to make some changes to the original plot functions. I have this code written up for you. put this function at the end of your cerebro initialization and you should be good.

def saveplots(cerebro, numfigs=1, iplot=True, start=None, end=None,
             width=16, height=9, dpi=300, tight=True, use=None, file_path = '', **kwargs):

        from backtrader import plot
        if cerebro.p.oldsync:
            plotter = plot.Plot_OldSync(**kwargs)
        else:
            plotter = plot.Plot(**kwargs)

        figs = []
        for stratlist in cerebro.runstrats:
            for si, strat in enumerate(stratlist):
                rfig = plotter.plot(strat, figid=si * 100,
                                    numfigs=numfigs, iplot=iplot,
                                    start=start, end=end, use=use)
                figs.append(rfig)

        for fig in figs:
            for f in fig:
                f.savefig(file_path, bbox_inches='tight')
        return figs

saveplots(cerebro, file_path = 'savefig.png') #run it

Just dont plot. Write up the savefig method and not the cerebro.plot. Try to read into the docs to see the plotting features.

@hamid-zargar the best way to resolve your issue is to head to the docs. You can essentially add order info to whenever you are generating an order so for example in a long situation:

long_order = self.buy()
long_order.addinfo(name = 'long entry')

or you can essentially add a log statement/print each time you are sending an order in next()that is long or short.
either way, give the docs a good read.
Cheers

You have to import the indicators as such:

bt.indicators.SimpleMovingAverage(self.datas[0].close, period = 40)

You will be benefitted greatly if you just took a look at the docs and navigate to the quickstart section.

@lammy the initialization all depends on you so for example:

I have my close prices loaded into BT as:
self.dataclose = self.datas[0].close

Now I my strategy buys the asset/instrument when (self.dataclose x 2) is greater than 'x' value.

self.close2 = self.dataclose*2
So essentially, all I did was take the pandas column and just explicitly times it by two and assigned it to another object self.close2

Now you can take this object use it in your next() method and create your buy/sell orders

I am not too sure what you are trying to accomplish, but in my opinion, I found that direct manipulation of pandas data frame using pandas itself is quite effective before you import it into backtrader. However, in the case, you want to create additional lines for your data, for example, creating a new line data based on some data manipulation on the moving average data, this you can actually initialize in the strategy class itself.

I am actually a bit confused. First off use those backticks for future reference
"For code/output blocks: Use ``` (aka backtick or grave accent) in a single line before and after the block. See: http://commonmark.org/help/"
Coming back to your question, what do you mean by verifying real transactions?