Difference between revisions of "July14, 2016 Calorimeter"

From GlueXWiki
Jump to: navigation, search
(Minutes)
Line 57: Line 57:
 
#* Schedule of analysis reports:  [https://mailman.jlab.org/pipermail/halld-physics/2016-June/000698.html e-mail] from Paul Mattione
 
#* Schedule of analysis reports:  [https://mailman.jlab.org/pipermail/halld-physics/2016-June/000698.html e-mail] from Paul Mattione
 
# FCAL update
 
# FCAL update
#* [https://logbooks.jlab.org/files/2016/07/3413081/FCAL%20Efficiency%20Studies%207.14.compressed.pdf Efficiency Studies (from July 12 Analysis Meeting)]
+
## Hardware update
#*[https://logbooks.jlab.org/files/2016/07/3413092/pi0s_FCAL.pdf FCAL Gain Calibration Survey] Adesh Subedi
+
##* Test setup for Fcal bases is operational at JLab. Chris is learning on how to test and fix bases. There is a Linux computer with software to communicate with the bases.
 +
##* Paul has found that there are four resistors on the mult board that seem to be the source of HV problems. Replacing them should fix those problems.
 +
##* Paul is providing documentation on the fixes and is transferring the information to Chris.
 +
##* Start by fixing dividers with problems seen both on the detector and on the test setup.
 +
## [https://logbooks.jlab.org/files/2016/07/3413081/FCAL%20Efficiency%20Studies%207.14.compressed.pdf Efficiency Studies (from July 12 Analysis Meeting)]
 +
##* Jon has posted the slides from his presentation to the analysis meeting on Tuesday with a few updates based on feedback. Most of this information was presented at a previous Cal meeting.
 +
##* He notes that the behavior across the Bcal/Fcal interface is surprisingly smooth, even when tighter cuts are applied to energy conservation.
 +
## [https://logbooks.jlab.org/files/2016/07/3413092/pi0s_FCAL.pdf FCAL Gain Calibration Survey] Adesh Subedi
 +
##* Used the output of the monitoring plugins from the REST production to investigate systematics of the calibration as a function of run number and energy
 +
##* The production covered three periods of calibration corresponding to three HV settings.
 +
##* The single calibration for the first period is not adequate to cover the entire period. The early runs yield a pi0 peak below the nominal.
 +
##* For Eg > 1 GeV, Mpi ~ 135 +/- 1 MeV, simga_pi ~ 7.1 MeV (sigma/E ~5.3%)
 +
##* Same trends shown for Eg > 0.5 GeV.
 +
##* Investigated empty target runs. Spectrum has additional peaks, speculated to be due to pi0s reconstructed with incorrect vertex. However, this analysis uses the reconstructed vertex determined from charged tracks, so this may not be the explanation.
 +
##* Investigated runs with no beginning of run record (i.e. incorrect number of samples used in sum). Examples of runs 10591, 10563 have very high Mpi. Will likely remove these runs from the "good runs" list
 +
##* Looked briefly at Mpi and Sigma_pi for photons in Bcal. The systematics seem more stable than for the Fcal (mass varies by 0.5 MeV total). Merged monitoring histograms are available if anyone else would like to use them. Contact Adesh.
 +
##* Plotted stability of Mpi and Sigma_pi vs energy bins (requiring both photons to lie in an energy interval).
 +
##* -> Need to update calibration for early runs ~ run 10400
 +
##* Systematics in pi0 mass (changes from 136 down to 134 MeV) over some in the mid period. Sean: Could be due to beam instabilities and radiator changes.
 +
##* Next meeting will report on Fcal timing
 +
##* Curtis: Good to improve early runs, but beam conditions were not optimal.
 +
##* Matt: Sigma_pi is constant as a function of energy, where a downward trend in sigma/E is expected. Elton: Notes that if Sigma_pi is constant, then sigma/E improves faster than expected for higher energies. Mark: The pi0 resolution combines position and energy, so there could be compensating effects.
 +
##* Will: Has requested that Mpi and Sigma_pi for Bcal be added to the time data base. Sean: Will check that it has been incorporated.
 
# BCAL update
 
# BCAL update
 
# Calibrations
 
# Calibrations

Revision as of 13:48, 14 July 2016

Video Conferencing Information

Meeting Time: 11:00 p.m.

  1. To join via a Web Browser, go to the page [1] https://bluejeans.com/907185247.
  2. To join via Polycom room system go to the IP Address: 199.48.152.152 (bjn.vc) and enter the meeting ID: 907185247.
  3. To join via phone, use one of the following numbers and the Conference ID: 907185247.
    • US or Canada: +1 408 740 7256 or
    • US or Canada: +1 888 240 2560
  4. Upon connection all microphones are automatically muted. To unmute your mike on a Polycom or equivalent unit, enter *4. Unmuting on a computer is trivial as there is a microphone button than can be clicked.
  5. More information on connecting to bluejeans is available.

Participant Direct Lines

  • JLab Phone: in CC F326 is 757-269-6460 (usual room)
  • JLab Phone in CC L207 is 757-269-7084
  • Phone in the Regina Video-conference Suite is 306-585-4204
  • Athens Phone: in Christina's office is 011-30-210-727-6947

Action Items

References

  1. FCAL HDFCAL log book
  2. BCAL HDBCAL log book
  3. BCAL Action Items and Working Tasks

Tentative Agenda

  1. Announcements
  2. Action Items
  3. Preparation for REST production
    • Analysis Train e-mail from Paul Mattione. Deadline is July 22.
    • Schedule of analysis reports: e-mail from Paul Mattione
  4. FCAL update
  5. BCAL update
  6. Calibrations
  7. Reconstruction and Simulation
  8. Any other business

Minutes

Attendees: Elton, Mark, Adesh, Jon (JLab); Christina, George (Athens); Sean (NW); Will, Curtis, Mike (CMU); Andrei, Ahmed, Tegan, Colleen (UofR).

  1. Announcements
  2. Action Items
  3. Preparation for REST production
    • Analysis Train e-mail from Paul Mattione. Deadline is July 22.
    • Schedule of analysis reports: e-mail from Paul Mattione
  4. FCAL update
    1. Hardware update
      • Test setup for Fcal bases is operational at JLab. Chris is learning on how to test and fix bases. There is a Linux computer with software to communicate with the bases.
      • Paul has found that there are four resistors on the mult board that seem to be the source of HV problems. Replacing them should fix those problems.
      • Paul is providing documentation on the fixes and is transferring the information to Chris.
      • Start by fixing dividers with problems seen both on the detector and on the test setup.
    2. Efficiency Studies (from July 12 Analysis Meeting)
      • Jon has posted the slides from his presentation to the analysis meeting on Tuesday with a few updates based on feedback. Most of this information was presented at a previous Cal meeting.
      • He notes that the behavior across the Bcal/Fcal interface is surprisingly smooth, even when tighter cuts are applied to energy conservation.
    3. FCAL Gain Calibration Survey Adesh Subedi
      • Used the output of the monitoring plugins from the REST production to investigate systematics of the calibration as a function of run number and energy
      • The production covered three periods of calibration corresponding to three HV settings.
      • The single calibration for the first period is not adequate to cover the entire period. The early runs yield a pi0 peak below the nominal.
      • For Eg > 1 GeV, Mpi ~ 135 +/- 1 MeV, simga_pi ~ 7.1 MeV (sigma/E ~5.3%)
      • Same trends shown for Eg > 0.5 GeV.
      • Investigated empty target runs. Spectrum has additional peaks, speculated to be due to pi0s reconstructed with incorrect vertex. However, this analysis uses the reconstructed vertex determined from charged tracks, so this may not be the explanation.
      • Investigated runs with no beginning of run record (i.e. incorrect number of samples used in sum). Examples of runs 10591, 10563 have very high Mpi. Will likely remove these runs from the "good runs" list
      • Looked briefly at Mpi and Sigma_pi for photons in Bcal. The systematics seem more stable than for the Fcal (mass varies by 0.5 MeV total). Merged monitoring histograms are available if anyone else would like to use them. Contact Adesh.
      • Plotted stability of Mpi and Sigma_pi vs energy bins (requiring both photons to lie in an energy interval).
      • -> Need to update calibration for early runs ~ run 10400
      • Systematics in pi0 mass (changes from 136 down to 134 MeV) over some in the mid period. Sean: Could be due to beam instabilities and radiator changes.
      • Next meeting will report on Fcal timing
      • Curtis: Good to improve early runs, but beam conditions were not optimal.
      • Matt: Sigma_pi is constant as a function of energy, where a downward trend in sigma/E is expected. Elton: Notes that if Sigma_pi is constant, then sigma/E improves faster than expected for higher energies. Mark: The pi0 resolution combines position and energy, so there could be compensating effects.
      • Will: Has requested that Mpi and Sigma_pi for Bcal be added to the time data base. Sean: Will check that it has been incorporated.
  5. BCAL update
  6. Calibrations
  7. Reconstruction and Simulation
  8. Any other business