Difference between revisions of "Π polarizability Meeting Jun 1, 2022"

From GlueXWiki
Jump to: navigation, search
(Preliminary Agenda)
(Minutes)
 
(10 intermediate revisions by the same user not shown)
Line 48: Line 48:
 
== Action Items ==
 
== Action Items ==
  
# Produce vertex distributions using MC to verify the software is be available for full/empty target commissioning (Andrew)
+
# <strike> Produce vertex distributions using MC to verify the software is be available for full/empty target commissioning (Andrew) </string> Plots have been produced but the reaction specification had a bug, so few entries were generated. Should work on next try </strike>
 +
# <strike> Schedule training for FCAL Darkroom and Pb shield alignment (Elton) </strike> Training scheduled for Friday at 9:30.
  
 
== Preliminary Agenda  ==
 
== Preliminary Agenda  ==
Line 54: Line 55:
 
# Previous CPP Software meeting: [[Π polarizability Software Meeting May 5, 2022]]
 
# Previous CPP Software meeting: [[Π polarizability Software Meeting May 5, 2022]]
 
# Announcements
 
# Announcements
#* [[GlueX-Collaboration-May-2022 | Collaboration Meeting]] Mon May 23 (Software/tutorials), Tue-Thu 24-26 (Meeting)
 
 
#* [[Run Coordination Meetings:Summer2022 | Run Coordinator Meetings]]
 
#* [[Run Coordination Meetings:Summer2022 | Run Coordinator Meetings]]
#** Add names to items in [[CPP and NPP Run Conditions]]
 
#** Do we want 0,90,0,90, amorphous or 0,0,90,90,amorphous ? Elton: Suggests the 0,0,90,90,AMO to minimize beamline changes. Beni: Would like to see alternating 0,90,0,90,AMO to minimize systematics. David H: Mainz experience shows that changes on the scale of hours does not introduce systematics.
 
#** With the 3.5mm collimator, do we want more frequent harp scans at least at the beginning? Beam conditions are expected to be much more sensitive to drifts/focus changes. Elton: Play it by ear: start with one scan per day and check beam stability.
 
 
# Action Items
 
# Action Items
# Need volunteer for 10min presentation at MCC 1:30pm meeting (Wednesdays) about CPP: Audience MCC/technicians
+
# CPP-NPP Trigger (Sasha)
#* Andrew was volunteered and could give a presentation on Wed Jun 1.
+
# CPP-NPP Trigger (Sasha not present)
+
#* Beni: DAQ is taking data reading out all subsystems. Trigger used is Fcal/Bcal + CTOF. Rory: What is the status of the TOF trigger? Beni: TOF trigger firmware has been downloaded by Sasha and he has checked that relevant detectors are readout out. We need to push for further testing. Beni will ask Sasha to add the TOF trigger to the current configuration.
+
 
# [[CPP and NPP Run Conditions]]
 
# [[CPP and NPP Run Conditions]]
#* Empty target running (Rory): Plan is to take data with the neutral trigger, use Andrew's code to select e+/e- events and use those to generate vertex distributions. (They will review this at their local UMass meeting). Elton: Could possibly use the CTOF trigger to select mu+/mu- pairs and use those to look at the vertex distributions.
 
 
# Photon beam / tagger / diamonds
 
# Photon beam / tagger / diamonds
#* Beni: Should make sure that shift workers keep track of the coherent peak. Elton: We may not be very sensitive to the edge because of the diamond quality.
 
 
# Software/Calibration, Simulations
 
# Software/Calibration, Simulations
#* Simon: Has added CTOF factories and calibration placeholders in ccdb for timing offsets.
+
#* hdview2 event display
#* Andrew: Added the e/pi neural net factory and added angular distributions to the online histograms. They need considerable data, so statistics may be an issue online.
+
#* Alex: Pull request failed in the automatic build. Need to sort this out.
+
#* data skims and quick analysis feedback (polarization, [https://logbooks.jlab.org/entry/3992221 vertex])
+
 
# MWPC Testing  
 
# MWPC Testing  
 
#* [https://logbooks.jlab.org/book/hdfmwpc FMWPC Log Book]
 
#* [https://logbooks.jlab.org/book/hdfmwpc FMWPC Log Book]
 
#* [https://halldweb.jlab.org/talks/2022/CPP_NPP/ halldweb/talks/CPP_NPP]
 
#* [https://halldweb.jlab.org/talks/2022/CPP_NPP/ halldweb/talks/CPP_NPP]
#* Alex: High level histograms are available in the 2pi0 channel, See [https://logbooks.jlab.org/files/2022/05/3993985/NPP_monitoring_v2.PNG Log Entry 3993985 Comment]. With MC generated with only Primakoff and Sigma production, very nice signals are observed.
 
 
# [[CPP and NPP Experiment Configuration]]
 
# [[CPP and NPP Experiment Configuration]]
 
# DAQ and Electronic Setup (Sergey and Beni)
 
# DAQ and Electronic Setup (Sergey and Beni)
Line 83: Line 71:
 
#* [https://halldweb.jlab.org/hdops/wiki/index.php/Forward_Multi-Wire_Proportional_Chambers_Shift Description of FMWCP and CTOF for Shift Takers]
 
#* [https://halldweb.jlab.org/hdops/wiki/index.php/Forward_Multi-Wire_Proportional_Chambers_Shift Description of FMWCP and CTOF for Shift Takers]
 
#* Tim has drafted a procedure to align the Pb picture-frame.
 
#* Tim has drafted a procedure to align the Pb picture-frame.
#** Schedule training.....
 
 
# Other business
 
# Other business
 
# Next meeting
 
# Next meeting
Line 89: Line 76:
 
== Minutes ==
 
== Minutes ==
  
''Attending:
+
''Attending: Albert, Alex, Andrew, Beni, David H., David L., Elton, Eugene, Ilya, Sergey, Simon. [Note: I forgot to check on the participants list. Please add your name if it is missing].
 +
 
 +
# Previous CPP meeting: [[%CE%A0_polarizability_Meeting_May 18,_2022|May 18, 2022]]
 +
# Previous CPP Software meeting: [[Π polarizability Software Meeting May 5, 2022]]
 +
# Announcements
 +
#* [[Run Coordination Meetings:Summer2022 | Run Coordinator Meetings]]
 +
#* Rory: At the collaboration meeting, Curtis suggested that we use 45/135 instead of 0/90 orientations. David H: At the Crystal Ball they moved from 0/90 to 45/135 because the detector had openings at 0 and 180deg, generating systematics with the 0/90 configuration. Alex: In 2016 we used only 0/90 and false asymmetries were seen because the beam was off center in the horizontal direction. We decided to use the 45, 45, 135, 135, AMO configuration. Elton will close the loop with Alexandre and Hovanes.
 +
#* Rory: How much should we change the beam current (photon flux) for the empty target runs, relative to nominal? Running at x2 nominal seems reasonable. Ilya: We should take a run at the full target current to check for systematics.
 +
# Action Items
 +
# CPP-NPP Trigger
 +
#* Sasha was not present
 +
#* Ilya: Reviewed data in raw mode taken in December. Initial rate estimates showed a 25% increase relative to previous studies (although under slightly different conditions). Plot of TOF pulses shows that increasing the threshold from 175 counts -> 400 counts, still low relative to minimum ionizing peak at 1000 counts, gives a rate back in line with original estimates. Beni: Goal of TOF calibration is to set the Landau peak at the same location for all counters (~ 800 counts).  Noted that there are two thresholds: trigger threshold and readout threshold. The readout threshold should be lower than the trigger threshold in order to be able to easily monitor effect of trigger thresholds. Elton: What is the attenuation length? Beni: About 400 cm. Note the the (full length) TOF scintillators are 252 cm long -> Change in pulse height from center to edge is exp(-126/400) ~ 0.73.
 +
# [[CPP and NPP Run Conditions]]
 +
#* Elton to update table based on previous discussions.
 +
# Photon beam / tagger / diamonds
 +
# Software/Calibration, Simulations
 +
#* hdview2 event display. David L: In the process of updating event display to show CTOF counters. Elton: If one filters on the trigger type, it might be easier to investigate BH muons.
 +
#* Vertex distributions. Andrew: Generated 500k e+e- BH events with Rory's generator. Only about 6 satisfied the reaction filter. (The problem was traced to the event filter definition).
 +
# MWPC Testing
 +
#* [https://logbooks.jlab.org/book/hdfmwpc FMWPC Log Book]
 +
#* [https://halldweb.jlab.org/talks/2022/CPP_NPP/ halldweb/talks/CPP_NPP]
 +
#* Beni: FMWPC LV tripped, apparently due to DIRC interlock that shares a common crate. This needs to be sorted out. Beni will contact Nick.
 +
#* Data taken with the CTOF trigger can be useful in checking data, even with cosmics. CTOF FP trigger does not show up in monitoring plots. Alex will update plots to histogram CTOP bit 6 (counting from 1).
 +
# [[CPP and NPP Experiment Configuration]]
 +
#* Andrew: Path to recent BH e+e- events has been added to the list of MC files.
 +
# DAQ and Electronic Setup (Sergey and Beni)
 +
# Documentation (Elton and Simon)
 +
#* See [https://halldweb.jlab.org/hdops/wiki/index.php/Approved_Procedures List of Approved Procedures]
 +
#* [https://halldweb.jlab.org/hdops/wiki/index.php/Forward_Multi-Wire_Proportional_Chambers_Shift Description of FMWCP and CTOF for Shift Takers]
 +
#* Tim has drafted a procedure to align the Pb picture-frame. Elton needs to add this to the shift-taker's page.
 +
# Other business
 +
# Next meeting

Latest revision as of 11:49, 1 June 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. Produce vertex distributions using MC to verify the software is be available for full/empty target commissioning (Andrew) </string> Plots have been produced but the reaction specification had a bug, so few entries were generated. Should work on next try
  2. Schedule training for FCAL Darkroom and Pb shield alignment (Elton) Training scheduled for Friday at 9:30.

Preliminary Agenda

  1. Previous CPP meeting: May 18, 2022
  2. Previous CPP Software meeting: Π polarizability Software Meeting May 5, 2022
  3. Announcements
  4. Action Items
  5. CPP-NPP Trigger (Sasha)
  6. CPP and NPP Run Conditions
  7. Photon beam / tagger / diamonds
  8. Software/Calibration, Simulations
    • hdview2 event display
  9. MWPC Testing
  10. CPP and NPP Experiment Configuration
  11. DAQ and Electronic Setup (Sergey and Beni)
  12. Documentation (Elton and Simon)
  13. Other business
  14. Next meeting

Minutes

Attending: Albert, Alex, Andrew, Beni, David H., David L., Elton, Eugene, Ilya, Sergey, Simon. [Note: I forgot to check on the participants list. Please add your name if it is missing].

  1. Previous CPP meeting: May 18, 2022
  2. Previous CPP Software meeting: Π polarizability Software Meeting May 5, 2022
  3. Announcements
    • Run Coordinator Meetings
    • Rory: At the collaboration meeting, Curtis suggested that we use 45/135 instead of 0/90 orientations. David H: At the Crystal Ball they moved from 0/90 to 45/135 because the detector had openings at 0 and 180deg, generating systematics with the 0/90 configuration. Alex: In 2016 we used only 0/90 and false asymmetries were seen because the beam was off center in the horizontal direction. We decided to use the 45, 45, 135, 135, AMO configuration. Elton will close the loop with Alexandre and Hovanes.
    • Rory: How much should we change the beam current (photon flux) for the empty target runs, relative to nominal? Running at x2 nominal seems reasonable. Ilya: We should take a run at the full target current to check for systematics.
  4. Action Items
  5. CPP-NPP Trigger
    • Sasha was not present
    • Ilya: Reviewed data in raw mode taken in December. Initial rate estimates showed a 25% increase relative to previous studies (although under slightly different conditions). Plot of TOF pulses shows that increasing the threshold from 175 counts -> 400 counts, still low relative to minimum ionizing peak at 1000 counts, gives a rate back in line with original estimates. Beni: Goal of TOF calibration is to set the Landau peak at the same location for all counters (~ 800 counts). Noted that there are two thresholds: trigger threshold and readout threshold. The readout threshold should be lower than the trigger threshold in order to be able to easily monitor effect of trigger thresholds. Elton: What is the attenuation length? Beni: About 400 cm. Note the the (full length) TOF scintillators are 252 cm long -> Change in pulse height from center to edge is exp(-126/400) ~ 0.73.
  6. CPP and NPP Run Conditions
    • Elton to update table based on previous discussions.
  7. Photon beam / tagger / diamonds
  8. Software/Calibration, Simulations
    • hdview2 event display. David L: In the process of updating event display to show CTOF counters. Elton: If one filters on the trigger type, it might be easier to investigate BH muons.
    • Vertex distributions. Andrew: Generated 500k e+e- BH events with Rory's generator. Only about 6 satisfied the reaction filter. (The problem was traced to the event filter definition).
  9. MWPC Testing
    • FMWPC Log Book
    • halldweb/talks/CPP_NPP
    • Beni: FMWPC LV tripped, apparently due to DIRC interlock that shares a common crate. This needs to be sorted out. Beni will contact Nick.
    • Data taken with the CTOF trigger can be useful in checking data, even with cosmics. CTOF FP trigger does not show up in monitoring plots. Alex will update plots to histogram CTOP bit 6 (counting from 1).
  10. CPP and NPP Experiment Configuration
    • Andrew: Path to recent BH e+e- events has been added to the list of MC files.
  11. DAQ and Electronic Setup (Sergey and Beni)
  12. Documentation (Elton and Simon)
  13. Other business
  14. Next meeting