20200605-Analyzer-Mtg

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

Work for PREX respin2

• All open PRs have been merged, including the new change to use "bcm_target" as the main BCM cut for all runs
• Other checks in the code
  • The burst limit is set at 9000 patterns for all of PREX
  • Addition of some un-decoded EPICS variables to the slow tree: several injector variables have been added, but it looks like only RTPAPOSUCNT and RTPAPOSVCNT are included in the EPICS events in the data stream
• Last minute changes
  • Two runs (3571 and 3433) have blinder issues and should have the target flag forced. Discussed in [1].
  • Other changes?
• I will merge develop into master, and then create a "prex-respin2" branch later today. That is what we should use for respin2. The "crex-respin1" branch will be bumped to that point as well, and then folks working on additions for CREX should branch from crex-respin1.

• Farm job submission
  • Robert's submission script if giving job failure errors; the jobs get submitted but fail immediately in the job interpretation step
• "Prompt" updates on the farm
  • Do we have all are farm updates ready to go?
• Directory structure: Do we have our output directories set up?
  • Make /group/prex/analysis/www/prex2/summary_respin2 & set up the web links for it
    • We should have enough space on the web directory for the respin2 files without removing either prompt or pass1.
  • We should have a set of "respin2" directories set up on volatile: I'd suggest /volatile/halla/parity/prex-respin2/*. What subdirs do we need from there?
  • MSS: have we saved all our outputs from respin1 to tape? What should we save: pass1 files, postpan, etc? We may want to tar up some files before putting to tape.
• Plans for starting the respin
  • Once we have all the issues resolved, Robert should submit a slug (which one?), and various experts should check their outputs.
  • After experts give the go ahead, Robert & Sakib will submit all the runs.

Preparations for CREX respins

1. 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.