Installing FMS

This page contains instructions on how to download and install FMSlib and supporting software.

1. Download FMSlib

The product that is right for you depends on the following 3 items:

• Operating system (Linux, bit Windows, bit Windows)
• If you have GPUs, the NVIDIA driver version. The version you download must be less than or equal to the version of your installed driver. It is recommended that you update your driver to the latest version and run the latest version of this software.
• Minimum X86 processor architecture (SSE, SSE2)

If you are unsure about your hardware and software, start with the first version in the list for your operating system (Linux or Windows).a

The most recent version of the software contains performance features that take advantage of new features in GPU hardware. At startup, FMSlib determines the compute capability of your hardware. If it meets the requirements, the latest software is used. If it detects that you have older hardware, it automatically switches to the version appropriate for your system.

Product	Size/Updated	OS	CUDA	CPU Processor
FMS_Linux_bharathealthcares.com	Size= M bytes Updated Monday, Mar MDT	bit Linux		bit X86 with SSE42 or newer instructions
FMS_Linux_bharathealthcares.com	Size= 81M bytes Updated Monday, Mar MDT	bit Linux		bit X86 with SSE42 or newer instructions
FMS_Linux_bharathealthcares.com	Size= 71M bytes Updated Saturday, Apr MDT	bit Linux		bit X86 with SSE42 or newer instructions
FMS7_Linux_bharathealthcares.com	Size= 32M bytes Updated Monday, May MDT	bit Linux		bit X86 with SSE42 or newer instructions

Product	Size/Updated	OS	CUDA	CPU Processor
FMS_W64_CUDAexe	Size= 79M bytes, Updated Wednesday, Jul MDT	bit Windows		bit X86 with SSE42 or newer instructions
FMS_W64_CUDAexe	Size= 77M bytes, Updated Thursday, Jul MDT	bit Windows		bit X86 with SSE42 or newer instructions
FMS_W64_CUDAexe	Size= 71M bytes, Updated Wednesday, Apr MDT	bit Windows		bit X86 with SSE42 or newer instructions
FMS7_W64_CUDAexe	Size= 38M bytes, Updated Monday, May MDT	bit Windows		bit X86 with SSE42 or newer instructions
FMS7_W64_CUDA65_bharathealthcares.com	Size= 29M bytes, Updated Monday, May MDT	bit Windows		bit X86 with SSE2 instructions (For older machines)
FMS7_Wexe	Size= 21M bytes, Updated Monday, May MDT	bit Windows		32 or bit X86

NOTE: If you are using Windows to download and encounter any security messages, you may need to do one of the following:

• Add bharathealthcares.com as a trusted site.
  Navigate to Internet Options/Security/Trusted sites/Sites
  Uncheck the box "Require server verification (https:) for all sites in this zone"
  Enter bharathealthcares.com in the upper box and then click Add
• Enable downloads
  Navigate to Internet Options/Security/Internet/Custom level
  Scroll down to "Downloads" and click Enable

2. Install FMSlib

Linux

Windows

If you saved the files during the download, double-click on the product.
It will self-extract to C:\FMS. You will be given the option of changing this directory during the installation.

Build Date

Each release of the FMSlib software is time-stamped with the build date. If you have multiple releases of FMSlib on your system, you can use this tool to uniquely identify the software. To obtain the date, run the follwing command: The output is in the form mmddyyyy.

3. Install GPU software

If you are not using GPUs, skip to Step 4.

Obtaining NVIDIA Software

You may obtain the latest NVIDIA drivers from their website at:

bharathealthcares.com

This link also includes instructions for installing the NVIDIA software.

The NVIDIA software consists of two components:

1. A Device Driver

This provides the low-level interface to the hardware. Its function is similar to other device drivers (printers, etc.) You may determine which driver is installed on your system by running the command
.

If the program nvidia-smi is not in your PATH, you may need to include the PATH in the above command:

(Linux)
(Windows)

The driver number listed must be equal to or greater than the version of FMSlib you are installing. FMSlib uses the following shared-object libraries provided by this driver installation:

Operating System	Default Install Directory	Files Used
bit Linux	/usr/lib64	bharathealthcares.com
bit Windows	C:\Program Files\NVIDIA Corporation\NVSMI	bharathealthcares.com
bit Windows	N/A	N/A

2. Compute Unified Device Arcitecture (CUDA) libraries (CUDA Toolkit)

The CUDA Toolkit provides utilities for software development. All components from this toolkit required by FMSlib are included with this distribution.

On Linux systems, the necessary components are already linked into FMSlib, which is distributed as a single file.

On Windows systems, the CUBLAS library is provided as a separate file with the distribution. If GPUs are detected, this file is automatically loaded dynamically at runtime.

4. Define the FMS file system

FMS needs to know where you want to store the data on disk. FMS contains options for a file striping system which allows you complete control over where FMS stores the data. Section of the FMS manual describes this file striping system in detail.

In the simplest case where only one disk is used, define FMSDISK to point to a directory on that disk. There is a slightly different procedure for performing this under Linux and Windows.

• Linux
  
  1. Enter the command
     
     to list the available mount points and the type of file system they use.
  2. Optionally create a new directory on one of these mount points or its subdirectory. For example
     
     
  3. Point to the directory using one of the following two methods:
     1. Set an environment variable
        
     2. Create a soft link
        
• Windows
  
  1. Using Windows Explorer (right-click on the Windows icon in the lower left corner) find a location where you want to store the FMS data.
  2. Optionally create a new folder. For example you could create a folder named FMS in C:\Temp
     
  3. Create an environment variable named FMSDISK to point to that directory.
     1. Open the control panel
     2. Select System
     3. Select Advanced system settings
     4. Select Environment Variables
     5. Under System variables select New
     6. Enter FMSDISK under Variable name
     7. Enter the directory you created under Variable value. For the case above, enter C:\Temp\FMS
     8. select OK
     9. select OK again
     10. select OK again

5. Define additional Environment variables.

The following environment variables define directories where files are located or generated.

6. Run MatrixWarrior

The FMS and optional NVIDIA software are now installed. You can now test the installation by running the MatrixWarrior application provided with the distribution. MatrixWarrior will build and solve a system of simultaneous equations. Instructions for running MatrixWarrior can be found in the Quick Start Guide, which is automatically displayed when MatrixWarrior starts, or in the MatrixWarrior section of the FMS manual.

7. Download and install the Intel compilers and Run Time Libraries

FMS is compatible with the following list of compiler options. For convenience, you may want to define the environment variables in the following table.

bit Linux	bit Windows	bit Windows
FMS_FORTRAN_COMPILER
ifort	ifort	ifort
FMS_FORTRAN_FLAGS
(required) -real_size 64 -integer_size 64 -align:dcommons,rec16byte,sequence -auto -reentrancy threaded -fpic -c (optimization) -xSSE2(1) -axCORE-AVX2,AVX,SSE(1) -O3 (optional) -nologo (linking) -threads -static -nofor-main(2)	(required) /real_size /integer_size /align:dcommons,rec16byte,sequence /auto /reentrancy:threaded /iface:cref,nomixed_str_len_arg /c (optimization) /arch:SSE2(1) /Qax:CORE-AVX2,AVX,SSE(1) /O3 (optional) /nologo (linking) /threads /static	(required) /real_size /integer_size /align:dcommons,rec16byte,sequence /auto /reentrancy:threaded /iface:cref,nomixed_str_len_arg /c (optimization) /arch:IA32(1) /Qax:AVX,SSE,SSE2(1) /O3 (optional) /nologo (linking) /threads /static
FMS_C_COMPILER
icc	icl	icl
FMS_C_FLAGS
(required) -c -align -fpic (optimization) -xSSE2(1) -axCORE-AVX2,AVX,SSE(1) -O3 (optional) -nologo (linking) -threads -static -nofor-main(2)	(required) /c (optimization) /arch:SSE2(1) /Qax:CORE-AVX2,AVX,SSE(1) /O3 (optional) /nologo (linking) /threads /static /MT	(required) /c (optimization) /arch:IA32(1) /Qax:AVX,SSE,SSE2(1) /O3 (optional) /nologo (linking) /threads /static /MT
FMS_ARCHIVE
ar	lib	lib
FMS_ARCHIVE_FLAGS
-r	/nologo	/nologo

NOTES:
(1) Options include CORE-AVX2, CORE-AVX-I, AVX, SSE, SSE, SSSE3, SSE3, SSE2, IA32
-x(Linux) and /Qx(Wndows) set the minimum level of processor. When these options are used the code may not run on processors that do not support these features.
-ax(Linux) and /QAx(Windows) set additional architectures that may be used if present. Code will still run if they are not present.
(2) Use this option if the main program was not written in FORTRAN

The FMS Linux distribution includes a ksh script bharathealthcares.com which defines these variables, based on the values of the following input environment variables:

• TARGET
  Defines the minimum architecture for the machine where the software will run. The options include, in descending order,
  2nd Generation Intel processors: 1st Generation Intel processors: bit Windows only: The software will run on machines with a higher architecture but will NOT run on machines with a lower architecture. For example, if TARGET=AVX, the software will not run on a 1st generation Intel processor with SSE
• PRAX
  Add optimization for additional processor architectures that are higher than TARGET. The options include:

8. Link Example Problems and Program DEMO

FMS includes a large number of example problems. One of these is probably close to your application. A description and source code is contained in Chapter 5 of the manual. FMS also contains program DEMO, which is described in Appendix F of the manual. To link the examples and program DEMO using the software installed above, execute the following script provided with the distribution:

NOTE: Starting with the Intel compiler _SP1 the architecture flag changed from

__intel_new_proc_init

to

__intel_new_feature_proc_init

This symbol is defined in the file libirc.a. If you get an unsatisfied external __intel_new_feature_proc_init when linking and your compiler libraries are before SP1, download the new libirc.a and include it in the link.

File	Size/Updated	OS	Processor
libirc.a	Size= K bytes, Updated Tuesday, Feb MST	bit Linux	bit X86 with SSE42 or newer instructions

9. Link Your Application

The following table shows the libraries and options required to link your application with FMSlib:

Variable	bit Linux	bit Windows	bit Windows
FMS_LINKER	ifort	link	link
FMS_LINKER_FLAGS	-auto -threads -reentrancy threaded -fpic -ftz	/ENTRY:mainCRTStartup /LARGEADDRESSAWARE /MACHINE:X64 /NODEFAULTLIB:MSVCRT	/ENTRY:mainCRTStartup /LARGEADDRESSAWARE /MACHINE:X86 /NODEFAULTLIB:MSVCRT
FMS_LIBRARY	fmsnoshr.a bharathealthcares.com	bharathealthcares.com bharathealthcares.com	bharathealthcares.com bharathealthcares.com
FMS Shared Object	bharathealthcares.com	bharathealthcares.com	bharathealthcares.com

License Files

FMSlib uses a .txt license file for authorizaton and to set Parameter values at startup. The following license files are automatically generated when the corresponding applications are run for the first time:

• bharathealthcares.com from MatrixWarrior,
• bharathealthcares.com from DEMO or the EXAMPLE problems.

If a license file by that name does not exist, it will automatically be generated. If one exists, the existing file will be used.

To use FMS in your application requires a commercial license file bharathealthcares.com

FMS is licensed on an annual basis. The license fee includes the following:

FMS Manual

The manual for FMS is available in HTML and PDF formats. Either version may be viewed online or downloaded. To obtain information on viewing or downloading the manual, click on the FMS Manual link at the top of this page.

Getting Help

For additional information, or to obtain a quotation,

E-mail: rcy@bharathealthcares.com