Difference between revisions of "Jan 26, 2017 Calorimeter"

From GlueXWiki
Jump to: navigation, search
(Action Items)
 
(One intermediate revision by the same user not shown)
Line 55: Line 55:
 
#* Please focus the talks on performance, calibration status and Monte Carlo agreement with data.
 
#* Please focus the talks on performance, calibration status and Monte Carlo agreement with data.
 
# Action Items
 
# Action Items
 +
#* (Sean and Will) CCDB update addresses the timing in MC
 +
#* (Elton) Pedestals seemed to be ok, but overflows in monitoring plots on log scale exaggerate tail contributions.
 
# Run preparations
 
# Run preparations
 +
## BCAL
 +
##* Chiller set to 5 degC and operating since last week. Biases are set for 5deg C and Vover = 1.4 V.
 +
##* LED data to check individual SiPM status has not been run, but planned for this afternoon
 +
##* Plan to set the NSB=1, NSA=26 as for the spring 2016 run. This was decided after Justin showed his plots on saturation. The resolution shows a shallow minimum, which includes the 1-26.
 +
##* Might take some data with other window(s) to study.
 +
## FCAL
 +
##* Checking failures vs time. Will replace 20 bases today to complete HCO
 +
##* There are currently 57 spares.
 +
##* Policy to replace bases: Jon: Up to now bases are left in detector till they fail completely. Matt: May wish to revisit this policy and remove bases as practical to implement fixes since we understand the failures now.
 +
##* Curtis: How many bases have been replaced to date? Matt: About 10%.
 +
##* Adesh: Data from December shows a pi0 mass of about 130 MeV (down from 135) and width of about 7.5 MeV. Compared to last spring there are new firmware changes, but the integration window (NSB=1, NSA=15) is unchanged. Will keep this for the present run as well.
 +
##* May also consider taking some data for different integration windows for study.
 +
##* Justin: What about using the data with waveforms to study effects of integration window? Could be considered, but rates are limited due to high data rates.
 +
##* Pulser information should have been recorded during the December run, but checking data files is cumbersome. Sean has been using the trigger bits to skim the files and that may have some issues.
 +
##* Hovanes planes to add the LED pulser information into the archiver, but this may not happen till mid run. The data should be included on the data tapes and should be checked at the beginning of the run.
 
# FCAL update
 
# FCAL update
 
## [https://docs.google.com/spreadsheets/d/1zRR8tYKStI9cDz_XRU7Tm7wGbv-5tl8SyIkx-c8ywPA/edit#gid=0| JLab Base Daily Monitor]
 
## [https://docs.google.com/spreadsheets/d/1zRR8tYKStI9cDz_XRU7Tm7wGbv-5tl8SyIkx-c8ywPA/edit#gid=0| JLab Base Daily Monitor]
 +
##* Plotted failures vs time. Over the past week we get about 1.4 failures per day.
 
# BCAL update
 
# BCAL update
 
##[https://halldweb.jlab.org/wiki/images/9/9c/Pi0_dalitz_decay_v3.pdf &pi;<sup>0</sup> Dalitz decay - Signal extraction] - George
 
##[https://halldweb.jlab.org/wiki/images/9/9c/Pi0_dalitz_decay_v3.pdf &pi;<sup>0</sup> Dalitz decay - Signal extraction] - George
 +
##* Analyzed the golden runs from 2016 and also MC data.
 +
##* After all cuts except the kinematic fit, about 13k events remain. The kinematic fit convergence reduced the number to 2.5k events.
 +
##* Adesh: Why is there a tail on the high side of the mass? Not understood
 +
##* Adesh: Consider plotting the angular distribution of events in the FCAL. Selecting on high-angle events may eliminate beam related background, which comes at low angles.
 +
##* Justin: Could consider kinematic fit with only the vertex (not 4-momenta) to constrain the p and e+,e- to come from the same point and eliminate conversions
 +
##* Will: Radiative decays in BCAL? George: None in the MC. Events in the data are included with out the E/p cut because no clear peak is apparent as in the FCAL. Will: Could cut on this variable anyway to remove clear background at low E/p
 +
##* Will: No events in MC could be due to event generation at low t
 
##[https://logbooks.jlab.org/entry/3452738 fADC saturation] - Justin
 
##[https://logbooks.jlab.org/entry/3452738 fADC saturation] - Justin
 
# Calibrations
 
# Calibrations
 +
#* Mark: Plotting ln(Ratio up/down) vs z from timing show distortions. Likely calibrations are affecting the reconstructed z position. This may be a cause of the increased pi0 width.
 +
#* Sean: George's plugging to calibrate the veff and position is being run through today.
 
# Reconstruction and Simulation
 
# Reconstruction and Simulation
 
# NIM articles
 
# NIM articles
 
# Any other business
 
# Any other business

Latest revision as of 13:22, 26 January 2017

Video Conferencing Information

Meeting Time: 10:00 a.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 L207 is 757-269-7084 (usual room)
  • JLab Phone: in CC F326 is 757-269-6460
  • 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

  1. Will and Sean: investigate strange time outputs for BCAL times (cutoff of negative times in TDC, large offsets in ADC) in the Geant/mcsmear. See Sean's Log Enry 3450814.
  2. Elton: check on new pedestal information in data stream. See Elton's Log Entry 3451484
  3. Marc: Check on "LED noise" on four ADC/TDC channels.

References

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

Tentative Agenda

  1. Announcements
  2. Collaboration Meeting
    • Please focus the talks on performance, calibration status and Monte Carlo agreement with data.
  3. Action Items
  4. Run preparations
  5. FCAL update
    1. JLab Base Daily Monitor
  6. BCAL update
    1. π0 Dalitz decay - Signal extraction - George
    2. fADC saturation - Justin
  7. Calibrations
  8. Reconstruction and Simulation
  9. NIM articles
  10. Any other business

Minutes

Attendees: Elton, Adesh, Jon, Eugene, Mark (JLab); George, Christine (Athens); Justin (W&M); Will, Curtis (CMU); Ahmed (Regina); Matt (IU); Sean (NW).

  1. Announcements
  2. Collaboration Meeting
    • Please focus the talks on performance, calibration status and Monte Carlo agreement with data.
  3. Action Items
    • (Sean and Will) CCDB update addresses the timing in MC
    • (Elton) Pedestals seemed to be ok, but overflows in monitoring plots on log scale exaggerate tail contributions.
  4. Run preparations
    1. BCAL
      • Chiller set to 5 degC and operating since last week. Biases are set for 5deg C and Vover = 1.4 V.
      • LED data to check individual SiPM status has not been run, but planned for this afternoon
      • Plan to set the NSB=1, NSA=26 as for the spring 2016 run. This was decided after Justin showed his plots on saturation. The resolution shows a shallow minimum, which includes the 1-26.
      • Might take some data with other window(s) to study.
    2. FCAL
      • Checking failures vs time. Will replace 20 bases today to complete HCO
      • There are currently 57 spares.
      • Policy to replace bases: Jon: Up to now bases are left in detector till they fail completely. Matt: May wish to revisit this policy and remove bases as practical to implement fixes since we understand the failures now.
      • Curtis: How many bases have been replaced to date? Matt: About 10%.
      • Adesh: Data from December shows a pi0 mass of about 130 MeV (down from 135) and width of about 7.5 MeV. Compared to last spring there are new firmware changes, but the integration window (NSB=1, NSA=15) is unchanged. Will keep this for the present run as well.
      • May also consider taking some data for different integration windows for study.
      • Justin: What about using the data with waveforms to study effects of integration window? Could be considered, but rates are limited due to high data rates.
      • Pulser information should have been recorded during the December run, but checking data files is cumbersome. Sean has been using the trigger bits to skim the files and that may have some issues.
      • Hovanes planes to add the LED pulser information into the archiver, but this may not happen till mid run. The data should be included on the data tapes and should be checked at the beginning of the run.
  5. FCAL update
    1. JLab Base Daily Monitor
      • Plotted failures vs time. Over the past week we get about 1.4 failures per day.
  6. BCAL update
    1. π0 Dalitz decay - Signal extraction - George
      • Analyzed the golden runs from 2016 and also MC data.
      • After all cuts except the kinematic fit, about 13k events remain. The kinematic fit convergence reduced the number to 2.5k events.
      • Adesh: Why is there a tail on the high side of the mass? Not understood
      • Adesh: Consider plotting the angular distribution of events in the FCAL. Selecting on high-angle events may eliminate beam related background, which comes at low angles.
      • Justin: Could consider kinematic fit with only the vertex (not 4-momenta) to constrain the p and e+,e- to come from the same point and eliminate conversions
      • Will: Radiative decays in BCAL? George: None in the MC. Events in the data are included with out the E/p cut because no clear peak is apparent as in the FCAL. Will: Could cut on this variable anyway to remove clear background at low E/p
      • Will: No events in MC could be due to event generation at low t
    2. fADC saturation - Justin
  7. Calibrations
    • Mark: Plotting ln(Ratio up/down) vs z from timing show distortions. Likely calibrations are affecting the reconstructed z position. This may be a cause of the increased pi0 width.
    • Sean: George's plugging to calibrate the veff and position is being run through today.
  8. Reconstruction and Simulation
  9. NIM articles
  10. Any other business