CONTENTS

• Installation
• Some Suggested Aliases
• Executive Summary

The "executive summary" summarizes the basic installation procedure and may be all you really want to know

INSTALLATION

To install CFL3v6 on a particular machine, you must have the following file:

• cfl3dv6.tar.DATE.gz (tarred and gzipped version 6 package)
  Note: DATE indicates the release date in the form MMM_DD_YYYY For example, cfl3dv6.tar.Sep_12_2003 indicates the code as of September 12, 2003.

Make sure that:

• ./ is in your path; if not, you will have to explicitly prepend ./ to all the commands below

STEP 1)

Type:

You should end up with the following directory structure:

                            cfl3dv6 directory structure:

                                   CFL3DV6
                                      |
                             -------------------
                             |        |        |
                           SOURCE   BUILD   HEADER
                             |
      --------------------------------------------
      |       |         |      |         |       |
    CFL3D  PRECFL3D  RONNIE  MAGGIE  SPLITTER  TOOLS 
      |
   -------
   |     |
  DIST  LIBS


                          build directory structure:

                                    BUILD
                                      |
        ----------------------------------------------------------------
        |             |        |      |      |    |     |      |       |
       CFL        CFLCMPLX  PRECFL  PRERON  RON  MAG  TOOLS  SPLIT SPLITCMPLX
        |             |        |      |      |    |     |      |       |
    ---------    ----------    |      |      |    |     |      |       |
    |   |   |    |    |   |    |      |      |    |     |      |       |
  LIBS SEQ MPI  LIBS SEQ MPI  SEQ    SEQ    SEQ  SEQ   SEQ    SEQ     SEQ

The cfl3dv6 directory will reside one directory level below the one in which you executed the packitup script. The source directory and its associated subdirectories hold the source code for CFL3D and its supporting codes. The build directory is used to create execuatbles from the code in the source directories. Some pieces of source code get copied into the build directories, while other pieces of source code get soft-linked to the build directories. Thus, source code appears visible in the build directories; however, if the user desires to make any permanent changes to the source code, the changes need to be made an the source code directory level, not the build directory level.

The cfl3dv6 directory will have a README file which contains most of the installation information included here, though you may want to check for additional or late-breaking information. Next, cd to the build directory. Make sure the script file Install has execute permission.

STEP 2)

Type:

Where [options] may be one or more of the following:

-no_opt

create executables with little optimization but fast compilation

-single

create single precision executables

-noredirect

disallow redirected input file; often needed for SP2 and for Linux with MPI (generally recommended for MPI - see note below)

-mpichdir=dir1

use MPICH on a workstation cluster; dir1 is the directory where mpich is located - not used on MPP machines

-purify

fortran memory checker: need 3rd party license for this

-fastio

fast I/O option when using MPI: creates cfl3d.out.reass file (in place of standard output file)... this option may help speed up some very large MPI runs by writing output to local files then reassembling at the end, rather than sending the output back to the master for writing-on-the-fly (acknowledgment: Robert Bergeron, NASA Ames)

-cgnsdir=dir2

allow the use of CGNS files instead of the standard grid/restart files; dir2 is the directory where the CGNS libraries are located; the directory should contain the file cgnslib_f.h as well as the subdirectory appropriate to the system you are running on (for example subdirectory LINUX/) with the library file libcgns.a in it

-linux_compiler_flags=flag

sets up to compile using special compiler flags for use on Linux operating systems only; flag is currently Intel, PG, Lahey, or Alpha (Intel is currently the default)

-help

print out the Install options

Note: the directory paths for either the mpichdir or cgnsdir options should be either absolute paths or paths relative to the installation directory; the use of ~ to denote a home directory is not allowed.

• If -no_opt is not specified, various compiler optimization levels are used to speed execution but results in slower compilation.
• If -mpichdir=dir1 is not used, then it is assumed "native" MPI is available, and will use a default location for the necessary MPI libraries.
• If -single is not used, then double precision exectables will be created at the make [ ] command.
• If -noredirect is not used, then input file redirection will be allowed, i.e. you can use: cfl3d_seq < filename.inp to tell CFL3D to use the input data in the file filename.inp. Otherwise, with the -noredirect option invoked, the input file must be named cfl3d.inp when running the code. Unfortunately, the SP2 and many Linux systems cannot deal with file redirection in many cases when MPI is used, so the -noredirect option needs to be added. Our current recommendation is: on the SP2 and on Linux systems, always install with -noredirect when using MPI, always name the input file cfl3d.inp, and never use file redirection (just type the executable name).
• If -cgnsdir=dir2 is used, then you must download the free CGNS system from (CGNS Home Page). Compile CGNS according to the instructions. Using a CGNS file requires that the CFL3D input file contain the keyword icgns 1 (see New Features) in addition to having installed the code with the -cgnsdir option. It is the user's responsibility to download the CGNS software from the CGNS website and insure it is installed correctly in the user-specified directory dir2. NOTE: while you are free to specify the name of the directory dir2, please note that the CFL3D Install file makes the following assumptions about this directory: 1) that it contains a file called cgnslib_f.h and 2) that it contains a subdirectory with a specific name assigned by CGNS for your particular system, in which is located the file libcgns.a. Please insure that the subdirectory assigned by the CFL3D Install file matches the name of the subdirectory created by CGNS for your particular system. Also NOTE: if you would like to use CGNS but do not have a CGNS grid available, you can create one using the program plot3dg_to_cgns in the Tools/ directory (compiled using make cfl3d_tools).
• NOTE FOR LINUX USERS: due to the variability of Linux installations, available compilers, etc., it is not possible to set FFLAGS, FTN, etc varables universally once Linux has been identified as the OS: the default flags are currently set for the Intel compiler. Note the default Fortran compiler for Linux is currently set as mpif77 - if this does not work, you will need to change this to a compiler that is available on your machine: e.g. ifc, pgf90, etc. For certain implementations of MPI on Linux you may need to use the -noredirect install option to turn off input file redirection.
• A known problem exists for MPI on alphas using myrinet. The following 2 lines of code in main.F cause an error:

  sysfile = 'rm -f stop'
  call system(sysfile)
  

  If you are running under these circumstances, you will need to comment out these 2 lines of code, and manually delete the "stop" file if it exists. prior to your run.

Standard installation on all MPPs (except for the SP2), Cray C90, and stand-alone workstations would simply be:

Install

This will create a makefile set up for optimized compilation, double precision, using native MPI libraries when needed. Note: the install script assumes some very basic locations for the MPI directories - you may need to alter these for your own particular system.

Standard installation on a workstation cluster would be:

Install -mpichdir=/some_appropriate_path/mpich

This will create a makefile set up for optimzed compilation, double precision, using the MPI routines contained in the MPICH libraries when needed.

The Install script works by querying the current machine for its' achitecture, then sets up the various compilation flags based on the architecture, and creates a file called makefile by edititing the Makefile.in file and inserting the proper compiler flags. This eliminates the need for multiple makefiles that are typical of other versions of CFL3D.

At this point CFL3Dv6 has been installed on your machine and you should have a makefile suited to the particular machine on which you are running. At the end of the install script, several messages are written out, indicating which platform it thinks you are using, where it assumes the mpi directories are, etc. The script will also suggest you type make to see a description of the various make options. The next step is to build the executables you want Building Executables.

Return To Top

SOME SUGGESTED ALIASES

Once you have CFL3Dv6 installed on your machine, you may want to make an alias to the build directory, since compilation of the various executables will always be done in that directory. If you tend to edit the source code frequently, you may want to make a similar alias to the source directory. Such aliases will relieve you from having to type or remember the whole path. Some examples include:

alias build "cd ~myhome/cfl3dv6/build"

alias code "cd ~myhome/cfl3dv6/source/cfl3d/dist"

Return To Top

EXECUTIVE SUMMARY

To install the CFL3Dv6 system:

gunzip cfl3dv6.tar.DATE.gz

tar -xvf cfl3dv6.tar.DATE

cd cfl3dv6/build

Install [options]

Return To Top

Building Executables

Return To Top

Page Curator and NASA Responsible Official: Christopher L. Rumsey

Last Updated: February 20, 2008

Privacy Statement

LMS Feedback Form