Difference between revisions of "SoLID Ecal Weekly 20230818"
From solidwiki
(→Rate discussion) |
(→Rate discussion) |
||
(10 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
=Rate discussion= | =Rate discussion= | ||
− | *Mike's slides | + | *Mike's slides on MIP shift (integral): [https://solid.jlab.org/wiki/images/6/67/High_Rate_08_17.pdf 08_17] |
− | *Ye's slides | + | *Ye's slides [https://solid.jlab.org/wiki/images/e/ec/081720223_beamtest_update.pdf] on MIP and baseline shift (height), and expected rate of low-energy background in ECal from beam-on-target simulation |
− | *suggest: | + | *suggest for the MIP shift study: |
+ | **Ye can apply beam current cut to get baseline (from "before pulse" window) for intermediate beam current values; | ||
+ | **decompose MIP shift as sum of baseline shift and PMT gain shift. To do so, we need a few plots clearly indicating each component: | ||
+ | #plot total MIP peak integral vs beam current (Mike already has this) | ||
+ | #use 2D peak integral vs. peak height plot, extract a "time factor", let's call it t_trig | ||
+ | #plot baseline vs beam current (Ye already has this but need more current values), expect an exp() function | ||
+ | #multiply baseline (minus pedestal) with "t_trig" then times two (2), plot this vs. beam current; expect an exp() function | ||
+ | #plot MIP height (minus baseline) vs. beam current | ||
+ | #multiply MIP height (minus baseline) from above with t_trig, plot this vs. beam current | ||
+ | #add 4 and 6 from above, do they agree with 1? | ||
+ | #check how much horizontal scaling is needed for the Shower histogram to match the 5 uA run (from Ye) | ||
+ | #does the scaling from 8 resembles the inverse of the values from 3 above? (make a comparison or plot) | ||
+ | #If possible, plot all above vs. background rate instead of beam current (but only if we have a reliable way to get the rate). | ||
+ | |||
+ | *suggest for rate comparison with beam-on-target simulation: | ||
+ | #Can we add a tiny Edep cut, rather than greater than zero? | ||
+ | #Can we possibly get this from random trigger FADC raw signals? | ||
=SPD timing= | =SPD timing= | ||
− | *Carter's slides | + | *[https://solid.jlab.org/wiki/images/0/02/Carter_08182023.pdf Carter's slides] |
*need to add C-D data, perhaps check the timing propagation | *need to add C-D data, perhaps check the timing propagation |
Latest revision as of 00:01, 1 September 2023
Rate discussion
- Mike's slides on MIP shift (integral): 08_17
- Ye's slides [1] on MIP and baseline shift (height), and expected rate of low-energy background in ECal from beam-on-target simulation
- suggest for the MIP shift study:
- Ye can apply beam current cut to get baseline (from "before pulse" window) for intermediate beam current values;
- decompose MIP shift as sum of baseline shift and PMT gain shift. To do so, we need a few plots clearly indicating each component:
- plot total MIP peak integral vs beam current (Mike already has this)
- use 2D peak integral vs. peak height plot, extract a "time factor", let's call it t_trig
- plot baseline vs beam current (Ye already has this but need more current values), expect an exp() function
- multiply baseline (minus pedestal) with "t_trig" then times two (2), plot this vs. beam current; expect an exp() function
- plot MIP height (minus baseline) vs. beam current
- multiply MIP height (minus baseline) from above with t_trig, plot this vs. beam current
- add 4 and 6 from above, do they agree with 1?
- check how much horizontal scaling is needed for the Shower histogram to match the 5 uA run (from Ye)
- does the scaling from 8 resembles the inverse of the values from 3 above? (make a comparison or plot)
- If possible, plot all above vs. background rate instead of beam current (but only if we have a reliable way to get the rate).
- suggest for rate comparison with beam-on-target simulation:
- Can we add a tiny Edep cut, rather than greater than zero?
- Can we possibly get this from random trigger FADC raw signals?
SPD timing
- Carter's slides
- need to add C-D data, perhaps check the timing propagation