Executing DesignSight Simulations Remotely

The two methods for performing remote DesignSight simulations require slightly different hardware and software configurations. This section provides an overview of the different configurations and procedures for using the Abaqus Simulation Engine.

This task shows you how to:

Related Topics
Remote Execution
Queue Submission
Direct Host Submission

Use remote queue submission

Remote queue submission uses a preconfigured submission host to manage the distribution of the simulation execution across multiple CPUs.

  1. In the client application, select Tools > Options.

    The Options dialog box appears.

  2. Select the Simulation > DesignSight category in the left-hand box.

    The options for DesignSight settings appear.

  3. Specify the following information in the Simulation Execution options:

    1. Select Run remotely using submission host.
    2. Enter a submission host. This host must be part of a predefined LSF or Windows HPC queue, and the Abaqus Simulation Engine must be available on each node of this queue (see Running the Installation Procedure).
    3. Select Use queue.
    4. Enter the Total number of CPUs that you want to utilize when executing a simulation. This number cannot exceed the number of CPUs available in the selected queue.

  4. Click OK to save the settings.

    Tip: The simulation execution options can be modified at any time prior to submitting the simulation.

  5. In the DesignSight workbench, create a simulation and click Simulate (see "Performing DesignSight Simulations" in the DesignSight User's Guide).

  6. DesignSight establishes communication with the submission host using the Server Monitor and passes the simulation to the submission host (see Configuring the Server Monitor).

  7. The submission host generates a submission form for the simulation and passes it to the job scheduler for the queue (see Creating the Submission Template).

  8. The job scheduler allocates the simulation to the appropriate machines within the queue based on the parameters defined in the submission form. The simulation is executed according to the options defined in the aqs.env environment file (see Adding Queue Controls to the aqs.env File).

  9. When the simulation is complete, the results are passed back to the client.

    The results are displayed in the DesignSight workbench.

Use direct host submission

Direct host submission requires that you explicitly indicate the CPUs on which the execution will be distributed.

  1. In the client application, select Tools > Options.

    The Options dialog box appears.

  2. Select the Simulation > DesignSight category in the left-hand box.

    The options for DesignSight settings appear.

  3. Specify the following information in the Simulation Execution options:

    1. Select Run remotely using submission host.
    2. Enter a submission host.
    3. Select Use hosts specified below.
    4. Enter a list of host names and the number of CPUs to allocate on each host. The Abaqus Simulation Engine must be available on each of these hosts (see Running the Installation Procedure).
    5. Enter the Total number of CPUs that you want to utilize when executing a simulation. This number cannot exceed the number of CPUs that are allocated on the specified hosts.

  4. Click OK to save the settings.

    Tip: The simulation execution options can be modified at any time prior to submitting the simulation.

  5. In the DesignSight workbench, create a simulation and click Simulate (see "Performing DesignSight Simulations" in the DesignSight User's Guide).

  6. DesignSight establishes communication with the submission host using the Server Monitor and passes the simulation to the submission host (see Configuring the Server Monitor).

  7. The simulation is executed on the specified hosts according to the options defined in the aqs.env environment file (see Configuring the aqs.env Environment File).

  8. When the simulation is complete, the results are passed back to the client.

    The results are displayed in the DesignSight workbench.