You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an evaluation of the initial current performed in simulation when setting up events. Drive cycles are turned into interpolant and code accounts for this when doing a current step but when doing a c_rate step the object is a multiplication and the logic fails
Something like this will fix it in simulation line 290
if (isinstance(op.value, pybamm.Interpolant) or
isinstance(op.value, pybamm.Multiplication)):
inpt = {"start time":0}
init_curr = op.value.evaluate(t=0, inputs=inpt).flatten()[0]
sign = np.sign(init_curr)
PyBaMM Version
23/5
Python Version
all
Describe the bug
There is an evaluation of the initial current performed in simulation when setting up events. Drive cycles are turned into interpolant and code accounts for this when doing a current step but when doing a c_rate step the object is a multiplication and the logic fails
Something like this will fix it in simulation line 290
Steps to Reproduce
Relevant log output
No response
The text was updated successfully, but these errors were encountered: