In general, for a system property or option, you add -D as a command option. For example, to set the system property cs.precmp to val, use the command option -Dcs.precmd = val.
|
<target> -h
|
|
-alloc native | scalable
|
|
-applicationsroot <path>
|
|
-autosave {on} | off
|
|
-blaspath <path>
|
|
-c <path>
|
|
Cluster storage format. The single format does I/O only from the root node, while the shared format does I/O using distributed I/O operations. The shared format requires that all nodes have access to the same storage area and the same temporary storage area.
|
|
-comsolinifile <path>
|
|
-configuration <path>
|
Path to directory for storing the state for the GUI between sessions and for performing different caching tasks. The configuration directory is by default a subdirectory to the preference directory. When running in batch or cluster mode, add @process.id to get a unique identifier to the path (for example, -configuration /tmp/comsol_@process.id).
|
Path to a workspace directory for storing internal workspace information. The workspace directory is by default a subdirectory to the preference directory. The workspace directory is cleared when COMSOL is launched. When running in batch or cluster mode, add @process.id to get a unique identifier to the path (for example, -data /tmp/comsol_@process.id).
|
|
-docroot <path>
|
|
-keeplicenses on | {off}
|
|
-np <no. of cores>
|
|
-numafirst <numa number>
|
|
-numasets <no. of sets>
|
Number of NUMA sets.3 -numasets 1 represents the case where there is only one nonuniform memory access node — that is, the entire computer.
|
-prefsdir <path>
|
|
-recoverydir <path>
|
|
-tmpdir <path>
|
|
You can also specify the number of cores and sockets and the use of the scalable allocators as preferences on the Multicore and Cluster Computing page in the Preferences dialog box. To specify those numbers manually, select the Number of cores and Number of sockets check boxes to enter a number in the associated text fields. By default, all cores are used and the number of sockets are set automatically. If you lower the number of cores, it is good practice to also lower the number of sockets. The preference option for the scalable allocator is called Optimized for multicore. If you want to choose another memory allocator than the default setting, select the Memory allocator check box and the choose Native or Optimized for multicore.
|
Use a BLAS library specified using the option -blaspath or the environment variable COMSOL_BLAS_PATH.
|
-appargnames <names>
|
|
-appargvalues <values>
|
|
-appargsfile <filename>
|
|
-appargvarlist <names>
|
|
-appargfilelist <filenames>
|
-edit <file>
|
|
-open <file>
|
|
-run <file>
|
Ask for login information. info means that only missing information is asked for. force resets the password. never requires that the login information is available. auto automatically creates a new username and password.
|
|
-passwd reset | nostore
|
|
-port <port>
|
Specify a TCP/IP port, <port>, to listen for attempts to connect. The <port> is the server port, or 0 for a random free port.
|
-portfile <path>
|
Specify that COMSOL Multiphysics writes its server port to the given <path> when it has started listening.
|
-user <user>
|
Always make sure that untrusted users cannot access the COMSOL login information. Protect the file .comsol/v55/login.properties in your home directory. This is important when running COMSOL Multiphysics in client-server mode. Alternatively, start the COMSOL Multiphysics server with the -passwd nostore option, and clear the Remember username and password check box when connecting to the server. This ensures that your login information is not stored on file.
|
-open <file>
|
|
-port <port>
|
|
-server <server name>
|
-alivetime <seconds>
|
|
-batchlog <filename>
|
|
-checklicense <filename>
|
|
-classpathadd <classpath>
|
|
-error {on} | off
|
|
-inputfile <filename>
|
|
-job <job tag>
|
|
-jobfile <filename>
|
Specify a text file using the following format:
<inputfile0> <outputfile0> <inputfile1> <outputfile1> <inputfile2> <outputfile2> |
Run a method call with the given tag. The file in <filename> contains the method call. See the documentation for model.methodCall() in the COMSOL Multiphysics Programming Reference Manual for additional input arguments that can be used from batch commands with -methodcall for passing input values as arguments to a method call.
|
|
-mode {batch} | desktop
|
|
Do not compute the model. This option is useful if you, for example, just want to run -clearsolution or -clearmesh on a model that already includes a solution or mesh and then save it, without a solution or mesh, without computing the model first.
|
|
-outputfile <filename>
|
|
-paramfile <filename>
|
|
-pindex <parameter indices>
|
|
-plist <parameter value>
|
|
-pname <parameter name>
|
|
Add extra command-line arguments using -prodargs followed by the arguments last in the call to COMSOL batch.
|
|
-stoptime <time to stop>
|
|
-study <study tag>
|
|
-update <path1;path2;path3>
|
|
-outputfolder <folder path>
|
|
-batchlog <filename>
|
|
-applications <path1;path2;path3>
|
|
-applicationnames <shortName1,shortName2,shortName3>
|
|
-applicationsfile <path>
|
|
-applicationsroot <path>
|
|
-applicationpaths <path1;path2;path3>
|
|
-classpathadd <classpath>
|
|
-jdkroot <path>
|
|
-icon <path>
|
|
-outputdir <path>
|
|
Specify where to store the runtime when running the application. The default option is the platform’s default location. The ask option asks the user for the location of the runtime when running the application. The <path> option provides a location where the runtime should be unpacked and stored. Only specify a path when compiling for a single platform.
|
|
-runtimewindows <path>
|
|
-runtimelinux <path>
|
|
-runtimemacOS <path>
|
|
-splash <path>
|
Micromixer — Cluster Version: Application Library path COMSOL_Multiphysics/Tutorials/micromixer_cluster
|
•
|
Make sure that the Windows HPC Server working directory is set to point to the comsol command directory (<path to COMSOL install directory>
\bin\win64). The install directory must be shared between the nodes on your cluster. In some network configurations, the firewall prevents you from starting MPI on a shared executable. To register the executable with the firewall, use the clusrun command to execute the hpcfwutil command on all nodes (for instance, to register comsolclusterbatch) use clusrun /all hpcfwutil register comsolclusterbatch.exe <shared path to COMSOL install directory>\bin\win64\comsolclusterbatch.exe |
•
|
You need to install Microsoft Visual Studio® runtime libraries on each compute node. You can install them from the \ext directory of the DVD using the clusrun command, for instance. (See https://www.comsol.com/support/knowledgebase/1083.)
|
-mpipath <file>
|
|
-scalapackpath <path>
|
Start the server with graphics libraries. This enables plotting on the server. Available only when running comsolmphserver matlab [<options>].
|
|
-host <hostname>
|
|
-mlroot <path>
|
|
-port <hostname>
|