Batch (Job Configurations)

) job configuration is the main node for running batch jobs. Batch jobs run in separate processes. You can therefore continue working in the COMSOL Desktop once a batch job is run. Model changes in the COMSOL Desktop after the batch job is submitted do not affect the model in the batch job. The job has a special Batch Data subnode, which collects External Process subnodes containing job status information.

As in the Parametric Sweep (Job Configurations) node, the batch job is defined by a number of subnodes. The batch job then runs each subnode. Use the button in the toolbar to save the current directory setting as the default directory for batch files.

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

Set the number of cores that the batch job should use in the field if desired, by first selecting the corresponding check box. The default behavior is to use all available cores. If you set jobs to more than one, several jobs can run at once. When you are running more than one job at once, it is important that the product of and jobs does not exceed the number of cores available on the computer. Otherwise you experience performance degradation. When you run multiple batch jobs on your computer, COMSOL Multiphysics makes sure this does not happen if you are using the automatic setting. If you have a multicore machine, you can change these settings to control the number of simultaneous processes that are allowed to run in the batch sweep and also how many cores each of them is allowed to use. If you have a six-core machine, for example, change the to three and the to two. This allows three parameters to be solved in parallel, where each solver process gets access to two cores. For simulations where each parameter represents a small computational problem, you can increase the number of simultaneous jobs to as many cores as you have on your computer. For larger problems, keep this setting to one simultaneous job (the default setting) to fully utilize the multicore processing power of the solvers.

	You can also control the number of simultaneous jobs from the Batch Sweep node’ Settings window, in the Study Extensions section. In that case, the number of cores is automatically computed from the number of physical cores divided by the number of simultaneous jobs (for this to be automatic, you must not select the Number of cores check box).

Select the check box when the batch process should run results nodes that create graphical contents such as exporting to file.

Enter the . The default is 0. This is the maximum number of times the job can be restarted if it fails to complete.

Enter a value for the . The default is 300 seconds. This is the longest time the process is allowed to run before it must inform that it is still running. Failure to do so means that the process is considered dead and a new process is started if the maximum number of job restarts is not reached.

You can set a if you want the batch process to start at a later time. Select the hour (0–23 hours) to start the run from the list, or select to start the batch process without a delay.

Set the of the model. If the batch job is generated from a parametric sweep, a unique name that depends on the parameter names and values is created. The default is to overwrite any previous models with the same name. Disable the default by clearing the check box. Select the check box to clear the meshes before running the batch sweep. The default is to not clear the meshes. Select the check box to clear the solutions before running the batch sweep.

Specify the to store the model. The directory refers to the location where the client (COMSOL Desktop) reads and writes data. Click if you want to browse to a directory.

From the list, choose (the default), or choose , which instead of parameter names and parameter values uses an index scheme iX, iY,...., where same indices relate to the same parameter value. This option gives much shorter filenames.

•

If you are connected to a COMSOL Multiphysics server on another computer, you can control the working directory used by the COMSOL Multiphysics server if you select the check box and enter the path to the server or for the path. Otherwise a temporary directory on the COMSOL Multiphysics server is used to save files. The server directory path refers to the location where the COMSOL Multiphysics server reads and writes the corresponding data (assuming a client-server configuration).

•

If the batch job has another path to the directory, you select the check box and enter the path to the batch or for the path. If the batch job has another path to the directory, you select the check box and enter the path to the batch or for the path. The external COMSOL batch directory path refers to the location where the batch process reads and writes the data.

•

If COMSOL Multiphysics is installed in a different directory from where the batch job runs, enable the and specify the install directory (click or enter the path to the ). This can occur if you are submitting jobs to a job scheduler with the node.

Click the button (

) at the top of the window to save the current directory setting as the default directory for batch files.

Some examples of how to specify the paths for the directories where the batch job reads and writes data:

•

If you use a Windows client connected to a server running on a Linux server head node that in turn is submitting a job to a job scheduler, that setup then requires the main (which is a local Windows path) and a server directory path (which is a Linux path on the head node). Most likely, an external COMSOL batch directory path is not needed in this case because it is likely that the cluster and the head node are using the same file system.

To summarize: If the batch job and the COMSOL Desktop do not share the same view of the file system, you must specify at least the main and the external COMSOL batch directory.

Select the check box to synchronize the solutions computed by the batch processes with the model. This allows additional postprocessing after the sweep has finished. The default is to disable solution synchronization. Select the check box to synchronize the accumulated probes computed by the batch processes with the model. The accumulated probe synchronization is enabled by default. Select the check box to enable that all batch processes save the models to file. In most cases, use the solution synchronization and probe synchronization functionality instead because otherwise the data ends up in one file for each process and cannot be postprocessed efficiently. Use the list to select probes to update during the batch sweep. The default is , which selects all probes for plotting and tabulation of probe data. Select to open a list with all available probes. Use the (

), (

), and (

) buttons to make the list contain the probes that you want to see results from while solving. Select to disable probe updating for batch sweep.

Select the check box to activate the accumulation of probe updates for both the variation on the solver level (time, frequency, and so forth) and on the batch sweep level. Use the to select where to put the data. Select the check box if all the model probes should be accumulated in the table. If the check box is not selected, the probes selected by the selector are used.

The node can also be used as a client to drive a server on another machine. You enable the client functionality by selecting the check box. You can then set the (default: localhost) and of the server for the batch job (default: 2036) to connect to. This number is the default port number. If the server you want to connect to is using another port, then edit this number accordingly.