20200529-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

Open PRs for PREX respin2

• PR#295: Feature changes goodevents slug0to2
  • Ready for merge
• PR#294: Feature prex respin2 burp cut
  • Weibin will modify this branch to include the increase in the BPM wire burp cut to 2000
  • This branch has increased BPM position burp cuts on 4aX, 4aY, 4eX, and 4eY. We'll keep all 4 of these.
• PR#291: Feature respin2 dit corrector
  • Ready for merge
• PR#290: Updating global event cuts for PREX respin 2 to include AT detectors
  • Ready for merge
• PR#289: Prex mapfile changes
  • Robert will fix the gain factors for the DSL and DSR main detectors to be the 76microvolts/adc-unit.
• PR#287: Cuts for PREX respin cleanup
  • Ready for merge

New work for PREX respin2

• Making change in BCM event cut to use "bcm_target" for all runs; this is the defined normalization BCM of either the two analog BCMs or the dg_ds.
  • Paul is testing this now, and will send a slack message if he needs more help to go through all the files,
• BPM burp cut changes: increase position burp cut to 0.6 for all runs, increasse wire burp cuts by factor of two
  • See comment above of PR294
• Anything else?
  • We should check that the burst limit is set at 9000 patterns for all of PREX
    • Paul will take a look
  • Addition of some un-decoded EPICS variables to the slow tree.
    • Paul has this in a working directory and just needs to make a commit and PR

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.

Present

Phone: