Difference between revisions of "Meetings-2-25-2021"

From GlueXWiki
Jump to: navigation, search
(Minutes)
 
(9 intermediate revisions by 4 users not shown)
Line 9: Line 9:
 
#* CDC
 
#* CDC
 
#* FDC
 
#* FDC
[https://halldweb.jlab.org/wiki/images/5/51/Kshort_alignment.pdf status of alignment using Ks->pi+pi-]
+
## [https://halldweb.jlab.org/wiki/images/5/51/Kshort_alignment.pdf status of alignment using Ks->pi+pi-]
 
# GEM-TRD
 
# GEM-TRD
 
#* [http://www.jlab.org/Hall-D/detector/trd/GEM_TRD_tracking_Feb25.pdf gas analysis and GEM-TRD in GlueX]
 
#* [http://www.jlab.org/Hall-D/detector/trd/GEM_TRD_tracking_Feb25.pdf gas analysis and GEM-TRD in GlueX]
Line 16: Line 16:
 
= Minutes =
 
= Minutes =
 
# Tracking
 
# Tracking
 +
#* Alex A. observed steps and wiggles in the pull in p_x for π- tracks from ρ events after a kinematic fit of the reaction γp→pπ+π-
 +
#** Some wiggles also seen in other momentum components
 +
#** Different behavior seen for π+ tracks
 +
#* Several people have been meeting over the past week trying to understand this behavior
 +
#** Simon applied rotations to the CDC and FDC separately and was able to mimic some but not all of the observed behavior
 +
#** Trying to find appropriate rotations/offsets to apply to MC geometry for Alex to use in his SDME analysis 
 
# Detector related reports
 
# Detector related reports
 
#* CDC
 
#* CDC
 
#* FDC
 
#* FDC
 +
#** Keigo reported status of alignment using Ks->π+π- events. Two issues:
 +
#*** Pion tracks from Ks decay are not cleanly selected. Sean suggested to check the distance b/w primary & secondary vertices to purify the Ks->π+π- tracks.
 +
#*** Plugin crashes when constraining Ks mass in kinematic fitting.
 +
#* FA125
 +
#**Naomi used the corrected readout code to look for eventnumber-itrigger mismatches and found many instances, from modules which are otherwise ok (in sync); presumably the firmware is not working perfectly for itrigger. Cody said he would look at it.
 +
#**[https://logbooks.jlab.org/entry/3865982 See the logbook entry] The misbehaving fadc in roc 25 slot 6 output some presumably older data when the other fadcs output data for event 1. The event 1 data for the misbehaving fadc appeared in the following block, in the other evio file. This can be verified by comparing the timestamps. The last evio file from the previous run was not available.
 +
#**Sergey said he would contact Cody about running some tests.   
 
# GEM-TRD
 
# GEM-TRD
 +
#* Comparison of the gas analysis with CDC and FDC shows different rates of reduction of Ar (once it was stopped). Also the Nitrogen contamination in the FDC is about a factor of 2 higher than in the CDC. Once the Ar level in the FDC is low enough will be able to measure Oxygen there.
 +
#* There were discussions with people from UVA for building a large-scale GEM-TRD prototype. As the prototype should reflect the full detector design, different configuration were discussed for such a GEM-TRD detector in GlueX. We try to minimize the material in the GlueX forward acceptance, the number of electronic channels, at the same time have enough coverage and good reliability. Many ideas were discussed.
 
# Other
 
# Other

Latest revision as of 09:31, 26 February 2021

  1. Instructions for Bluejeans meeting connection
  2. Meeting ID: 290664653
  3. To join via a Web Browser, go to the page [1] https://bluejeans.com/290664653.

Thu 2/25/2021 2pm

Agenda

  1. Tracking
  2. Detector related reports
    • CDC
    • FDC
    1. status of alignment using Ks->pi+pi-
  3. GEM-TRD
  4. Other

Minutes

  1. Tracking
    • Alex A. observed steps and wiggles in the pull in p_x for π- tracks from ρ events after a kinematic fit of the reaction γp→pπ+π-
      • Some wiggles also seen in other momentum components
      • Different behavior seen for π+ tracks
    • Several people have been meeting over the past week trying to understand this behavior
      • Simon applied rotations to the CDC and FDC separately and was able to mimic some but not all of the observed behavior
      • Trying to find appropriate rotations/offsets to apply to MC geometry for Alex to use in his SDME analysis
  2. Detector related reports
    • CDC
    • FDC
      • Keigo reported status of alignment using Ks->π+π- events. Two issues:
        • Pion tracks from Ks decay are not cleanly selected. Sean suggested to check the distance b/w primary & secondary vertices to purify the Ks->π+π- tracks.
        • Plugin crashes when constraining Ks mass in kinematic fitting.
    • FA125
      • Naomi used the corrected readout code to look for eventnumber-itrigger mismatches and found many instances, from modules which are otherwise ok (in sync); presumably the firmware is not working perfectly for itrigger. Cody said he would look at it.
      • See the logbook entry The misbehaving fadc in roc 25 slot 6 output some presumably older data when the other fadcs output data for event 1. The event 1 data for the misbehaving fadc appeared in the following block, in the other evio file. This can be verified by comparing the timestamps. The last evio file from the previous run was not available.
      • Sergey said he would contact Cody about running some tests.
  3. GEM-TRD
    • Comparison of the gas analysis with CDC and FDC shows different rates of reduction of Ar (once it was stopped). Also the Nitrogen contamination in the FDC is about a factor of 2 higher than in the CDC. Once the Ar level in the FDC is low enough will be able to measure Oxygen there.
    • There were discussions with people from UVA for building a large-scale GEM-TRD prototype. As the prototype should reflect the full detector design, different configuration were discussed for such a GEM-TRD detector in GlueX. We try to minimize the material in the GlueX forward acceptance, the number of electronic channels, at the same time have enough coverage and good reliability. Many ideas were discussed.
  4. Other