The ANSYS Thin Server will start without any message and will continue running in the background until the machine is restarted or you kill the process. You may close or minimize the window in which the ANSYS Thin Server was started.

Stop the ANSYS Thin Server

The ANSYS Thin Server should be stopped once the parallel process is complete.

Stopping on a PC

You may stop the process by closing the command prompt window or using Ctrl-C.

Stopping on a Linux Machine

On a Linux machine use ps -u UserId | grep tclsh in the command line to determine under which process ID the ANSYS Thin Server is running. Here, UserId is your user account name on the machine. With this "ps" command should get two processes running. Typically, there will be two processes listed, one process for anstclsh and another for tclsh. Use kill -9 process-id to kill both processes. Under certain circumstances, killing the anstclsh process also kills the tclsh process. (Issue the ps command again to verify.) If this does not happen, then kill the tclsh process separately.

1.3.9.3.1.4. Configuring the Master Machine

After you have configured the slave machines you need to configure the master machine for the type of ANSYS Thin Server startup you chose to use on the slave machines. The communication from the master machine to the slave machines is done by the ANSYS Nanny which is a program running in the parent process. It takes care of running the necessary simulations on different slave machines. It will establish the connection to the slave machines, copy the necessary files over to the slave machines,

start and monitor the running simulations and clean up the working directories after the entire sequence of simulations is finished. The ANSYS Nanny will be started automatically as you start executing PDS simulations in parallel, distributed mode.

For parallel processing you need to specify the remote hosts you want to use. This information is placed in a file named hosts150.ans. You can create this file using a text editor or you can use the ANS_ADMIN utility (see the online help available with the ANS_ADMIN utility for more information). This file contains host information for all remote machines on which you may want to run. This file is global and does not contain job-specific information. Typically, your IT administrator would provide

this file, including all the information about the slave machines a typical user can use in your network. If you have multiple users running parallel or distributed jobs at your site, you should have one hosts150.ans file for all users. But you can copy this file to your local working directory and make adjustments. ANSYS searches for this file first in the local directory, followed by the home directory, and finally the apdl directory.

You have two options when setting up the Master Machine to use the ANSYS Thin Server on the slave machines.

Configuration when the Thin Server uses the Remote Shell Option

Let's assume that the slave machine called "MySlaveMachine" has been prepared to work under the remote shell option as outlined above. The slave machine "MySlaveMachine" is an SGI machine and it has 4 CPUs. On the slave machine we also want to use the directory "/tmp/sdr/pds_runs" as the local directory for the remote simulations to run in. In this case your hosts150.ans file must include the lines:

vk.com/club152685050Probabi istic Design | vk.com/id446425943

Configuration when the Thin Server uses the Port Option

Assume that you now want to use the same slave machine "MySlaveMachine" using the ANSYS Thin Server. The ANSYS Thin Server has been started on a slave machine called “MySlaveMachine" using the command ansysts150 62000 as shown above. Assume also that the file AnsysClients looks exactly like shown in the section above, i.e. your master machine "MyMasterMachine" can communicate to the ANSYS Thin Server using the communication port numbers 59400-59430. In this case, your hosts150.ans file must include the lines:

This will ensure that the ANSYS Thin Server on the slave machine will be contacted using the same connection port it has been started with, i.e. 62000 in this case. Also the communication will use the same communication port numbers the ANSYS Thin Server accepts from the machine "MyMasterMachine" where you try to connect from.

An example hosts150.ans file looks like this:

#This file is used to specify those hosts that the ANSYS Nanny may

#run children on.

#

#Each host entry is to be on its own line. The host entry consists of

#several fields which are space delimited.

#

#Field 1 - host IP address or name

#Field 2 - host machine type

#Field 3 - execution key (used for Probabilistic Design only):

#0-Use a remote shell to start the child process;

#this requires a remote shell server to be

#running on the host machine.

#>1024-Use a running ANSYS thin server on the host

#which is listening on this port number.

#Field 4 - The default maximum number of jobs to run on this host

#Field 5 - The time in minutes to check again if the host is available.

#If this is zero then the host will not be checked again.

#Field 6 - The local port number to start the communication with the

#ANSYS Thin Server on. This is tied to authentication on the

#ANSYS Thin Server.

#Field 7 - The directory to create the children subdirectories in

#Field 8 - The cluster type. Only valid entry is MPI.

#Field 9 - The speed factor (relative speed to other machines listed).

Only valid entry is 1.

#Field 10 - Number of OpenMP threads. Only valid entry is 1.

#Example:

#

#UNIX box that has five processors

#Microsoft box using the ANSYS Thin Server

1.3.9.3.1.5. Host setup using port option

The picture below illustrates an example of the set-up of a network with 2 master machines and 4 slave machines using the connection port option. Here, the first master machines uses slave machines 1, 2 and 3, while the second master machine is using only slave machines 2, 3 and 4. In this illustration "NN" represents the revision number of ANSYS.

1.3.9.3.1.6. Host and Product selection for a particular analysis

After specifying the hosts145.ans file, provide the specific information that may change from analysis to analysis.

If you are working in interactive mode then select:

Main Menu> Prob Design> Run> Exec Parallel> Host Select

In this menu you can:

•Select the slave machines you want to use for a particular analysis. This is necessary, for example, if you know that some machines in your network are in use by another user at the time you want to start the analysis.

•Select the licenses you want to use for the particular analysis. If there are multiple levels of licenses of ANSYS available in your network, then you should first select the lower license that will be able to run your analysis.

Based on the information provided in the menu, a Jobname.hosts file is created or updated as you press OK in the menu.