Skip to content
Snippets Groups Projects
  1. Oct 07, 2013
  2. Sep 26, 2013
    • Mark Jones's avatar
    • Stephen A. Wood's avatar
      Parameters to optionally correct small ENGINE DC hit handling errors. · 6a33dcf3
      Stephen A. Wood authored
         {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
      6a33dcf3
  3. Aug 21, 2013
  4. Aug 19, 2013
  5. Aug 12, 2013
  6. Aug 08, 2013
  7. Jul 23, 2013
  8. Jul 22, 2013
  9. Jul 17, 2013
  10. Jun 20, 2013
  11. Jun 13, 2013
  12. Jun 11, 2013
  13. Jun 02, 2013
  14. May 30, 2013
  15. May 15, 2013
  16. May 01, 2013
  17. Apr 30, 2013
    • Stephen A. Wood's avatar
      Implement DC Space Point finding · b519f00b
      Stephen A. Wood authored
        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.
      b519f00b
  18. Mar 19, 2013
  19. Mar 08, 2013
    • Stephen A. Wood's avatar
      Add computation of drift distance from drift time. · 58c45eee
      Stephen A. Wood authored
        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
      58c45eee
  20. Jan 21, 2013
    • Stephen A. Wood's avatar
      Drift chamber code work. Modeled on podd and h_trans_dc.f · b1b202d2
      Stephen A. Wood authored
            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.
      b1b202d2
  21. Sep 07, 2012
  22. Aug 23, 2012
  23. Jun 27, 2012
  24. May 01, 2012
  25. Apr 30, 2012
  26. Apr 24, 2012
  27. Apr 23, 2012
  28. Apr 21, 2012
  29. Apr 19, 2012
  30. Apr 18, 2012
  31. Apr 17, 2012
  32. Apr 16, 2012
Loading