Replies: 2 comments 7 replies
-
@brosaplanella @Saransh-cpp Can you please check whether latest version works fine in your PC for longer simulations, using above minimal code? Thanks. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Was your crash from running out of memory? I was trying out the block of code you shared, and the estimate from the process monitor was 16GB of memory by around 30% of the simulation. |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
It was mentioned on the release note that latest version was optimised for speed and memory usage. However, I noticed the opposite with my simulations. I noticed that ageing simulations have become slower and crashing for longer cycles, even for SPM model. I tried different methods to speed up the solver, but it is still slower for SPM. Below code has crashed after 41% of progress. Can someone check whether the case is the same with you as well or it is only the problem with my installation please? Here is the minimal example. Let me know if I missed anything. I use WSL (Ubuntu 22) on Windows and updated recently with latest PyBaMM version. Python 3.10.12
Here is the error that was shown after crash on Jupyter notebook on VS code:
The Kernel crashed while executing code in the the current cell or a previous cell. Please review the code in the cell(s) to identify a possible cause of the failure. Click [here](https://aka.ms/vscodeJupyterKernelCrash) for more info. View Jupyter [log](command:jupyter.viewOutput) for further details
which could be due to eating up of RAM by PyBaMM.
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions