starccm+ [options] [SIMULATION]
starccm+ -server [options] [SIMULATION]
The starccm+ command can start either the STAR-CCM+ client or server process. Without any arguments, the STAR-CCM+ GUI client will be started. No server process will be started at this point as that is only required when a simulation is created or loaded.
If a SIMULATION file is named without any options, both the STAR-CCM+ client and a server will be started, and the named file will be loaded into the server.
If the -server argument is specified, only the STAR-CCM+ server process will be started. Any server option may also be specified on the command line to start the client; the client will pass those options on when it starts the server process.
-batch FILEStarts STAR-CCM+ in batch mode, that is without a GUI. Takes input commands from the specified Java macro FILE. The batch file will usually have been created using the macro record facility, and then possibly edited.
-macro FILERuns the macro FILE upon client startup. This is similar to the -batch option in that a macro file is read, but in this case a GUI is opened. This option requires a SIMULATION file to be specified. Since it is impossible to record a macro that includes the opening of a simulation file, there will never be a conflict.
-host HOST -port PORTSpecifies the HOST and PORT of a running STAR-CCM+ server process that the client should connect to. A SIMULATION file cannot be specified if the -host and -port options are used.
-master HOSTSpecifies which machine should run the parallel master process. If a parallel server is started (by specifying the -np or the -on options), a parallel master process will be started to control the parallel worker processes. By default, the master process will be started on one of the hosts used for the parallel workers.
-noexitPrevents the server process from shutting down after batch file execution has completed. By default, the client and server processes shut down after the macro completes.
-on HOSTSpecifies the HOST machine to start the server process on. By default, when a new simulation is created or an existing simulation file is opened, the STAR-CCM+ client starts a server process on the local machine. If the -on option is specified however, the client will attempt to start the server process on the named HOST machine via rsh.
-resetRestores the default client layout (including window positions) and settings (options and mounted directories).
-vVerbose mode, prints environment changes and subcommands.
-mesaUses the alternative mesa graphics libraries when there is a problem with the graphics driver or you when you want to use software rendering (when running in batch or when displaying a client remotely using an X-server).
-arch ARCHITECTUREThis allows you to override the automatic determination of the architecture of the machine. It is very similar to the -env argument in that after installation you should not need to use these options. The architecture specified must exist within the installation and must be compatible with the machine architecture. If these conditions are not met, STAR-CCM+ will exit or runtime errors will occur.
-arch linux-x86-2.2.5
-batchsystem SYSTEMThis option can be used to aid the startup of parallel STAR-CCM+ under the control of a supported Batch Management SYSTEM (for usage see Using Batch Management Systems). Currently the supported systems are:
-coutMessages are directed to the console rather than to the STAR-CCM+ client.
-loadLoads the specified SIMULATION file as soon as the server starts. Without this option the simulation database will be loaded on demand when the client connects to the server.
-machinefile FILEMPI machine resource FILE name. Only used with parallel operation. The processes are allocated to the machines in the resource list starting with the first entry. If the number of requested processes (as defined by the -np option) is greater than the number of machines listed, the remaining processes will continue being allocated starting with the first entry in the resource list. Cannot be used with -on.
-mpidriver hp2This chooses the HP MPI distribution. In addition, this command can help if you do not know the specific inter-connect hardware available on a machine. When activated, HP MPI will choose the fastest transport layer it detects on the machine.
-np NNumber of worker processes to use. Only used for parallel operation. If the -np option is omitted and -machinefile or -on is specified, the number of worker processes is assumed to be the number prescribed by the resource list. If neither -on or -machinefile is specified in conjunction with this option, then -on localhost:N is assumed.
-on HOST[:NP][,HOST[:NP]]...>List of HOSTs to run parallel processes on. If :NP is specified, then NP worker processes will be put on that machine. There must be no spaces in the list of hosts. The processes are allocated to the machines in the resource list starting with the first entry adding NP processes before moving on to the next machine in the list. If the number of requested processes (as defined by the -np option) is greater than the number of machines listed, the remaining processes will continue being allocated starting with the first entry in the resource list. Cannot be used with -machinefile.
-serverStarts the STAR-CCM+ server, which selects an unused port and then starts the STAR-CCM+ client.
-server -port [portnumber]
-use-path-envUses the $PATH environment variable to find the STAR-CCM+ script on each resource. Without this option the absolute path to the STAR-CCM+ script is assumed to be the same on all resources.
-rshSpecifies the remote shell command to be used to start remote servers and parallel servers. The default remote shell command is rsh.