INTRODUCTION

This explains the meaning of the different file extensions of
the input files in this directory and of the different types of 
input files. In the BaselineMilestone/out directory these same 
file extensions are used and correspond to the same runs as this 
input in this BaselineMilestone/in directory.


FILE EXTENSION MEANINGS

*.15003 means that the file was used as part of the input 
for the Baseline Milestone run. The 15003 refers to the number 
of elements in the model (3 boundary condition elements and 15000 
elements for which the simulation computes the behavior). This 
uses the multipole library, as is caused by specifying the MMP flag 
in the input prk.input.15003 file to be 1

*.715 means that the file was used as part of the input 
for one of two smaller runs that can be used for comparison for 
validation of one's own runs. The 715 refers to the number 
of elements in the model (3 boundary condition elements and 712 
elements for which the simulation computes the behavior). This 
uses the multipole library, as is caused by specifying the MMP flag 
in the input prk.input.15003 file to be 1

*.715noMP means that the file was used as part of the output 
for one of two smaller runs that can be used for comparison for 
validation of one's own runs. The 715 refers to the number 
of elements in the model (3 boundary condition elements and 712 
elements for which the simulation computes the behavior). This 
uses does not use the multipole library, as is caused by specifying 
the MMP flag in the input prk.input.15003 file to be 0


DIFFERENT FILE TYPES

Four file types are in this directory. If running interactively, only 
the first two files below are needed. The last two files types are 
need if running a batch job. The last one, the script file, may 
have to be modified when running on a different system.

prk.input.*     Primarily a list of file names used for input and 
                 output, but also has other parameters, such as one 
                 determining if the Fast Multipole library is used 
                 for this run or not.

prk.dat.*       Contains data that defines the geometry of the 
                 elements and the assignment of constitutive 
                 parameters to the elements.

run.prk.*       Two lines that would be entered manually if job is 
                 run interactively. The first line is the 
                 relative_path/name for the prk.dat.* file from 
                 the directory in which the job is run. The second 
                 line is the frequency (in time steps) for writing 
                 out a file that gives the clock time at that that 
                 time step.

PBS-script-chapman.*    Script for the PBS system that gives parameters  
                         for doing the run as a batch job.


DIFFERENCES IN INPUT FILES BETWEEN DIFFERENT RUNS

The only essential differences in the input files for these 
different models is in two items:
1) the value of ne (15000 or 712) and of MMP (1 or 0) in the 
   prk.input.* files
2) the nature of the model as defined in the prk.dat.* files. 
   Since this data file defines the model geometry and the number 
   of elements, it can be the same for both the 715 and the 
   715noMp versions, so no prk.dat.715noMP file exists.
There are other differences in the prk.input.* files, namely the 
names of the input and output files are contained therein and 
these differ, just so each run will make its own set of output 
files and will use the correct prk.dat.* file.


HINTS FOR DOING VALIDATION RUNS TO COMPARE OUTPUT FILES

If one wants to validate one's own runs, the number of time 
steps ndt set in the prk.dat.*file could be made smaller than 
500. For the first run just to be sure everything is working 
one can set ndt to 2 for example. 

Making plots of the prk.tecplot.* files can provide a quick way 
to see if one's own output is giving similar results to those in 
the validation suite or even those in the Baseline Milestone run. 
These give the history of the stress, velocity, and displacement 
on two cells. The second Tecplot ZONE does this for the cell with 
the most negative A-B, and the first ZONE does it for the cell at 
that same depth, but at a spot to the North where A-B is positive.