Matrix manipulations. 

 The Monte Carlo generates a file named 'mupdn' which contains the up
 and down matrices.  It is probably useful to rename this file to identify
 the MC input.  It is operated on with the programs described below.
 
 NOTE: Transfer asks for the FULL name of the mupdn input file
 to be typed in and also asks for the extension to be attached to the 
 mdl.XXX, etc. files.  The extension may (likely will) be a three 
 digit number that is sequenced chronologically.  Transfer will also ask
 for a threshold which you may wish to put on the s4xy hits.  If you input
 a number less than 1, it will default to 1.

     Merge        combines files to produce composite matrices, e.g.
                  D and J/psi, if needed.  The routine OR's the Trigger
                  Matrix inputs and ADD's the s4xy inputs.

     Transfer     converts the (renamed) 'mupdn' file to the four
                  individual matrices mdl.XXX, mul.XXX, mu4.XXX, and md4.XXX,
		  which are used below.  It also outputs a trigmat.XXX file
	          which is the concatenated version of mdl.XXX+mdr.XXX+
                  mu4.XXX+md4.XXX matrices where the entries in the s4xy 
                  files (mu4.XXX and md4.XXX) are 0 for no hits and 1 if 
                  there are hits.  The program will prompt for a threshold
	          value to be set on the s4xy hits. 

     Updn         checks the mdl and mul matrices for any overlaps of the up
                  and down tracks.

     Matchk       checks the mdl and mul matrix entries against the wiring
                  pattern of the matrices, currently in TMHARD.866, to ensure
                  that they fit in the matrix module memories.

     Tmfile       converts the matrix entries into the memory
                  contents of the modules, producing the file MATDAT.XXX
                  needed to program the trigger matrices.


 P. Nord has routines that convert the matdat.XXX files into triggers
 that can be loaded into the trigger matrix modules.