Cluster Computing (Job Configurations)

) job configuration is useful when you want to submit a batch job to a job scheduler or you want to run the model in distributed mode as a batch job. When you have specified the cluster computing settings, click the button (

) in the window’s toolbar to save the current setting as default.

	These settings are saved to The Preferences Dialog Box in the Multicore and Cluster Computing section.

Use the list to specify if the settings are synchronized with the corresponding study step.

If you want to use a job scheduler or do some other operations before or after the job, you set the command line in the and fields. You can define a default command line with the system properties cs.precmd and cs.postcmd. If the command line contains {nn} or {perhost} they are replaced by the values in the field and field, respectively.

From the list, select which batch job to submit. Click the button

) to move to the window for the selected node.

	After making these settings, click the Save as Default () button on the Settings window toolbar to save the current directory settings as the default preference.

Choose the : (the default), , , , , or :

Select (the default) to configure to run on many types of clusters and schedulers, including Linux clusters.

•

When is selected, and you have started a multiprocessor daemon (MPD) on the computer, click to select the check box.

•

The entry in the field specifies the host file used for the job. If left empty, MPD looks for a file mpd.hosts in the Linux home directory.

•

Select which bootstrap server should be used by MPI using the setting.

•

If your cluster is Linux and it requires that an SSH (secure shell) or RSH (remote shell) is installed in an uncommon directory, use the field to set the RSH communication protocol.

•

If you must provide extra arguments to MPI, use the field.

•

Enter the (physical nodes) to use (default is 1 node).

Select to use the Windows HPC Server 2008 or HPC Pack 2012 job scheduler to submit the batch job.

•

If you want to include scheduler arguments, add them to the field (for example, for mpiexec).

•

If you must provide extra arguments to MPI, use the field.

•

Enter the (physical nodes) to use (the default is 1 node).

•

Select a : (the default), , or . allocates one process on each host, allocates one process on each socket, and allocates one process on each core.

•

The check box is selected by default. Click to clear if you want to run on nodes shared by other users.

•

The entry in the field is the IP address of the enterprise adapter of the head node or the DNS name of the head node. The default is localhost.

•

Set the names of . The job scheduler only allocates jobs on the nodes listed by you.

•

Enter the . The job scheduler only allocates jobs on the nodes belonging to the group.

•

Enter the minimum required . The default is 0. The job scheduler only allocates jobs to nodes with at least as many cores as set.

•

Enter the minimum required . The default is 0. The job scheduler only allocates jobs to nodes with at least as much memory as set.

•

Enter the before the job is canceled. The default is .

•

The entry in the field is the user account that COMSOL Multiphysics uses for submitting the job. You provide the password in a separate command window that opens at execution time with the possibility to save the credentials.

•

Select a — , , (the default), , or — for the scheduled job.

Select to use the Windows Compute Cluster Server 2003 job scheduler to submit the batch job.

•

If you want to include scheduler arguments, add them to the field (for example, for mpiexec).

•

If you must provide extra arguments to MPI, use the field.

•

Enter the (physical nodes) to use (the default is 1 node).

•

The check box is selected by default. Click to clear if you want to run on nodes shared by other users.

•

The entry in the field is the IP address of the enterprise adapter of the head node or the DNS name of the head node. The default is localhost.

•

Set the names of .

•

Enter the before the job is canceled. The default is .

•

The entry in the field is the user account that the COMSOL software uses for submitting the job. You provide the password in a separate command window that opens at execution time with the possibility to save the credentials.

•

Select a — , , (the default), , or — for the scheduled job.

•

If you want to include scheduler arguments, add them to the field (for example, for mpiexec).

•

Select the that should be used by MPI.

•

If your cluster is Linux and it requires that an SSH (secure shell) or an RSH (remote shell) is installed in an uncommon directory, use the field to set the RSH communication protocol.

•

If you must provide extra arguments to MPI, use the field.

•

Select a — , , or — to specify if COMSOL Multiphysics should parallelize on the physical level or on the OGS/GE-allocated level. For and , specify the to allocateThe setting can be used to control the granularity more. In this case set the number of computational nodes to use in the . For and , the number of processes on each node is set in the field; usually this is 1.

•

Enter the to set the name of the Sun Grid Engine.

•

Enter the to set the number of processes on each host.

•

If you want to include scheduler arguments, add them to the field (for example, for mpiexec).

•

If you must provide extra arguments to MPI, use the field.

•

Enter the (physical nodes) to use (the default is 1 node).

•

Enter the to set the name of the Sun Grid Engine.

•

The check box is selected by default. Click to clear if you want to run on nodes shared by other users.

•

The entry in the field is the IP address of the enterprise adapter of the head node or the DNS name of the head node. The default is localhost.

•

Set the names of .

•

Enter the minimum required . The default is 0. The job scheduler only allocates jobs to nodes with at least as much memory as set.

•

Enter the before the job is canceled. The default is ; that is, the job is never canceled.

•

Select when you want to submit a batch job to a job scheduler without running a distributed job.