Open the Application Management tool from the start menu list.

The methods authorised for your account are shown in either a tile or row layout within the Application Management pane. Permission to use a particular method is provided through a team construct. Application methods are allocated to one or more teams. To use a given method your identity must be a member of the respective team.

Any documentation provided with the application can be seen by clicking the Wiki icon (row layout ) or the Open the Wiki page button in the right pane (row or tile layout). Note that this right pane can be resized of hidden by clicking the vertical separator. Below is a sample wiki for an Abaqus solver run method.


From the Application Management pane there are several actions that can be performance on a given application. This guide describes the Open action to prepare and run a job using the selected application. Double-click on the application icon to directly open the application for input.

The other actions relate to editing an application. Refer to the onboarding guide for details.

Opening an application displays a window to set the parameters for submitting a job. This input panel is sometimes referred to as a job profile. The profile window has two parts:

  • Execution environment – Parameters related to the cluster system and batch resource manager.
  • Application parameters – Parameters specific to the application method.

^ Name | A name that will be used by the job to the batch resource manager.\\
Abaqus also uses the notion of job name. This **Name** has no relation to any such application parameters. \\
This is a required parameter. The format is controlled, so the actual value may be compacted or abridged to fit. |
Cluster Select the cluster to run this job from the list.
Project Choose the relevant project code to assign to this job. The list of project codes is limited to those allowed for the identified login.
This is a required parameter.
Accounting Choose an appropriate accounting code for the selected project.
Description Free field for adding some information about this job.
It is good practice to include at least some text to aid later interpretation of the job purpose.


In this set the parameters for the batch resource manager to schedule the job. The name of the scheduler is give in brackets, eg. PBS-PRO.

The parameter fields are grouped into three categories:

  • Basic – The minimal standard set of parameters set be any user.
  • Advanced – An extended set of batch parameters to allow more precise scheduling control for users having some familiarity with the underlying batch manager behaviour.
  • Expert – The complete set of possible batch manager options giving full scheduling control to expert users.

Generally the Basic options comprises two settings for the user.

Queue The batch queue name to use for this job. If not set a default is usually assigned.
Cores The number of computing cores to use for parallel execution. This translates into the number of MPI processes assigned in the application, or the number of shared-memory threads, or a hybrid of both.

Execution directory

In general the HPC Gateway supports two choices for where jobs will run:

  1. Automatically defined – Gateway will create a unique directory under a system shared filesystem. This directory will be owned by and visible only to the connected user.
  2. Manually defined – The user should define the precise directory on the cluster where this job will run. The location can be selected by using a reduced File Explorer started from the adjacent icon

When the execution directory is automatically defined all input files will be implicitly transferred or linked into this directory prior to the execution phase. In this case it will be necessary for the input files or folder to be explicitly identified as application parameters with type file.

The area on the right of the profile window shows the input parameters used by this application method. Each setup will be specific to the application.

Parameters can be defined with different types: test, file, boolean, int, float, script. The type can be inferred from the field that is provided for user to select or input, e.g.:

  • File type parameters will be accompanied by a file selector icon.
  • Integer type parameters will have a numeric selection wheel. This may be constrained within a range of allowed values. (The GPU count is a constrained unit.)
  • Boolean type parameters have a check box only.
  • Text type parameters can have a free input field, or a list of valid settings.

The choice of parameters is made by the editor of the application method. A best practice approach to such development is to clearly state the meaning of the parameter within this input profile window. Further explanation should also be provided as a tooltip for each parameter. Additional directions should be found within the wiki documentation associated to the application method.

A completed job profile can be saved for later reuse; to rerun, to clone for a subsequent job, or retain for traceability. A profile can be named in the entry field at the bottom-left of the profile panel. Previously saved profile can be located by clicking the arrowhead inside this field.

Controls for profile organisation are:

  • Reload profile – if changes are made but not required.
  • Save profile – store under the given name.
  • Add profile shortcut to desktop – place entry onto the web desktop for fast access.
  • Delete profile – remove named profile.

Once all parameters have been set click the Submit button to send the job to the batch resource manager.

If a required parameter has not been set the submit button will not be usable. The entry field for missing parameters will be highlighted in red.

Return to topics page if followed as part of the training programme.

Return to Quickstart page.