Running Your Jobs on an LSF Cluster

You can control the LSF-specific options in the Abaqus Component Editor. If you are connecting to an LSF cluster, this option is highly recommended.

Related Topics
About Configuring Abaqus Jobs to Run on an LSF Cluster
Supported Versions of Software

  1. Double-click the Abaqus component icon .

    The Abaqus Component Editor appears.

  2. From the Abaqus Component Editor, click the Grid tab.

    The tab appears with no grid option selected.

  3. Select LSF from the Grid Type list.

  4. Select the type of operating system that the LSF system is running using the Target Machine list.

    You can select either Windows (64-bit) or Linux (64-bit).

  5. Select the correct release of Abaqus using the Abaqus Release list.

    You can select any release of Abaqus from this list.

  6. Click Generate Script.

    The script that is used to submit the job to an LSF cluster appears in the large text box at the bottom of the tab.

  7. Edit the generated script directly in the large text box, as necessary.

    For example, you may need to add cpus=N for MPI jobs or *StudyRunCount* to supply design study information from Isight to Abaqus for reduced Abaqus license token consumption, when appropriate.

    Note: The Command is Script File check box cannot be used with the component. This setting can be ignored.

  8. Enter the following information, as desired.

    You can edit one or all of the values. You can also accept the default values.

    Option Description
    Queue Specifies the queue where the job should run. You can obtain the available queue names from the LSF “bqueues” command. Refer to the bsub -q option on the man page for more information.
    Hosts Lists the candidate hosts (space-separated) where the job should run. Refer to the bsub -m option for more information.
    Resources Specifies the resource requirements for the LSF job. Refer to the bsub -R option for more information.
    Number of Parallel Job Processors Specifies the number of processors to be used by Abaqus when running in MPI mode. It must match any ncpus= argument on the Abaqus command in the script (as mentioned in Step 6) or the job may fail.

    Note: The Automatically transfer input/output files (bsub-f) should not be used in this scenario, since the component probably does not contain all necessary files as file parameters. Only the use of a shared filesystem is supported.

  9. To use any bsub arguments that are not provided in the component editor, click Advanced to access the Additional Grid Options dialog box.

    1. Type the commands in the large text area using standard bsub command-line option syntax (see the bsub man page). Line breaks are ignored, so the commands can be space-separated and/or on separate lines.

      Typically, these options are those that are used less frequently. However, there may be a need for them in specific scenarios. For example, you could use -G for fairshare scheduling or -M to change the per-process memory limit.

    2. Click OK to return to the Abaqus Component Editor.

  10. Click OK to save your changes and to close the Abaqus Component Editor.