Prime User Manual - ISP
Prime User Manual - ISP
Prime User Manual - ISP
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
96<br />
Chapter 11: Command Syntax<br />
Files<br />
In addition to the jobname.log and jobname.err files, multirefine produces the following<br />
output files:<br />
jobname-out.mae Final structures, all in a single file.<br />
jobname.pdb PDB format file corresponding to lowest-energy structure.<br />
Other structures will have corresponding files jobname-<br />
2.pdb, and so on.<br />
jobname.restart Contains information that allows a job to be restarted if it<br />
fails.<br />
jobname-run-N.archive.zip Archives of subjob output files.<br />
Temporary files, which are normally deleted when no longer needed unless the debugging<br />
option is used, are named according to the following patterns:<br />
jobname-conf-N.* Files associated with temporary structures. All active structures in the<br />
ensemble have a unique serial number N.<br />
jobname-run-N.* Files associated with a given subjob. All subjobs have a unique serial<br />
number N.<br />
Return Value and Errors<br />
multirefine returns a value of 0 on successful completion, 1 otherwise. All scripts run by<br />
multirefine that return a value of 1 also print a message to the file jobname.err. This file is<br />
empty otherwise, as all non-fatal messages are printed to the file jobname.log. Output from<br />
Job Control goes to standard output, and any errors arising before the driver script has started<br />
likewise go to standard output or standard error.<br />
Restarting an Incomplete Job<br />
If a job fails, you can restart it by submitting it again from the same directory. The<br />
jobname.restart file and the archives of subjobs must be present in the directory, and the<br />
directory must be accessible from the host on which the driver job runs. Also, the job records<br />
for the failed jobs must not be purged from the job database, so that the restart mechanism has<br />
access to information on the failed subjobs. If the job records are missing, the subjobs are<br />
repeated.<br />
Failed jobs that were started from Maestro must be restarted from the command line. You can<br />
use the -PROJ and -D<strong>ISP</strong> options to assign the job to the Maestro project and set the incorporation<br />
mode.<br />
Once the job finishes successfully, the subjob archives and the restart file are removed.<br />
<strong>Prime</strong> 2.1 <strong>User</strong> <strong>Manual</strong>