Π polarizability Meeting Apr 27, 2022

From GlueXWiki
Jump to: navigation, search

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. Check with Justin about loading translation table into ccdb. (Beni)
  2. Produce vertex distributions using MC to verify the software is be available for full/empty target commissioning (Andrew)

Preliminary Agenda

  1. Previous CPP meeting: Apr 20, 2022
  2. Previous CPP Software meeting: Π polarizability Software Meeting Apr 21, 2022
  3. Announcements
    • Collaboration Meeting May 23-26 (Tue - software/tutiorials, Wed-Thu)
    • Run Coordinator Meetings start tomorrow on a weekly basis
    • Please volunteer to fill Run Coordinator positions during the run. [Jun 8-22: Alexandre Deur, Jun 22-29: Mark Dalton, Jun 29-Jul 6: Beni, Jul 6-13: Open, Jul 13-20: Elton, Jul 20-27: Open]
  4. Action Items
  5. CPP-NPP Trigger (Sasha will try to connect; see message below)
  6. CPP and NPP Run Conditions
  7. Photon beam / tagger / diamonds
  8. Software/Calibration, Simulations
  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

Present: Albert, Alex, Andrew, Beni, David H., David L., Elton, Eugene, Ilya, Nikhil, Rory, Sergey, Simon

  1. Previous CPP meeting: Apr 20, 2022
  2. Previous CPP Software meeting: Π polarizability Software Meeting Apr 21, 2022
  3. Announcements
    • Collaboration Meeting May 23-26 (Tue - software/tutiorials, Wed-Thu)
    • Run Coordinator Meetings start tomorrow on a weekly basis
    • Please volunteer to fill Run Coordinator positions during the run. [Jun 8-22: Alexandre Deur, Jun 22-29: Mark Dalton, Jun 29-Jul 6: Beni, Jul 6-13: Open, Jul 13-20: Elton, Jul 20-27: Open]
  4. Action Items
  5. CPP-NPP Trigger (Sasha, see message below)
    • New firmware for TOF trigger was installed with Hai's assistance.
    • Managed to boot and initialize the firmware. Triggering the TOF one could see some associated hits.
    • Installed 5 failed FADC250 modules in FCAL and BCAL
    • Cables for FP trigger still need to be connected.
    • Beni: cables from scintillator are in hand and the scintillator has been repaired. Plan to implement the trigger logic this afternoon.
  6. CPP and NPP Run Conditions
  7. Photon beam / tagger / diamonds
  8. Software/Calibration, Simulations
    • CPP DAQ/Monitoring Test Spring 2022
    • David: Has prepared a draft plan for DAQ activities prior to the run. The initial draft seemed reasonable. Elton: Make sure to include data taken with FP trigger.
    • The tentative plan will be passed on to Alexandre and presented at the RC meeting. Will coordinate with other groups regarding use of DAQ.
  9. MWPC Testing
    • FMWPC Log Book
    • halldweb/talks/CPP_NPP
    • Beni: Several problems with installation have been identified and fixed:
    • HV breakout box had two shorted channels. These have been moved to working connectors.
    • The LV channel for chamber #3 is still broken. Rory: Suggested that one measured the resistance to ground between +/-5V and compare to "good" chamber. The plan is to remove the cover and access the electronics to debug. The chair lift is required but has been lent. When it is returned Chris and Nick will trouble shoot this channel.
    • Cosmic-ray data is being collected and Beni showed showed pulses from each chamber. See Log Entry 3992071
    • Rory: The pulses look similar to what we have seen in the EEL. The negative pre-pulse can be caused by adjacent wires firing and is normal in MWPCs.
    • Beni: We may wish to raise the pedestal value to 200 or 300 counts so that the negative pre-pulse does not affect the FADC performance.
    • Beni: Showed that there is still some noise in the MWPC. Grounding might reduce the effect, but we can probably live with it.
    • Simon: When will the CTOF signals be available? Beni: They are not yet cabled to electronics, but this should happen soon. Sergey will add them to the configuration when they are ready.
  10. CPP and NPP Experiment Configuration
  11. DAQ and Electronic Setup (Sergey and Beni)
    • Sergey: DAQ is working, but adjustments will need to be made to the readout parameters of the MWPC. Elton: In the EEL test, we set the thresholds to 100 counts above threshold for the efficiency studies.
    • Will check pedestal settings and perhaps raise the pedestal to 200-300 counts.
    • The CTOF will be added to the configuration as soon as it is ready.
  12. Documentation (Elton and Simon)
    • Elton has posted a draft of the MWPC OSP to the EHS web site for comments. Mark Dalton needs to update the procedure for accessing the FCAL Dark Room.
  13. Other business
    • Andrew: Has generated 100 runs with BGGEN and 0 polarization to study the kaon contamination. The number of events is still not sufficient for his studies. It appears that the kaon peak is more prominent in data.
  14. Next meeting


Message from Sasha:

In brief:

I made some progress with the trigger. Hai had to fix some firmware issues, the new    
firmware version was installed. Eventually I was able to get TOF triggers from the detector
(and saw associated hits). I am working on the trigger configuration now.
 
I will need a NIM signal (from Beni) with the hit coincidence from the newly installed paddles.

We had a lot of issues with FADCs. I've replaced several modules 
https://logbooks.jlab.org/entry/3991809
(there are still some minor issues, I am going to fix them during this  week).