a) mkdir Vulcan (this is the directory where VULCAN is to reside)

b) cd Vulcan

c) use a web browser to access the VULCAN website vulcan-cfd.larc.nasa.gov

d) select the VULCAN SOFTWARE REQUEST link

e) call me at (757) 864-9016 to obtain:

a user id

a user password

f) then click on the ftp the gzipped vulcan.tar file link and enter the user id and password to download the tar file

a) un-zip (gunzip Ver_6.1.0.tar.gz) and extract (tar -xvf Ver_6.1.0.tar) the tar file

b) cd Ver_6.1.0/Scripts

c) type pwd and record the complete pathname (you will need it later)

d) edit the vulcan_config file and complete the following steps:

NOTE: This file assumes that the tcsh shell is available on your system. if this is not the case, change the first line of this file from #!/bin/tcsh to #!/bin/csh

1) select the platform type that VULCAN is to be installed on (i.e. remove the leading # signs for the desired platform type)

• Linux_IFORT => Intel 32-bit processor with Linux o.s. using the Intel 10.X (or higher) FORTRAN compiler
• Linux_LFC => Intel 32-bit processor with Linux o.s. using the Lahey/Fujitsu 8.X (or higher) FORTRAN compiler
• Linux_PGC => Intel 32-bit processor with Linux o.s. using the Portland Group 7.X (or higher) FORTRAN compiler
• Linux_PSC => Intel 32-bit processor with Linux o.s. using the PathScale 3.X (or higher) FORTRAN compiler
• Linux_Sun => Intel 32-bit processor with Linux o.s. using the Sun 8.X (or higher) FORTRAN compiler
• Linux_G95 => Intel 32-bit processor with Linux o.s. using the GNU G95 0.X (or higher) FORTRAN compiler
• Linux_GFC => Intel 32-bit processor with Linux o.s. using the GNU GFORTRAN 4.1.X (or higher) FORTRAN compiler
• Linux_IFORT_64 => Intel 64-bit processor with Linux o.s. using the Intel 10.X (or higher) FORTRAN compiler
• Linux_LFC_64 => Intel 64-bit processor with Linux o.s. using the Lahey/Fujitsu 8.X (or higher) FORTRAN compiler
• Linux_PGC_64 => Intel 64-bit processor with Linux o.s. using the Portland Group 7.X (or higher) FORTRAN compiler
• Linux_PSC_64 => Intel 64-bit processor with Linux o.s. using the PathScale 3.X (or higher) FORTRAN compiler
• Linux_Sun_64 => Intel 64-bit processor with Linux o.s. using the Sun 8.X (or higher) FORTRAN compiler
• Linux_G95_64 => Intel 64-bit processor with Linux o.s. using the GNU G95 0.X (or higher) FORTRAN compiler
• Linux_GFC_64 => Intel 64-bit processor with Linux o.s. using the GNU GFORTRAN 4.1.X (or higher) FORTRAN compiler
• Linux_AMD_IFORT => AMD 32-bit processor with Linux o.s. using the Intel 10.X (or higher) FORTRAN compiler
• Linux_AMD_LFC => AMD 32-bit processor with Linux o.s. using the Lahey/Fujitsu 8.X (or higher) FORTRAN compiler
• Linux_AMD_PGC => AMD 32-bit processor with Linux o.s. using the Portland Group 7.X (or higher) FORTRAN compiler
• Linux_AMD_PSC => AMD 32-bit processor with Linux o.s. using the PathScale 3.X (or higher) FORTRAN compiler
• Linux_AMD_Sun => AMD 32-bit processor with Linux o.s. using the Sun 8.X (or higher) FORTRAN compiler
• Linux_AMD_G95 => AMD 32-bit processor with Linux o.s. using the GNU G95 0.X (or higher) FORTRAN compiler
• Linux_AMD_GFC => AMD 32-bit processor with Linux o.s. using the GNU GFORTRAN 4.1.X (or higher) FORTRAN compiler
• Linux_AMD_IFORT_64 => AMD 64-bit processor with Linux o.s. using the Intel 10.X (or higher) FORTRAN compiler
• Linux_AMD_LFC_64 => AMD 64-bit processor with Linux o.s. using the Lahey/Fujitsu 8.X (or higher) FORTRAN compiler
• Linux_AMD_PGC_64 => AMD 64-bit processor with Linux o.s. using the Portland Group 7.X (or higher) FORTRAN compiler
• Linux_AMD_PSC_64 => AMD 64-bit processor with Linux o.s. using the PathScale 3.X (or higher) FORTRAN compiler
• Linux_AMD_Sun_64 => AMD 64-bit processor with Linux o.s. using the Sun 8.X (or higher) FORTRAN compiler
• Linux_AMD_G95_64 => AMD 64-bit processor with Linux o.s. using the GNU G95 0.X (or higher) FORTRAN compiler
• Linux_AMD_GFC_64 => AMD 64-bit processor with Linux o.s. using the GNU GFORTRAN 4.1.X (or higher) FORTRAN compiler
• Linux_DEC => DEC Alpha with Linux o.s. using the DEC FORTRAN compiler
• DecAlpha => DEC Alpha with True64 o.s. using the DEC FORTRAN compiler
• HP-UX => HP with HP Unix o.s. using the HP FORTRAN compiler
• Sun => Sun with Solaris o.s. using the Sun FORTRAN compiler
• IBM => IBM with AIX Unix o.s. using the IBM FORTRAN compiler
• CrayXT => Cray XT with Cray UNICOS o.s. and Cray FORTRAN compiler
• SGI => SGI with IRIX o.s. using the SGI FORTRAN compiler (big endian bit order only)

2) select the compilation precision:

• setenv VULCAN_comp_prec single_prec
• setenv VULCAN_comp_prec double_prec (recommended)

3) select the bit order for unformatted I/O files:

• setenv VULCAN_endian little (native option for most platforms)
• setenv VULCAN_endian big (only option for SGI with IRIX)

4) select the desired execution mode to configure VULCAN for execution on single-cpu serial machines or multiple-cpu parallel machines by selecting one of the following:

• setenv VULCAN_run_mode serial (single-cpu execution only)
• setenv VULCAN_run_mode parallel_mpi (multi-cpu execution via proprietary versions of MPI)
• setenv VULCAN_run_mode parallel_mpich (multi-cpu execution via MPICH 1 or MPICH 2 w/out automated start-up of daemons)
• setenv VULCAN_run_mode parallel_mpich2 (multi-cpu execution via MPICH 2 with automated start-up of daemons)
• setenv VULCAN_run_mode parallel_openmpi (multi-cpu execution via OpenMPI)
• setenv VULCAN_run_mode parallel_lammpi (multi-cpu execution via LAM/MPI)
• setenv VULCAN_run_mode parallel_myrinet (multi-cpu execution via Myrinet)
• setenv VULCAN_run_mode parallel_mvapich (multi-cpu execution via INFINIBAND)

5) select the desired remote shell protocol:

• setenv VULCAN_rmt_protocol rsh
• setenv VULCAN_rmt_protocol ssh

6) set the vulcanpath shell variable to point to the Ver_6.1.0 directory created by the tar -xvf command (step a above)

7) set the VULCAN_METIS environment variable to enable or disable the use of METIS V4.0 for partitioning blocks to processors via the automated block splitter. METIS V4.0 must be pre-installed in the vulcanpath/Utilities/Load_Balance_codes directory prior to enabling this option.

8) set the VULCAN_debug_mode environment variable to on or off. The setting should be set to off unless source code problems are suspected.

9) set the shell variable that defines the command line structure for your multi-cpu execution environment. Several examples are given to draw from.

NOTE: Skip this step if the execution mode was set to serial in step 4 above

e) edit your personal ~/.tcshrc (or ~/.cshrc) file and add the following line (at a location that will always be executed):

source pathname/vulcan_config

NOTE: the pathname is the complete pathname that resulted from step c) above

f) type source ~/.tcshrc (or source ~/.cshrc)

g) type either:

1) install_vulcan new

   or if you want to prevent access to the source code

2) install_vulcan new secure_source

WARNING! this command causes the automatic removal of the source (*.F) files and the downloaded tar file to prevent unauthorized technology transfer.

There are two VULCAN Graphical User Interfaces (G.U.I.s):

1) The VULCAN input file G.U.I provides an interface to help with the creation of a VULCAN input deck. The VULCAN input G.U.I. is invoked by typing (vulcanig).

2) The VULCAN CFD Desktop G.U.I provides an interface to the following types of CFD application software:

a) Grid generation codes (e.g. Gridgen, Gridpro, etc.)
b) VULCAN input G.U.I.
c) VULCAN code
d) Plotting of VULCAN residual, force, and moment history files using Tecplot
e) Plotting of post-processing files (e.g. Fieldview or Tecplot)

The VULCAN CFD Desktop G.U.I is invoked by typing VULCAN-CFD.

The VULCAN Graphical User Interfaces were written to utilize a scripting language called Tcl/Tk (version 8.2.2 or higher). The Tcl/Tk package can be downloaded for no charge from the site:

http://www.tcl.tk/software/tcltk/

To determine if this package is already installed in your system, type:

which wish

If wish appears, then the version of wish that is installed on your system can then be ascertained by following the steps below:

1) in a shell window, type:

wish

2) in the same shell window, type:

info tclversion

3) exit the wish interpreter, type:

exit

Once a compatible version of Tcl/Tk has been installed on the host machine, follow the steps below to configure the VULCAN Graphical User Interfaces:

a) cd Ver_6.1.0/Scripts

b) edit the vulcan_config_gui file and complete the following steps:

1) set the WHICHWISH environment variable to point to the wish shell interpreter

2) set the TCLGRIDGPATH environment variable to point to the desired grid generator executable (e.g. /usr/local/bin/gridgen)

3) set the TCLTECPLPATH environment variable to point to the Tecplot executable (e.g. /usr/local/bin/tecplot)

4) set the TCLPOSTPPATH environment variable to point to the desired post-processing software executable (e.g. /usr/local/bin/tecplot or /usr/local/bin/fv)

5) set the TCLBROWSER environment variable to point to the desired HTML browser executable (e.g. /usr/local/bin/firefox)

6) set the cluster processor and mapping information

NOTE: skip this step if a serial installion was performed

If the parallel execution environment utilizes a batch scheduler (or if a user-specified host file is not required), specify:

• the no. of nodes in the cluster (setenv VULCAN_sc_nods_1 N)
• the no. of processors per node  (setenv VULCAN_sc_cpus_1 N)

If the parallel execution environment does not utilize a batch scheduler (i.e. a user-specified host file is required), specify:

• the name of the master node
  
  
  setenv VULCAN_master_node XXXX
  
  
• the number of sub-clusters belonging to the cluster (1 <= VULCAN_sc_noof <= 5)
  
  
  setenv VULCAN_sc_noof N
  
  
• the prefix of the compute node names in the sub-cluster
  
  
  setenv VULCAN_sc_prfx_1 XXXX
  .
  .
  .
  setenv VULCAN_sc_prfx_N XXXX
  
  
• the no. of nodes in the sub-cluster
  
  
  setenv VULCAN_sc_nods_1 N
  .
  .
  .
  setenv VULCAN_sc_nods_N N
  
  
• the no. of cpus per node in the sub-cluster
  
  
  setenv VULCAN_sc_cpus_1 N
  .
  .
  .
  setenv VULCAN_sc_cpus_N N
  
  

  ---

  Example: A beowulf cluster consisting of two sub-clusters:
  15 dual-cpu nodes (flim) and 48 single-cpu nodes (flam)
  
      setenv VULCAN_sc_noof 2
  
      setenv VULCAN_sc_prfx_1 flim
      setenv VULCAN_sc_nods_1 15
      setenv VULCAN_sc_cpus_1 2
  
      setenv VULCAN_sc_prfx_2 flam
      setenv VULCAN_sc_nods_2 48
      setenv VULCAN_sc_cpus_2 1
  

  ---

  
  

c) edit your personal ~/.tcshrc (or ~/.cshrc) file and add the following line just after the vulcan_config line that was added previously:

source pathname/vulcan_config_gui

NOTE: the pathname should be identical to that used in the vulcan_config line

d) type source ~/.tcshrc (or source ~/.cshrc)

a) A complete input description resides in the Doc_manual/WebPage_manual directory in HTML, Microsoft Word, and postscript formats.

b) A brief write up of the governing equations solved and some turbulence modeling issues can be found as a postscript file under the Doc_manual directory.

a) Using VULCAN-CFD will hide all of the command syntax and walk you through the options list as well as automatically adjust the command syntax for your installation. However, if you prefer to use the command line mode, you can obtain the command line syntax and options by typing vulcan <return> and a complete list of all the possible options and syntax will be displayed.

i) To submit a serial mode job on the local host, type:

vulcan -psg your.input.file your.output.file

where:

-psg are the code execution options, which are defined as:
p = Execute the VULCAN pre-processor
s = Execute the VULCAN flow solver
g = Execute the VULCAN post-processor to generate the plot files


your.input.file = file name of the VULCAN input file that controls how VULCAN executes

your.output.file = file name of a file to which the VULCAN runstream will be written

ii) To submit a multiple cpu parallel job on the local host, type:

vulcan no_cpus vulcan.hosts -psg your.input.file your.output.file

where:

no_cpus is the number of processors (cpus) to be used (this needs to be consistent with the no. of PROCESSORS specified in the VULCAN input file)

vulcan.hosts is the file name of a file containing the host node names to be used by the mpi job (use a dummy name if your system does not require this file)

-psg are the code execution options, which are defined as:
p = Execute the VULCAN pre-processor
s = Execute the VULCAN flow solver
g = Execute the VULCAN post-processor to generate the plot files


your.input.file = file name of the VULCAN input file that controls how VULCAN runs

your.output.file = file name of a file to which the VULCAN runstream will be written

b) To submit a batch job you must set up the batch submittal file to access the directories and software as needed

c) The code has extensive error checking logic to assist you in detecting input errors

With the introduction of multi-processor / parallel capabilities, stopping an active simulation became more tedious than simply issuing a control C or kill -9 ##### command. MPI can spawn processes on multiple nodes which must all be killed to completely stop an active run. If VULCAN was installed to execute in parallel mode, then an active VULCAN simulation can be terminated by placing a file called STOP_VULCAN in the current working directory. If one wants to specify the precise iteration number (elliptic problems) or plane number (parabolic problems), then this number should be placed on the first line of the file. If the region currently being solved is an elliptic region, and an iteration number is not specified, then execution will terminate within 5-15 iterations of the current iterate (the iteration lag is an attempt to account for any network lag that may be present on network mounted disks). If the current region being solved is a parabolic region, and no plane number is specified, then execution will terminate as soon as the simulation finishes on the current plane. The STOP_VULCAN file should be removed before trying to execute VULCAN again in the directory containing the file. Placing a file called STOP_VULCAN_WR performs the same task as STOP_VULCAN, except that a restart file dump is performed prior to termination. Placing a file called STOP_VULCAN_PP performs the same task as STOP_VULCAN_WR but continues on with the post-processing step.

The general input file, stdin, consists of several different sections (see chapters 2-6 below):

a) General control data input, required for overall code configuration
b) Block control
c) Region control
d) Boundary condition input
e) Block-to-block interface (cut) condition input
f) Non-C0 block-to-block interface (patch) condition input
g) Laminar/turbulence/transition region input (optional)
h) Ignition region input (optional)
i) Time history region input (optional)

In addition, VULCAN requires a computational grid input file that was written according to the PLOT3D multi-block standards (NASA TM 101067)

a) Runstream output file: your.output.file (if no runstream output file is specified, then the runstream is written to the device connected to unit 6)

b) Restart files as named in the Output Control Data section of your input file. If you named the restart file "restart" and have one region, then three files will be produced, making up the restart named:

1) restart_M
2) restart_1_S
3) restart_1_F

where the extensions _M , _#_S and _#_F are:

_M   = map file which contains the number of regions and block numbers that belong to each region
_#_S = specification file for region no. # which contains the number of blocks, block sizes, gas model, turbulence model, and chemistry model specifications for the designated region
_#_F = flow file for block no. # which contains the flowfield data for the designated block

The _M, _#_S, and _#_F extensions are appended by the flow solver to the base restart file name provided in the input deck

c) Integrated force & moment history file: vulcan.ifam_his_#.tec (this file is only written out for elliptic regions, where the # refers to the region number)

c) Residual history file: vulcan.res.tec

d) Surface data file: vulcan.loads.tec

e) PLOT3D format files will be created in a sub-directory of your current working directory called Plot3d_files:

1) a multi-block PLOT3D grid file based on the no. of blocks specified to be merged in the VULCAN input file:

plot3d.g

2) a corresponding solution file being either:

plot3d.q (a multi-block PLOT3D Q file, if PLOT Q was requested in the input file)

plot3d.f (a multi-block PLOT3D function file, if PLOT FUNCTION was requested in the input file)

3) a Fieldview function name file

plot3d.nam

4) a Fieldview boundary file

plot3d.g.fvbnd

f) Time-averaged restart files as named in your input file if OUTPUT TIME AVERAGE (see the "Output Control Data" section of Chapter 2) is specified, will reside in the directory Time_files. The naming convention is identical to that used for restart files.

g) Time history files as named in your input file if OUTPUT TIME HISTORY (see the "Output Control Data" section in Chapter 2) is specified, will either reside in the directory Time_files/Plot3d_files (if a path is not included in the file name), or if a full or partial path is given, then the files will reside at the location given by the supplied path. The naming convention is as follows:

plot3d_file_#_#_0.g   AND
plot3d_file_#_#_#.q   OR   plot3d_file_#_#_#.f

where the first # is the block number, the second # is the sub-zone number for that block (as given in the TIME HISTORY I/O section), and the third # is the counter for each time history data dump.

Several utility codes are supplied with VULCAN in the Utilities directory located in the main VULCAN directory. These codes are provided to either increase the flexibility of VULCAN, or allow VULCAN to interface with other software. A brief description of each utility is given below:

a) In the directory Dbase_codes there are several FORTRAN codes that can be used to perform operations on database files. The utility conv_chem reads a CHEMKIN format kinetic database file and translates it to a VULCAN kinetic database format. The utility ls_fit performs least squares fits between various thermodynamic functional forms. This utility can also be used to fit various functional forms for transport properties. The utility mix_fit can be used to determine thermodynamic and/or transport property curve fits for a given species mixture. The utility vulcan_gas reads in a VULCAN gas property database and outputs the properties for plotting purposes.

b) In the directory Grid_codes there are several FORTRAN utilities that relate to grid files or how the grid boundary information interfaces with VULCAN. The Plot3d directory houses the utility grid_plot3d. This utility can perform a variety of manipulations to PLOT3D (or PLOT2D) format grid files (coarsening, scaling, shifting, swapping coordinates, changing file formats, etc), as well as provide information on the number of grid levels that the grid can support and how many processors it can efficiently be load balanced over. The utility can also be used to manually split grid blocks as necessary for efficient processing on parallel machines. In the Gridgen directory, the utility gridgent allows one to read a generic flow solver boundary condition file produced by Gridgen and translate the information into the boundary condition and cut condition sections of a VULCAN input file. There are also two glyph files that one can import into Gridgen to aid with the specification of the boundary conditions. The vulcan_bcs.glf file contains all of the VULCAN specific boundary conditions, which is particularly useful if one knows the precise boundary conditions to impose at the time that the grid is being generated. The vulcan_bcgrps.glf file contains generic boundary condition classes that might be more suitable when the specific boundary conditions to be applied have not yet been decided upon. The Gridpro directory contains a similar set of utilities built for the Gridpro mesh generation software. gridprot reads a connectivity file produced by Gridpro and translates the information into the boundary condition and cut condition sections of a VULCAN input file. Two property map files are available to aid with the setting of boundary conditions as a part of the grid generation process. The ptymap.vulcan_bcs file provides the VULCAN specific boundary conditions to the az manager of Gridpro, or alternatively the ptymap.vulcan_bcgrps file provides boundary condition classes to choose from. The ptymap.menu file provides the interface that allows the user to select one of the property map files described above from within Gridpro. The gridfmt.menu file provides an interface to Gridpro that allows the user to select a grid output format that is suitable for VULCAN. The scripts that perform the operations to output the grid coordinates in a PLOT3D format are outE_vulcan.script and outM_vulcan.script. To utilize the files described above, simply copy them into the az_mngr directory of Gridpro. Finally, the V2K directory contains the utility v2knmapt which reads a neutral map file produced by the GeoLab V2K software and translates the information into the boundary condition and cut condition sections of a VULCAN input file. A "tog" file exists (vulcan_bcs.tog) to aid with the setting of VULCAN specific boundary conditions with V2K.

c) In the directory Load_Balance_codes/SGLD there is a key utility that modifies (splits) grid blocks for efficient parallel processing. The grid splitting executable (grid_split) splits the grid blocks of a PLOT3D format grid file based on the number of processors desired and a given load balance tolerance. The utility also performs the required splitting operations to the input deck associated with the grid file to be split. The use of this utility is highly recommended if one intends to utilize VULCAN on massively parallel machines. The utility can either be run from the command line, or it can be directly accessed from the VULCAN input GUI (vulcan_input_gui). A separate utility (restart_split) is available to split any restart files that may be present. Recomposition utilities (VULCAN_mrgrst and VULCAN_mrgpst) are also available to recompose the VULCAN restart files and the PLOT3D solution files generated by VULCAN back to their original un-split state. The recomposition of the plotting files greatly simplifies the post-processing of solution files. The recomposition of the restart files allows for the capability to perform an alternative decomposition, or the creation of a loads files consistent with the un-split grid (the vulcan.loads.tec file is not currently included in the recomposition process). The recomposed files will reside in the sub-directory Recomp_files. The recomposition process is performed as part of the simulation process whenever the decomposition mapping file (MERGE_MAP.DAT) is present in the current working directory. If the recomposition is not desired, then this file should be removed (or renamed) after the decomposition utility has been executed. Detailed instructions on the use of these utilities are given in the SGLD User Guide.

d) In the directory Perf_codes there is a FORTRAN utility (perf_plot3d) that can be used to extract one-dimensional properties from multi-dimensional dat sets. The paper Extracting One-Dimensional Flow Properties from Multi-Dimensional Data Sets describes the various methodologies incorporated into this utility. The following list highlights the various features of this utility:

Options for performing the one-dimensionalization:
   - area weighting
   - mass-flux weighting
   - conserved-flux average
   - conserved-flux average with Langley distortion methodology
   - conserved-flux average with AFRL distortion methodology
   - conserved-entropy average
Options for providing required flux information:
   - compute fluxes (central differences) from nodal PLOT3D or Tecplot data
   - read flux data output from VULCAN
   - compute integrated fluxes from Fieldview (Conserved-flux average only)
Options for performance data output:
   - impulse function
   - total pressure recovery
   - mass flow rates
   - equivalence ratio
   - mixing efficiency
   - several measures of combustion efficiency
   - several measures of inlet compression efficiency
   - temperature based pattern factor
   - one-dimensionalization of any given output variable
   - one-dimensional representation of the streamwise component of vorticity

A README file is also available in the Perf_codes directory with further details on how to use this utility. An additional README file is available in the Perf_codes/FV_files directory describing the procedure for utilizing the scripts located in this directory to automate the output of flux data when the Fieldview option is desired for providing fluxes to perf_plot3d.

e) In the directory Point there is a C utility that can be used to perform various point calculations involving unit conversions and thermodynamic relations. This utility is driven by a Tcl/Tk graphical user interface named gui.

f) In the directory Profile_codes there are two FORTRAN utilities called propatch and vulcan_prof. propatch takes a VULCAN 3-D profile file and a target grid file, and creates a new 3-D VULCAN profile file by interpolatng the profile data onto a user specified block face of the target grid. vulcan_prof allows one to perform a variety of manipulations to VULCAN profile files as well as extract integrated boundary layer properties. The current options include:

- add (remove) conserved variables
- modify (scale) conserved variables
- coarsen the profile w/out regard to grid spacing
- spline fit the profile to a new grid distribution
- mirror a velocity component in the profile
- split a profile file at a specified index
- convert an axisymmetric profile to a 3-D profile
- compute boundary layer properties

Further details on vulcan_prof are documented in the README file that resides in this directory.

g) In the directory Restart_codes there is a FORTRAN utility called vulcan_rest that can be used to manipulate VULCAN restart files. This utility can also be used extract integrated boundary layer properties at a specified location. The current options that are available include:

- add (remove) conserved variables
- add (remove) grid blocks
- merge region restart files
- modify (scale) conserved variables
- refine (coarsen) restart files in a given coordinate direction
- convert binary restart files to ASCII
- convert ASCII restart files to binary
- convert 2-D restart files to 3-D
- convert calorically perfect restart files to thermally perfect files
- compute boundary layer properties

See the README file in this directory for further information on how to use this utility.

h) In the directory Merge_codes is a FORTRAN utility called time_merge that can be used to merge time history files output by the VULCAN flow solver to simplify the post-processing of time histories. Several options are available to control how the files are to be merged. See the README file in this directory for further information on how to use this utility. The code used by VULCAN to merge the PLOT3D/PLOT2D files produced by the VULCAN post-processor also resides in this directory.