|
||||||||||||||||
|
G03 (Gaussian 03)
|
|
|
The following text shows the commands in the sample batch command, along with a description of what each section is doing.
Red indicates sections which need some customization by the user, with items in red bold italics ALWAYS needing customization for the individual user name or directory/file names. Black sections would normally not need any modification.
The .xml file sets the machine requirements and provides information for the Velocity Scheduler to schedule the job. This section requires modification by the user.
The next section calls the G03 setup file.
This section should not be modified by the user.
The next section defines variables:
ROOTDIR, which points to the folder containing the input file(s) OUTDIR, where you will find the output
INPUT_FILE, which is the name of the input file OUTPUT_FILE, which is the name of the output file CHECKPOINT_FILE, which is the name of the checkpoint file, if you are going to use one. Defining variables in one place makes it easy to modify the script for other jobs. This section should be modified by the user.
The next section makes a temporary directory on the local T: drive. It then cleans up any pre-existing files in the temporary directories and copies the input file into the temporary directories.
This section should not normally be modified by the user.
The next section executes G03W and then copies the output file(s) back to the user's output directory.
This section should not normally be modified by the user, although jobs which do not use a create checkpoint file can comment out the line copying the checkpoint file (leaving the command in the script will not cause a problem). Notice the warning that I/O should always be specified with the full pathname; it is not sufficient to simply "cd" to the directory before calling g03.exe.
The next section cleans up the local temporary space on T: drive. The last line releases the node. This section should not normally be modified by the user.
|
|
![]() |
||