INTRODUCTION

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


OUTPUT FILE NAMES AND CONTENTS

prk.output.*      step no, time, time stepsize, clocktime, cell w/ max vel, plus other optional data, unit=26
prk.clocktime.*   step no, time, time stepsize, clocktime after selected step numbers to check timing, unit=27
prk.prt.*         print output file with considerable information on run, unit=7 
prk.sum.*         summary output file with less information on run, unit=8 
prk.flt.*         binary file for output of slip velocities, unit=4
prk.crp.*         binary file for output of data at location of creepmeters, unit=9
prk.a.*           binary file for checking distribution of A, unit=20 
prk.amb.*         for checking distribution of A-B, unit=21
prk.tecplot.*     for making tecplot plots, unit=50


OUTPUT 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 that create 
the output 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.