Closed NickKarpowicz closed 1 year ago
Found the cause: if the currently-loaded simulation is very large (this one had 2810 total simulations in the batch), the count timer will allocate new memory, and fail when the system runs out.
This job was so large that when I worked around the problem (run a small simulation first), it ran out of memory on the cluster. Maybe it would be good to have a max size warning
I was making a 2D parameter scan (delay1, delay2) on a sequence, and it crashed under windows, reproducibly