general.param - include SOS parameter for most devices
  hcana.param - add sos versions of previous hardwired parameters
  db_run.dat - put in an angle and mometum for SOS
  output.def - include sos detectors in root tree
  hodtest.C - Add SOS spectrometer and some of its detectors

just for test purpose.

   {prefix}dc_fix_lr
        Historically, in the ENGINE, if a hit is used in multiple
        space points/stubs, the left/right assignment for that hit, which
        is later used in track fitting, is that assigned for the last stub
        encountered with that hit.  Properly, the left right assignment
        should be allowed to be different in different space points.  If
        this parameter is set to zero (e.g. in hcana.param), then the
        ENGINE behavior is used.  For new analyses, it should be set to one.
        (Which is the default)
   {prefix}dc_fix_propcorr
        When a hit gets put into a stub, the distance of the hit from the
        discriminator can then be estimated.  In the engine, a correction to
        the drift time (and thus drift distance) is applied.  However, if
        that hit ends up in another stub, the correction will get applied again,
        resulting in a over correction.  Setting this flag to 1 will give that
        hit a different corection for each stub that it is in.

These flags will default to the new "correct" way of handling hits if
the above parameters are not set in a parameter file.  Currently, both
flags are set to zero in hcana.param to replicate the ENGINE behavior.

To implement these changes, the propagation correction and L/R information
for each hit is saved in space point and track classes.  This information
is still saved in the hit class, but only used if in ENGINE compatibility
mode.

The THcDCTrack class now saves a list of space point pointers instead
of space point indices.

The AddSpacePoint method now also copies all the hit information into
the track object so that THcDC doesn't need to explicitely copy all
the hits.

The FindStub method, which fits a stub track to a space point is passed
the space point rather than a list of hits

  Name of coefficient file in hcana.param
  Some basic hms setting parameters added to test.database for run 50017
  Traceback code in THcHalCSpectrometer

GN: finished debugging the hodoscope start time calculation. Results match 1-to-1 the corresponding "engine" result.

Started with Simon's code, but reworked:
	Use podd style arrays in RVarDef.
	Get plane names (1pr, 2ta, 3ta, 4ta) from parameter file.
	Get block counts from parameters instead of hardwiring.
	Rename histogram names to be A,B,C,D 1-13, instead of 1-52

of hardwiring them.

  It has not been check that we are getting a good start time yet.
  Drift time and distance added to tree
  Change DC plane names from 1, 2, 3, ... to 1x1, 1y1, ...
    This is so that the parameters holding the time to distance maps
       can be found.  (The parameters are e.g. hwc1x1fract)
    Need to find a way not to have to hard code these plane names.
       Either use wire angles (alpha) or some kind of parameter name mapping
  Changed output.def to match new plane names

    Define constants (e.g. plane counts) that are not defined in
    the ENGINE parameter files so that the detector classes
    can be more generic.
    Hodoscope and Aerogel now pick up plane and tube counts from this file

      Start adding to the drift chamber code.   Setup a class structure
      similar to what podd uses for the VDCs.  Raw hit class renamed
      to THcRawDCHit.  Signal hits are how THcDCHit, modeled after
      podd hits.  Add THcDCWire, and classes for time to distance conversion.
      Time to distnace conversion doesn't do anything yet.

      Find some improved DC parameter files so that min and max TDC limits
      are good for the run we are using.

      THcDriftChamberPlane asks ThcDriftChamber for many parameters.

detector parameters from the gHcParms (THcParmList).