             The STARFISH Parallel file-system simulator
       (Simulation Tool for Advanced Research in File Systems)

                              David Kotz
                          Dartmouth College
                             Version 3.0
                             October 1996
                         dfk@cs.dartmouth.edu
    
I use this directory for running tests and analyzing data.

I generate a set of interesting configurations, which are defined by
the parameters in the *.param include files.  Each configuration
requires a directory to hold the *.param files and the resulting
compiled version of proteus.  These configuration directories are in
subdirectories of this directory, mostly in configs/ and luconfigs.
Each config subdirectory eventually contains a 'results' subdirectory,
after the experiments have been run, with two files for each run:
*.out containing the stdout/stderr of proteus while it ran, and *.sim
containing the binary dump of metrics and events produced by proteus.
Analysis scripts tend to generate several more derived files from the
*.sim files (*.data, *.avg, *.imp, etc). 

There are several subdirectories here:
	bin/		scripts for generating configurations, running
			tests, and analyzing data

	base/		the base parameter set for generating configs
	lubase/		the base parameter set for generating luconfigs

	configs/	configurations used for basic tests
	luconfigs/	configurations used for LU-decomposition tests

	pats/		lists of patterns used for suite-all
	
	exact-vs-model/	comparing proteus exact network simulation
			with proteus modeled network simulation

Some interesting files include
s.*   - 'suite' files, ie, simple scripts that run through a suite of tests

set.* -  'set' files, which list sets of configs that are used when
	doing certain analyses.  Used as a csh parameter, eg, `cat set.basic`

shapes- what are the specific matrix shapes we used


