3.1. Starting the Dual Process Build

The dual process build allows you to run Cortex on your local machine (host) and Fluent on a remote machine. The advantage of using the dual process build is faster response to graphics actions (such as zoom-in, zoom-out, opening a dialog box, and so on) when you use Fluent remotely. If the network connectivity is slow, then graphics actions may appear slow and jerky. By controlling the graphics actions locally, the slow response of the graphics actions can be avoided. For example, if you are handling a big mesh (such as the underhood mesh), you can start a dual process build to run Fluent remotely with only the display set to your local machine.

To start the dual process build of Fluent in meshing mode, do the following:

  1. Start Fluent on your local machine using the command fluent -serv -meshing.

    The Fluent window will appear with the version prompt in the console.

  2. Type listen and press Enter.

    You will be prompted for a timeout (the period of time to wait for a connection from remote Fluent). The default value is 300 seconds. You can also specify the timeout value based on your requirement. Utilize this time to log into the remote machine and to start Fluent.

  3. Press Enter again.

    A message will prompt you to start Fluent on the remote machine with the following arguments:

    -cx host:p1:p2

    where,

    host is the name of the host (local) machine on which Cortex is running.

    p1 and p2 are the two integers indicating the connecting port numbers that are used to communicate information between Cortex on the host machine and Fluent on the remote machine.

  4. Login to the remote machine and set the display to the host machine.

  5. Start Fluent from the remote machine using the following command: fluent 3d -cx host:p1:p2

    The host and port numbers are displayed in the message window.


Note:  The user interface commands related to the File menu (such as reading files, importing files) and other Select File dialog boxes do not work for the dual process build. You need to use the TUI commands instead (for example, /file/read-mesh).



Important:
  • The host cannot be detached and reattached; once the connection is broken the data is lost. You need to save the data if the machine needs to be shut down in between.

  • All graphics information will be sent over the network, so initially it could take a long time to assemble graphical information (especially if the host and remote server are across continents) but after that the graphics manipulation is fast.



Release 18.2 - © ANSYS, Inc. All rights reserved.