Thank you.

And, this is the output:

in live data islive in live data start in live data load in MyInd prenext in MyInd prenext in MyInd prenext in MyInd prenext in live data timer in MyInd data0 next: 2006-12-07, 4018.69 in MyInd data0 next: 2006-12-08, 4019.89 in MyInd data0 next: 2006-12-11, 4052.89 in MyInd data0 next: 2006-12-12, 4059.74 in MyInd data0 next: 2006-12-13, 4094.33 in MyInd data0 next: 2006-12-14, 4118.84 in MyInd data0 next: 2006-12-15, 4140.66 in MyInd data0 next: 2006-12-18, 4130.06 in MyInd data0 next: 2006-12-19, 4100.48 in MyInd data0 next: 2006-12-20, 4118.54 in MyInd data0 next: 2006-12-21, 4112.10 in MyInd data0 next: 2006-12-22, 4073.50 in MyInd data0 next: 2006-12-27, 4134.86 in MyInd data0 next: 2006-12-28, 4130.66 in MyInd data0 next: 2006-12-29, 4119.94 in MyInd data0 next: 2006-12-29, 4119.94 in MyStrategy data0 next: date: 2006-12-29, close: 4119.94, ma: 4114.21 in MyStrategy data1 next: date: 2021-11-23, close: 91.00, ma: 4114.21 in live data load in MyInd data0 next: 2006-12-29, 4119.94 in MyStrategy data0 next: date: 2006-12-29, close: 4119.94, ma: 4114.21 in MyStrategy data1 next: date: 2021-11-23, close: 92.00, ma: 4114.21

@drew-clayman said in 'AutoInfoClass_OrderBase_Order_SellOrder' object has no attribute 'isclosed' (for trade.isclosed):

self.notify_trade(self.order)

Few notes:

notify_trade method is defined to accept the 'Tradeinstance and not anOrder` instance. usually the notify_trade is not called directly, instead it is used by the Cerebro instance to notify the strategy about the trade status change

More on Trade class (https://www.backtrader.com/docu/trade/)
More on notify_trade method (https://community.backtrader.com/topic/1047/notify_trade)
There are few examples of notify_trade usage in QuickStart Guide.

@run-out thank u for your help

@chewbacca Try this thread. https://community.backtrader.com/topic/2707/out-of-memory-error-when-running-optstrategy/8?_=1637411279547

@littleking Try this thread. https://community.backtrader.com/topic/2707/out-of-memory-error-when-running-optstrategy/8?_=1637411279547

@littleking you may take a look at the following code in my fork and compare it to the current code used in backtrader:

https://github.com/vladisld/backtrader/blob/lazytrader/backtrader/feeds/influxfeed.py

@nsananguly

Please take a look at the following post about extending the PandasData to include custom columns:
https://community.backtrader.com/topic/1828/how-to-feed-a-custom-pandas-dataframe-in-backtrader/6

@adamb032 I solved the issue, the data needs to have at least an open and close value in it for the simulated broker to work, once i made an open/high/low/close dataframe of all close values it works as expected.

@adamb032 Trade position gets closed every time the units for the position reaches or crosses zero. See the docs here.

@carameldragon I have the same confusion.I guess we are mislead by the sample in documnet.
when in some old version, the order.executed.value of sellorder is depended on sell price ;now, it is depended on buy price

IBStore is using the IBPy library for communication with Interactive Brokers. This library seems to be thread safe theoretically. However I'm not sure that sharing the IBStore instance between multiple Cerebro instances is supported and/or tested.

For example, I'm not sure how the notification mechanism will work, when multiple instances of the Cerebro engines will have to be somehow connected to the same instance of the IBStore.

@walt This behavior is by design although I would agree is somewhat unexpected.

During first few prenext calls only the first data datas[0] is actually iterated ( since the second data datas[1] is still not started). Getting the 'current' value of the datas[1] doesn't make sense at this point - however the current implementation of GenericCSVData will just return the latest loaded bar value. Other data feed classes may just throw exception for example.

To be on the safe side I'd suggest to just test that the data was actually iterated before trying to access the current bar:

if len(self.datas[1]): px2 = self.datas[1].close[0]

the len(self.datas[1]) will be zero unless the first bar of the data will be iterated.

@tony-shacklock said in #ValueError #Invalid #literal for #int() while running #cereber.run():

@nsananguly
Have you tried setting maxcpus=1?
cerebro.run(maxcpus=1)
I think this is needed when optimising, but I don't know if it's related to your error.

I tried it out. Didnt work. But I am sure your suggestion will come handy further down the line. Thanks on that

@atori Can you suggest what did you do to correct the error ?
I am also facing the same error.

Error that I get is :
ValueError -> 14 cerebro.run()

ValueError: invalid literal for int() with base 10: '28-0'

Seeking guidance on what has gone wrong and how can this be course corrected .

@ab_trader In my case, cheat-on-close is set to True, but the order.executed.price still is the next bar open price, rather than curr bar close price.

@backtrader This is a common requirement. I don't understand why PandasData doesn't add a custom_ fields parameter to meet this feature.