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
Long simulation runs can generate a lot of data files. This seems to cause delays at the file system level when lots of files accumulate in PCXMC's MCRUN folder, where the simulation results are saved.
Probably should build in a section where periodically, the result files are moved somewhere else (after the rotation loop perhaps) so that they can be collected and put into the database.
This would interfere with the way simulations are restarted after being interrupted, so that part would need to be re-done.
The text was updated successfully, but these errors were encountered:
I think this can be solved by storing the simulation results to the database as each run is completed. Then there's no need to write separate output files for each run. This wouldn't solve the problem of restarting an interrupted simulation run though.
Description
Long simulation runs can generate a lot of data files. This seems to cause delays at the file system level when lots of files accumulate in PCXMC's MCRUN folder, where the simulation results are saved.
Probably should build in a section where periodically, the result files are moved somewhere else (after the rotation loop perhaps) so that they can be collected and put into the database.
This would interfere with the way simulations are restarted after being interrupted, so that part would need to be re-done.
The text was updated successfully, but these errors were encountered: