THE FHX2 DATA FORMAT

     The FHX2 data format is character-based.  Specific characters are
used to indicate a particular property of the fire history information
contained in the tree rings.  This notation makes use of the seasons of
fire occurrence as denoted by the position of the fire scar within the
annual ring.  If a fire scar is positioned between the latewood of the
previous year and the earlywood of the current year, then the fire most
likely occurred in the dormant season.  The earlywood is divided into
thirds denoted as early earlywood, middle earlywood, and late earlywood.
A fire scar or injury can also occur during the formation of the latewood
as well.  Often, the position of the fire scar can not be determined due
to decay, wood borers that obscure the fire scar, or subsequent fires
that burn off much of the scar surface.
     There are several conventions that make it easy to understand the
logic behind the use of certain symbols.  First, note that a firm pith
date and a firm bark date are denoted by "closed" brackets ([ and ]).
Second, note that inside and outside ring dates that are not pith or bark
dates are denoted by using "curly" brackets ({ and }).  Fire scars are
always denoted by CAPITAL letters, while any other injury, whether or not
it is related to fire, is denoted by lowercase letters.  The season of
the injury denotes which letter: "D" or "d" for dormant season scars and
injuries, "E" and "e" for scars or injuries in the first one-third
portion of the earlywood, etc.
     A "null" year is designated when there is no information about fire
history available for that particular year.  A "null" year can arise due
to three reasons.  First, a tree does not become a recorder of fires
until it has first become damaged by fire or other agents (e.g. rock
falls, blaze marks, or any mechanism that creates an open wound). 
Therefore, any years prior to the tree being scarred should be denoted as
"null" years.  Second, after a tree has become scarred, the outer surface
of the tree containing the fire scars may be so badly damaged or burned
off that the researcher cannot tell if fire scars were ever present on
this particular area of the wood.  In this case, "null" years should be
entered.  Third, "null" years should also be entered if the researcher is
not certain whether a tree is already a recorder tree (having already
been scarred by fire).
     "Recorder" years are the exact opposite.  After the tree has been
scarred by fire, the tree then becomes a recorder tree.  After the
initial fire, "recorder" years should be entered by the user unless the
record of fire scars becomes obscure, as mentioned above.  If the record
becomes obscure, "null" years should be entered until the record once
again becomes clear and "recorder" rings should once again be entered. 
The use of "null" and "recorder" years is necessary because these
designations are important for determining the sample size in any given
year.  "Null" years are not included in the sample size because there is
no information from tree rings available for those years.  If a user
enters recorder years for years when the surface is burned off (meaning
"null" years should be entered), those years will be counted in all
statistical and graphical analyses as being valid recorder years.  Know
your wood.  Keep careful notes on which portions of the sample should be
recorder years and which should be "null" years.
     As an example, let's take a simple case in which we have a tree
with a pith date of 1650, three fire scars at 1685, 1698, and 1716 (all
dormant season scars), and an outside ring of 1730.  When entering the
data for this tree, the user would first enter a right bracket ("[") for
the pith date at 1650.  Because the tree is not a recorder of fires yet,
the user would enter "null" years (".") for the interval 1651 to 1684.
The user would next enter "D" for the year 1685, followed by a series of
recorder years ("|") until the year 1697 because the tree is now
considered a recorder tree.  Once again, a "D" is entered for 1698,
followed by more recorder years until 1715.  A "D" is entered for 1716,
followed by "|" for each year until 1729.  Finally, the outer year, 1730,
is denoted by a right curly bracket ("}").  The Data Entry Module makes
this task fast and relatively easy.
     A special situation arises when a tree that has been injured by
fire (and is therefore considered a recorder tree) grows over the
fire-scar wounds, essentially becoming a non-recorder again until the
next large fire comes along to scar the outer cambium.  For example, a
tree with a pith date of 1383 was scarred by fire in the year 1403 and
the tree became a recorder tree.  The user should therefore enter the
recorder symbol "|" for all years after 1403.  Fires also scarred the
tree in 1410 and 1424.  However, after 1424, the tree quickly healed
itself, growing over the wounds caused by these three fires, and causing
the tree to temporarily have an appearance that it has never been scarred
by fire.  In 1716, the tree is once again severely damaged by fire and
the tree became a recorder of subsequent fires until it died in the early
1900s.  Note that we have four phases regarding the classification of
this tree.  First, the tree was a non-recorder from 1383 to 1402 and the
user would enter null years for this segment.  Second, the tree becomes a
recorder from the period 1404 to 1424 and the user would enter recorder
years for this segment.  Third, the tree then becomes a non-recorder from
1425 to 1715 and the user would once again enter null years for this
segment.  Finally, after 1716, the tree once again becomes a recorder
tree.
     The data portion of each FHX2 data file begins the fire history data
with the words "FHX2 FORMAT" to let the software know this is a legiti-
mate FHX2 fire history data file.  If these words are NOT encountered,
then FHX2 will abort reading the data file.  An error message will alert
the user of the invalid data format.  The succeeding line contains three
numbers: the beginning year of the data file, the number of samples, and
the length of the ID field.  All this information is entered by the user
during data entry.  Each column must also be identified by the ID given
that particular tree.  For example, if the tree in the example above had
an ID of CBE01, then the five characters in the ID would precede the fire
history information in the column beginning with the year 1650.  The rest
of the data file takes the form of a matrix.  The number of samples per
site determines the number of columns per file, while the number of years
represented by a site is the number of rows. Therefore, all the informa-
tion we entered for the example above would be stored in one column
beginning with the year 1650.
     The FHX2 system can analyze two general sizes of data matrices, a
long set (from 500 BC) and a short set (from AD 1200).  All data matrices
must end prior to the year 2006.  The beginning year of -500 allows the
user to enter fire history information from such long-lived trees as
giant sequoia.  Sequoias collected for  fire history analyses are
generally less than 2,000 years of age, so the limit of -500 will allow
data entry of most fire history series.  The ending year of 2005 is
simply set to ensure the usefulness of the FHX2 system well into the next
century, though upgrades will be released in the future.  All Modules in
the FHX2 system can analyze matrices that range between one to 254 series.

THE DATA YOU'LL NEED

     In the analysis of fire history from tree rings, the information
obtained should be recorded on a standard form to help facilitate data
entry.  The exact information recorded on each form will depend on the
research objective and the locations of the study sites, but there are
certain aspects that should be recorded for all samples.  The form should
have space where the user can enter the site name, the site abbreviation,
the date of collection, and the name of the collectors.  This may seem
trivial to record on all forms from one site, but we have found it is
better to have excess information than not enough.  The form should
contain lines that contain the sample ID, the beginning year, the type of
beginning year (pith or innermost ring), the outside year, and the type
of outer year (bark or outermost dated ring).  The species should also be
recorded using the standard four-letter species code developed by the
International Tree-Ring Data Bank.  After all this header information,
the form should be divided into lines that contain the year of the fire
or injury, the type of injury (fire scar or other injury), the season of
the fire scar/injury, and the clarity of the fire event within the ring.
Additional information for each fire event year can also be entered on
this form, including:

1. whether excess resin ducts are present in the ring (indicating an
   injury);

2. whether the injury was associated with a subsequent growth release or
   growth suppression;

3. whether abnormal ring growth had occurred (e.g. "expanded latewood"
   common in giant sequoia during fire years) during or after the year of
   injury;

4. the estimated length of the scar in centimeters or expressed as a
   percentage of the circumference;

5. the side of the tree on which the fire scar or injury occurred;

6. any additional comments that may be useful for interpreting fire
   history.

Note that sometimes an inner date for a sample can be a fire-scar date.
This sometimes occurs when a section is removed from a tree, living or
dead, and the inner portion of the sample breaks along a weakness in the
xylem caused by a past fire.  Usually these inner scars are quite obvious
and the exact determination of their year of occurrence can be confirmed
by fire-scar dates from other samples, as discussed previously.

SETTING UP A NEW MATRIX

     To set up a new matrix, you need four pieces of information
regarding the matrix.  First, the user needs the earliest tree ring date
represented by any of the samples.  Second, the user needs the latest
year of any sample.  Third, the user needs to know the number of samples
to be entered.  Finally, the user needs to know how many characters to
specify for the ID's.  When these four items are recorded, the user is
ready to enter information by selecting "1" to begin setting up the data
matrix.
     After pressing "1", a new menu opens.  This menu contains options
to "Set up a new matrix," "Import an old matrix," and "Change matrix
settings."  Choose to set up a new matrix, either by pressing "S", or by
clicking on that line once with the left mouse button.  Another menu will
drop down that contains four lines for the four items to be entered, as
well as the default settings used by the system.  Begin by telling the
FHX2 system the very first year represented by any sample at your site.
Do the same for the very last year represented by your site.  Then enter
the number of samples to be entered into the matrix.  Finally, enter the
length (number of characters) of the sample ID's.  Note that you must
enter the number of samples or else the matrix will not be considered set
up yet.  Using the example shown in Figure 1, we would have entered the
following information in this first step: First Year of Matrix: 1810;
Last Year of Matrix: 1994; Number of Samples: 9; ID Length: 5.  After the
information has been entered, hit "Q" or the ESC key to exit back to the
previous menu.  Also close this next menu to put you back at the Main
Menu.  The lines in Step One will now show the settings input by the
user, and you're now ready to move on to Step Two.

IMPORTING AN OLD MATRIX

     The user can import any data file in FHX2 format entered from a
previous data entry session.  The user may then finish adding the
remainder of the samples, or add a new sample.  A matrix may be imported
when a user wishes to update new information to samples already entered.
To import a matrix, type "I" from the menu and type in the name of the
data file to be imported.  Remember to include the complete DOS path if
the file exists in a directory other than the one currently logged into.
Once the data have been imported, the parameter information is listed
below Step One and the program informs the user that the data was
imported.  The data are now ready to be re-edited, or new data input.

CHANGING MATRIX SETTINGS

     After importing or setting up a new matrix, the user may wish to
change one or more of the four matrix settings (i.e., first or last year
of matrix, number of samples, or ID length).  Note that, if the user
tries to enter a sample and this sample will exceed the number of samples
currently specified, the program will alert the user to first change the
matrix settings to include the new sample (i.e. increase the sample size
by one).  Likewise, if the user tries to enter a beginning year for a
sample that precedes the currently specified beginning year of the
matrix, the software will alert the user to change the beginning year of
the matrix first.  This is necessary because the software must first
initialize the new cells that will contain the fire history information
within the matrix.  To change any of the currently specified matrix
settings, simply choose "C" from the Step One menu and select which
setting you wish to change.  Once you return to the Main Menu, the new
settings will be listed in the lines below Step One.

OUTPUT FILE NAME

     After selecting "2" from the Main Menu, the user must specify an
output file name in the dialog box that pops up.  Remember to include the
full DOS path if you have not specified the path in the Workspace.  If
you wish to create the file in the current subdirectory, just give a file
name without a path preceding it.  You should note that if a file name is
specified and the file already exists, the FHX2 system will assume you
wish to overwrite the old file when you save the data in Step Six.  No
data is overwritten until the user saves the data in the final step.  If
you are unsure whether the file exists or not, simply exit to the DOS
shell and inspect the current directory.  Keep backup copies of all your
data!  The user can actually specify the output file name in Step Two
prior to reading the data in Step One, and the file names in both steps
can actually be the same.  However, it is good practice to keep the file
names unique unless the user wishes to update a file already created in a
previous session.

ENTERING FIRE HISTORY DATA

     At this point, the user should have all the fire history
information sheets for each sample in front of them in the order the user
wishes to enter the data.  After selecting "3" from the Main Menu, a
dialog box will open, and the user should enter the ID as shown on the
sample form.  The length in characters of the ID had already been
specified in Step One above, and the program will not accept lengths
greater than the length specified.  If the length entered by the user is
shorter than the length specified, the remainder of the ID is filled with
spaces.  If the user enters a sample ID and the program determines this
will exceed the data matrix limits specified in Step One, the program
will not accept the new entry and will remind the user to change the
matrix settings prior to additional data entry.
     The user should then enter the beginning year for that particular
sample.  Do not worry about entering what type of beginning year it is
(pith or innermost ring).  This will be specified in the next step.
Remember that the user can not enter years that are outside the range of
the beginning and ending years as specified in Step One.
     The program is now ready to have fire history data entered.  Note
that the user does not need to enter all information on the form.  You
will need:

1. the type of the innermost ring date (pith or innermost ring);

2. the type of the outermost ring date (bark or outermost ring);

3. the year of the fire scar or injury;

4. the type of injury (fire scar or other injury);

5. the season of the injury determined from the intra-annual position of
   the injury within the tree ring;

6. which segments of the sample should be null years or recorder years.

Remember that seasonal information for a fire scar is always represented
by capital letters while all other injuries are designated by lowercase
letters.  The information on the form should contain this seasonal
designation.  If the seasonal designation for any scar or injury could
not be determined, the user should enter either "U" for fire scars, or
"u" for other injuries.  Because data entry is a keyboard process, the
mouse becomes temporarily de-activated.
     The next screen is divided into two areas.  The right half contains
a list of all the character symbols the user will need to enter the fire
history information, along with their explanation.  The left half of the
screen is the actual data entry window.  This window is divided into
three columns: a year column, a column containing the old symbol, and a
column that will contain the new symbol.  A cursor will appear, and the
program will place the user in the third column at the first year entered
in Step Four for this particular sample.  The sample ID is also listed at
the top of the window as a reminder.  In the second column is the present
symbol associated for that year.  At this point, the user should enter
the appropriate symbol.  For example, if this is the beginning year, the
user should type in either a left bracket (pith data) or left curly
bracket (innermost ring date).  After entering the symbol, the program
will advance to the next year, and the user should continue entering the
appropriate symbol.
     Some additional symbols are listed in the right portion of the
screen that the user may recognize as not being symbols used in fire
history analyses.  These are: the plus sign (+), the up arrow ( ), the
minus sign (-), the down arrow ( ), and the letter "F".  These are used
to facilitate movement around the data entry window.  If the user wishes
to advance one year and keep the symbol for that year represented in the
"Old Symbol" column, then the user can press the "+" key or the down
arrow.  If the user wishes to back up one year at a time, perhaps to
correct a mistake, the user can press the "-" key or the up arrow.  The
"F" key is a special function used to save time during data entry.  "F"
stands for "Fill next 50 years."  While entering data, the user notices
the next 200 years are null years.  Rather than pressing the null symbol
(".") 200 times, the user can enter the null symbol once and then press
"F" on the next year.  This will enter, or "fill," the next 50 years with
the null symbol.  Pressing "F" three more times will quickly enter the
null symbol for all 200 years in just a fraction of a second.  If certain
years interspersed in these 200 years are not null years, the user can go
back to those years in Step Four, enter the appropriate year, return to
Step Five, and enter the appropriate symbol.  The program will "fill" the
series with the last symbol entered.  It is up to the user to make sure
that the "fill" symbol is accurate, although a mistake using this
function can easily be corrected.
     Once all data have been entered for the entire series, the user
should hit "Q" to stop the data entry process.  At this point, the user
will be placed back in the Main Menu of the Data Entry Module.  It is
good practice to review the data that have been entered.  Go back to Step
Four, and enter the beginning year for the sample for which data had just
been entered.  Exit back to the Main Menu, and begin Step Five.  Using
the plus key or the down arrow, advance one year at a time, checking the
symbols that were entered.  This may seem unnecessary at first, but
mistakes may be found.  The data entered should always be checked by the
principal investigator as well.  If the data entered are correct, then
the user can return to the Main Menu.

ENTERING SITE INFORMATION

     The final step in completing the fire history data file is the entry
of the requisite site information.  Prior to data entry, the researcher
should have the following information at hand, preferably entered on a
worksheet to facilitate entry: Name of Site, Site Code, Country, State,
County, National Park or Monument, National Forest, Ranger District, Town-
ship, Range, Section, Quarter Section, UTM East and North Coordinates,
Latitude, Longitude, Topographic Map Name, Lowest Elevation, Highest Ele-
vation, Collection date, Collectors, Crossdaters, Substrate Type, Total
Number of Samples, Latin Name for Species, Common Name for Species, Slope,
Aspect, and Total Area Sampled.  Note that the completion of this step
is optional - all data files will be readable without this information,
although we STRONGLY urge you to enter this necessary site information.
     The Data Entry Module will guide the user through each of the
fields that need to be entered.  If no information is available for a
particular field, the user should simply hit "return."  The maximum number
of characters allowed per field is also indicated to help guide the user.
All information remains in the memory buffer until the user exits the
Data Entry Module.  This means that the user can return to Step Six and
enter or correct previous information.
     If a file is imported using the Data Entry Module, all site informa-
tion is read as well as the fire history data.  If the user wishes,
comments may be added to the data file after the site information but
before the line that begins with "FHX2 FORMAT".  As many comment lines
as are necessary can be added - all modules will simply ignore these
lines.  They are strictly for data management purposes only and have no
influence on the FHX2 system.

SAVING YOUR DATA FILE

     After data have been entered, the user should always save the
matrix after each sample entered.  This is a good habit because a sudden
loss of power, for whatever reason, will cause the user to lose all data
entered if it has not been saved to the hard disk.  Never enter sample
after sample without saving the samples first.  A line will appear next
to the Step Six line reminding the user that new data have been entered,
or old data have been changed, and that these data need to be saved
immediately.  Whenever any cell in the matrix has been altered from its
previous symbol, the line will appear saying "Data need to be saved."
Pressing "7" at this point will save the current data matrix to the hard
disk, and the reminder will disappear.  At this point, the program is now
ready for the user to enter fire history information for the next sample.
     If the user tries to exit the Data Entry Module without first
saving the data, the program will alert the user that the data have not
been saved, and ask whether or not to exit the program.  If the user does
not choose to save the data, all changes made to cells in the matrix will
be lost.  This feature may be convenient if the user decides to abort the
data entry process for one reason or another.  Simply exit without saving
the data.  If the user tries to save the data without first specifying an
output file, the program will alert the user to first enter an output
file name prior to saving the data.

DATA ENTRY UTILITIES

     "Show Series" does exactly that.  By selecting "S" from this menu,
a new window will open in the upper righthand corner of the screen
showing the sample ID's in the order they were been entered.  Each series
ID will have a number beside it to the left indicating its column
position in the data matrix.  The window will only display 19 sample ID's
at a time.  The next 19 ID's can be viewed by hitting the "return" key,
or by clicking the left mouse button.  The user can close the window at
any time by hitting the ESC key, or by clicking the right mouse button.
This function is particularly useful because the user will need to know
the position of the sample within the matrix before any information can
be changed.

Inserting Series:
     If the user wishes to insert a sample between two series that have
already been entered, the user should select "I" from this menu.  The
user should have already determined in which column the new sample should
be inserted by using the "Show Series" function described above.  A
dialog box will open asking the user in which column to place the new
sample.  After specifying in which column the sample should be inserted,
the program will then increase by one column position all the succeeding
series.  For example, if you specify column four to insert a series, and
the data file already contains five series, the data for the sample
already in column five will first be placed in column six, then the data
for sample four will be placed in column five.  All cells for column four
will be initialized by the software, and the Module is now ready for you
to enter the information for the inserted series.  Note that, at this
point, the sample ID has been set by default to be all X's (e.g. "XXXXX"
for an ID length of five).  This should be changed in the next function.
Also note that if the user tries to insert a series and the total number
of series exceeds that specified in Step One, the software will alert the
user to first change the matrix settings prior to inserting a new series.

Renaming series:
     To rename a series, select "R" from the menu.  A dialog box will
open asking the user for the number of the sample to be renamed.  The
number corresponds to the column occupied by that sample in the matrix
obtained by showing the series.  In the example above, the user needs to
change the sample ID from the default given by the software.  The user
would enter "4" when asked which sample to rename.  At this point, the
dialog box will list the old sample ID, and ask the user to enter the new
sample ID.  After entering the new ID, the user can check to see its
correct placement by showing the series.  The same rules for sample ID's
regarding their length as described previously applies to the entry of
ID's in this function.

Deleting series:
     To delete one or more series from a matrix, select "L" from the
menu.  A dialog box will open asking the user for the number of the first
series to be deleted, as well as the number of the last series to be
deleted.  As with renaming series, the number is simply the column
positions of the samples to be deleted, which can be obtained by using
the function to show the series described above.  Once the column number
for both the beginning and ending series to be deleted have been entered,
the software will decrease all succeeding samples by one column.  For
example, if the user selects to delete the one series inserted in the
example above, the user should enter column "4" for both the beginning
series and ending series to delete.  The data for the sample in column
five will first be copied to the cells in column four, and the data in
column six will be copied to the cells in column five.  The sample ID's
will, of course, follow the data as well.  If a range of series is
specified to be deleted, all series within and inclusive of the columns
specified by the user will be deleted.  Note that deleting a series de-
stroys the data in the column because it must be overwritten by the
succeeding series.  There is no way to retrieve a column (sample) once
the sample has been deleted and the file has been saved.  If you have
deleted a series, and you realize it should not have been deleted, the
user should exit the data entry procedure for this matrix without saving.
Remember that the original data file is not overwritten until the user
chooses to save the data in Step Five.

Moving series:
     To move a series, select "M" from the Step Three menu.  A dialog
box will open that asks the user which series to move.  As before, the
number to be entered is the column number of the series obtained from the
function to show the series described above.  The program will then ask
the user to enter which column to move the series to.  Once the user has
entered this information, the program must rearrange the matrix.  It does
so by first copying the column to be overwritten by the move to a
temporary buffer.  The column to be moved is then placed in the vacated
column, and the program then proceeds using the same functions to either
increase or decrease the columns, depending on whether the move is "up"
or "down."  Sample ID's always accompany the data as well.  The move and
subsequent rearrangement of the new matrix can be verified by once again
using the "Show Series" function.

Sorting series:
     Sorting the series is one of the most powerful tools for analyzing
past spatial and temporal patterns in fire history data sets, and the
investigator should try several of these options to gain a better
understanding of factors influencing fire regimes.  For example, by
sorting the data set on the year of the first fire scar of each series,
the researcher may observe which fires were particularly severe to scar
the majority of trees, and possibly causing changes in age structures.
Sorting the entire data set by the first year of each series may help the
investigator isolate which fire year caused an increase in establishment.
     To begin, select "O" from the Utilities Menu.  A new window will
open showing the eight available options for sorting the data.  These
options include sorting by: (1) inside beginning year for the samples;
(2) outside ending year; (3) inside first fire scar for the samples; and
(4) outside last fire scar.  Note that the sort order can be either
ascending or descending, giving the full eight options.  The user may
also sort by sample identification.  When sorting on fire scars, other
indicators are ignored.  Example ranges are displayed to help the
researcher envision the final order in which the series will be sorted.
(These ranges are just examples, and do not reflect the ranges in the
actual data set.)  Remember that when the data are saved in Step Seven,
the original data set will be overwritten unless the user has supplied
a new file name.

Merging data files:
     An important feature of the Data Entry Module is its ability to
merge one or more matrices into one larger matrix.  For example, the user
may wish to combine the fire history information from two sites into one
site because the sites are essentially homogeneous and close to each
other.  Or, the user may wish to perform statistical tests to determine
whether the fire regime at one site is statistically different from the
fire regime at another site.  Using this feature will allow the user to
merge one or more matrices into one larger matrix.  To merge two
matrices, select the "Merge Matrices" Option from the Utilities Menu by
typing "M", or by clicking the left mouse button on that line.  A new
menu will drop down containing three lines which the user must first
enter.  The user should enter the file name of the first matrix to be
merged, then the file name of the second matrix to be merged.  Note that
the first matrix will occupy the columns to the left of the second
matrix.  Next, the user should specify the file name that will contain
the merged fire history information.  Note here that the output file name
must not be the same as either of the first two files names because all
three files must essentially be open at once, and no software can read
and write to two files with the same file name at the same time.  Because
both files contain site information, the user must select from which data
file to extract and save the information to the new merged file. Finally,
selecting "M" from this menu will merge the two files.  The user will be
notified when the merging process is complete (usually this is a very
fast operation).
     The user can easily merge three or more matrices as well.  The
first two matrices should be merged according to the methods described
above.  The output file containing the two merged data files should then
be input as the First Matrix to be merged in the next step.  The third
matrix to be merged should be entered on the line for the Second Matrix.
This process can be repeated until all matrices have been merged into one
data file.  Note that more than 255 samples can be merged into one data
file, but the FHX2 software will only read the first 255 samples.  During
the merging process, the software will determine which beginning year to
use based on the earliest of the two beginning years from the two
matrices.  The same process will determine the last year of the matrix.
The sample ID length will be the longer of the two ID lengths specified
on the second line of each data file.
     The user can also merge one or more data files and actually
separate these sites for greater visibility when graphing the
information.  For example, the user may wish to merge two data files from
nearby sites, but maintain some separation between them for visual
purposes.  The data files should first be merged according to the
processes described above.  The user should then ESC back to the "Step 1"
Menu and increase the size of the matrix by one sample.  (From this point
onward, the discussion concerns functions described in later sections and
the user should refer to those sections for more details on their
operation.)  To continue, the user should then ESC back to the Utilities
Menu.  Here, the user should first "Show" the series and note the column
numbers of the last sample in the first data file and the first column of
the second data file.  The user should then choose "Insert" and enter the
column number after the last sample in the first data file.  Finally, the
user should "Rename" the sample with all spaces to prevent the printing
of anything where ID's are normally drawn in the Graphics Module.
     The separation between the two data files can either be blank or a
line.  To keep the separation blank, the user does not need to do
anything more.  To ensure a line is drawn between the two sites, the user
can enter "Step 5" and enter nothing but the recorder symbol ("|") for
all years from the beginning of the data file to the end for the inserted
sample.  Note, however, that this particular data file should not be used
in statistical analyses because the inserted "sample," with its recorder
years, would be considered a valid sample and be included in all
determinations of sample sizes and percentage scarred classes.  This
option is strictly for graphics purposes only.  The user can
alternatively choose to draw Custom Lines using that particular function
in the Graphics Module rather than adding a fictitious sample to a data
file.
