Difference between revisions of "Π polarizability Meeting Jul 6, 2022"

From GlueXWiki
Jump to: navigation, search
(Preliminary Agenda)
(Minutes)
 
(2 intermediate revisions by the same user not shown)
Line 48: Line 48:
 
== Action Items ==
 
== Action Items ==
  
# Update trigger summary file to include entries for empty target, including summary table (Albert)
+
# <strike> Update trigger summary file to include entries for empty target, including summary table (Albert) </strike> Spreadsheet was updated.
 
# Take a current rate scan on full target later in the run to investigate any rate dependent effects. (Rory and Elton)
 
# Take a current rate scan on full target later in the run to investigate any rate dependent effects. (Rory and Elton)
# Send out a message to the collaboration that one should use the JANA_GEOMETRY_URL environment variable to ccdb://GEOMETRY/cpp_HDDS.xml for the CPP run period.
+
# <strike> Send out a message to the collaboration that one should use the JANA_GEOMETRY_URL environment variable to ccdb://GEOMETRY/cpp_HDDS.xml for the CPP run period. </strike> Simon sent out the message.  
  
 
== Preliminary Agenda  ==
 
== Preliminary Agenda  ==
Line 75: Line 75:
 
== Minutes ==
 
== Minutes ==
  
''Attending:
+
''Attending: Alex, Albert, Andrew, Beni, David H., David L., Elton, Ilya, Rory, Simon.
 +
 
 +
# Previous CPP meeting: [[%CE%A0_polarizability_Meeting_Jun 29,_2022|Jun 29, 2022]]
 +
# Previous CPP Software meeting: [[Π polarizability Software Meeting May 5, 2022]]
 +
# Announcements
 +
# Action Items
 +
# [https://docs.google.com/spreadsheets/d/1sdluzy7p5vnlhw9AWJHBrYbXKTBet45o4den4zWX9dc/edit#gid=1855021251 Spread Sheet with Run List] (Albert)
 +
#* [https://halldweb.jlab.org/data_monitoring/run_statistics/RunPeriod-2022-05/index.html Statistics for CPP-NPP]
 +
#* Elton updated the summary tables in the Spreadsheet and estimated the amount of PAC days collected. So far we have completed most of our commissioning activities and collected about 22% of the approved full and empty target data.
 +
#* Our current estimate is that we would need to extend the current run by 6 PAC days (12 calendar days) to acquire all the approved statistics for the experiment.
 +
# Software/Calibration, Simulations
 +
#* Elton: We have nice demonstrations of data and beam quality from rho production. It would be nice to investigate a signal with all neutrals.
 +
#* Alex showed the output of monitoring for rho events, demonstrating a high beam polarization. The "pi+pi-" events at low di-pion mass (shown to be mostly electrons) azimuthal asymmetry, presumably coming from BH events.
 +
#* Alex also processed data searching for g Pb -> g omega, omega -> gamma pi0. A pi0 peak on top of a large background is visible. The gamma-pi0 mass nearly shows any omega at all. This channel will be challenging.
 +
#* Rory: Consider requiring a cut on the elasticity Energy (beam - gamma - pi0).
 +
#* Elton and Ilya: Consider adding a threshold on individual photons used in reconstruction. Ilya: Eg > 1 GeV.
 +
#* Alex showed the 2pi0 spectrum. After the kinetic fit, the di-pion mass peaks at threshold. Simon: Interesting that no f2(1270) peak is visible?
 +
#* Simon agreed to look into searching from eta -> 3 pi0 in the data. That is also an all-neutral channel.
 +
# Photon beam / tagger / diamonds
 +
# DAQ and Electronic Setup (Sergey and Beni)
 +
# CPP-NPP Trigger
 +
#* [https://userweb.jlab.org/~ilarin/cpp/fcal_map.png FCAL occupancy map for single counter TOF&NOFCAL and FCAL trigger events] (Ilya)
 +
#* Ilya looked at FCAL hit distributions for FCAL/BCAL trigger and also the TOF&(NOT FCAL/BCAL). First one notices that the inner two FCAL rings are not in the trigger. He suggested that we should see if the rate allows us to include these into the data stream. He will contact Sasha to schedule a time to do this.
 +
#* There are blocks in the FCAL that do not seem to be quite calibrated. Ilya will contact Mark Dalton to pass on his analysis and inquire about plan for equalizing FCAL.
 +
#* Note that the inner region of FCAL is particularly important to look for single pi0 and eta->2g events in this data sample.
 +
# MWPCs
 +
#* [https://logbooks.jlab.org/book/hdfmwpc FMWPC Log Book]
 +
#* [https://halldweb.jlab.org/talks/2022/CPP_NPP/ halldweb/talks/CPP_NPP]
 +
#* [https://logbooks.jlab.org/entry/4011353 MWPC alignment and low-high rate runs comparison with muon events]
 +
#* The studies are consistent with the "low rate" period as being produced with a target ~ 2-3% of a rad len and with low Z, producing higher fraction of hadronic events and smaller number of electromagnetic showers than we see in the "high rate" production runs.
 +
#* We agreed that taking beam time to try to reproduce the target position in an intermediate position (between full and empty) is not a priority.
 +
# [[CPP and NPP Experiment Configuration]]
 +
# Documentation
 +
# Other business
 +
# Next meeting

Latest revision as of 14:39, 6 July 2022

09:30 EST (JLab time) Weekly Meeting

REMOTE during Covid-19

Connecting

Join ZoomGov Meeting
https://jlab-org.zoomgov.com/j/1608628791?pwd=bXhtZjdNRi8xeXZqWFh5T1R3TDBFdz09
Meeting ID: 160 862 8791
Passcode: CPP

Elton Smith is inviting you to a scheduled ZoomGov meeting.

Topic: CPP Weekly Meeting
Time: This is a recurring meeting Meet anytime

Join ZoomGov Meeting
https://jlab-org.zoomgov.com/j/1608628791?pwd=bXhtZjdNRi8xeXZqWFh5T1R3TDBFdz09

Meeting ID: 160 862 8791
Passcode: CPP
One tap mobile
+16692545252,,1608628791# US (San Jose)
+16468287666,,1608628791# US (New York)

Dial by your location
       +1 669 254 5252 US (San Jose)
       +1 646 828 7666 US (New York)
       +1 669 216 1590 US (San Jose)
       +1 551 285 1373 US
       833 568 8864 US Toll-free
Meeting ID: 160 862 8791
Find your local number: https://jlab-org.zoomgov.com/u/acZK7hDWFf
 
Join by SIP
1608628791@sip.zoomgov.com

Join by H.323
161.199.138.10 (US West)
161.199.136.10 (US East)
Meeting ID: 160 862 8791
Passcode: 112160

Action Items

  1. Update trigger summary file to include entries for empty target, including summary table (Albert) Spreadsheet was updated.
  2. Take a current rate scan on full target later in the run to investigate any rate dependent effects. (Rory and Elton)
  3. Send out a message to the collaboration that one should use the JANA_GEOMETRY_URL environment variable to ccdb://GEOMETRY/cpp_HDDS.xml for the CPP run period. Simon sent out the message.

Preliminary Agenda

  1. Previous CPP meeting: Jun 29, 2022
  2. Previous CPP Software meeting: Π polarizability Software Meeting May 5, 2022
  3. Announcements
  4. Action Items
  5. Spread Sheet with Run List (Albert)
  6. Software/Calibration, Simulations
  7. Photon beam / tagger / diamonds
  8. DAQ and Electronic Setup (Sergey and Beni)
  9. CPP-NPP Trigger
  10. MWPCs
  11. CPP and NPP Experiment Configuration
  12. Documentation
  13. Other business
  14. Next meeting

Minutes

Attending: Alex, Albert, Andrew, Beni, David H., David L., Elton, Ilya, Rory, Simon.

  1. Previous CPP meeting: Jun 29, 2022
  2. Previous CPP Software meeting: Π polarizability Software Meeting May 5, 2022
  3. Announcements
  4. Action Items
  5. Spread Sheet with Run List (Albert)
    • Statistics for CPP-NPP
    • Elton updated the summary tables in the Spreadsheet and estimated the amount of PAC days collected. So far we have completed most of our commissioning activities and collected about 22% of the approved full and empty target data.
    • Our current estimate is that we would need to extend the current run by 6 PAC days (12 calendar days) to acquire all the approved statistics for the experiment.
  6. Software/Calibration, Simulations
    • Elton: We have nice demonstrations of data and beam quality from rho production. It would be nice to investigate a signal with all neutrals.
    • Alex showed the output of monitoring for rho events, demonstrating a high beam polarization. The "pi+pi-" events at low di-pion mass (shown to be mostly electrons) azimuthal asymmetry, presumably coming from BH events.
    • Alex also processed data searching for g Pb -> g omega, omega -> gamma pi0. A pi0 peak on top of a large background is visible. The gamma-pi0 mass nearly shows any omega at all. This channel will be challenging.
    • Rory: Consider requiring a cut on the elasticity Energy (beam - gamma - pi0).
    • Elton and Ilya: Consider adding a threshold on individual photons used in reconstruction. Ilya: Eg > 1 GeV.
    • Alex showed the 2pi0 spectrum. After the kinetic fit, the di-pion mass peaks at threshold. Simon: Interesting that no f2(1270) peak is visible?
    • Simon agreed to look into searching from eta -> 3 pi0 in the data. That is also an all-neutral channel.
  7. Photon beam / tagger / diamonds
  8. DAQ and Electronic Setup (Sergey and Beni)
  9. CPP-NPP Trigger
    • FCAL occupancy map for single counter TOF&NOFCAL and FCAL trigger events (Ilya)
    • Ilya looked at FCAL hit distributions for FCAL/BCAL trigger and also the TOF&(NOT FCAL/BCAL). First one notices that the inner two FCAL rings are not in the trigger. He suggested that we should see if the rate allows us to include these into the data stream. He will contact Sasha to schedule a time to do this.
    • There are blocks in the FCAL that do not seem to be quite calibrated. Ilya will contact Mark Dalton to pass on his analysis and inquire about plan for equalizing FCAL.
    • Note that the inner region of FCAL is particularly important to look for single pi0 and eta->2g events in this data sample.
  10. MWPCs
    • FMWPC Log Book
    • halldweb/talks/CPP_NPP
    • MWPC alignment and low-high rate runs comparison with muon events
    • The studies are consistent with the "low rate" period as being produced with a target ~ 2-3% of a rad len and with low Z, producing higher fraction of hadronic events and smaller number of electromagnetic showers than we see in the "high rate" production runs.
    • We agreed that taking beam time to try to reproduce the target position in an intermediate position (between full and empty) is not a priority.
  11. CPP and NPP Experiment Configuration
  12. Documentation
  13. Other business
  14. Next meeting