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 1st_Code_Improv_Milestone/out directory these 
same file extensions are used and correspond to the same runs as 
this input in this 1st_Code_Improv_Milestone/in directory.


INPUT FILE NAMES AND CONTENTS

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.

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.

FILE EXTENSION MEANINGS

*.nnn means that the number of elements in the model is nnn-3 
(3 boundary condition elements and nnn-3 elements for which the 
simulation computes the behavior). Thus for the files for the 
First Code Improvement milestone run, with the solution being
made on 150000 elements, nnn = 150003. 


DIFFERENCES IN INPUT FILES BETWEEN DIFFERENT RUNS

The only essential differences in the input files for different 
models is in two items:
1) the value of ne (150000 for example) 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.
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 
5000. For one's 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 First Code Improvement 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.