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
Once we have a stable version, it would be great to look into optimizing memory in the pipeline. I am currently running with 64GB allocation (with long heating simulations). The job runs out of memory once all of my layered acoustic and heating simulations are run, at the stage of posthoc water simulations. Not a critical problem as this is the last stage and it is straightforward to run water simulations. But this likely arises from keeping all of the prior outputs in memory. There are likely many temporary outputs that can be dropped during execution.
The text was updated successfully, but these errors were encountered:
[feature improvement]
Once we have a stable version, it would be great to look into optimizing memory in the pipeline. I am currently running with 64GB allocation (with long heating simulations). The job runs out of memory once all of my layered acoustic and heating simulations are run, at the stage of posthoc water simulations. Not a critical problem as this is the last stage and it is straightforward to run water simulations. But this likely arises from keeping all of the prior outputs in memory. There are likely many temporary outputs that can be dropped during execution.
The text was updated successfully, but these errors were encountered: