Parametric Sweep (Job Configurations)

) job configuration, which can loop over a given set of parameters. For each set of parameters, it runs the sequence defined by its subnodes. You can combine the sequence with other Batch, Parametric, or Cluster Computing sequences in a hierarchical way by adding a job configuration that points to another node. You can, for instance, create a node that does a LiveLink™ update and then runs a node that in turn runs a second sequence on another node.

A parametric sweep can contain steps to run all solutions, save the model to a file, and evaluate derived values, for example. You add those steps by right-clicking the node and selecting one of the following options:

refers to another job that is to be run from this parametric sweep, while (see Solution) runs a node as available under the node, available further up in the tree.

Under , you can choose (see External Class), which calls an external Java® class file. Another option, (see Method Call), runs a model method. The (see Geometry), builds the node (runs the geometry sequence). This can be used, for example, in combination with a parametric sweep to generate a sequence of MPH-files with different geometry parameters. The option (see Mesh) builds the node (runs the meshing sequence).

Under , you can choose (see Plot Group) to run all or a selected set of plot groups. This is useful for automating the generation of plot groups after solving. The option is there for legacy reason, and it is instead recommended that you use the option (see Evaluate Derived Value), which evaluates nodes under . The option (see Export to File) runs any node for data export under the node.

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

You define the parameters in the and fields. The parameters can be loaded from file by clicking the button when you have selected the file through the dialog box, which you open by clicking . You can add a that is evaluated after each solution. The last solution, which breaks the stop condition, is discarded from the set of solutions returned (the node) but is included in probe table outputs. Once the condition evaluates to a negative value, the node is stopped. Select the check box to store both solutions — before and after the stop condition has been satisfied — in the parametric solutions storage.

Select the check box to allow plotting of results while solving. Select what to plot and when from the list. The dataset of the selected plot group is plotted as soon as the results become available.

Use the list to select any probes to evaluate. Use the to accumulate data during a sweep. The accumulation is over solver variations (time, frequency, and so forth) and variations over the parametric sweep. For independent variation of parameters, you can use the accumulated table with the to change the table data into a matrix format that can be used for response surface plots.

Errors are usually stored in the table. If you want to get the error message at once, select the check box.

You can distribute the sweep on several computational nodes by selecting the check box. If the problem is too large to run on a single node, enable the field to use the nodes’ memory more efficiently. In this case, the same parameter is solved for by several nodes that cooperate as if running a nondistributed sweep. The number of nodes that cooperate is equal to the maximum of the total number of nodes divided by the setting and 1. So if the total number of nodes is 12 and the is 3, 3 groups with 4 nodes each cooperate.

Select the check box as needed.