Project

General

Profile

Hall C Commissioning Analysis Meetings » History » Version 17

Richard Trotta, 05/07/2020 04:57 PM

1 6 Richard Trotta
{{>toc}}
2
3 1 Richard Trotta
h1. Hall C Commissioning Analysis Meetings
4
5 2 Richard Trotta
* "BlueJeans Page":https://redmine.jlab.org/projects/kltexp/wiki/BlueJeans_Information
6
* "Hall C Wiki Meetings Page":https://hallcweb.jlab.org/wiki/index.php/Commissioning_analysis_meetings
7 3 Richard Trotta
8 12 Richard Trotta
----
9
10 14 Richard Trotta
h2. *Notes following-up from the Hall C Analysis meeting on 4/30/20*
11
12 17 Richard Trotta
"Mark's slides":https://redmine.jlab.org/attachments/download/991/ReferenceTimeStudy_May2020.pdf
13 15 Richard Trotta
"Steve's slides":
14 14 Richard Trotta
15 15 Richard Trotta
* Mark and Peter's changes
16
** Additional hodohit corrected times method
17
*** Issue is Start Time made no sense and sometimes the code was being too generous for higher rates and therefore lots of trigger accidentals.
18
*** New code: creates new method SetCorrectedTimes which redefines the corrected start times.
19
**** determines time peaks to try and get rid of accidentals that were previously allowed.
20
*** Old code: NTimeSum> 0 (i.e. if any hits then iterate TimeSum)
21
*** New code: NTimeSum> 3 (i.e. if more than 3 hits then iterate TimeSum)
22
**** Note that this will result in more Start Time failures, but fewer accidentals in successful Start Times
23
** Scin plane
24
*** save TDC and ADC ref time for each plane
25
*** changed the matching of ADC hit to TDC hit
26
**** if ADCrawAMP=0, now tests that hit occurred rather than skipping
27
**** assumes time-walk is close to zero
28
*** In the slides, the ADC vs TDC plot shows the structure of the timing
29
**** The width of the TDC is from its 25 ns resolution
30
**** The 3 bands of ADC are from...
31
***** Top: reference time, this may be the cause of weird peaks in SHMS Cherenkov (a rate dependent correction factor may fix this)
32
***** Middle: Mark is not sure of the cause, further investigation required.
33
** Reference time cuts don't need to be changed but should be cleaner to make these cuts
34
*** So may be useful to redo cuts for higher rate runs, but only once we need to check 1% systematics
35
**** Mark suggested using ref time vs coin time to apply ref time cuts
36
*** Peter looking into the effect of changes on ref time  
37
** Peter's pedestal fixes for the ref time (changes from October 2019) will be included in hcana changes.
38
** Mark is pushing as a new branch first to get feedback before pushing to main branch
39 16 Richard Trotta
* Steve Wood looked at the scalers because there has been some issues with very high values being read in from DAQ
40
** It may be some corruption with bits 
41
** BCM ok and no one has complained yet (Although Burcu said she has seen some of these issues)
42
** Coin runs are ok if HMS scalers are used 
43
** He has only scanned a few SIDIS runs
44
** This will need to be fixed for future runs but, for us, he has a few improvements he is testing.
45 14 Richard Trotta
46
----
47
48 9 Richard Trotta
h2. *Notes following-up from the Hall C Analysis meeting on 5/17*
49 3 Richard Trotta
50 10 Richard Trotta
* *Notes from Dave Mack on BCM calibrations*
51
** The bcm constants to use for now are the same one's we're having Eric P load for the F2/EMC Pass 1 analysis at https://github.com/JeffersonLab/hallc-replay-f2xem/blob/master/PARAM/GEN/gscalers.param .
52
** These are from Deb's March results. The March bcm calibration was large and roughly in the middle of the run. You can see the quality of the fits in the ATTACHED.
53
** We haven't done a global analysis yet, nor have I resolved all discrepancies between Deb and Deepak. These values are just a +-2% place-holder since F2/EMC wanted to replay all their runs sooner rather than later.
54
** All the BCMs are linear down to very low currents, so the only things that affects a lumi analysis between 5 and 70 muA are:
55
** the offsets are uncertain to about +-0.1 muA.  (So Carbon Yield vs I can be expected to deviate by O(1)% at 10 muA.) If calibrations are stable, a global analysis will reduce this.
56
** my slight preference would be to use BCM4A for a lumi scan. The only bcm I would NOT use for a lumi scan is BCM4B since it was almost as noisy as the Unser signal. (eg, note the higher Chi2/ndf for this channel in Deb's plots)
57 3 Richard Trotta
58 10 Richard Trotta
* *Notes from Mark on tree variables for tracking efficiency*
59
** The tree variable for the tracking efficiency is H.hod.goodscinhit
60
** For the tracking efficiency calculated in the report file
61 3 Richard Trotta
<pre>
62
HMSScinGood           H.hod.goodscinhit == 1
63
HMSGoodBetanotrk      H.hod.betanotrack > 0.8 && H.hod.betanotrack < 1.3
64
65
66
HMSScinShould         HMSScinGood && HMSGoodBetanotrk && !hmsDCany_large
67
HMSScinShoulde        HMSScinShould && H.cal.etotnorm > 0.6&& H.cal.etotnorm < 2.0&& H.cer.npeSum > 0.5
68
HMSScinShouldh        HMSScinGood && H.cal.etotnorm <0.6&& H.cal.etotnorm>0.0&& H.cer.npeSum < 0.5
69
70
HMSScinDid            HMSScinShould && H.dc.ntrack > 0
71
HMSScinDide           HMSScinShoulde && H.dc.ntrack > 0
72
HMSScinDidh           HMSScinShouldh && H.dc.ntrack > 0
73
74
</pre>
75 10 Richard Trotta
** H.cal.etotnorm  is the ratio of the total calorimeter energy to the central momentum so it does not involve tracking.
76
** H.hod.goodscinhit is set to 1 if certain scintillator criterion are met. This code is in the method THcHodoscope::TrackEffTest
77 13 Richard Trotta
78
----