Feb 4, 2015 BCAL Commissioning

Video Conferencing Information

Meeting Time: 3:00 p.m. Eastern

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

Resources

• HDBCAL log book
• Low-level calibration constants for BCAL GlueX-doc-2618

Tentative Agenda

1. Announcements
   • Beam schedule: opportunistic physics in the fall
2. Action Items
3. What do we need to do before the spring run?
   • Verify fixes with LED runs
   • Humidity settings
   • Attempt +5 C?
   • Check channel efficiencies
   • Verify pi0 statistics, estimate amount required
4. Parameters
   • DAQ thresholds (Nominal: 105, or 5 above pedestal)
   • Bias voltage setting (Nominal: 1.2V above breakdown)
   • Temperature setting (Chiller = 64 deg F, 18 deg C)
   • N_sa and N_sb (N_sa=55 , N_sb=5)
   • Effective velocity
   • Time offsets
   • Time-walk corrections
5. LED pulser runs
   • Verify fixes to hardware channels
   • Check humidity readback/settings
   • Create configuration that takes data through the TS for concurrent north and south running
   • Automate and enhance scripts to analyze the pulser runs.
6. Cosmic-Ray runs
   • Settings for cosmic runs: shall we match settings for April running?
   • Can we check efficiencies for a given DAQ threshold?
   • How to effectively use data triggered on the BCAL?
   • How to calibrate timing?
   • What simulations are needed to support all calibration?
7. Any other business

Minutes

Attendees: Elton, Will, Noemi, Mark (JLab); Zisis, Tegan, Ahmed, Andrei (UofR)

1. Announcements
   • Beam schedule: opportunistic physics in the fall.
2. Action Items
3. What do we need to do before the spring run?
   • Verify fixes with LED runs
   • Humidity settings
   • Attempt +5 C?
   • Check channel efficiencies
   • Verify pi0 statistics, estimate amount required
4. Parameters
   • DAQ thresholds
   • Bias voltage setting
   • N_sa and N_sb
   • Effective velocity
   • Time offsets
   • Time-walk corrections
5. LED pulser runs
   • Verify fixes to hardware channels
   • Check humidity readback/settings
   • Create configuration that takes data through the TS for concurrent north and south running
   • Automate and enhance scripts to analyze the pulser runs.
6. Cosmic-Ray runs
   • Settings for cosmic runs: shall we match settings for April running?
   • Can we check efficiencies for a given DAQ threshold?
   • How to effectively use data triggered on the BCAL?
   • How to calibrate timing?
   • What simulations are needed to support all calibration?
7. Any other business

Action Items

1. Take LED runs to check system (Elton and Noemi)
2. Investigate pedestal parameters for different temperatures (Tegan)
3. Analyze runs at different overbias for efficiency/noise (?)
4. Think about how best to use BCAL-triggered runs to study calibrations (Andrei and Zisis)
5. Investigate how to check efficiency vs DAQ thresholds (Elton)
6. Determine effective velocity for each channel (George?)
7. Determine time-walk corrections (George?)
8. Determine time offsets (?)