One of the goals is to minimize size of the code used, so
by design Stntuple is mostly independent on other packages and
can be used in standalone mode when running on STNTUPLE data
files

- all the initializations - interface to CDF offline is happening
  in the Stntuple/mod code
- library libStntuple_obj.so depends only on ROOT, can be loaded into
  ROOT session
- library libStntuple_alg.so depends only on libStntuple_obj.so, so
  can be loaded at run-time after it.
- some offline constant include files are used to build 
  libStntuple_obj.so and libStntuple_alg.so, these files do not introduce 
  any physical dependencies on offline classes

  CalorGeometry/CalConstants.hh
  CalorGeometry/CalParameters.hh
  Muon/Muon/CmuGeometry.hh
  inc/misc.hh



Streamers: the key issue - compression of the data and I/O performance, looks like
it can be done extremely fast.

calorimeter - 9 different tower types

type0: 
       cem[2], 
       cha[2], 
       strip and crack - commented out
       cha_time (all shorts)

type1: 
       cem[2]
       cha[2]
       wha[2]
       strip and crack - commented out
       cha_time
       wha_time
type2:
       cem[2]
       wha[2]
       strip and crack commented out
       wha_time
type3:
	pem[2]
	wha[2]
	ppr[2]
	wha_time
type4:
	pem[2]
	pha[2]
	wha[2]
	ppr[2]
	wha_time
	pha_time
type5:
	pem
	pha
	ppr
	pha_time
type6:
	pem
	pha
	ppr
	pha_time
type7:
	pem
	pha
	ppr
	mip[2]
	pha_time
type8:
	mip[2]