Install Guide

Release 8.0.0

Prometech Software, Inc.

Jun 05, 2023

 CONTENTS

1 Folder Configuration of the DVD-ROM 1

1.1 Installation DVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Installation Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 System Requirements 3
2.1 Particleworks/Granuleworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 MPI-Compatible Solver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.1 Hardware Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.2 Driver and Runtime Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 GPU-Compatible Solver (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3.1 Hardware Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3.2 Driver and Runtime Software (Single GPU for Windows) . . . . . . . . . . . . . . 6
2.3.3 Driver and Runtime Software (Multi-GPUs for Windows) . . . . . . . . . . . . . . 7
2.3.4 Driver and Runtime Software (Single GPU for Linux) . . . . . . . . . . . . . . . . 7
2.3.5 Driver and Runtime Software (Multi-GPUs for Linux) . . . . . . . . . . . . . . . 7
2.4 Verified Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.5 Verified GPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3 Installing Particleworks/Granuleworks (Windows) 9

3.1 Acquiring the License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2.1 Starting the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2.2 Setup Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2.3 Setting up License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.4 Execute Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.3 Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.4 Supplement for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.5 Starting Particleworks/Granuleworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.5.1 Starting the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.5.2 Starting Particleworks/Granuleworks . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.5.3 Settings after Starting Particleworks/Granuleworks . . . . . . . . . . . . . . . . . 16

4 Installing Particleworks/Granuleworks (Linux) 17

4.1 Acquiring the License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

i
 4.2.1 Extracting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2.2 Setting the License Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.3 Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4 Supplement for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.5 Starting Particleworks/Granuleworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.5.1 Starting the License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.5.2 Starting Particleworks/Granuleworks . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.5.3 Settings after Starting Particleworks/Granuleworks . . . . . . . . . . . . . . . . . 20

5 Supplement for Installation 21

5.1 Settings after Starting Particleworks/Granuleworks . . . . . . . . . . . . . . . . . . . . . . 21
5.1.1 Setting a Module Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2 License Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2.1 License Path Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.2.2 Examples of license paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.2.3 Specifying Multiple License Servers . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3 Port Number of License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3.1 Default Port Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3.2 Specifying the Port Number of License Server . . . . . . . . . . . . . . . . . . . . 23

6 Licenses 25
6.1 License Management Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.2 The Number of Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
6.3 License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.4 License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.5 System Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.5.1 Standalone (Node-Locked License) . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.5.2 Standalone (Floating License) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.5.3 Node-locked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.5.4 Floating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.5.5 Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

7 Service Registration 33

8 Firewall Settings 35

9 Uninstalling Particleworks/Granuleworks 39
9.1 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.1.1 Silent Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.2 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

10 Frequently Asked Questions 41

11 Troubleshooting 43

ii
 CHAPTER

ONE

FOLDER CONFIGURATION OF THE DVD-ROM

1.1 Installation DVD

Filename Description
eula_en.txt License Agreement (English)
eula_ja.txt License Agreement (Japanese)
InstallGuide_en.pdf Installation Guide (English)
InstallGuide_ja.pdf Installation Guide (Japanese)
linux/ Linux Installer
windows/ Windows Installer
third_party/ Licenses of Open Source Software used by or bun-
dled with Particleworks/Granuleworks
third_party.txt List of Open Source Software used by or bundled
with Particleworks/Granuleworks

1.2 Installation Location

Filename Description
bin/ Modules
doc/en/ Documents (English)
doc/ja/ Documents (Japanese)
lib/ Shared libraries (Linux only)
opt/ Python, OpenSSL
license/ License Server Files
sdk/ SDK files
share/recurdyn/ Setting file for RecurDyn Co-simulation
share/samples/ Shape files and airflow data used in the tutorials

doc/en/ contains following files :

1
Install Guide, Release 8.0.0

Filename Description
AnsysIF/ Particleworks for Ansys Manual (HTML)
Particleworks for Ansys.pdf Particleworks for Ansys Manual (PDF)
InstallGuide/ Installation Guide (HTML)
InstallGuide.pdf Installation Guide (PDF)
RecurDyn/ RecurDyn Co-simulation Manual (HTML)
RecurDyn CosimulationManual.pdf RecurDyn Co-simulation Manual (PDF)
ReleaseNote/ Release Note (HTML)
ReleaseNote.pdf Release Note (PDF)
Samples/ MPS/DEM Tutorials (HTML)
Particleworks Tutorial.pdf MPS Tutorials (PDF)
Granuleworks Tutorial.pdf DEM Tutorials (PDF)
SDK/ SDK Manual (HTML)
SDK Manual.pdf SDK Manual (PDF)
TheoryManual/ MPS/DEM Theory Manual (HTML)
Particleworks TheoryManual.pdf MPS Theory Manual (PDF)
Granuleworks TheoryManual.pdf DEM Theory Manual (PDF)

2 Chapter 1. Folder Configuration of the DVD-ROM

 CHAPTER

TWO

SYSTEM REQUIREMENTS

2.1 Particleworks/Granuleworks

CPU Intel or AMD 64-bit processor, 2GHz or faster (Mi-

croarchitecture that can execute AVX2 instructions
is recommended)
Memory 4GB or more
HDD 5GB or more
Graphics OpenGL-compatible video card (OpenGL 4.x or
later)
OS
Microsoft Windows 10 (64bit)
Microsoft Windows 11
Microsoft Windows Server 2019
Red Hat Enterprise Linux 7.x
Red Hat Enterprise Linux 8.x
Red Hat Enterprise Linux 9.x
Note that 6.x or older versions cannot be used.
CentOS 7.x
Note that 6.x or older versions cannot be used.

• There is a restriction on usable memory size depending on the Operating System.

• For the full simulation performance, CPUs that support AVX2 instructions are recommended.
• Particleworks 3.0 and later requires a Graphics Card and Drivers that support rendering of 3D graphics.
– Please install a Graphics Card and Drivers that support OpenGL 4.0 or later. The latest drivers
are available on the web sites of card manufacturers.
– May not display properly with AMD GPUs or Intel HD Graphics which is used with laptop PCs
and other devices. If problems are experienced, consider using a different environment.
– May not display properly through remote desktop software such as Remote Desktop Connec-
tion (a component of Microsoft Windows). If problems occur, use Particleworks/Granuleworks

3
Install Guide, Release 8.0.0

locally without remote desktop software.

2.2 MPI-Compatible Solver

When a distributed memory environment is created by connecting multiple nodes (machines) via a high-
speed network, e.g. a cluster environment, the MPI-compatible solver can be used. Parallel use of multiple
CPUs enables improvement in calculation speed, and the use of distributed memory space enables larger-
scale calculation. However, such an environment requires the installation of expensive hardware and high
maintenance costs and can be described as a specific environment specialized in large-scale high-speed cal-
culations.

2.2.1 Hardware Platform

• The environment required in order to run the MPI-compatible solver is the same as described in Par-
ticleworks/Granuleworks.
• In many cases, a network develops a bottleneck. Use in a high-speed network environment.

2.2.2 Driver and Runtime Software

Windows
• When you run the MPI-compatible solver in the Windows environment, the following MPI library is
required.
• If you install Particleworks/Granuleworks by following Installing Particleworks/Granuleworks (Win-
dows), the MPI library is automatically installed.

MPI MS-MPI v10.1.2 (Included in the installation me-

dia)

• The MPI library can be downloaded free of charge from the Microsoft Corporation website (https:
//www.microsoft.com/en-us/download).
• For how to create and use the MPI environment, see the support page of the Microsoft Corporation
website. Please note that Prometech Software, Inc. is unable to support and respond to inquiries
concerning MPI environments.
Linux
• When you run the MPI-compatible solver in the Linux environment, the following MPI library is
required.

MPI Intel MPI Library 2021.4.0 (Included in the instal-

lation media)

• On a Linux machine, separately install l_mpi_oneapi_p_2021.4.0.441_offline.sh to create an

MPI environment. It is included in the installation media.

4 Chapter 2. System Requirements

 Install Guide, Release 8.0.0

• For how to create and use the MPI environment, see the support page of the Intel Corporation website.
Please note that Prometech Software, Inc. is unable to support and respond to inquiries concerning
MPI environments.
The following error message may occur if you submit a job for inter-node parallel calculation using PBS.

[mpiexec@node01] check_exit_codes (../../../../../src/pm/i_hydra/libhydra/demux/

˓→hydra_demux_poll.c:117): unable to run bstrap_proxy on node02 (pid 94805, exit␣

˓→code 256)

[mpiexec@node01] poll_for_event (../../../../../src/pm/i_hydra/libhydra/demux/

˓→hydra_demux_poll.c:159): check exit codes error

[mpiexec@node01] HYD_dmx_poll_wait_for_proxy_event (../../../../../src/pm/i_

˓→hydra/libhydra/demux/hydra_demux_poll.c:212): poll for event error

[mpiexec@node01] HYD_bstrap_setup (../../../../../src/pm/i_hydra/libhydra/bstrap/

˓→src/intel/i_hydra_bstrap.c:1062): error waiting for event

[mpiexec@node01] HYD_print_bstrap_setup_error_message (../../../../../src/pm/i_

˓→hydra/mpiexec/intel/i_mpiexec.c:1015): error setting up the bootstrap proxies

[mpiexec@node01] Possible reasons:

[mpiexec@node01] 1. Host is unavailable. Please check that all hosts are␣
˓→available.

[mpiexec@node01] 2. Cannot launch hydra_bstrap_proxy or it crashed on one of the␣

˓→hosts. Make sure hydra_bstrap_proxy is available on all hosts and it has right␣

˓→permissions.

[mpiexec@node01] 3. Firewall refused connection. Check that enough ports are␣

˓→allowed in the firewall and specify them with the I_MPI_PORT_RANGE variable.

[mpiexec@node01] 4. pbs bootstrap cannot launch processes on remote host. You␣

˓→may try using -bootstrap option to select alternative launcher.

One of the following methods may solve the problem.

• Run mpirun with the -bootstrap ssh option
• Set the environment variable I_MPI_HYDRA_BOOTSTRAP to ssh
See the Intel MPI Reference Manual or other sources for details on these settings.

2.3 GPU-Compatible Solver (Optional)

To accelerate computation, Particleworks/Granuleworks employs CUDA GPU computing technology. To

compute using GPU,

Note:
• The CUDA environment needs to be updated according to the Particleworks/Granuleworks version.
• The GPU-compatible solver is optional, therefore requires another optional license.

2.3. GPU-Compatible Solver (Optional) 5

Install Guide, Release 8.0.0

2.3.1 Hardware Platform

CPU Intel or AMD 64-bit processor, 2GHz or faster

Memory 4GB or more
HDD 5GB or more
OS
Microsoft Windows 10 (64bit)
Microsoft Windows 11
Red Hat Enterprise Linux 7.x
Red Hat Enterprise Linux 8.x
Red Hat Enterprise Linux 9.x
Note that 6.x or older versions cannot be used.
CentOS 7.x
Note that 6.x or older versions cannot be used.

GPU NVIDIA GPU with CUDA double-precision capa-

bility: compute capability 3.5 (Kepler) or higher

• Ensure the CPU memory is the same size or larger than the GPU memory.
– When either memory runs short, the analysis is stopped.
– In addition, if you use multi-GPUs, you need more CPU memory than the total of GPU memory.
• The GPU needs to be Compute Capability 3.5 (Kepler) or higher.

2.3.2 Driver and Runtime Software (Single GPU for Windows)

When you use only one GPU in the Windows environment, the following driver and the runtime software are
required.

Common NVIDIA Driver (Prepare separately)

VC++ Visual C++ 2022 Runtime (Included in the instal-
lation media)

• To use the GPU-compatible solver, you need the driver of the GPU you will be using.
– From the download page of the NVIDIA Corporation website (http://www.nvidia.com/
Download/index.aspx?lang=en-us), separately download and install the NVIDIA Driver.
– If the driver is already installed, update to the latest driver that supports CUDA Toolkit 11.8.

6 Chapter 2. System Requirements

 Install Guide, Release 8.0.0

2.3.3 Driver and Runtime Software (Multi-GPUs for Windows)

When multiple GPUs are used in parallel in the Windows environment, the driver and the runtime software
given below are required in addition to Driver and Runtime Software (Single GPU for Windows).

MPI
MS-MPI v10.1.2 (Included in the installation
media)
Microsoft Visual C++ 2022 Redistributable
Package (Included in the installation media)

• The MPI library can be downloaded free of charge from the Microsoft Corporation website (https:
//www.microsoft.com/en-us/download).
• For how to create and use the MPI environment, see the support page of the Microsoft Corporation
website. Please note that Prometech Software, Inc. is unable to support and respond to inquiries
concerning MPI environments.

2.3.4 Driver and Runtime Software (Single GPU for Linux)

When you use only one GPU in the Linux environment, the following driver and the runtime software are
required.

Common NVIDIA Driver (Prepare separately)

• To use the GPU-compatible solver, you need the driver of the GPU you will be using.
– From the download page of the NVIDIA Corporation website (http://www.nvidia.com/
Download/index.aspx?lang=en-us), separately download and install the NVIDIA Driver.
– If the driver is already installed, update to the latest driver that supports CUDA Toolkit 11.8.

2.3.5 Driver and Runtime Software (Multi-GPUs for Linux)

When multiple GPUs are used in parallel in the Linux environment, the driver and runtime software given
below are required in addition to Driver and Runtime Software (Single GPU for Linux).

MPI Intel MPI Library 2021.4.0 (Included in the instal-

lation media)

• Separately install l_mpi_oneapi_p_2021.4.0.441_offline.sh, which is included in the installa-

tion media, to create an MPI environment.
• For how to create and use the MPI environment, see the support page of the Intel Corporation website.
Please note that Prometech Software, Inc. is unable to support and respond to inquiries concerning
MPI environments.

2.3. GPU-Compatible Solver (Optional) 7

Install Guide, Release 8.0.0

2.4 Verified Operating Systems

• Windows 10 (64bit)
• Windows 11
• Windows Server 2012 R2 (License server only)
• Windows Server 2016 (License server only)
• Windows Server 2019
• Red Hat Enterprise Linux Server release 7.5 (Simulation only)
• Red Hat Enterprise Linux Server release 8.6 (Simulation only)
• Red Hat Enterprise Linux Server release 9.2 (Simulation only)
• CentOS 7.6

2.5 Verified GPUs

• Rendering
– GeForce GTX TITAN V
– GeForce GTX TITAN X
– Quadro P620
– Quadro P400
– Quadro GP100
• Simulation
– Tesla P100
– Tesla V100
– A100
– H100
– Quadro GP100
– Quadro GV100

8 Chapter 2. System Requirements

 CHAPTER

THREE

INSTALLING PARTICLEWORKS/GRANULEWORKS (WINDOWS)

Follow the procedure below to install Particleworks/Granuleworks and confirm startup.

3.1 Acquiring the License File

Fill out the license application form, and contact your sales representative to receive your license file. You
will need to know the MAC address information of any machine to run Particleworks/Granuleworks with a
node-locked license, or any machine to be used as a license server with a floating license. For details, please
contact your sales representative. In addition, please see Licenses.

Note:
• If you make a new license server(or make a standalone environment), please prepare your license file.
• If you already have a license server, check the hostname/port number of the license server.

3.2 Installation

3.2.1 Starting the Installer

Run the installer (windows\setup.exe) from the installation media, and install Particleworks/Granuleworks
by following instructions.

Note:
• Before starting the setup, close all unnecessary applications.
• The installer application must be run by a user account with administrative rights.

9
Install Guide, Release 8.0.0

3.2.2 Setup Installation

A dialog box to select a setup language is displayed. Select English and click the OK button.

The setup window is displayed. Click [Next].

10 Chapter 3. Installing Particleworks/Granuleworks (Windows)

 Install Guide, Release 8.0.0

The license agreement window is displayed. Read the terms of the License Agreement. Click the [I accept
the agreement] radio button and then click [Next].

The window to specify an installation location is displayed.

C:\Prometech\Particleworks_version_yymmdd is set by default.
After specifying the installation location, click [Next].

3.2. Installation 11
Install Guide, Release 8.0.0

Select the component to install and click [Next].

3.2.3 Setting up License Information

You can skip license settings if you select Free Viewer Only in Select Components.

The window to enter the license path is displayed. Perform the following procedure according to the license
server type.
• When installing the license server into your current PC
– Then, just click [Next] and go to When installing the license server into your current PC.

12 Chapter 3. Installing Particleworks/Granuleworks (Windows)

 Install Guide, Release 8.0.0

• When using an existing license server

– Go to When using an existing license server.

When installing the license server into your current PC

When the license path was not specified in the previous window, your current PC is set as the license server.

The window to select a license file is displayed. Click [Browse], specify the license file and then click [Next].
Go to Execute Installation.

When using an existing license server

If the license server is already installed on another PC, and you want to refer to that license server (you will
not install the license server on your current PC), fill the License Path field to specify the license server.
• License path format: [port number]@<hostname or IP address of the license server>
• Example. 27000@servername
• For details about the license path, see License Path.
Then, click [Next] and go to Execute Installation.

3.2. Installation 13
Install Guide, Release 8.0.0

3.2.4 Execute Installation

The window to specify a program group is displayed. Select the location to create the program icon. By
default, the installation location is displayed. To select a different directory, click [Browse], and specify a
directory. Then, click [Next].

The window to complete installation preparation is displayed. Confirm the installation location and program
group. To continue the installation task, select [Install]. If you want to check or change the settings, select
[Back].
The Command Prompt automatically starts. When the installation is completed, the Command Prompt au-
tomatically closes.

14 Chapter 3. Installing Particleworks/Granuleworks (Windows)

 Install Guide, Release 8.0.0

The window to complete the Setup wizard is displayed. To close the Setup wizard, click [Finish].

3.3 Silent Installation

You can install Particleworks/Granuleworks silently using the batch file (windows\silent_install.bat)
in the installation media.
Please edit the batch file according to your environment. The meanings of the options are as follows.

Option Description
/lang The language to use. japanese or en
/dir Installation folder
/group Start menu folder
/type The component to install. full or freeviewer
/components The component to install. full or freeviewer
/LicenseAccepted Acceptance of the license agreement. yes or no
/LicensePath License path (case-sensitive)
/LicenseFile0-4 License file

Note:
• Before starting the installation, close all unnecessary applications.
• The installer application must be run by a user account with administrative rights.
• By setting /LicenseAccepted=”yes” and proceeding with an installation, it is assumed you agree to the
license agreement.
• Please be sure to check the license agreement before the installation.
• You can find the license agreement in eula_en.txt in the installation media.

3.4 Supplement for Installation

If you use the MPI or GPU solver, see System Requirements, and install their drivers required.

3.5 Starting Particleworks/Granuleworks

3.5.1 Starting the License Server

Note: This operation is not required when using an existing license server on another PC.

3.3. Silent Installation 15

Install Guide, Release 8.0.0

From the Start menu, run [Start License Server].

Note: To stop the license server, from the Start menu, run [Stop License Server].

3.5.2 Starting Particleworks/Granuleworks

From the Start menu, run “Particleworks” to start Particleworks/Granuleworks.

3.5.3 Settings after Starting Particleworks/Granuleworks

See Settings after Starting Particleworks/Granuleworks.

16 Chapter 3. Installing Particleworks/Granuleworks (Windows)

 CHAPTER

FOUR

INSTALLING PARTICLEWORKS/GRANULEWORKS (LINUX)

Follow the procedure below to install Particleworks/Granuleworks and confirm that it starts normally.

4.1 Acquiring the License File

Fill out the license application form, and contact your sales representative, Inc. to receive your license file.
You will need to know the MAC address information of any machine to run Particleworks/Granuleworks
with a node-locked license, or any machine to be used as a license server with a floating license. For details,
please contact your sales representative. In addition, please see Licenses.

Note:
• If you make a new license server(or make a standalone environment), please prepare your license file.
• If you already have a license server, check the hostname/port number of the license server.

4.2 Installation

4.2.1 Extracting

From the installation media, copy the run file (.run) to the machine that runs Particleworks/Granuleworks,
and the machine that is used as the license server, and execute the file.

$ sh /path/to/installer/linux/pw-{version}_linux_64.run

Read through the End User License Agreement. Pages can be scrolled by pressing the Space key. After
reading the whole EULA, a prompt is shown asking if you can agree with the license. Type y and Enter if
you can agree.

Please type y to accept, n otherwise:

Specify the installation path of Particleworks/Granuleworks. Note that the absolute path for a non-existing
directory is required here.

17
Install Guide, Release 8.0.0

Verifying archive integrity... 100% MD5 checksums are OK. All good.
Uncompressing Particleworks 7.0.0 100%
Please specify the destination directory :

After copying of files is complete, the message below is shown.

Copy complete.

4.2.2 Setting the License Path

Set the license path for the environment variable, PARTICLE_LICENSE_FILE.

License path format: [port number]@<hostname or IP address of the license server>
Example

$ export PARTICLE_LICENSE_FILE=27000@servername

For details about the license path, see License Path.

Note:
• If you make a new license server(or make a standalone environment), specify the machine name on
which you are working.

4.3 Silent Installation

You can install Particleworks/Granuleworks silently using the script (linux\silent_install.sh) in the
installation media.

$ cd /path/to/installer/linux
$ sh silent_install.sh

Please edit the script according to your environment. The meanings of the variables are as follows.

Variable Description
dir Installation directory
LicenseAccepted Acceptance of the license agreement. y (yes) or n (no)

Note:
• By setting LicenseAccepted=y and proceeding with an installation, it is assumed you agree to the
license agreement.
• Please be sure to check the license agreement before the installation.

18 Chapter 4. Installing Particleworks/Granuleworks (Linux)

 Install Guide, Release 8.0.0

• You can find the license agreement in eula_en.txt in the installation media.

4.4 Supplement for Installation

If you use the MPI or GPU solver, confirm System Requirements, and install their driver, etc.

4.5 Starting Particleworks/Granuleworks

4.5.1 Starting the License Server

Note: This operation is not required when using an existing license server.

On the machine that will be the license server, execute the following command to start the license server.

$ cd /path/to/install_directory/bin
$ ./lmgrd -c /path/to/license_file -l /path/to/license_log

• When multiple license files are used, connect them with a colon (:).
– Example) Particleworks1.lic:Particleworks2.lic
• The license server log is output to license_log.
– Specify a directory with writing rights.
– Example of license_log: ParticleworksLicense.log
• Invoking lmgrd with -local option prevents client machines from making the license server stop.
– The command line is as follows:

$ cd /path/to/install_directory/bin
$ ./lmgrd -local -c /path/to/license_file -l /path/to/license_log

4.5.2 Starting Particleworks/Granuleworks

On the client machine, execute the following commands to run Particleworks/Granuleworks.

$ export LD_LIBRARY_PATH=/path/to/install_directory/lib:$LD_LIBRARY_PATH
$ /path/to/install_directory/bin/app.viewer.float

Note:

4.4. Supplement for Installation 19

Install Guide, Release 8.0.0

• It is useful to define the environment variable, LD_LIBRARY_PATH, in configuration files such as

.bashrc.
• The environment variable LD_LIBRARY_PATH must be an absolute path, not a relative path.

4.5.3 Settings after Starting Particleworks/Granuleworks

See Settings after Starting Particleworks/Granuleworks.

20 Chapter 4. Installing Particleworks/Granuleworks (Linux)

 CHAPTER

FIVE

SUPPLEMENT FOR INSTALLATION

5.1 Settings after Starting Particleworks/Granuleworks

5.1.1 Setting a Module Path

To run external modules such as the preprocessor or the solver, you need to set the module path in advance.
1. From the menu, select [Tools] > [Options].
2. Enter the module path in Module Directory
• (Example) C:\Prometech\Particleworks_version_yymmdd\bin
3. Click the [OK] button to close the window.

Note:
• The module path is stored for each user.
• You need to specify the module path only on the first startup of Particleworks/Granuleworks after
installation.

5.2 License Path

Particleworks/Granuleworks searches the license server location by following the license path. Normally
you will set the license path via an environment variable PARTICLE_LICENSE_FILE or set one in the
windows installer.

21
Install Guide, Release 8.0.0

5.2.1 License Path Format

The license path has the following format:

[port]@<license_server>

• port
– TCP/IP port number of the license server (optional)
– When you omit this field, a default port number in the range of 27000-27009 is used.
– If your license server administrator conducted Specifying the Port Number of License Server, you
need to specify the port number which the server uses.
• @license_server
– The hostname, the IPv4 address, or the IPv6 address of the license server preceded by an @
character
– Following types of IPv6 addresses are supported:
∗ Unique-local unicast address (fc00::/7)
∗ Global unicast address (2000::/3)

Note: Link-local unicast address (fe80::/10) is not supported.

5.2.2 Examples of license paths

License Path Actual Port Number License Server

@servername Port numbers in the range of A machine whose hostname is servername
27000-27009
27700@servername27700 A machine whose hostname is servername
[email protected]. 27001 A machine to which IPv4 address 192.0.2.1 is
2.1 assigned.
27002
27002@2001:db8::1 A machine to which IPv6 address 2001:db8::1
is assigned.

5.2.3 Specifying Multiple License Servers

You can specify multiple license servers at a time by connecting their license paths shown as License Path
Format with suitable delimiting characters.
• To specify multiple license servers from a Windows client:
– Use a semicolon (;) as a delimiter.
– Example. 27000@server1;@servername2

22 Chapter 5. Supplement for Installation

 Install Guide, Release 8.0.0

• To specify multiple license servers from a Linux client:

– Use a colon (:) as a delimiter.
– Example. 27000@servername1:27001@servername2:[email protected]
• To specify redundant license servers from both Windows and Linux client:
– Use a comma (,) as a delimiter.
– Example. 27000@server1,27000@server2,27000@server3

5.3 Port Number of License Server

5.3.1 Default Port Number

When you start the license server with the original License File, the TCP/IP ports are selected from the
following table. Note that you can check the actually-used ports in the license log file.

lmgrd An unused port in the range of 27000-27009

PARTICLE A dynamic port automatically assigned by OS

5.3.2 Specifying the Port Number of License Server

You may want to change the port number of the license server from Default Port Number in some situations:
• To avoid conflicts of port numbers where some other software on the license server uses port numbers
in the range of 27000-27009.
• To make the license server use a fixed port number when it starts.
• For a security purpose.
You can change the port number of the license server by the following procedure:

Note:
• Changing the port number of the license server involves a manual edit of the original license file.
• You should backup the original license file before the edit.
• If the license file is corrupted during the edit, you cannot start the license server with the corrupted
license file anymore. In such cases, try to start the license server with the backup license file.

1. Stop the license server if it is still running.

2. Open the license file with a text editor.
3. If you want to change the port number of lmgrd, locate and edit the line that starts with the SERVER
string.

5.3. Port Number of License Server 23

Install Guide, Release 8.0.0

• Before

SERVER <servername> <hostid>

• After

SERVER <servername> <hostid> 27700

• servername is the hostname of the license server or the “this_host” string.

• hostid is the MAC address of the license server or the “ANY” string.
• This example changes the port number of lmgrd to 27700.
4. If you want to change the port number of PARTICLE, locate and edit the line that starts with the VEN-
DOR string.
• Before

VENDOR PARTICLE

• After

VENDOR PARTICLE PORT=27800

• This example changes the port number of PARTICLE to 27800.

5. Save your change to overwrite the license file.
6. Start the license server with the modified license file.

Note:
• When you specify the License Path, use the port number of lmgrd that you changed in the SERVER
line.
• Note that the port number to use should satisfy the following conditions:
– lmgrd and PARTICLE do not share the same port number.
– The port number is not used by any other software on the license server.
– The port number is not reserved either by any system processes nor any protocols.
– The port number is outside the range of dynamic port numbers possibly used by OS.

24 Chapter 5. Supplement for Installation

 CHAPTER

SIX

LICENSES

6.1 License Management Formats

The license of this software is managed by two types of format: a node-locked license or a floating license.
Before purchasing this product, please consider which license format is most appropriate. If you need to
change the license format at a later date, please contact your sales representative.
• Node-Locked License
– Particleworks/Granuleworks can start only on the licensed machines.
– Even if Particleworks/Granuleworks is installed into any machine other than the licensed ma-
chine, Particleworks/Granuleworks will not start.
• Floating License
– This license format dynamically allocates licenses to any selected number of client machines
connected via a network.
– Particleworks/Granuleworks can start on any client machines on the network. However, the num-
ber of threads that can be run concurrently is limited to the number of licenses issued.

6.2 The Number of Licenses

The software license is managed by limiting the number of CPU cores that can be used simultaneously, the
number of GPUs, or the number of executable jobs.

Note: The number of GPU boards and the number of GPUs do not always match. If the number of GPUs
is not known, please contact the support team.

The license is managed as shown in the table below. For optional licenses, at least one CPU solver license
will be consumed.

25
Install Guide, Release 8.0.0

Group Feature Kind Unit Notes

MPS 10001 CPU solver Core/Job Job license only when using HPC pack
10006 CPU MPI solver Job
10003 GPU option Process
10200 HPC pack option Pack
DEM 20007 CPU solver Core/Job Job license only when using HPC pack
20009 GPU option Process
20200 HPC pack option Pack
Others 10004 Viewer Job
10002 Preprocessor Job
10002 Postprocessor Core/Job Job license only during the simulation
30001 I/F option Job
40001 SDK (Standalone) Job
40002 SDK (Viewer) Job
40002 SDK (Python API) Job
40003 SDK (Solver) Job
10100
20100
90002 Ansys I/F (Workbench) Job
90003 Ansys I/F (Mechanical) Job

Note:
• MPS: Represents Particleworks license.
• DEM: Represents Granuleworks license.
• I/F: Represents DEM-MPS interface. It is also necessary for aeration calculation.

Note: When running the SDK (Solver), a license of 40003, 10100, and 20100 is consumed for each job.

Note: Two MPS solver jobs are consumed when performing a LBM-MPS co-simulation.

License Unit
• Core
– Consumes licenses for the number of CPU cores to be used.
• Job
– Consumes one license for one execution (job).
• Process
– Consumes licenses for the number of GPUs to be used.

26 Chapter 6. Licenses
 Install Guide, Release 8.0.0

• Pack
– Consumes licenses for the number of HPC packs correspond to the number of CPU cores to be
used.
– The number of HPC packs corresponds to that of CPU cores as follows.

The number of HPC packs The number of CPU cores

1 1 ~ 16
2 17 ~ 32
3 33 ~ 64
4 65 ~ 128
5 129 ~ 256

License Type
• Node-locked:
– Particleworks/Granuleworks can start only on the licensed machines.
– With 4 CPU solver (core) licenses, you can run four solvers with one CPU core or one solver with
four CPU cores.
• Floating:
– With 4 solver (core) licenses, the solver can use 1 CPU core on each of the 4 clients concurrently.
– It is also possible to use 2 CPU cores on each of 2 clients concurrently.

6.3 License Server

A system in which licensing is managed is called a license server system, and the operating environment or
hardware is called a license server. On the other hand, the operating environment or hardware that request
license service is called a client.
Suppose you want to check out the license by referring to the license server on the network. Particle-
works/Granuleworks requires that the license server and the client are connected via a network and the license
server operates normally.
When you want to run Particleworks/Granuleworks on a computer that is not connected via a network, a
license server and Particleworks/Granuleworks need to be installed into a single machine. Such an environ-
ment is called a standalone environment.
In a standalone environment, Particleworks/Granuleworks does not require that computers are connected to
a network. Particularly, with a node-locked license, a standalone environment is often created.

6.3. License Server 27

Install Guide, Release 8.0.0

6.4 License File

A text file that stipulates the number of licenses, expiry date, and other items is called a license file. One
license file is required for one license server.
To acquire and change the license file, fill out and return the Particleworks License Request Form.

6.5 System Configuration Examples

6.5.1 Standalone (Node-Locked License)

A configuration in which Particleworks/Granuleworks and a license server are installed into a single machine,
and they are not affected by others is called ‘standalone.’ In this case, the machine does not need to be
connected to a network. Particleworks/Granuleworks acquires permission to run, by referring to the license
server which runs on the same machine. The license server confirms the license content by referring to the
license file.
Particleworks License Request Form
• Confirm that ‘Node-locked license’ is selected. Record the MAC address of the machine.
• Enter the MAC address of the machine.
• Enter the number of threads that you want to use concurrently in the Number of Cores field.
• Enter the number of pre/post that you want to use concurrently in the Pre/Post field.
• Enter the number of options that you want to use concurrently in each option field.

28 Chapter 6. Licenses
 Install Guide, Release 8.0.0

6.5.2 Standalone (Floating License)

A standalone (floating license) has the same system configuration as the standalone (node-locked license)
described in the previous section.
Particleworks License Request Form
• Confirm that ‘Floating license’ is selected.
• Enter the MAC address of the machine.
• Confirm the number of cores and licenses. The content is the same as described in the Standalone
(Node-Locked License) in the previous section.
• The number of cores and licenses are set for each license server.

6.5. System Configuration Examples 29

Install Guide, Release 8.0.0

6.5.3 Node-locked

Particleworks/Granuleworks can be run on the licensed machines (PC-C/PC-D). Particleworks/Granuleworks

cannot be run on PC-B because it is not licensed. The machines (PC-C/PC-D), which have Particle-
works/Granuleworks installed, run Particleworks/Granuleworks after acquiring the license from the license
server (PC-A).
When an application has been made for PC-A as well, by installing the Particleworks/Granuleworks in PC-A,
Particleworks/Granuleworks can also be run in PC-A (license server).
Particleworks License Request Form
An application form is required for each machine in which Particleworks/Granuleworks will be installed. In
the above example, two forms in total are required for the two machines (PC-C/PC-D).
• Confirm that ‘Node-locked license’ is selected. Record the MAC address of the machine.
• Record the MAC address of each machine (PC-C/PC-D).
• The information on the license server is not required.
• Confirm the number of cores and licenses. The content is the same as in the previously-mentioned
Standalone (Node-Locked License).
• The number of cores and licenses are set for each machine. Check them for PC-C/PC-D respectively.

30 Chapter 6. Licenses
 Install Guide, Release 8.0.0

6.5.4 Floating

The machines (PC-C/PC-D), which have Particleworks/Granuleworks installed, run Particle-

works/Granuleworks after acquiring the license from the license server (PC-A).
• Particleworks/Granuleworks can be run on any client machine that is connected with the license server
via a network (PC-A/PC-B/PC-C/PC-D).
• When an application has been made with 4 cores, the solver can be run concurrently up to a total of 4
cores on PC-B/PC-C/PC-D.
• When the number of pre/post licenses is one, and Particleworks/Granuleworks starts on PC-B, Parti-
cleworks/Granuleworks cannot start on other client machines.
Particleworks License Request Form
An application form is required for each license server to be installed. In the above example, one form is
required for one machine (PC-A).
• Confirm that ‘Floating license’ is selected.
• Record the MAC address of the license server (PC-A).
• Information on client machines (PC-B/PC-C/PC-D) is not required.
• Confirm the number of cores and licenses. The content is the same as in the previously-mentioned
Standalone (Node-Locked License).
• The number of cores and licenses are set for each license server.

6.5. System Configuration Examples 31

Install Guide, Release 8.0.0

6.5.5 Cluster

A cluster is a system configuration that is often found when parallel processing is conducted on multiple
nodes. When preprocessing is conducted on PC-B/PC-C, the node-locked license is acquired by referring
to the license server (PC-A). When the solver is run on node D and node G, in the same way, the floating
license is acquired by referring to the license server (PC-A).
Particleworks License Request Form
A total of three forms are required: one for the license server (PC-A) for the floating license; and two for the
client machines (PC-B/PC-C) for the node-locked license.
Record the following items in each application form.
• [PC-B / PC-C]
– Fill out the form for each client machine.
– Confirm that ‘Node-locked license’ is selected. Record the MAC address of the machine.
– Record the MAC address of each client machine.
• [PC-A]
– Confirm that ‘Floating license’ is selected.
– Record the MAC address of the license server (PC-A).
– Confirm the number of cores and licenses. The content is the same as in the previously-mentioned
Standalone (Node-Locked License).

32 Chapter 6. Licenses
 CHAPTER

SEVEN

SERVICE REGISTRATION

This chapter describes service registration on a Windows PC, using lmtools.exe, a license server man-
agement utility. This utility is stored in the bin folder under the Particleworks/Granuleworks installation
folder.
1. To start lmtools, select [Particleworks version yymmdd] > [lmtools] from the Start menu.
2. In the [Service/License File] tab, confirm that [Configuration using Service] is selected, and select the
[LMTOOLS ignores license file path environment variable] checkbox.
3. Select the [Config Service] tab, and enter an arbitrary name in [Service Name].
• Example: Particleworks License Manager
4. Click [Browse] of [Path to the lmgrd.exe file] and select lmgrd.exe. lmgrd.exe is stored in the bin
folder under the Particleworks/Granuleworks installation folder.
5. Click [Browse] of [Path to license file] and select the license file (Particleworks.lic).
6. In the [Path to the debug log file] field, enter the name of the debug log file with the absolute path.
• If the specified log file cannot be found, the log file will be newly created.
• If a file with the same name exists, the existing file will be overwritten.
• When creating a new log file, you must specify an existing folder to store the created log file.
7. Select the [Use Service] checkbox. By selecting [Use Service], Particleworks License Manager oper-
ates as a service.
8. Select the [Start Server at Power Up] checkbox. By selecting [Start Server at Power Up], Particleworks
License Manager automatically starts when the OS starts.
9. Click [Save Service].
10. Confirm on the window that you want to save the set service (e.g. Particleworks License Manager), by
clicking [Yes].
11. Select the [Start/Stop Reread] tab and then click [Start Server].
• By selecting [Edit Advanced settings] > [Start Server Options] > [Restrict lmdown to work only
from node where lmgrd is running.], it is possible to prevent stopping the started license server
from other PCs (client machines).
• After the selection, click [Save Advanced settings] before clicking [Start Server].

33
Install Guide, Release 8.0.0

12. Select the [Server Status] tab and then click [Perform Status Enquiry].
13. Check the display of the list box and confirm that Particleworks License Manager has started normally.

34 Chapter 7. Service Registration

 CHAPTER

EIGHT

FIREWALL SETTINGS

This chapter describes how to configure Windows Firewall settings. Follow the procedure below to configure
the Firewall on the machine to be used as the license server. The screen layout and how to configure varies
depending on the PC environment; change the wording of a phrase appropriately. (The following example is
for Windows 8.1.)
1. A user with administrative rights logs in to the system.
2. Click Control Panel to open Windows Firewall.

35
Install Guide, Release 8.0.0

3. Click ‘Change settings’ and then click ‘Allow another app’.

4. In the [Add an app] dialog box, click [Browse] and select lmgrd.exe, which is stored in the bin folder
under the Particleworks/Granuleworks installation folder.
5. Flexera Software LLC will be added to ‘Apps’. After confirming, click the [Add] button to close the
[Add an app] dialog box.
6. In the same manner, add PARTICLE.exe in the bin folder under the Particleworks/Granuleworks in-
stallation folder. Particleworks Vendor Daemon will be added to ‘Apps’.
7. In [Allowed apps and features], confirm the following two items are ticked and click [OK].

36 Chapter 8. Firewall Settings

 Install Guide, Release 8.0.0

• Flexera Software LLC (Created by adding lmgrd.exe.)

• Particleworks Vendor Daemon (Created by adding PARTICLE.exe.)

37
Install Guide, Release 8.0.0

38 Chapter 8. Firewall Settings

 CHAPTER

NINE

UNINSTALLING PARTICLEWORKS/GRANULEWORKS

9.1 Windows

Uninstall Particleworks/Granuleworks from Programs and Features of Control Panel.

9.1.1 Silent Uninstallation

Execute the following command from the Command Prompt. The following is an example with Particle-
works/Granuleworks installed in the default location. You must execute the command on a location except
for Particleworks_version_yymmdd.

C:\Prometech\Particleworks_version_yymmdd\unins000.exe /silent

39
Install Guide, Release 8.0.0

9.2 Linux

Remove the extracted (unzipped) Particleworks/Granuleworks package.

40 Chapter 9. Uninstalling Particleworks/Granuleworks

 CHAPTER

TEN

FREQUENTLY ASKED QUESTIONS

1. What operating systems are supported by Particleworks/Granuleworks?

Refer to Particleworks/Granuleworks.
2. An old version of Particleworks/Granuleworks has been installed. Is it possible to install a new
version?
Yes, it is. A separate application is registered for each version.
3. Can I use the old version data file with a new version of Particleworks/Granuleworks?
You can load data and carry out postprocessing. But basically, you cannot conduct restart cal-
culations from the old result data because the data structure has been changed.
4. Can I use Particleworks/Granuleworks with a GPU other than NVIDIA?
A GPU other than NVIDIA can be used for rendering but not for calculation. Particle-
works/Granuleworks GPU solver only employs NVIDIA’s CUDA technology.
5. Does Particleworks/Granuleworks run with NVIDIA’s GeForce or Quadro?
Both GeForce and Quadro can be used for rendering but are not designed for long GPU calcu-
lation. We recommend Tesla for GPU calculation in terms of quality and accuracy. However,
Quadro listed in Verified GPUs > Calculation can be used for GPU calculation.
6. Can I calculate on GPU with standard Particleworks/Granuleworks?
To run Particleworks/Granuleworks on a GPU, you will need the GPU optional license sepa-
rately.
7. Is it necessary to install the license server even if using a node-locked license?
Yes. Even for node-locked licenses, Particleworks/Granuleworks performs license authentica-
tion via the license server.

41
Install Guide, Release 8.0.0

42 Chapter 10. Frequently Asked Questions

 CHAPTER

ELEVEN

TROUBLESHOOTING

1. Particleworks/Granuleworks has started, but such problems as the non-display of shapes or particles
occur.
Probably because the version of OpenGL supported by the graphic driver is old. Particle-
works/Granuleworks supports OpenGL 4.x or later. Please install the latest graphic driver.

43