Π polarizability Meeting Apr 13, 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 Sasha on steps for analyzing the random triggers in raw mode to check firmware (replay) Sasha said that there is no simple way of reading in the raw mode data taken in December and processing it using the replay mode for the firmware. We will need to check the hardware directly using data taken when the beam is off before the run starts.
  2. Develop a plan for deciding on the fraction of empty target data to take (Rory and Ilya)

Preliminary Agenda

  1. Previous CPP meeting: Apr 6, 2022
  2. Previous CPP Software meeting: Π polarizability Software Meeting Mar 31, 2022
  3. Announcements
  4. Action Items
  5. CPP-NPP Trigger
    1. Fiber connections for DAQ integration
    2. Fiber connections for FP trigger for CTOF
    3. TOF trigger for CPP
    4. FCAL/BCAL trigger for NPP
  6. CPP and NPP Run Conditions
  7. Photon beam / tagger / diamonds
  8. Software/Calibration
    • (Elton) Updated ccdb with PHOTON_BEAM/microscope/scaled_energy_range, PHOTON_BEAM/RF/reference_plane_z. What about PHOTON_BEAM/RF/beam_splot?
    • Use var=mc_cpp for MC (typically starting at Run > 70,000) and var=default for data (Runs 100,000 - 109,999).
    • Simulations
  9. MWPC Testing
  10. CPP and NPP Experiment Configuration
  11. DAQ and Electronic Setup (Sergey and Beni)
  12. Other business
  13. Next meeting

Minutes

Attending: Alex, Andrew, Beni, David L., Elton, Eugene, Ilya, Nikhil, Rory, Sasha, Sergey

  1. Announcements
  2. Action Items
  3. CPP-NPP Trigger. See Log Entry 3990905
    1. DAQ Configuration
      • Use configurations originally setup for the FMWPC test (rocfmwpc1 and vmefmwpc1)
      • Fiber connected to the TS for integrating crate into global DAQ
      • Testing is underway. Some technical details need to be sorted and Sasha is working on these
    2. TOF trigger
      • Basic configuration has been downloaded. Next step is to check simplest responses.
    3. Front Panel Trigger from CTOF (Beni)
      • Signals will be collected into the NIM bin and used to generate a signal from the paddles using NIM logic.
      • This trigger signal will be provided to Sasha, that can plug it into fiber receptors that transport the signal to the TS crate and used to produce a FP trigger.
    4. Why is the Status of TOF Firmware (Eugene)
      • Sasha: Hai has affirmed that he has checked the firmware on the bench using playback mode and verified that it works for simple configurations.
      • Beni: The behavior of the trigger will depend on careful balancing of the TOF signals by setting their HV. Sasha: Indeed the efficiency of the trigger depends on this, but the testing of the trigger does not rely on gain matching.
      • Sasha will also check simple configurations without beam.
      • Note: Data taken in December cannot be easily processed using the playback mode for the firmware.
      • David: "Concerned" that we will be starting the experiment without solid testing of the TOF trigger. Therefore, we need to bring the system up quickly and start exercising the system.
  4. CPP and NPP Run Conditions
  5. Photon beam / tagger / diamonds
  6. Software/Calibration
    • (Elton) Updated ccdb with PHOTON_BEAM/microscope/scaled_energy_range, PHOTON_BEAM/RF/reference_plane_z. What about PHOTON_BEAM/RF/beam_splot?
    • Use var=mc_cpp for MC (typically starting at Run > 70,000) and var=default for data (Runs 100,000 - 109,999).
    • Simon: suggests that beam_splot be initialized with z=1 and other entries set to zero. Elton will do this.
    • Simon: Tim provided values for dimensions and material of the He bag. He will update the geometry in the software. The CPP geometry should also be loaded into the var=default (Runs 100,000-109,999) when it is ready. Simon will take care of this.
    • David: New performance plots from Alex have been merged into the master.
    • Simulations
  7. MWPC Testing
    • FMWPC Log Book
    • halldweb/talks/CPP_NPP
    • Update on installation (Beni)
    • Signal cables for 3 MWPCs have arrive (half of total). They have been connected and tested on the vertical chambers (1, 3 and 5).
    • LV on FMWPC #3 is still problematic. Beni does not think it is due to the chamber. Need to find a reliable way of turning off/on.
    • The electronic modules for the FP trigger are now in hand, but a new discriminator had to be located.
    • FMWPC #1 HV tripped last night and could not be reset remotely. (This is Arwen, that is a bit leaky). Beni will try increasing the flow rate and bring it back up to voltage.
    • Sergey: Would like to setup a cosmic-ray trigger for testing the DAQ. Elton: The FP trigger would probably be the best. The BCAL trigger might also be useful as it will fire on showers that might also hit the FMWPCs.
  8. CPP and NPP Experiment Configuration
  9. DAQ and Electronic Setup (Sergey and Beni)
  10. Other business
    • Rory: Mark Dalton inquired about possibly reducing the readout threshold on the FCAL and whether this might be useful to us. We agreed that an 'ALARA' detector would be beneficial to us. Elton will bring this up at the calorimeter meeting immediately following. [Note added: This was brought up at the meeting and Mark will see how much flexibility there is in lowering thresholds without adding much noise.]
  11. Next meeting