Questions Ab Initio

 Co>Op monitors & records the state of jobs so that if a job fails, it can be restarted. This state info is stored in files associated with the job and enables the Co>Op to roll back the system to its initial state, or to its state as of the most recent completed checkpoint. Generally, if the application encounters a failure, all hosts and their respective files will be rolled back to their initial state or their state as of the most recent completed checkpoint; you recover the job simply by rerunning it.    Details: An AI job is considered completed when the mp run command returns. This means that all the processes associated with the job — excluding commands u might have added in the script end — have completed. These include the process on the host system that executes the script, and all processes the job has started on remote computers. If any of these processes terminate abnormally, Co>Op terminates the entire job and cleans up as much as possible....

 These are temporary files used by the checkout process. Under normal circumstances you should not see them. However, if the checkout failed or was interrupted, these files can be left behind. Delete them and try checking out again.    Details: The checkout procedure includes two steps to ensure that a checkout does not leave your sandbox in a half-checked-out state: 1. It checks out the files, but gives them the .abi-unc suffix (for "uncommitted"). 2. Once every file is successfully checked out, the . abi-unc files replace the real files. If an error occurs midway through checkout, any .abi-unc files that have been created might be left behind. If you receive the error message "Cannot write project parameters file: /path/filename.abi-unc" during checkout and you see . abi-unc files, delete them and try checking out again. Uncommitted files are usually left behind because a checkout process was aborted.