Difference between revisions of "20200424-Analyzer-Mtg"

From PREX Wiki
Jump to navigationJump to search
(Created page with "Back to Main Page >> Analyzer_Meeting previous meeting << >> following meeting == Logistic informatio...")
 
Line 20: Line 20:
 
#  Issue [https://github.com/JeffersonLab/japan/issues/245 245]:  Burp / stability cuts adversely affect Beam Mod
 
#  Issue [https://github.com/JeffersonLab/japan/issues/245 245]:  Burp / stability cuts adversely affect Beam Mod
 
#*  Quinn's changes are simply to expland the cut limits for the burp cut.  An expansion of a factor of 2-3 from what was initially set seems to allow all BMOD data to pass.  The impact on data quality is to be investigated.
 
#*  Quinn's changes are simply to expland the cut limits for the burp cut.  An expansion of a factor of 2-3 from what was initially set seems to allow all BMOD data to pass.  The impact on data quality is to be investigated.
 +
#*  Victoria is working on a summary of the impact this has on data quality:  short answer is that it looks pretty good.
  
 
===  Preparations for new respins ===
 
===  Preparations for new respins ===
Line 29: Line 30:
 
#*  '''Paul''':  Merge operations & prex-respin1 back to develop and create a prex-respin2 branch
 
#*  '''Paul''':  Merge operations & prex-respin1 back to develop and create a prex-respin2 branch
 
#*  Devi recommended adding the AT detectors to the global error; we should make a list of all the changes we are planning, and present them at the analysis meeting next week
 
#*  Devi recommended adding the AT detectors to the global error; we should make a list of all the changes we are planning, and present them at the analysis meeting next week
 +
#**  Here's the list:
 +
#**#  Burp cut changes
 +
#**#  Change in the normalizing BCM
 +
#**#  Pedestal updates, similar to what Cameron presented at [[20200424-PREX2-Analysis April 24 PREX analysis meeting]]
 +
#**#  Use of combined BPM 11 & 12 in both regression and dithering
 +
#**#  AT detectors added to global error flag
 +
#**#  Automated merging of the last burst into the previous burst(?)
 
#*  What else do we need?
 
#*  What else do we need?
 
#  CREX respin1:  Start shortly after PREX-2 respin2 completes.  Estimate about 4 weeks
 
#  CREX respin1:  Start shortly after PREX-2 respin2 completes.  Estimate about 4 weeks
Line 35: Line 43:
 
#*  Run list updates
 
#*  Run list updates
 
#*  What else
 
#*  What else
 +
#**  Should we keep the same larger burp cut as in the PREX2 analysis?
  
  
 
===  Other issues ===
 
===  Other issues ===
 +
*  Maybe we can add a way to get a run-summary tree for events matching a certain ErrorFlag?  This would be one way to get the asymmetries for the events during beam modulation
 +
**  Can this be done just in QwParity, or would it need deeper changes in the supporting classes?
 +
**  The other way to get the beam modulation asymmetries would be to do it as a postprocessing step from the normal trees.
 +
  
 
== Present ==
 
== Present ==
  
−
Phone:  
+
Phone: Paul K., Adam, Cameron, Tao, Victoria, Weibin
  
  

Revision as of 15:36, 24 April 2020

Back to Main Page >> Analyzer_Meeting

previous meeting << >> following meeting

Logistic information

Meeting room at JLab: No meeting room at JLab 

 BlueJeans calling instructions:
 Toll-Free Number (U.S.&  Canada):  888-240-2560
 International toll number:         408-740-7256
 Bluejeans CODE:                  385 600 867
 Bluejeans link: https://bluejeans.com/385600867

Agenda

Old issues

  1. Issue 275: Change of EPICS variables for the IHWP state
    • This was pulled into operations, but we need to verify it doesn't break PREX-2 analysis before this gets pulled to develop.
  2. Issue 269: diff* variables are missing in burst and muls trees
    • Merging is in progress and undergoing final comparisons to develop/operations.
  3. Issue 245: Burp / stability cuts adversely affect Beam Mod
    • Quinn's changes are simply to expland the cut limits for the burp cut. An expansion of a factor of 2-3 from what was initially set seems to allow all BMOD data to pass. The impact on data quality is to be investigated.
    • Victoria is working on a summary of the impact this has on data quality: short answer is that it looks pretty good.

Preparations for new respins

  1. PREX-2 respin2: We want to start this very soon
    • Paul: Create a comboBCM to be (2*bcm_an_us + bcm_an_ds)/3 except for runs 3594-3573, for which we would use bcm_dg_ds; use this as the normalizing BCM
    • Cameron: Add certain BPM combinations such as the average of 11 and 12 as combined objects, and use them in regression/dithering. Use run-ranging on this combined object to allow us to have a consistent name for the BPMs we use in regression/dithering even as we change the "best choice".
      • This also needs us to collect the "best choice" into run-rnaged lists.
    • Robert: Pedestal re-evaluation
    • Paul: Merge operations & prex-respin1 back to develop and create a prex-respin2 branch
    • Devi recommended adding the AT detectors to the global error; we should make a list of all the changes we are planning, and present them at the analysis meeting next week
      • Here's the list:
        1. Burp cut changes
        2. Change in the normalizing BCM
        3. Pedestal updates, similar to what Cameron presented at 20200424-PREX2-Analysis April 24 PREX analysis meeting
        4. Use of combined BPM 11 & 12 in both regression and dithering
        5. AT detectors added to global error flag
        6. Automated merging of the last burst into the previous burst(?)
    • What else do we need?
  2. CREX respin1: Start shortly after PREX-2 respin2 completes. Estimate about 4 weeks
    • Dithering correction map updates
    • Pedestal changes
    • Run list updates
    • What else
      • Should we keep the same larger burp cut as in the PREX2 analysis?


Other issues

  • Maybe we can add a way to get a run-summary tree for events matching a certain ErrorFlag? This would be one way to get the asymmetries for the events during beam modulation
    • Can this be done just in QwParity, or would it need deeper changes in the supporting classes?
    • The other way to get the beam modulation asymmetries would be to do it as a postprocessing step from the normal trees.


Present

Phone: Paul K., Adam, Cameron, Tao, Victoria, Weibin


Excused

Retrieved from "https://prex.jlab.org/wiki/index.php?title=20200424-Analyzer-Mtg&oldid=10786"