When you configure a job, you can request that Abaqus/CAE route the job to a specified queue on a remote Linux host computer. You can specify the remote queue by selecting an associated queue name in the Submission tabbed page of the job editor.
Note: The job editor displays default settings for memory usage, parallelization, and precision based on the environment files effective for the current session on the local machine. When you submit a job to a remote machine, Abaqus replaces the default settings with those from the environment files on the remote machine. Non-default settings in the job editor are saved with the job and will be used regardless of where you run the analysis.
Each queue name that appears in the job editor refers to an entry in your Abaqus environment file in which you specify how you want the job to be run on the host computer. In other words, when you select a queue name in the job editor, you specify not only the desired queue on the host computer but also other options, such as the directory on the host computer in which you want to run the job and the files you want copied back to your local directory when the job is complete.
You can specify your preferences for running a job remotely by adding the following to your Abaqus environment file:
def onCaeStartup():
import os
def makeQueues(*args):
session.Queue(name,
queueName,
hostName,
fileCopy,
directory,
driver,
localPlatform,
filesToCopy,
description)
addImportCallback('job', makeQueues)This entry is written using the Abaqus command language. The following list describes each argument in the entry above. name
The queue name that you want to appear in the job editor.
queueName
The name of an existing queue on the host computer. (For information on creating queues on the host computer, refer to the Abaqus Installation and Licensing Guide.)
hostName
The name of the host computer. The default is the name of the local computer.
fileCopy
When the analysis is complete, the value of this argument determines whether or not the analysis files will be copied back to the directory from which the job was submitted. The default value is ON.
directory
The name of the directory on the host computer where you want the job run. You must have write privileges to this directory. The default is the local directory (the directory from which you are submitting the job).
driver
The name of the command on the host computer to execute Abaqus/Standard or Abaqus/Explicit. The default is abaqus.
localPlatform
The platform on the local computer. You can specify either UNIX (for Linux) or WINDOWS; UNIX is the default.
filesToCopy
The three-letter extensions of the analysis files that you want copied back to the local directory when the job is complete. By default, the files with the following extensions are copied: log, dat, msg, sta, odb, res, abq, and pac.
Note: The restart (.res) file, the Abaqus/Explicit state (.abq) file, and the packaging (.pac) file are platform-dependent; if your local platform and remote platform settings differ, you will not be able to copy and use these files without some kind of translation. All of the other files listed above can be copied across platforms without any difficulty.
description
A short description of the queue.
def onCaeStartup():
import os
def makeQueues(*args):
session.Queue(name='long',
queueName='aba_long',
hostName='jobserver',
directory='/scratch/' + os.environ['USER'])
addImportCallback('job', makeQueues)The commands in the example above configure the following:name
The queue name displayed in the job editor is long.
queueName
The queue name on the host computer is aba_long.
hostName
The name of the host computer is jobserver.
directory
The directory on the host computer where Abaqus will store the input file and all other files associated with the job is /scratch/your user name.
Since the fileCopy, driver, localPlatform, and filesToCopy arguments have been left out of the entry above, the default options for these parameters are assigned to this queue automatically.
If you want to create two or more queues, you can repeat the line containing the session.Queue command as many times as necessary. For example, the following Abaqus environment file entry specifies two queues, one named long and the other named job:
def onCaeStartup():
import os
def makeQueues(*args):
session.Queue(name='long',
queueName='aba_long',
hostName='jobserver',
directory='/scratch/' + os.environ['USER'])
session.Queue(name='job',
queueName='aba_job',
hostName='jobserver',
fileCopy=OFF)
addImportCallback('job', makeQueues)The monitoring functions described in “Monitoring the progress of an analysis job,” Section 19.2.6, are available for jobs run remotely just as they are for jobs run locally. However, the output database for the job, like any other analysis files that you may have requested, is not copied to your local directory until after the job is complete. As a result, you must create and start a network output database connector if you want to use the Visualization module to view the results being generated by an analysis running on a remote system. For more information, see “Accessing an output database on a remote computer,” Section 9.3.
