INTRODUCTION

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

FILE EXTENSION MEANINGS

*.15003 means that the file was generated as part of the output 
from 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 
was computed using the MMP flag in the input prk.input.15003 file
set equal to 1

*.715 means that the file was generated as part of the output 
from 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 
was computed using the MMP flag in the input prk.input.715 file
set equal to 1

*.715noMP means that the file was generated as part of the output 
from 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 
was computed using the MMP flag in the input prk.input.715noMP 
file set equal to 0

DIFFERENCES IN INPUT FILES BETWEEN DIFFERENT RUNS

The only essential differences in the input files to generate 
these three sets of outputs was 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.
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 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.