Difference between revisions of "Π polarizability Meeting Jan 12, 2022"
From GlueXWiki
(→Minutes) |
(→Minutes) |
||
Line 102: | Line 102: | ||
#* There have been some improvements to the light coverings of the microscope, which should make it easier to access electronics. | #* There have been some improvements to the light coverings of the microscope, which should make it easier to access electronics. | ||
# Diamond for CPP (Richard) | # Diamond for CPP (Richard) | ||
− | #* Richard (and his team) tested diamonds at the light source at Saskatoon. These are thick diamonds and were tested before thinning. | + | #* Richard (and his team) tested diamonds at the light source at Saskatoon in December. These are thick diamonds and were tested before thinning. |
#* The Type III (electronic grade) diamond generated a disappointedly wide rocking curve and is not expected to produce sharp coherent peaks seen in some of our diamonds. | #* The Type III (electronic grade) diamond generated a disappointedly wide rocking curve and is not expected to produce sharp coherent peaks seen in some of our diamonds. | ||
#* The other two (?) diamonds tested (1.2 mm) generated very high quality rocking curves. However, there are several steps required before a thin 50 um diamond that could be used for CPP (or GlueX). The sequence of tasks needed to produce a (50 um) physics diamond are roughly: slice diamond into three wafers (200 um after material removed) / re-test for quality / thin wafers down to 80 um / re-test for quality / polish wafer down to 50 um / test final sample. Testing requires scheduling and use of an X-ray light source, which often takes months to schedule. In principle, testing is not required at each stage, but that is the best way to control the process. | #* The other two (?) diamonds tested (1.2 mm) generated very high quality rocking curves. However, there are several steps required before a thin 50 um diamond that could be used for CPP (or GlueX). The sequence of tasks needed to produce a (50 um) physics diamond are roughly: slice diamond into three wafers (200 um after material removed) / re-test for quality / thin wafers down to 80 um / re-test for quality / polish wafer down to 50 um / test final sample. Testing requires scheduling and use of an X-ray light source, which often takes months to schedule. In principle, testing is not required at each stage, but that is the best way to control the process. | ||
Line 110: | Line 110: | ||
#* [Aside note: Richard has a proposal for using Hall D as a test location for diamonds using "parametric x-rays", but that is a longer term project.] | #* [Aside note: Richard has a proposal for using Hall D as a test location for diamonds using "parametric x-rays", but that is a longer term project.] | ||
# Software/Calibration for CPP (David, Alex and Sean) | # Software/Calibration for CPP (David, Alex and Sean) | ||
+ | #* David is planning (hoping) to work on the software this week. Nikhil is out for the next couple of weeks. | ||
+ | #* Andrew has a working version of the halld_recon CPP branch. | ||
+ | #* Albert had some issues getting a version working, but these are now resolved. | ||
# PID + AI | # PID + AI | ||
#* Data for AI (Andrew) | #* Data for AI (Andrew) | ||
Line 118: | Line 121: | ||
# Electronic Configuration (Beni) | # Electronic Configuration (Beni) | ||
# hdgeant4 updates (Mark) | # hdgeant4 updates (Mark) | ||
+ | #* There was considerable discussion about the sequence necessary for generating a useful hdgeant4 executable for use with CPP. Mark, Simon and Andrew were going to meet following this meeting to decide on a plan. | ||
# Software consolidation (Simon) | # Software consolidation (Simon) | ||
# GlueX Data Analysis | # GlueX Data Analysis |
Revision as of 17:05, 12 January 2022
Meeting Time And Location
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
- Generate MC samples of pi+pi- (Elton and Andrew)
- Make a pull request for hdds (Simon)
Preliminary Agenda
- Previous CPP meeting: Jan 5, 2022
- Announcements
- Bluejeans being phased out between now and end of January. New system will be ZOOM.
- Action Items
- CPP-NPP trigger
- Log Entry 3966089 Swing Shift Summary 12/19/2021
- Log Entry 3966194 CPP Tests
- Log Entry 3966193 Run 90646
- Microscope move (in progress)
- Software/Calibration for CPP (David, Alex and Sean)
- PID + AI
- Data for AI (Andrew)
- CPP and NPP Readiness Review
- MWPC Testing
- CPP and NPP Experiment Configuration
- Electronic Configuration (Beni)
- hdgeant4 updates (Mark)
- Software consolidation (Simon)
- GlueX Data Analysis
- CPP Simulations
- Other business
- Next meeting
Minutes
Present: Albert, Andrew, Beni, David H., David L., Elton, Ilya, Mark, Richard Jones and Daniel Prather (UConn), Rory, Simon.
- Previous CPP meeting: Jan 5, 2022
- The minutes from last week's meeting was reviewed as there were only a few participants.
- Announcements
- Bluejeans being phased out between now and end of January. New system will be ZOOM.
- Action Items
- Elton will generate some pi+pi- events with the current software
- Simon submitted a pull request for hdds; it is still waiting.
- CPP-NPP trigger
- Log Entry 3966089 Swing Shift Summary 12/19/2021
- Log Entry 3966194 CPP Tests
- Log Entry 3966193 Run 90646
- The file with waveform data is available. Ilya will check for rates and compare to previous runs.
- Sasha needs to download the TOF trigger firmware to the hardware.
- Sasha and/or Serguei will need to run the data through the emulation in 'replay' mode to check the trigger. Ilya will check with them on their schedule/plans for this analysis.
- There was some discussion of this at the bi-weekly Hall D staff meeting on Monday.
- Microscope move. [Note this discussion occurred at the time that Richard and Daniel joined the meeting]
- Tagger microscope has been reconfigured. James McIntyre supervised the operation and passed on the information to Daniel. Jim has returned to UConn.
- Richard and Daniel are fixing some electronic preamp boards, which will be installed into the new setup.
- Hall D staff will move it into its final location later today.
- There have been some improvements to the light coverings of the microscope, which should make it easier to access electronics.
- Diamond for CPP (Richard)
- Richard (and his team) tested diamonds at the light source at Saskatoon in December. These are thick diamonds and were tested before thinning.
- The Type III (electronic grade) diamond generated a disappointedly wide rocking curve and is not expected to produce sharp coherent peaks seen in some of our diamonds.
- The other two (?) diamonds tested (1.2 mm) generated very high quality rocking curves. However, there are several steps required before a thin 50 um diamond that could be used for CPP (or GlueX). The sequence of tasks needed to produce a (50 um) physics diamond are roughly: slice diamond into three wafers (200 um after material removed) / re-test for quality / thin wafers down to 80 um / re-test for quality / polish wafer down to 50 um / test final sample. Testing requires scheduling and use of an X-ray light source, which often takes months to schedule. In principle, testing is not required at each stage, but that is the best way to control the process.
- The use of these new diamonds does not appear to be feasible before June.
- The alternative is to use and existing JD103 diamond (already mounted in the goniometer). It has a broad rocking curve, which will lead to a degraded coherent edge. It has not yet been checked in Hall D. Nevertheless, it could still provide a high polarization. It appears this is our best (only) option for running CPP this summer. We should check with Hovanes and Alexandre for their opinion on using this diamond.
- One can simulate the shape of the coherent edge using the pixelated light source data and convoluting it with the electron beam profile. We should find a "volunteer" to work with Richard to build an online tool to do this kind of simulation,
- [Aside note: Richard has a proposal for using Hall D as a test location for diamonds using "parametric x-rays", but that is a longer term project.]
- Software/Calibration for CPP (David, Alex and Sean)
- David is planning (hoping) to work on the software this week. Nikhil is out for the next couple of weeks.
- Andrew has a working version of the halld_recon CPP branch.
- Albert had some issues getting a version working, but these are now resolved.
- PID + AI
- Data for AI (Andrew)
- CPP and NPP Readiness Review
- MWPC Testing
- CPP and NPP Experiment Configuration
- Electronic Configuration (Beni)
- hdgeant4 updates (Mark)
- There was considerable discussion about the sequence necessary for generating a useful hdgeant4 executable for use with CPP. Mark, Simon and Andrew were going to meet following this meeting to decide on a plan.
- Software consolidation (Simon)
- GlueX Data Analysis
- CPP Simulations
- Other business
- Next meeting