In tree they are called tnhit and trawhit.
Created two new variables for THcDriftChamber, fNthits and fN_True_RawHits.
In tree they are called tnhit and trawhit.
THcDC defined subdetector THcDriftChamber to have name Ch1 and Ch2 to do used in the tree.
THcDriftChamberPlane defined new method GetNRawhits to return fNRawhits for each plane.
Added member fNRawhits to THcDriftChamberPlane

  Fix from Mark Jones with additional cleanup for
  saw's misunderstanding of space point criterion

  Compare wire coordinate, not wire number

  THcDriftChamber::AddPlane didn't know if style was HMS, because
  style was only determined in Init.  Now fHMSStyleFlag is set in
  only one place.  Right now determined from spectrometer name, but
  could be a parameter in the future.

Modified ReadDatabase : Added fdebugstubchisq and Corrected fhdebugflagpr to be Int
Added PrintDecode( void ) to print the drift chamber info in fHits
Modified FindSpacePoints to use the proper PlaneInd and PlanePInd
    for HMS and SOS style chambers
Changed THcDriftChamber::FindEasySpacePoint(Int_t yplane_hitind,Int_t yplanep_hitind) to
THcDriftChamber::FindEasySpacePoint_HMS(Int_t yplane_hitind,Int_t yplanep_hitind)
Added  THcDriftChamber::FindEasySpacePoint_SOS(Int_t xplane_hitind,Int_t xplanep_hitind)
commented out many fhdebugflagpr  output statements

Should compare (pindex1%2), not pindex1, to determine evenness.

  THcDriftChamber
    New flag fHMSStyleChambers to determine if HMS or SOS style
    tracking should be done.  Flag is set on if the spectrometer
    name begins with 'h'.
    THcDriftChamber::LeftRight fSmallAngleApprox must be set and
    fHMSStyleChambers must be off to do SOS style.
    If not HMS style, ignore all the Yplane optimizations
  THcDC
    SOS code does "project to chamber" in link stubs.  Need to evaluate
    if this is necessary, or if HMS style should also do it.

   {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

1.  nplusminus was not initialized corectly so small angle approximation
was never used.
2.  Change MAXTRACKS from 50 to 10 to match ENGINE.

Since we have not yet overwritten the = operator for space points
had to add code to do this.

Set fDebugDriftCh in DefineVariables
Put if fDebugDriftCh in front of all cout statements
In THcDriftChamber::DestroyPoorSpacePoints replace line (*fSpacePoints)[isp] = (*fSpacePoints)[osp];
In THcDriftChamber::SelectSpacePoints() replace line (*fSpacePoints)[sp_count] = (*fSpacePoints)[isp];

   for first hit. Added an else branch to increase finalnum
2)  In THcDriftChamber::LeftRight() when using the small angle
    approximation then assignment of sign to the y planes was reversed.

  Compiles and doesn't crash.

  THcDriftChamber::SpacePoint -> THcSpacePoint
  That way space points can be put in a TClonesArray and be made known
  to THcDC when stub information is added.

  1)   Moved hardcoding of Yplane plane number to Addplane since it is called
     before ReadDatabase
  2) In FindEasySpacePoint add variable max_dist to match the code in
     h_find_easy_space_point.f more and fix problem
  3) As in h_find_easy_space_point  use max_dist instead
     of FSpacePointCriterion in IF statement to pick matching "x" hits.
In THCDC.h
  1) Set GetPicth and GetCentralWire as Double_t
  2) Set  GetSpacePointCriterion to return fSpace_Point_Criterion2[chamber-1]
     instead of sqrt

In the ENGINE, this can happen if a hit belongs to more than one space point.

  New class THcDC is whole set of wire chambers.
  THcDriftChamber is one chamber (6 planes)
  Implement space point finding from h_pattern_recognition up to point
     before where space point lists from the two chambers are combined.
  Includes
      FindEasySpacePoint   (h_find_easy_space_point)
      FindHardSpacePoints  (find_space_points)
      DestroyPoorSpacePoints (h_sp_destroy)
      SpacePointMultiwire  (h_sp_multiwire)
      ChooseSingleHit 	   (h_choose_single_hit)
      SelectSpacePoint	   (select_space_points)

Space points are arrays of structures in the THcDriftChamber class.  Will
probably need to take space points out class so that they can be looked at
at the THcDC level.

New code is only tested to see that it compiles and that space points
are sometimes found.

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

      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.

be made either in output.def or by analyzing root tree.

TClonesArray ConstructedAt method.

Raw hit class for drift chambers and skeleton drift chamber that prints
out drift chamber package hits.

Move Compare method from THcHodoscopeHit to ThcRawHit since it should
work for any derived class.

Get detector name -> ID mapping from the map file comments

THcHodoscope, a multiplane scintillator array.  Make a Hall
C style spectrometer (so that default Hall A detectors are not
included.)  Can read a Hall C data file and print out hodoscope hits
where the left/right TDC/ADC are matched up per counter.