Command Line Options Reference

Design Manager Options

The starccm+ [project] command launches the Design Manager server and loads the specified Design Manager project file (*.dmprj). The following Design Manager server options are available:

-dmnoshare

Specifies the Unlicensed Design Manager Server Licensing Scheme.

Note	This option is not supported when running Design Manager in Pre-Allocation Mode.

-passtodesign <options>

Specifies simulation options to pass to the design simulations, such as License Options or other Simcenter STAR-CCM+ options, see Command-Line Reference.

Passing simulation options from the command line is useful for machine-specific or user-specific options—such as a Power on Demand license key.

Example: starccm+ [project] -dmnoshare -passtodesign "-power -podkey <value> -licpath 1999@flex.cd-adapco.com"

Alternatively, you can pass command line options from the GUI, see STAR-CCM+ Command-Line. Passing command line options from the GUI is useful for general simulation command line options that you want to save within your Design Manager project.

As Design Manager controls the resource management for the design simulations, you must not pass resource management options to the design simulations. Therefore, the following resource specification options are not supported:

• -batchsystem
• -bs
• -hostregexpr
• -machinefile
• -np
• -on

Note	The -passtodesign <options> option does not support arguments that require double quotes, such as -mpidriver intel:"-genv VARIABLE value". You must pass these options from the GUI.

-preallocpower

Specifies to use only Power Session licenses when running in Pre-Allocation Mode.

Similar to -dmnoshare, the specified option instructs the Design Manager server to not pull any licenses.

Additionally, it implicitly passes -power to the design simulations. The option -passtodesign "-power" is not required.

Example: starlaunch jobmanager --command "starccm+ [project] -preallocpower"

-doepower

Specifies to pull a Power Session license (ccmppower) instead of a ccmpsuite license as session license when using the Default Licensing Scheme. Using this option together with -podkey <value> uses a Power on Demand license.

When running Design Manager in Pre-Allocation Mode and using the -doepower option, you must pass this option also to the Design Manager server.

Example: starlaunch jobmanager --command "starccm+ [project] -doepower -passtodesign \"-doepower\""

-notokens

Specifies to not use doetoken licenses for the design simulations.

When running Design Manager in Pre-Allocation Mode and passing the -notokens option to the design simulations, you must pass this option also to the Design Manager server.

Example: starlaunch jobmanager --command "starccm+ [project] -notokens -passtodesign \"-notokens\""

Resource Manager Options

When running Design Manager in Pre-Allocation Mode, Resource Manager provides the actual resource management functionality. The following command line options are available for starlaunch:

--command <batch_command>

Specifies the command that runs your Design Manager project in batch.

--scratch_root <path>

Invokes the usage of local scratch space and specifies the path to the scratch root directory on the local disk. You must have write access for this directory and the directory path must be the same on all cluster nodes. For more information, see Running on a Linux Cluster with Local Scratch Space.

--cwd <path>

Specifies the path to the working directory. When running Design Manager on a cluster with local scratch space, this working directory must be under the scratch root directory specified in the --scratch_root <path> command line option.

When this option is not set, Design Manager defaults to the current working directory of the starlaunch process.

--slots 0

Specifies to allocate no processor for the jobmanager process.

--batchsystem <system>

Specifies the batch management system on your cluster.

--resources <host[:np][,host[:np]]>

Specifies a group of network machines on which Design Manager is allowed to run the design simulations.

--resourcefile <file>

Specifies an MPI file that lists the machines on which Design Manager is allowed to run the design simulations.

Example: starlaunch jobmanager --command "[STARCCM+_INSTALL_DIR]/star/bin/starccm+ -rsh ssh -batch run -preallocpower [project]" --slots 0 --batchsystem pbs

License Options

The following options control the license usage when running a design study in Design Manager:

-doepower

Uses a Power Session license (ccmppower) instead of a ccmpsuite license as session license when using the Default Licensing Scheme. Using this option together with -podkey <value> uses a Power on Demand license.

-licpath <path:...>

Specifies a license path that overrides the default license path. When this option is used, Simcenter STAR-CCM+ uses the path to define a new CDLMD_LICENSE_FILE environment variable for the spawned server session.

Example: -licpath 1999@flex.cd-adapco.com (Power on Demand license server)

-nosuite

Prevents ccmpsuite licenses from being used to enable cores for parallel computation. Only parallel licenses, such as Power Tokens, are used to enable cores for parallel computation.

-notokens

Specifies to not use doetoken licenses for the design simulations.

-podkey <value>

Specifies a Power on Demand license key.

-power

Specifies to check out Power Session licenses for each design simulation. Using this option together with -podkey <value> enables Power on Demand licensing.

Note	This option is not supported when running Design Manager in Pre-Allocation Mode. To check out Power Session licenses in pre-allocation mode, use the Design Manager Option -preallocpower.

-tokensonly

Specifies to only use doetoken licenses for the design simulations. With this option, you can also use doetoken licenses for regular parallel runs in Simcenter STAR-CCM+.

For the Default Licensing Scheme, the following table displays the supported combinations of license option and the associated license usage:

where DOEtoken / ccmpsuite or DOEtoken / ccmppower means:

1. Design Manager tries to satisfy the license requirement with DOEtoken.
2. If insufficient licenses, Design Manager tries to satisfy the remaining requirement with ccmpsuite or ccmppower, respectively.