To obtain information about available startup options, you can type fluent -help before starting up the solver. Typing fluent -env will list all environment variables before running FLUENT. All available options are listed below:
Usage: fluent [version] [-help] [options] options: -cl following argument passed to fluent, -checknetwork check the network connections before spawning compute nodes, -cxarg following argument passed to cortex, -cx host:p1:p2 connect to the specified cortex process, -driver [ opengl | x11 | null ], sets the graphics driver (available drivers vary by platform), -env show environment variables, -g run without gui or graphics, -gr run without graphics, -gu run without gui, -hcl following argument passed to fluent host, -help this listing, -i journal read the specified journal file, -loadx load mpp from host x, -lsf run fluent under LSF, -manspa manually spawn compute nodes, -n no execute, -ncl following argument passed to fluent node, -nocheck disable checks for valid license file and server, -pathx specify root path x to Fluent.Inc, -post run a post-processing-only executable, -project x write project x start and end times to license log, -px specify communicator x, -r list all releases, -rx specify release x, -sge run fluent under Sun Grid Engine, -sgeq queue name of queue for a given computing grid, -sgeckpt ckpt_obj, set Checkpointing object to ckpt_obj for SGE, -sgepe fluent_pe min_n-max_n, set parallel environment for SGE to fluent_pe, min_n and max_n are number of min and max nodes requested, -v list all versions, -vx specify version x, -tx specify number of processors x, -cnf=x specify the host file
Windows Startup Options
On Windows systems, -env, -help, -i journal, -g, -hidden, -post, -driver, -r, -rx, -v, -vx, -e, and -ex are available. The parallel startup options that are available are -tx, -px, -pathx, and -cnf=x.
Most of the Windows startup options are common to Linux/UNIX startup options and are described in the proceeding sections. Options that are unique to Windows include -hidden, -e, and -ex.
fluent -hidden allows you to run in batch mode.
fluent -e allows you to list all executable revisions, while typing fluent -ex will specify executable revision x.
-cl, -cxarg, and -cx host:p1:p2 are for specifying arguments for FLUENT and Cortex. Cortex is a process that provides the user interface and graphics for FLUENT. The option -cx host:p1:p2 is used only when you are starting the solver manually (see Section 1.1.2).
If you type fluent -driver, you can specify the graphics driver to be used in the solver session. For example, on Linux/UNIX you can specify fluent -driver opengl, fluent -driver x11, and fluent -driver null. These options are described in detail in Section 28.1.6.
On Windows you can specify fluent -driver opengl and fluent -driver msw to enable graphics display. Using msw in stead of opengl instructs FLUENT to use the Operating Systems Windows rather than the hardware OpenGL driver.
fluent -g will run Cortex without graphics and without the graphical user interface. This option is useful if you are not on an X Window display or if you want to submit a batch job.
fluent -gu will run Cortex without the graphical user interface. (On Windows systems, fluent -gu will run FLUENT, keeping it in a minimized window; if you maximize the window, the GUI will be available.)
fluent -gr will run Cortex without graphics. This option can be used in conjunction with the -i journal option to run a job in "background'' mode.
To start the solver and immediately read a journal file, type fluent -i journal, replacing journal with the name of the journal file you want to read.
The -project x option allows you to record CPU time for individual "projects'' separately. If a job is started by typing fluent -project x (where x is replaced by the name of the project), extra information related to CPU time will be written to the license manager log file (usually license.log in the license subdirectory of your FLUENT installation directory). To determine the CPU time for the project, add the USER CPU and SYSTEM CPU values that appear in license.log. See the installation notes for more information about the license manager.
The -nocheck option speeds up the solver startup by not checking to see if the license server is running. This is useful if you know that the license daemon is running or you would rather not try to start it if it is not running (e.g., if you do not have privileges to do so).
You can type fluent -n or use the -n option in conjunction with any of the others to see where the (specified) executable is without actually running it.
The -lsf option allows you to run FLUENT under Platform Computing Corporation's LSF software, and thereby take advantage of the checkpointing features of that load management tool. For further details about using the -lsf option, go to the documentation page on the Fluent Inc. User Services Center.
These options are used in association with the parallel solver.
-hcl is used to pass an argument to the FLUENT host process.
-ncl is used to pass an argument to the FLUENT compute node process(es).
-loadx is used to start the parallel compute node processes on a dedicated parallel machine from its remote front-end machine ( x). -manspa is used to disable the default automatic spawning of compute node processes.
-px specifies the use of parallel communicator x, where x can be any of the communicators listed in Section 31.3.1.
-pathx specifies the root path ( path) to the Fluent.Inc installation directory.
-tx specifies that x processors are to be used. For more information about starting the parallel version of FLUENT, see Section 31.3.
-cnf=x (where x is the name of a hosts file) spawns a compute node on each machine listed in the hosts file. Otherwise, you can spawn the processes as described in Section 31.3.1.
The -checknetwork allows you to check the configuration of the machines you are using for parallel spawning. This option has to be used with the -cnf=x command. This option is only valid when running the parallel version of FLUENT. The command you will invoke to check if your machines are configured properly is
-t0 -pnet -cnf=x
If your hosts file specifies more machines than you want to use, it will check only those machines which it needs for the current run and will not go over the complete list. To learn more about hosts files, refer to Sections 31.2.1 and 31.3.1.
An alternative to using the
-checknetwork command line option is to set your environment such that
FLUENT_CHECK_NETWORK is set to
1. With this specified,
FLUENT will always check the network without the
-checknetwork command being invoked.
fluent -post will run a version of the solver that allows you to set up a problem or perform postprocessing, but will not allow you to perform calculations. Running FLUENT for pre- and postprocessing requires you to use the -post flag on startup. To use this option on Linux/UNIX, launch FLUENT by adding the -post flag after the version number, for example,
fluent 3d -post
To use this option on Windows, you will use the Version panel, as described in Section 1.1.3.
The -sge option runs FLUENT under Sun Grid Engine (SGE) software, and allows you to use the features of this software to manage your distributed computing resources. Other options that can be employed in conjunction with -sge are -sgeq queue, -sgeckpt ckpt_obj, and -sgepe fluent_pe min_n-max_n. For a detailed explanation of these options, go to the documentation page on the Fluent Inc. User Services Center.
Version and Release Options
Typing fluent version -r, replacing version with the desired version, will list all releases of the specified version.
fluent -rx will run release x of FLUENT. You may specify a version as well, or you can wait and specify the version when prompted by the solver.
fluent -v will list the available versions.
fluent -vx will run version x of FLUENT.
Other Startup Options
There are other startup options that are not listed when you type the fluent -help command. These options can be used to customize your graphical user interface. For example, to change the FLUENT window size and position you can either modify the .Xdefaults file described in Section 2.2, or you can simply type the following command at startup:
fluent [version] [-geometry] [XXxYY+00-50]
where XX and YY are the width and height in pixels, respectively, and +00-50 is the position of the window.
Therefore, typing fluent 3d -geometry 700x500+20-400 will start the 3D version of FLUENT, sizing the FLUENT console to 700x500 pixels and positioning it on your monitor screen at +20-400.