SimFactory should abort if there are no checkpoint files when submitting an existing configuration

Create issue
Issue #1335 new
Ian Hinder created an issue

When submitting a simulation which already contains at least one restart, simfactory should abort if there are no checkpoint files available. This likely means that something went wrong. Starting the simulation again is always the wrong thing to do in this case, as it will waste CPU time and might go unnoticed.


Comments (1)

  1. Ian Hinder reporter
    • removed comment

    Starting the simulation again would be the right thing to do if no checkpoint file had been written before the first restart crashed. Maybe SimFactory should look in all past restarts for checkpoint files, starting from the latest, in case there are restarts which aborted before the checkpoint files were linked in (this just happened to me, and wasted a day or so on stampede).

  2. Log in to comment