Job Control Glossary (JOB CONTROL IS DEPRECATED)
- entry
-
(1) A collection of settings in the hosts file that defines a configuration for running jobs on a given host. There can be more than one entry for a given host, with different settings.
(2) A structure and its properties in a Maestro project. - execution host
-
The computer that a job runs on.
- hosts file
-
The file that contains information on available hosts that is used by Job Control. This file is usually named
schrodinger.hosts. - job directory
-
The directory on the execution host to which the input files are copied from the submission host and from which the output files back to the submission host when the job is finished. This is usually a subdirectory of the scratch directory that is created by Job Control.
- launch directory
-
The directory from which the job is started. Same as submission directory.
- launch host
-
The computer that you submit a job from. Same as submission host.
- local host
-
The computer that you are logged on to. Usually this is also the computer you are using for job submission.
- Maestro user resources directory
-
The
maestro147subdirectory (folder) of your Schrödinger user resources directory. - output directory
-
The directory to which output files are copied at the end of the job. This is usually the same as the submission directory.
- queue host
-
A computer that can run the queueing software. This is not necessarily the queue manager: for example, if the queuing software is installed on an NFS-mounted file system, it could be any host that has that file system mounted.
- remote host
-
A computer that is available to you over a network.
- remote job submission
-
Submitting a job to a computer other than the one you are logged on to or that you are running Maestro on.
- Schrödinger user resources directory
-
location for storage of resources (files, scripts, data) used by Schrödinger software for an individual user, but shared across computers. This location is
$HOME/.schrodingeron Linux and%APPDATA%\Schrodingeron Windows. (%APPDATA%corresponds toC:\Users\username\AppData\Roaming) - scratch directory
-
The directory that is used for temporary files. The files are usually created in a subdirectory of this directory that is unique to the user and the job.
- submission directory
-
The directory from which the job is started. This is the directory from which input files (specified without a path) are copied to the job directory, and to which output files are copied at the end of the job. If a job is run from Maestro, this is usually a subdirectory of the Maestro working directory.
- submission host
-
The computer that you submit a job from. Same as launch host.