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
Describe the bug
This is a little bit of a placeholder since I have not pinned down a good MWE for this yet - but there is something about time-dependent models in pyGSTi 0.9.13 that causes a memory blowup when the time parameter for modelmembers is being set. It happens even when forward simulation is not being performed by PyGSTi, i.e. we are literally just calling .set_time() a bunch.
The bug was introduced sometime between f93fd3c and 0.9.13 release. MWE coming soon.
Environment (please complete the following information):
pyGSTi version 0.9.13 (at least)
python version 3.11.9
OSX 15.3
The text was updated successfully, but these errors were encountered:
Describe the bug
This is a little bit of a placeholder since I have not pinned down a good MWE for this yet - but there is something about time-dependent models in pyGSTi 0.9.13 that causes a memory blowup when the time parameter for modelmembers is being set. It happens even when forward simulation is not being performed by PyGSTi, i.e. we are literally just calling
.set_time()
a bunch.The bug was introduced sometime between f93fd3c and 0.9.13 release. MWE coming soon.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: