Skip to content
Snippets Groups Projects
  1. Apr 26, 2017
  2. Mar 23, 2017
    • hallc-online's avatar
      Modified THcHallCSpectrometer.cxx and THcHodoscope.cxx · 84bd549e
      hallc-online authored
      The change was made so that NonTrackingDetector could have information
      on the "best" track in their FineProcess method.
      
      In THcHallCSpectrometer::FindVertices the "best" track will be selected
      and the Track object will its SetIndex method to set the index to 0 for
      the best track. The other track will have index=1 or greater.
      
      In the NonTrackingDetector FineProcess, the track that is selected to
      be the "best" can be found by looping through the tracks checking
      track index using Track.GetIndex() for find the track with Index=0.
      
      In  the NonTrackingDetector's CoarseProcess they need to set quantities
      for the Track object needed for selection of "best" track for the
      "prune" and "usingscin" track selection methods.
      
      1) In THcHallCSpectrometer:
        a) Moved selection methods of "best" track from TrackCalc to FindVertices.
        b) Removed setting of Golden Track in the selection methods.
        c) Add setting of Track Index=0 for "best" track in each selection method.
        d) Modified TrackCalc method to loop through Track object and find
           the track with Index=0 and set the Golden Track equal to this Track.
      
      2) In THcHodoscope.cxx
        a) Moved all calculations in FineProcess into CoarseProcess
        b) CoarseProcess calculates the scintillator Beta for each Track
           and does Track->SetBeta.
        c) In determination "zcor" for corrected hits times
            use fBetaNominal instead fBetap from track. Still use Track
            to get distance.
        c) Eliminate fBetap variable which was using the Track momentum
        d) Add variable fBeta which is just from scintillator times.
        e) In FineProcess fill fBeta with the the beta associated
           with the "best" track determined by selecting Track with index=0
      84bd549e
  3. Dec 15, 2016
  4. May 18, 2016
  5. Sep 22, 2015
  6. Mar 02, 2015
    • Stephen A. Wood's avatar
      Track Selection code cleanup · 80368477
      Stephen A. Wood authored
        Enforce variable conventions
        Default using_scin and using_prune selection to off
        Break different track selection methods into different class methods
      80368477
  7. Feb 27, 2015
  8. Feb 23, 2015
  9. Jan 20, 2015
    • Mark Jones's avatar
      Modify THcHallCSpectrometer · 1c3012e5
      Mark Jones authored
          THcHallCSpectrometer inherits from THaSpectrometer which has method
          GetPcentral and a member fPcentral.
           THcHallCSpectrometer had been using fPCentral but decided to
          use fPcentral.
          Delete fPCentral in THcHallCSpectrometer.h
          Replace all fPCentral  by fPcentral in ReadDatabase and FindVertices methods.
      1c3012e5
  10. Jan 16, 2015
  11. Jan 14, 2015
  12. Jan 08, 2015
  13. Dec 22, 2014
  14. Dec 19, 2014
  15. Oct 24, 2014
  16. Oct 04, 2014
  17. Sep 26, 2014
    • Zafar's avatar
      Golden track using prune: · 71e27664
      Zafar authored
            Selection of golden track using prune method is added.
            A bug is also fixed in THcHodoscope class
            Number of pmts hits, focal plane time, good time for plane 4
            and good time for plane 3 are set to the tracks in
            THcHodoscope class.
      71e27664
  18. Sep 21, 2014
  19. Sep 10, 2014
  20. Sep 08, 2014
  21. Aug 30, 2014
  22. Aug 21, 2014
    • Zafar's avatar
      Golden track: · 0854d6f9
      Zafar authored
      Goldent track is moved to THcHallCSpectrometer::TrackCalc()
        if  fSelUsingScin == 0 then golden track is calculated just
        like podd. i.e. it is the first track with minimum chi2/ndf
        with sorting ON
      
        if fSelUsingScin == 1 then golden track is calculetd just like
        engine/HTRACKING/h_select_best_track_using_scin.h. This method
        gives the best track with minimum value of chi2/ndf but with
        additional cuts on the tracks. These cuts are on dedx, beta
        and on energy.
      
        This commit also corrects and modifies the beta code written
        in the THcHodoscope::FineProcess
      
        At this point we have godlend track and in additoion to
        previous vlues the following values are set to a track:
        Energy, beta, chi2 of beta and dedx[track][first hit].
      
      NOTE: For some tracks we have large differences in value of chi
            square between ENGINE and hcana and this is already
            discussed in the last group meeting. Following emails are
            exchanged regarding this difference of chisquare.
      
      email to Mark:
      
      Hi Mark,
      I tried to trace the origin of difference of the chi square value between
      ENGINE and hcana. Please see the attached file, it has long table which I
      cannot present in this email. Or you can see the file at the following
      link, thanks.
      
      https://userweb.jlab.org/~zahmed/chi2diff.txt
      
      Ahmed
      
      Mark's reply:
      Ahmed,
              Thanks. I agree with what you see, but there is also another reason
      for the difference. For the space point in ch2 the engine and hcana
      choose different left/right combinations. That is why you see the large
      jump in the summed chi2 from planes 9 and 10. The two codes pick
      different left/right because there is a cut on the difference between the
      measured stub xp and an expected xp = sp->GetX()/875  and one code has a combination
      slightly below the cut value and the other slightly above. I do not see a way
      to make the codes agree more exactly since the stub fitting involves a matrix
      inversion.
      
                      Cheers,
                             Mark
      0854d6f9
    • Zafar's avatar
      Golden track: · cf4b23b2
      Zafar authored
      Goldent track is moved to THcHallCSpectrometer::TrackCalc()
        if  fSelUsingScin == 0 then golden track is calculated just
        like podd. i.e. it is the first track with minimum chi2/ndf
        with sorting ON
      
        if fSelUsingScin == 1 then golden track is calculetd just like
        engine/HTRACKING/h_select_best_track_using_scin.h. This method
        gives the best track with minimum value of chi2/ndf but with
        additional cuts on the tracks. These cuts are on dedx, beta
        and on energy.
      
        This commit also corrects and modifies the beta code written
        in the THcHodoscope::FineProcess
      
        At this point we have godlend track and in additoion to
        previous vlues the following values are set to a track:
        Energy, beta, chi2 of beta and dedx[track][first hit].
      
      NOTE: For some tracks we have large differences in value of chi
            square between ENGINE and hcana and this is already
            discussed in the last group meeting. Following emails are
            exchanged regarding this difference of chisquare.
      
      email to Mark:
      
      Hi Mark,
      I tried to trace the origin of difference of the chi square value between
      ENGINE and hcana. Please see the attached file, it has long table which I
      cannot present in this email. Or you can see the file at the following
      link, thanks.
      
      https://userweb.jlab.org/~zahmed/chi2diff.txt
      
      Ahmed
      
      Mark's reply:
      Ahmed,
              Thanks. I agree with what you see, but there is also another reason
      for the difference. For the space point in ch2 the engine and hcana
      choose different left/right combinations. That is why you see the large
      jump in the summed chi2 from planes 9 and 10. The two codes pick
      different left/right because there is a cut on the difference between the
      measured stub xp and an expected xp = sp->GetX()/875  and one code has a combination
      slightly below the cut value and the other slightly above. I do not see a way
      to make the codes agree more exactly since the stub fitting involves a matrix
      inversion.
      
                      Cheers,
                             Mark
      cf4b23b2
  23. Aug 20, 2014
  24. Aug 19, 2014
    • Zafar's avatar
      Golden track. · f5da09b2
      Zafar authored
        Goldent track is moved to THcHallCSpectrometer::TrackCalc()
        if  fSelUsingScin == 0 then golden track is calculated just
        like podd. i.e. it is the first track with minimum chi2/ndf
        with sorting ON
      
        if fSelUsingScin == 1 then golden track is calculetd just like
        engine/HTRACKING/h_select_best_track_using_scin.h. This method
        gives the best track with minimum value of chi2/ndf but with
        additional cuts on the tracks. These cuts are on dedx, beta
        and on energy.
      
        This commit also corrects and modifies the beta code written
        in the THcHodoscope::FineProcess
      
        At this point we have godlend track and in additoion to
        previous vlues the following values are set to a track:
        Energy, beta, chi2 of beta and dedx[track][first hit].
      
      NOTE: For some tracks we have large differences in value of chi
            square between ENGINE and hcana and this is already
            discussed in the last group meeting. Following emails are
            exchanged regarding this difference of chisquare.
      
      email to Mark:
      
      Hi Mark,
      I tried to trace the origin of difference of the chi square value between
      ENGINE and hcana. Please see the attached file, it has long table which I
      cannot present in this email. Or you can see the file at the following
      link, thanks.
      
      https://userweb.jlab.org/~zahmed/chi2diff.txt
      
      Ahmed
      
      Mark's reply:
      Ahmed,
              Thanks. I agree with what you see, but there is also another reason
      for the difference. For the space point in ch2 the engine and hcana
      choose different left/right combinations. That is why you see the large
      jump in the summed chi2 from planes 9 and 10. The two codes pick
      different left/right because there is a cut on the difference between the
      measured stub xp and an expected xp = sp->GetX()/875  and one code has a combination
      slightly below the cut value and the other slightly above. I do not see a way
      to make the codes agree more exactly since the stub fitting involves a matrix
      inversion.
      
                      Cheers,
                             Mark
      
      ---------------------------------------------------------------------------------------
      f5da09b2
  25. Aug 18, 2014
  26. Feb 02, 2014
  27. Dec 10, 2013
  28. Nov 01, 2013
  29. Sep 26, 2013
  30. Aug 28, 2013
  31. Aug 21, 2013
  32. Apr 24, 2012
  33. Apr 21, 2012
Loading