Feb 20, 2020 Calorimeter

From GlueXWiki
Jump to: navigation, search

Meeting Time: 11: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

References

  1. FCAL HDFCAL log book
  2. BCAL HDBCAL log book

Goals for Calorimetry Group

  1. Determine preliminary photon reconstruction efficiencies as a function of E, phi and theta in data and simulation with a point-to-point precision of at least 5%.
  2. Measure systematics of pi0/eta mass calibration as a function of detector position to a precision of at east 5 MeV.
  3. Demonstrate agreement of photon reconstruction efficiency and resolution between data and simulation as a function of E, phi and theta to within 5%.

Action Items

  1. Check that the 4ns shifts in the BCAL FADCs is absent with the new firmware (Mark) No timing shifts have been seen
  2. Complete Calorimeter work packages

Long term items

Tentative Agenda

  1. Announcements
    • Announcement at Production and Analysis meeting. Complete calibrations by April 1? See 2020 Data Production
  2. Action Items
  3. Run Updates
    1. FCAL
    2. BCAL
  4. Calibrations
    1. BCAL Timing (Mark)
  5. Monitoring
    1. Module 26 LED plots (Varun)
  6. Reconstruction
    1. Discussion of neutron implementation in halld_recon? For reference, Simon's survey (not using halld_recon)
  7. Efficiencies
    1. BCAL simulation efficiency and FCAL+DIRC updates (Jon)
  8. Simulations
  9. NIM articles
  10. Any other business

Minutes

Attending: Elton, Mark, Zisis, Jon, Chandra (JLab); Karthik, Varun (UofR); Sean (FSU); Christina (Athens); Susan (Juelich); Drew (Duke).

  1. Announcements
    • Matt is on shift and Colin is RC this week.
    • Announcement at Production and Analysis meeting. Complete calibrations by April 1? See 2020 Data Production
  2. Action Items
    • (Mark) BCAL channel timing completed. See below. Differences from previous periods is ~50 ps. Position, Up/Down ratios will be done next week. Karthik should wait till these are complete before beginning the gain calibrations.
  3. Run Updates
    1. FCAL
      • (Jon) A few bases have been replaced; overall the rate has slowed. The PDU needs to be replaced. We need to make sure that gets done next week during the down time.
      • Elton shipped back bases to IU and they have been received.
    2. BCAL
      • BCAL Voltage Trip (Elton)
      • Temporary Fix
      • We need to take extra precautions when working around the magnet when the field is on.
      • Karthik should check calibrations before and after the incident to verify that there are no changes.
  4. Calibrations
    1. BCAL Timing (Mark)
      • Timing shift from previous periods is ~50 ps. New constants have been loaded into ccdb.
  5. Calibrations Spring 2019 (Sean)
    • Sean wanted to assess the status of calibrations for the PRIMEX run period and preparations for a monitoring run. PRIMEX uses the BCAL as a veto.
    • (Mark) 4 ns calibrations on BCAL have been completed for every run in a monitoring launch.
    • (Karthik) The pi0 gains were calibrated for spring 2019 and have been entered into ccdb.
    • Sean described what goes into the monitoring run. Here is more information from an email from Sean:
      • To look at the output of the monitoring launches, you can go to https://halldweb.jlab.org/data_monitoring/Plot_Browser.html and select (for example) Run Period = "RunPeriod-2019-01", and under Version, one of the choices labeled "Monitoring Launch"
      • The output ROOT files can be found under /work/halld/data_monitoring/RunPeriod-2019-01. You can familiarize yourself with the typical outputs by looking at these, and we can always add additional plugins.
      • It looks like we haven't done a full monitoring launch for the Primex runs, so this will be the first full look at that. </pre>
    • Would like to get initial calibrations into ccdb in preparation for the PRIMEX monitoring launch
      • FCAL timing: Drew has completed this for the PRIMEX run. He has passed on his pluggin to Colin to use for GlueX
      • (Susan) Will check the PRIMEX pi0 calibration and compare with MC. Proceed from there based on differences found.
      • (Drew) What does the monitoring launch cover. Sean: Essentially all detector subsystems. If more information is needed, pluggins can be added. Tagger timing calibrations should be coordinated with Olga Cortes who has taken this over, with copies to San and Mark.
  6. Monitoring
    1. Module 26 LED plots (Varun)
      • Checked LED response in module 26 before and after the event. M26 L1 S2 sees a 2% shift, and M26 L1 S3 shows a 5% shift. They see stable before and after the event. Monitoring will continue.
  7. Reconstruction
    1. Discussion of neutron implementation in halld_recon? For reference, Simon's survey (not using halld_recon) (Jon)
      • Simon presented a survey of reactions with neutrals, in particular a neutron in the final state. It is clear that many reactions were identified. The selections was crude (beta < 0.9 for neutron) and a guess at the covariance matrix.
      • Sean (and Alex A.) will implement some of these ideas into the analysis library. Initially Simon's covariance matrix would be used but should be improved.
      • (Elton) It would be nice to find a reaction that allows us to determine the neutron efficiency.
  8. Efficiencies
    1. BCAL simulation efficiency and FCAL+DIRC updates (Jon)
      • Photon gun + GEANT3/4 MC (using 1 thread). Use shower objects only.
      • In all simulations, there is good consistency between GEANT3 and GEANT4.
      • BCAL shows low efficiencies at about 15 degrees, presumably due to FDC frames
      • The DIRC has very little effect on the reconstruction (efficiency and energy measurement) in the FCAL.
      • Some differences between runs 30,000 and 60,000 were seen. Sean: For run dependencies one should look at real run numbers.
  9. Simulations
  10. NIM articles
  11. Any other business