Fluent as a Server commands are used to perform
client/server interactions with a connected Fluent as a Server session. These
include commands to upload files, set/get rpvar values, alter verbosity,
and so on. Fluent as a Server commands begin with the prefix fluent. Note that for the sake of convenience and accuracy, you do not
have to type the whole command, but can begin typing and use the Tab key to automatically complete it or display a list of
options.
The following commands collaborate with Fluent processes and therefore cannot be executed until Fluent is idle or at a stable point. This means that you are not guaranteed to have an instant response when you enter the command.
Tip: The following strategies can be used to minimize the lag between when you enter a command and when it is executed:
Set the fluent.set_aaslistening_step_at <number>
iteration|timestep command to a minimum value, based
on your objectives. Note that by decreasing the iterations / timesteps
between stable points, you are favoring cosimulation over simulation
(that is, you are prioritizing your ability to manipulate the settings
over the time it will take to calculate the solution).
You can nest a number of commands between fluent.pause and fluent.continue commands, so that they are all executed during the same stable point;
otherwise, each command will have to wait for a separate stable point.
continues remote execution of a journal file on the Fluent server.
displays a message of the remote TUI menu.
downloads a file, <filename>, from the remote Fluent session working directory to the local
machine. The file will be downloaded to the local directory from which Fluent Remote Console was
started. By default, fluent.download_file will not overwrite an existing local file. You can force an overwrite
by including the —f flag.
provides information about the aaslistener that listens for commands from Fluent as a Server clients.
provides the current flow time.
provides the current iteration.
provides the current time step.
provides the dimensionality of the current case.
provides the name of the last case file accessed before the current case. This can be useful if you have written the case file with a new name.
provides a list of the input parameters available in the current case.
provides a list of the output parameters available in the current case.
provides the number of input parameters available in the current case.
provides the number of output parameters available in the current case.
reports the current value of <parametername>.
returns an index indicating the “depth”
of pause. When Fluent is not paused, it will return 0. It is incremented with each successive pause instruction.
This can be useful to determine the state of a session if the connection
is lost while Fluent is paused.
specifies whether the solution calculations for the current case will be performed in single- or double-precision mode.
provides the name of the solver and the release number.
provides information about the status of the Fluent session
(for example, journaling, iterate).
reports the current value of <rpvarname>.
provides information about the status of the Fluent session
(for example, journaling, iterate).
displays the current setting of verbosity.
interrupts remote execution of a journal file on the Fluent server.
Note that this terminates reading of the journal file. If you want
to be able to resume execution where it was stopped, use fluent.pause.
returns a list of solver calculation activities (including the listening process for Fluent as a Server commands).
returns a JSON-formatted listing of the monitor definitions
in the current case. <monitor_type> may
be one of the following types: residuals, lift, drag, moment, surface, or volume. If no arguments are given, Fluent returns all defined monitors.
If only <monitor_type> is given, all
monitors of the specified type are returned.
returns a JSON-formatted listing of the monitor definitions
in the current case, including the data from the monitor history file
(if any). Options for <monitor_type> are
the same as those listed for fluent.list_monitors. <filter> allows you to return incremental
monitor data, by removing the data calculated before the specified <filter_value>; a single command can include one
or more of the following <filter> options: start-flow-time, start-iteration, and start-time-step.
reports the names and values of the input and output parameters defined in the current case.
returns a JSON-formatted listing of the report definitions in the current case. For more information about report definitions, see Creating Report Definitions in the Fluent User's Guide.
returns a JSON-formatted listing of the report file definitions in the current case. If no arguments are given, Fluent returns all defined report files. For more information about report files, see Report Files and Report Plots in the Fluent User's Guide.
returns a JSON-formatted listing of the report file
definitions in the current case, including the data from the report
file .out file (if any). For more information
about report files, see Report Files and Report Plots in the Fluent User's Guide. <filter> allows you to return incremental report file data, by removing the
data calculated before the specified <filter_value>; a single command can include one or more of the following <filter> options: start-iteration and start-time-step.
returns a JSON-formatted listing of the report plot definitions in the current case. For more information about report plots, see Report Files and Report Plots in the Fluent User's Guide.
lists all rpvars by name and their current values.
This command will not return anything until after fluent.retrieve_rpvars_info has been issued.
lists all rpvars matching the specified regular expression, <key>, and their current values. Note that <key> must be enclosed in single quotes. This command
will not return anything until after fluent.retrieve_rpvars_info has been issued.
lists all rpvars matching <key> with wildcard expansion. Use to match zero or more characters. Use *? to match exactly one character. Note that <key> must be enclosed in single quotes. This command will not return
anything until after fluent.retrieve_rpvars_info has been issued.
loads a case file over the network connection to the Fluent session.
Note that this is different from the read-case TUI command because it allows you to load a local case file to the
remote session. If <filename> is omitted,
a dialog box will open, allowing you to navigate to a file.
loads a data file over the network connection to the Fluent session.
Note that this is different from the read-data TUI command because it allows you to load a local data file to the
remote session. If <filename> is omitted,
a dialog box will open, allowing you to navigate to a file.
pauses remote execution of a journal file on the Fluent server.
Execution can be resumed using the fluent.continue command.
loads a journal and executes it asynchronously (control
is immediately returned to the user). The status of the journal execution
can be checked using fluent.get_status.
retrieves the list of rpvars from the connected Fluent as a Server session.
This command must be issued before the fluent.list_rpvars commands or completion suggestions for fluent.get_rpvar/fluent.set_rpvar will work.
saves a case file from the remote Fluent session
on the local machine. Note that this is different from the write-case TUI command because it allows you to save
the case file to the local machine. If <filename> is omitted, a dialog box will open, allowing you to navigate to
a file location.
saves a data file from the remote Fluent session
on the local machine. Note that this is different from the write-data TUI command because it allows you to save
the data file to the local machine. If <filename> is omitted, a dialog box will open, allowing you to navigate to
a file location.
saves a JSON-formatted file on the remote Fluent machine with the data (if it exists) from all monitors defined in the current case.
configures the aaslistener to listen for commands
from Fluent as a Server clients every <number> iterations
or timesteps.
allows you to change the period for when monitor history
data is automatically saved as a JSON-formatted file (named monitor.json) on the remote Fluent machine. By default,
the period is set to 60 minutes. Note that it is recommended that
you do not have multiple sessions in a single folder, as they will
all have the same name for the monitor history file.
sets the value of <paramtername> to <value>.
sets <rpvarname> to <value>.
disables prompts for TUI commands that are entered without all arguments. Fluent will automatically use the default values for any arguments that are not specified.
enables prompts for TUI commands that are entered without all arguments.
sets the output of TUI commands issued in the Fluent Remote Console to display in the Fluent Output window instead of in the Fluent Remote Console.
sets the output of TUI commands issued in the Fluent Remote Console to display in the Fluent Remote Console instead of in the Fluent Output window. This is the default behavior.
terminates the connected Fluent solver session.
uploads a file from the local client machine to the
remote Fluent session working directory. If <filename> is omitted, a dialog box will open, allowing you to navigate to
a file. By default, fluent.upload_file will
not overwrite an existing remote file. You can force an overwrite
by including the —f flag.